Comparison
AACSearch vs Typesense Cloud
AACSearch brings search, connectors, relevance controls and analytics into one console and API.
| Feature | AACSearch | Typesense Cloud |
|---|---|---|
Search service | Managed AACSearch platform | Typesense 30.x / 31 RC |
Typo tolerance, synonyms, facets, vector & hybrid search | Yes | Yes |
Natural-language query → filters Both use the engine's natural-language search with an LLM. | Yes | Yes |
Merchandising rules UI for business users Typesense has curation sets with scheduling via the API. | Yes | Partly |
Recommendations API Typesense documents a do-it-yourself approach with your own embedding model. | Yes | Partly |
Per-user personalization | Yes | Partly |
AI answers with citations Typesense conversational search returns hits next to the answer, without inline citations. | Yes | Partly |
Built-in A/B testing Typesense recommends external tools. | Yes | No |
Relevance evaluation (golden sets, nDCG) | Yes | No |
Search analytics dashboards | Yes | Partly |
Connectors (1C-Bitrix, Shopify, WordPress) Typesense lists community WordPress plugins. | Yes | No |
Multi-tenant platform: organisations, scoped keys, quotas, billing | Yes | No |
Pricing model | plan + usage | per cluster RAM / vCPU |
Competitor information is taken from their public pricing pages and documentation as of 2026-10-25. Plans change — check their site before deciding.
Choose Typesense Cloud if
You want the raw engine and will build the rest
Full API access, cluster sizing under your control, no platform layer in between.
Choose AACSearch if
You want a product, not an engine
Rules UI, analytics, evaluation, recommendations and AI answers ready to use.
You resell search to many clients
Organisations, scoped keys, quotas and usage metering are built in.