Algolia vs Typesense

Agent ops

1. ai-native userMy coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboard

   weight 3 · round to Algolia
   Algolia✓fullprobed8/10

   Algolia documents all three surfaces needed for an agent to do end-to-end index/document/query workflows without a dashboard: REST API for search/indexing/records (algolia-docs-4, algolia-docs-31), a full-featured CLI with auth and app selection (algolia-docs-2, algolia-docs-30, algolia-docs-19), and an official MCP server plus agent skills package covering CLI, MCP, crawler, and migrations (algolia-docs-17, algolia-docs-50, algolia-docs-60, algolia-probe-4). Docs explicitly call out AI-agent workflows ('Are you building with AI agents? ... Build with AI', algolia-docs-57). Missing for 10: independent/hands-on evidence of an agent actually completing create-index-to-query flow via CLI/MCP without touching a dashboard, and explicit confirmation the MCP server exposes write/index-creation operations rather than just search/analytics/recommendations.

   • [claimed-docs] “The Algolia CLI lets you work with Algolia's APIs from your terminal. It's great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [claimed-docs] “`algolia-mcp` Search, analytics, and recommendations via the Algolia MCP server”
   • [claimed-docs] “Authenticate the CLI with your Algolia account. This opens your browser so you can sign in or create a new account:”
   • [claimed-docs] “algolia application list # list your applications algolia application select # pick the current one interactively”
   • [claimed-docs] “Add these headers to authenticate requests: * `x-algolia-application-id`. Your Algolia application ID. * `x-algolia-api-key`.”
   • [claimed-docs] “`algolia-cli` Manage indices, settings, rules, and synonyms via the Algolia CLI”
   • [claimed-docs] “Are you building with AI agents? To prepare your agent to work with Algolia, see Build with AI.”
   • [claimed-docs] “MCP Server”
   • [probe] “official MCP server documented at https://github.com/algolia/skills”

   proof ↗⚑ flag

   Typesense~partialprobed7/10

   Typesense's REST API is thoroughly documented for the full workflow — creating a collection, adding documents, searching, filtering, faceting (typesense-docs-8/29/37) — and the dedicated MCP server for Typesense Cloud explicitly lets an AI agent 'create and configure clusters, build collections, index your data, tune search and read metrics, all from the conversation' (typesense-docs-43), satisfying the no-dashboard requirement via API/MCP. However, no CLI tool for creating indexes/adding docs/querying is evidenced — the CLI probe (typesense-probe-4) only points to installation instructions, not an actual query/index CLI. Missing for 10: a documented standalone CLI for index/document/query operations, and independent hands-on confirmation of the MCP server workflow.

   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”
   • [claimed-docs] “Creating a "books" collection ... Adding books to the collection ... Searching for books ... Filtering results ... Faceting”
   • [claimed-docs] “Creating a "books" collection”
   • [claimed-docs] “Filtering results”
   • [probe] “official CLI documented at https://typesense.org/docs/guide/install-typesense.html”

   proof ↗⚑ flag

2. ai-native userAgents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operations

   weight 2 · round to Algolia
   Algolia✓fullprobed8/10

   Algolia documents an official MCP server ('algolia-mcp' exposing search, analytics, and recommendations) plus a broader skills toolkit (CLI, crawler, migration) and lists 'MCP Server' directly in its docs index, alongside Agent Studio for grounding LLM responses in live index data. This directly satisfies the story of agents using indexes as a tool via an MCP/tool-calling surface covering query, analytics, and index operations. Missing for 10: independent hands-on validation of the MCP server's reliability/coverage and more detailed docs on the exact tool schema exposed.

   • [claimed-docs] “`algolia-mcp` Search, analytics, and recommendations via the Algolia MCP server”
   • [claimed-docs] “Agent skills for managing Algolia search, analytics, recommendations, and index configuration.”
   • [claimed-docs] “`algolia-cli` Manage indices, settings, rules, and synonyms via the Algolia CLI”
   • [claimed-docs] “MCP Server”
   • [claimed-docs] “Agent Studio connects your chosen LLM to Algolia search and tools. It manages the end-to-end workflow and grounds responses in live data fro…”
   • [probe] “official MCP server documented at https://github.com/algolia/skills”

   proof ↗⚑ flag

   Typesense✓fullclaimed7/10

   Typesense explicitly documents an MCP server for Typesense Cloud that lets an AI agent create/configure clusters, build collections, index data, tune search, and read metrics — directly matching the query/analytics/index-operations tool-surface story. Missing for 10: independent or hands-on verification of the MCP server's behavior, a full operation/tool list, and confirmation it works outside Typesense Cloud (self-hosted).

   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”
   • [claimed-docs] “Natural Language Search ... Typesense for AI Agents”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Algolia
   Algolia✓fullprobed9/10

   Algolia has a live, probe-verified llms.txt (algolia-probe-1) and a docs.md index (algolia-probe-2) explicitly designed for agent consumption, plus a dedicated 'Build with AI' doc callout for agents (algolia-docs-57) and an agent-skills repo (algolia-docs-25, algolia-docs-17) referencing Algolia-specific docs/tools. This directly satisfies pointing an agent at llms.txt/agent-oriented docs with both first-party and probe corroboration. Missing for 10: no independent/community report of an agent successfully using llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.algolia.com/llms.txt Algolia > Algolia is a search-and-discovery platform providing hosted APIs for…”
   • [probe] “PROBE docs-md: HTTP 200 at https://www.algolia.com/doc.md > ## Documentation Index > Fetch the complete documentation index at: https://www.…”
   • [claimed-docs] “Are you building with AI agents? To prepare your agent to work with Algolia, see Build with AI.”
   • [claimed-docs] “Agent skills for managing Algolia search, analytics, recommendations, and index configuration.”
   • [claimed-docs] “`algolia-mcp` Search, analytics, and recommendations via the Algolia MCP server”
   • [claimed-docs] “The algolia.com website content is indexed in Algolia and can be queried directly.”

   proof ↗⚑ flag

   Typesense✓fullprobed8/10

   A probe confirms a live, well-formed llms.txt at typesense.org/llms.txt describing Typesense for developers and AI agents, and docs explicitly include an 'AI Agents' guide and MCP server integration (typesense-probe-1, typesense-docs-17, typesense-docs-43). missing for 10: no independent/community corroboration of agents actually using llms.txt successfully, and a docs-markdown endpoint (docs/.md) returned 404 suggesting incomplete agent-oriented doc surface.

   • [probe] “PROBE llms.txt: HTTP 200 at https://typesense.org/llms.txt # Typesense > Typesense is an open source search engine for developers and AI ag…”
   • [claimed-docs] “Natural Language Search ... Typesense for AI Agents”
   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”
   • [probe] “PROBE docs-md: HTTP 404 at https://typesense.org/docs/.md”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Algolia
   Algolia✓fullprobed8/10

   Algolia ships a first-party REST API and official API clients across many languages, plus a dedicated CLI explicitly documented as 'great for interactive commands, scripts, and continuous integration workflows,' enabling fully headless/automated/CI use. Authentication via headers (x-algolia-application-id/x-algolia-api-key) supports non-interactive automation, and data ingestion pipelines (Crawler, integrations) can be scheduled/configured without deploying code, reinforcing automatable operation. Missing for 10: no independent hands-on CI pipeline example or explicit non-interactive CLI auth flow (docs show browser-based login) that would confirm frictionless headless CLI use in automated environments.

   • [claimed-docs] “The Algolia CLI lets you work with Algolia's APIs from your terminal. It's great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “The Algolia CLI lets you work with Algolia’s APIs from your terminal. It’s great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [claimed-docs] “Add these headers to authenticate requests: * `x-algolia-application-id`. Your Algolia application ID. * `x-algolia-api-key`.”
   • [claimed-docs] “To guarantee high availability, implement a retry strategy for all API requests using the URLs of your servers as fallbacks”
   • [claimed-docs] “Official clients for JavaScript, Python, PHP, Ruby, Go, Java, Swift, Kotlin, .NET”
   • [claimed-docs] “The official API clients are covered by Algolia’s Service Level Agreement”
   • [claimed-docs] “Algolia keeps the schedule, the retries, and the transformations. Configure them in the Algolia dashboard without deploying code.”
   • [probe] “official CLI documented at https://www.algolia.com/doc/tools/cli/get-started”

   proof ↗⚑ flag

   Typesense~partialprobed6/10

   Typesense supports Docker/binary installs, Docker Compose/Kubernetes/Terraform deployment, and docs explicitly mention Testcontainers and GitHub Actions for running tests, indicating it can be run headlessly and driven via CI automation. However, there's no dedicated CI/CD pipeline guide, no first-party GitHub Actions workflow templates, and no explicit 'headless mode' or automation-focused CLI documentation beyond install/test mentions. missing for 10: dedicated CI/CD automation guide, official GitHub Actions templates/workflows, explicit headless-mode documentation, and independent hands-on CI usage reports.

   • [claimed-docs] “Running Tests with Testcontainers ... Running Tests in Github Actions”
   • [claimed-docs] “Docker, Docker Compose, Kubernetes, Mac via Homebrew, Mac Binary, DEB package on Ubuntu/Debian, RPM package on CentOS/RHEL, Linux Binary”
   • [claimed-docs] “Terraform Module”
   • [probe] “official CLI documented at https://typesense.org/docs/guide/install-typesense.html”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Algolia
   Algolia✓fullprobed8/10

   Algolia documents an official MCP server ('algolia-mcp' for search/analytics/recommendations) alongside other agent skills in its GitHub skills repo, and its docs list 'MCP Server' explicitly as a product offering. This directly satisfies the story of connecting an agent via an official MCP server. Missing for 10: independent/hands-on third-party corroboration of the MCP server working in practice, and more detailed setup/config documentation beyond the brief skill listing.

   • [claimed-docs] “`algolia-mcp` Search, analytics, and recommendations via the Algolia MCP server”
   • [claimed-docs] “Agent skills for managing Algolia search, analytics, recommendations, and index configuration.”
   • [claimed-docs] “MCP Server”
   • [probe] “official MCP server documented at https://github.com/algolia/skills”

   proof ↗⚑ flag

   Typesense~partialclaimed6/10

   Typesense documents an official MCP server for Typesense Cloud that lets an AI agent create/configure clusters, build collections, index data, and tune search directly from a conversation, which is a genuine first-party MCP server offering. However this is scoped to the Cloud product (not the open-source self-hosted server), and there is no independent/hands-on corroboration of it working, nor detail on the full tool surface. missing for 10: independent corroboration/hands-on testing of the MCP server, confirmation it applies to self-hosted Typesense, full list of supported MCP tools/operations.

   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Algolia
   Algolia✓fullprobed8/10

   Algolia ships an official CLI documented for authenticating, managing applications, and scripting/CI workflows (algolia-docs-2, algolia-docs-19, algolia-docs-30, algolia-probe-5), and it also has an agent-oriented 'algolia-cli' skill package explicitly for agent-driven management of indices, settings, rules, and synonyms (algolia-docs-50), directly supporting AI-native agentic use. missing for 10: independent/hands-on confirmation of the CLI working well in agentic pipelines, and more detail on the full command surface beyond auth/app-selection.

   • [claimed-docs] “The Algolia CLI lets you work with Algolia's APIs from your terminal. It's great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “Authenticate the CLI with your Algolia account. This opens your browser so you can sign in or create a new account:”
   • [claimed-docs] “algolia application list # list your applications algolia application select # pick the current one interactively”
   • [claimed-docs] “`algolia-cli` Manage indices, settings, rules, and synonyms via the Algolia CLI”
   • [probe] “official CLI documented at https://www.algolia.com/doc/tools/cli/get-started”

   proof ↗⚑ flag

   Typesense—none0/10

   The evidence covers installation methods (Docker, packages, binaries) and an MCP server for AI agents, but there is no evidence of a distinct official CLI tool for AI-native command-line workflows; the one probe labeled 'official CLI documented' just points to the generic install-methods page, not an actual CLI feature description.

   • [claimed-docs] “Docker, Docker Compose, Kubernetes, Mac via Homebrew, Mac Binary, DEB package on Ubuntu/Debian, RPM package on CentOS/RHEL, Linux Binary”
   • [claimed-docs] “Docker Docker Compose Kubernetes Mac via Homebrew Mac Binary DEB package on Ubuntu/Debian RPM package on CentOS/RHEL Linux Binary Windows (W…”
   • [claimed-docs] “Docker Compose Kubernetes Mac via Homebrew Mac Binary DEB package on Ubuntu/Debian RPM package on CentOS/RHEL Linux Binary Windows (WSL) Ter…”
   • [probe] “official CLI documented at https://typesense.org/docs/guide/install-typesense.html”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Algolia
   Algolia✓fullprobed9/10

   Algolia documents a full public REST Search API with authentication headers, retry strategy guidance, and official client libraries in 9+ languages covered by an SLA, plus a CLI for scripting/CI workflows — all clearly AI-native-consumable interfaces. Additional evidence of llms.txt, agent skills, and MCP server support further reinforces machine/agent-driven access. Missing for 10: a discoverable OpenAPI/Swagger spec (probe found 404s on standard paths) and independent hands-on confirmation of API usage by an AI agent.

   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [claimed-docs] “Add these headers to authenticate requests: * `x-algolia-application-id`. Your Algolia application ID. * `x-algolia-api-key`.”
   • [claimed-docs] “To guarantee high availability, implement a retry strategy for all API requests using the URLs of your servers as fallbacks”
   • [claimed-docs] “Official clients for JavaScript, Python, PHP, Ruby, Go, Java, Swift, Kotlin, .NET”
   • [claimed-docs] “The official API clients are covered by Algolia’s Service Level Agreement”
   • [claimed-docs] “The Algolia CLI lets you work with Algolia's APIs from your terminal. It's great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “The Algolia CLI lets you work with Algolia’s APIs from your terminal. It’s great for interactive commands, scripts, and continuous integrati…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.algolia.com/openapi.json, https://www.algolia.com/swagger.json, https://www.algolia.com/…”
   • [probe] “official CLI documented at https://www.algolia.com/doc/tools/cli/get-started”

   proof ↗⚑ flag

   Typesense✓fullprobed8/10

   Typesense ships documented REST API reference pages (e.g. api/curation.html), an llms.txt explicitly framing itself as 'for developers and AI agents,' and a dedicated MCP server letting AI agents create clusters, index data, and tune search entirely via API/conversation — strong evidence of a documented, AI-drivable public API surface. Missing for 10: a discoverable machine-readable OpenAPI/Swagger spec (probe found 404s at all standard OpenAPI paths) and independent hands-on confirmation of API completeness beyond vendor docs.

   • [claimed-docs] “Copy Markdown”
   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”
   • [probe] “PROBE llms.txt: HTTP 200 at https://typesense.org/llms.txt # Typesense > Typesense is an open source search engine for developers and AI ag…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://typesense.org/openapi.json, https://typesense.org/swagger.json, https://typesense.org/api/op…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Algolia—none0/10

   The evidence describes application ID/API key headers for authentication (algolia-docs-31) and general API/CLI/MCP tooling, but nothing documents issuing scoped, least-privilege, or restricted API keys specifically for agent use. No mention of secured/restricted key generation, ACL scoping, or permission-limited credentials tailored for AI agents appears in the pack.

   • [claimed-docs] “Add these headers to authenticate requests: * `x-algolia-application-id`. Your Algolia application ID. * `x-algolia-api-key`.”
   • [claimed-docs] “`algolia-mcp` Search, analytics, and recommendations via the Algolia MCP server”
   • [claimed-docs] “MCP Server”

   proof ↗⚑ flag

   Typesense—none0/10

   The evidence pack only shows a general 'Security' section heading in the production docs and an MCP integration that grants an AI agent broad access to create/configure clusters and read metrics — not evidence of scoped or least-privilege API key issuance for agents. No documentation of restricted/scoped API keys, permission scopes, or credential minimization for agent use is present.

   • [claimed-docs] “Production Best Practices ... Configuration ... Monitoring ... Search Relevance ... Security ... Schema Management”
   • [claimed-docs] “Production Best Practices ... Monitoring ... Search Relevance ... Security ... Schema Management”
   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Algolia
   Algolia✓fullcommunity9/10

   Algolia documents official SDKs/API clients for JavaScript, Python, PHP, Ruby, Go, Java, Swift, Kotlin, .NET, covered by an SLA, plus REST API docs and community corroboration (React InstantSearch praised as great DX, easy plugin integration). Additional agent-oriented tooling (CLI, MCP server, skills) further supports AI-native developer workflows. Missing for 10: independent benchmarking or hands-on verification of SDK completeness/quality across all listed languages beyond docs and anecdotal HN praise.

   • [claimed-docs] “Official clients for JavaScript, Python, PHP, Ruby, Go, Java, Swift, Kotlin, .NET”
   • [claimed-docs] “The official API clients are covered by Algolia’s Service Level Agreement”
   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [community] “'Using them for a side project. Very impressed with their developer experience. Their React instant-search plugin is great, and very easy to…”
   • [community] “Comparing to Typesense, a user noted 'One of Algolia's strongest features is InstantSearch for vanilla JS, React, Vue, Angular, iOS and Andr…”
   • [claimed-docs] “Are you building with AI agents? To prepare your agent to work with Algolia, see Build with AI.”

   proof ↗⚑ flag

   Typesense—none0/10

   The evidence pack documents Typesense's installation options, CLI, API endpoints, MCP server for AI agents, and llms.txt, but contains no citation of official client SDKs (e.g., language libraries) that an AI-native developer could build against. Absence of evidence for an applicable capability yields 'none'.

   ⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Algolia—none0/10

   Algolia's evidence pack covers search, indexing, analytics, CLI, MCP server, and agent tooling, but no mention of webhooks or event subscription mechanisms for AI-native or any consumer. This is an applicable axis for a data/search platform, but no evidence supports it.

   ⚑ flag

   Typesense—none0/10

   No evidence anywhere in the pack of a webhook or event subscription mechanism for Typesense; the product surface described is search/indexing APIs, collections, ranking, and an MCP server for AI agents, none of which constitute an event/webhook subscription system.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Algolia
   Algolia✓fullclaimed7/10

   Algolia's Agent Studio explicitly connects an LLM to Algolia data to generate grounded conversational responses, summaries, and shopping-assistant suggestions, while Recommend and Personalization provide ML-based recommendations and affinity-driven insights from indexed data. These are first-party documented AI-generated insight/suggestion features directly matching the story. Missing for 10: independent/hands-on validation of Agent Studio's output quality or accuracy, and no community evidence specifically discussing AI-generated insights (community citations focus on search relevance/pricing, not AI insights).

   • [claimed-docs] “Agent Studio connects your chosen LLM to Algolia search and tools. It manages the end-to-end workflow and grounds responses in live data fro…”
   • [claimed-docs] “Agent Studio lets you create: **Shopping assistants** that answer product questions and recommend items.”
   • [claimed-docs] “Agent Studio lets you create: * **Shopping assistants** that answer product questions and recommend items. * **Content summarizers**...…”
   • [claimed-docs] “Recommend - ML-based product recommendations (frequently bought together, related items, trending)”
   • [claimed-docs] “Personalization - User-level affinity profiles for personalized ranking”
   • [claimed-docs] “AI Search (NeuralSearch) - Hybrid keyword + vector semantic search”
   • [claimed-docs] “Completions are cached by default to minimize your LLM provider token costs.”

   proof ↗⚑ flag

   Typesense~partialclaimed4/10

   Typesense documents Natural Language Search and 'built-in retrieval-augmented generation (RAG)' plus LLM integrations that let queries be interpreted and answered conversationally, which can surface AI-derived insights from indexed data, but this is a developer-facing API capability requiring integration, not a built-in insights/suggestions UI for end users inside the product. missing for 10: evidence of an out-of-the-box insights/suggestions UI or dashboard, first-party product screenshots of RAG-generated insights in use, independent user reports validating the RAG/NLS features work as advertised.

   • [claimed-docs] “Typesense is more battle-tested in high-scale production environments, and includes automatic Raft leader election in its open-source server…”
   • [claimed-docs] “It also offers native integrations with LLMs of your choice to enable Natural Language Search and built-in retrieval-augmented generation (R…”
   • [claimed-docs] “Natural Language Search ... Typesense for AI Agents”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Algolia
   Algolia~partialclaimed4/10

   Algolia documents scheduled, code-free data ingestion (schedule, retries, transformations configured in the dashboard) and an Agent Studio that manages 'end-to-end workflow' connecting an LLM to live index data, which are background-automation-adjacent capabilities. However these are mainly data-sync and query-time AI-agent features rather than a general user-facing framework for defining autonomous background automations/triggers. Missing for 10: a documented automation/workflow builder with triggers, independent evidence of autonomous background jobs actually running unattended, and confirmation these features extend beyond data ingestion/AI search assistants.

   • [claimed-docs] “Algolia keeps the schedule, the retries, and the transformations. Configure them in the Algolia dashboard without deploying code.”
   • [claimed-docs] “Agent Studio connects your chosen LLM to Algolia search and tools. It manages the end-to-end workflow and grounds responses in live data fro…”
   • [claimed-docs] “Agent Studio lets you create: * **Shopping assistants** that answer product questions and recommend items. * **Content summarizers**...…”
   • [claimed-docs] “If your content is only web pages, and you don't have an API or database export, use the Crawler. The Crawler extracts content from your pag…”

   proof ↗⚑ flag

   Typesense—none0/10

   Typesense's AI-agent evidence (MCP server) is only conversational/interactive—an agent issues commands during a live session ('all from the conversation')—with no mention of scheduling, triggers, or autonomous background execution. No evidence of cron-like jobs, event-driven automations, or persistent agent workers running without human interaction.

   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”
   • [claimed-docs] “Natural Language Search ... Typesense for AI Agents”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Algolia
   Algolia~partialclaimed5/10

   Algolia's Agent Studio lets customers wire an LLM to Algolia search/tools to build assistants (shopping assistants, conversational search, content summarizers) that are 'built-in' to the product's AI stack, which partially matches the story. However, this is aimed at end-users of the customer's own app rather than an AI-native user delegating administrative/config tasks to an assistant embedded in the Algolia dashboard itself — missing for 10: evidence of a first-party assistant inside the Algolia console/CLI that lets a user delegate index/config management tasks conversationally, and any hands-on/independent proof of Agent Studio's assistant behavior in practice.

   • [claimed-docs] “Agent Studio connects your chosen LLM to Algolia search and tools. It manages the end-to-end workflow and grounds responses in live data fro…”
   • [claimed-docs] “Agent Studio lets you create: **Shopping assistants** that answer product questions and recommend items.”
   • [claimed-docs] “Agent Studio lets you create: * **Shopping assistants** that answer product questions and recommend items. * **Content summarizers**...…”
   • [claimed-docs] “Completions are cached by default to minimize your LLM provider token costs.”

   proof ↗⚑ flag

   Typesense—none0/10

   Evidence shows Typesense exposes an MCP server so external AI agents can control Typesense Cloud (create clusters, index data, tune search) and supports Natural Language Search/RAG for querying data, but there is no evidence of a built-in AI assistant embedded within the Typesense product itself that a user delegates tasks to — the direction is Typesense being controlled by external agents, not an assistant inside the product.

   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”
   • [claimed-docs] “Natural Language Search ... Typesense for AI Agents”
   • [claimed-docs] “It also offers native integrations with LLMs of your choice to enable Natural Language Search and built-in retrieval-augmented generation (R…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Typesense
   Algolia~partialprobed7/10

   Algolia ships an official MCP server and a suite of 'agent skills' (algolia-cli, algolia-mcp, algolia-crawler, algolia-migration) that let an AI agent manage indices, settings, rules, synonyms and search/analytics via natural-language-driven tool calls, plus Agent Studio explicitly supports 'conversational search for natural language queries' grounding LLM responses in Algolia data. This is solid first-party documentation of agentic/natural-language operation of the product, but there is no independent/hands-on evidence confirming these flows work reliably in practice. Missing for 10: independent or community validation of the MCP/skills workflow actually succeeding, and more detail on breadth of natural-language coverage across all admin operations.

   • [claimed-docs] “Agent Studio connects your chosen LLM to Algolia search and tools. It manages the end-to-end workflow and grounds responses in live data fro…”
   • [claimed-docs] “`algolia-mcp` Search, analytics, and recommendations via the Algolia MCP server”
   • [claimed-docs] “Agent Studio lets you create: * **Shopping assistants** that answer product questions and recommend items. * **Content summarizers**...…”
   • [claimed-docs] “`algolia-cli` Manage indices, settings, rules, and synonyms via the Algolia CLI”
   • [claimed-docs] “MCP Server”
   • [claimed-docs] “Are you building with AI agents? To prepare your agent to work with Algolia, see Build with AI.”
   • [probe] “official MCP server documented at https://github.com/algolia/skills”

   proof ↗⚑ flag

   Typesense✓fullclaimed7/10

   Typesense documents built-in Natural Language Search and native LLM integrations for RAG, plus a dedicated MCP server that lets an AI agent create/configure clusters, build collections, index data, and tune search 'all from the conversation' — directly enabling natural-language operation of both search and admin tasks. Missing for 10: independent/hands-on validation of natural-language search accuracy and community confirmation that the MCP-driven conversational admin flow works reliably in practice.

   • [claimed-docs] “Natural Language Search ... Typesense for AI Agents”
   • [claimed-docs] “It also offers native integrations with LLMs of your choice to enable Natural Language Search and built-in retrieval-augmented generation (R…”
   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Algolia—none0/10

   Evidence shows Algolia has REST API reference docs (algolia-docs-4, algolia-docs-31, algolia-docs-53) and quickstart guides, but nothing describes an interactive 'try it' console or runnable code examples embedded in the API reference. The probe for an OpenAPI/Swagger spec (which typically powers interactive API explorers) returned 404 on all candidate paths, further indicating no such interactive reference is exposed.

   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [claimed-docs] “Add these headers to authenticate requests: * `x-algolia-application-id`. Your Algolia application ID. * `x-algolia-api-key`.”
   • [claimed-docs] “The official API clients are covered by Algolia’s Service Level Agreement”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.algolia.com/openapi.json, https://www.algolia.com/swagger.json, https://www.algolia.com/…”

   proof ↗⚑ flag

   Typesense—none0/10

   While Typesense has API documentation pages (e.g. curation.html referenced in docs-45), there is no evidence of an interactive, runnable API reference (like a Swagger/OpenAPI playground). The probe explicitly found no OpenAPI spec at any standard path (404s), and no evidence describes embedded runnable code samples or a live API console.

   • [claimed-docs] “Copy Markdown”
   • [probe] “PROBE openapi: all candidate paths 404 (https://typesense.org/openapi.json, https://typesense.org/swagger.json, https://typesense.org/api/op…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Algolia—none0/10

   Algolia publishes rich human-readable API docs and an llms.txt/doc.md index for LLM consumption, but a direct probe for a machine-readable OpenAPI/swagger spec at standard paths (openapi.json, swagger.json, etc.) returned 404 on all candidates, and no evidence pack item points to a downloadable OpenAPI file elsewhere. llms.txt/doc.md are documentation indexes, not a formal API spec (no endpoint/schema definitions), so they don't satisfy the story.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.algolia.com/openapi.json, https://www.algolia.com/swagger.json, https://www.algolia.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.algolia.com/llms.txt Algolia > Algolia is a search-and-discovery platform providing hosted APIs for…”
   • [probe] “PROBE docs-md: HTTP 200 at https://www.algolia.com/doc.md > ## Documentation Index > Fetch the complete documentation index at: https://www.…”
   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”

   proof ↗⚑ flag

   Typesense—none0/10

   The evidence pack shows an explicit probe for OpenAPI/swagger specs at typical locations returning 404 across all candidate paths, and no first-party documentation elsewhere claims a downloadable machine-readable API spec (only human-readable API reference docs and an llms.txt for markdown docs are mentioned).

   • [probe] “PROBE openapi: all candidate paths 404 (https://typesense.org/openapi.json, https://typesense.org/swagger.json, https://typesense.org/api/op…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://typesense.org/llms.txt # Typesense > Typesense is an open source search engine for developers and AI ag…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Algolia—none0/10

   No evidence describes a dedicated sandbox/test environment distinct from production for Algolia; the closest is multi-application CLI support (create/select different 'applications') but this is not documented as a sandbox mode and involves separate indices/billing rather than an explicit non-production testing environment.

   ⚑ flag

   Typesense—none0/10

   The evidence shows self-hosting options, testing guidance (Testcontainers, GitHub Actions), and an MCP server that lets agents manage real Typesense Cloud clusters, but nothing documents a dedicated sandbox/staging environment isolated from production data for testing purposes.

   • [claimed-docs] “Running Tests with Testcontainers ... Running Tests in Github Actions”
   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Algolia
   Algolia~partialclaimed3/10

   Evidence shows Algolia has major-versioned API clients and a migration tool/skill for upgrading between major versions (implying some versioning discipline), plus an SLA covering official clients, but there is no documented deprecation policy, EOL timeline, or versioning changelog cited anywhere in the pack. missing for 10: explicit deprecation policy/EOL schedule, API versioning changelog, sunset notice process, independent confirmation of policy adherence.

   • [claimed-docs] “`algolia-migration` Migrate API client code to the latest major version (JS, Python, Go, PHP, Java, C#, Ruby, Kotlin, Scala, Swift)”
   • [claimed-docs] “Migrate API client code to the latest major version (JS, Python, Go, PHP, Java, C#, Ruby, Kotlin, Scala, Swift)”
   • [claimed-docs] “The official API clients are covered by Algolia’s Service Level Agreement”
   • [claimed-docs] “To guarantee high availability, implement a retry strategy for all API requests using the URLs of your servers as fallbacks”

   proof ↗⚑ flag

   Typesense—none0/10

   Evidence shows only a 'latest' docs path and no OpenAPI spec found (404s across candidate paths), with no documented API versioning scheme or deprecation policy anywhere in the pack. Missing for 10: explicit API version numbers, a published deprecation/sunset policy, and migration guides between versions.

   • [claimed-docs] “Copy Markdown”
   • [probe] “PROBE openapi: all candidate paths 404 (https://typesense.org/openapi.json, https://typesense.org/swagger.json, https://typesense.org/api/op…”

   proof ↗⚑ flag

Hybrid

1. developerUse built-in or managed embedders so documents and queries are vectorized without running my own embedding pipeline

   weight 2 · round to Typesense
   Algolia~partialclaimed3/10

   The docs mention AI Search (NeuralSearch) as 'Hybrid keyword + vector semantic search' implying built-in vectorization without a custom pipeline, but this is a single one-line marketing mention with no detail on embedder configuration, model choice, or how vectorization works end-to-end. Missing for 10: dedicated documentation on managed embedders, configuration steps for enabling vector/semantic search, and independent/hands-on confirmation that vectorization works without a custom embedding pipeline.

   • [claimed-docs] “AI Search (NeuralSearch) - Hybrid keyword + vector semantic search”

   proof ↗⚑ flag

   Typesense~partialclaimed7/10

   Typesense docs reference built-in Semantic Search, vector/hybrid search, and Cloud-side 'GPU Acceleration for embedding generation,' plus native LLM integrations for NLS/RAG, indicating documents/queries can be auto-vectorized without a separate embedding pipeline. However, the evidence pack lacks detail on which specific built-in models or third-party embedder integrations (e.g., OpenAI) are supported and has no independent/hands-on confirmation of this workflow. Missing for 10: detailed docs enumerating built-in vs external embedder options, and independent verification of the auto-embedding feature working end-to-end.

   • [claimed-docs] “Semantic Search”
   • [claimed-docs] “GPU Acceleration Use GPUs for embedding generation”
   • [claimed-docs] “Typesense combines typo-tolerant keyword search with direct vector search, hybrid search, semantic search, and geo search.”
   • [claimed-docs] “It also offers native integrations with LLMs of your choice to enable Natural Language Search and built-in retrieval-augmented generation (R…”

   proof ↗⚑ flag

2. developerRun hybrid search — semantic vector similarity fused with keyword matching — in a single query

   weight 3 · round drawn
   Algolia✓fullclaimed8/10

   Algolia's docs explicitly claim 'AI Search (NeuralSearch) - Hybrid keyword + vector semantic search' as a first-party feature, directly matching the story of fusing vector similarity with keyword matching in a single query. Missing for 10: no independent/hands-on corroboration of NeuralSearch hybrid results quality or detailed API-level documentation of how the single-query fusion is configured.

   • [claimed-docs] “AI Search (NeuralSearch) - Hybrid keyword + vector semantic search”

   proof ↗⚑ flag

   Typesense✓fullclaimed8/10

   Typesense explicitly documents hybrid search combining vector similarity and keyword matching ('Typesense combines typo-tolerant keyword search with direct vector search, hybrid search, semantic search, and geo search'), with a dedicated 'Semantic Search' guide section and a public demo app explicitly labeled 'Semantic / Hybrid search on 300K HN comments'. Missing for 10: independent hands-on benchmarking of hybrid fusion quality/relevance beyond vendor docs and demo links.

   • [claimed-docs] “Typesense combines typo-tolerant keyword search with direct vector search, hybrid search, semantic search, and geo search.”
   • [claimed-docs] “Semantic Search”
   • [github] “Semantic / Hybrid search on 300K HN comments: hn-comments-search.typesense.org”

   proof ↗⚑ flag

Rag

1. developerPower RAG and conversational answers on top of my indexes with documented retrieval or answer APIs

   weight 1 · round to Algolia
   Algolia✓fullprobed7/10

   Algolia documents Agent Studio, which explicitly connects an LLM to Algolia search/tools to ground conversational answers and RAG-style responses ('grounds responses in live data,' supports conversational search, shopping assistants, content summarizers), plus a Crawler explicitly described as producing a 'RAG-optimized index.' This is first-party documented functionality directly addressing RAG/conversational answers on top of indexes, though it's a separate product layer rather than a single unified 'answer API' and lacks independent hands-on validation. Missing for 10: independent/community verification of Agent Studio's RAG quality, and a single dedicated 'Answers API' endpoint akin to competitors' generative-answer APIs.

   • [claimed-docs] “Agent Studio connects your chosen LLM to Algolia search and tools. It manages the end-to-end workflow and grounds responses in live data fro…”
   • [claimed-docs] “Agent Studio lets you create: **Shopping assistants** that answer product questions and recommend items.”
   • [claimed-docs] “Agent Studio lets you create: * **Shopping assistants** that answer product questions and recommend items. * **Content summarizers**...…”
   • [claimed-docs] “`algolia-crawler` Crawl web pages or whole sites into a RAG-optimized index with the Algolia Crawler”
   • [claimed-docs] “Completions are cached by default to minimize your LLM provider token costs.”
   • [probe] “official MCP server documented at https://github.com/algolia/skills”

   proof ↗⚑ flag

   Typesense~partialclaimed6/10

   Typesense explicitly documents built-in RAG and Natural Language Search features ('native integrations with LLMs... built-in retrieval-augmented generation (RAG)', a dedicated 'Typesense for AI Agents' guide section) plus semantic/hybrid search support. However, the evidence pack lacks concrete API reference details (endpoints, request/response schemas) for the RAG/answer APIs and has no independent hands-on corroboration of these RAG capabilities working in practice. Missing for 10: detailed API/conversation endpoint documentation, independent developer validation of RAG output quality.

   • [claimed-docs] “Natural Language Search ... Typesense for AI Agents”
   • [claimed-docs] “Typesense is more battle-tested in high-scale production environments, and includes automatic Raft leader election in its open-source server…”
   • [claimed-docs] “It also offers native integrations with LLMs of your choice to enable Natural Language Search and built-in retrieval-augmented generation (R…”
   • [claimed-docs] “Semantic Search”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Typesense
   Algolia~partialclaimed5/10

   Algolia's Search API and CLI let you manage indices and records programmatically/interactively (algolia-docs-4, algolia-docs-2/43), and integrations plus the Crawler can bulk-populate indices from various sources (algolia-docs-11/37, algolia-docs-12/38/49), which supports large-scale automation. However, there is no explicit documentation of dedicated bulk/batch endpoints, size/rate limits, or bulk-update workflows tailored for AI-native automation beyond general API/CLI usage. Missing for 10: explicit bulk/batch API documentation (e.g., saveObjects/partialUpdateObjects semantics), guidance on scaling bulk operations, and independent evidence confirming reliable bulk-operation performance at scale.

   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [claimed-docs] “The Algolia CLI lets you work with Algolia's APIs from your terminal. It's great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “The Algolia CLI lets you work with Algolia’s APIs from your terminal. It’s great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “If your data is in one of these platforms, use an integration: Shopify, Adobe Commerce, BigCommerce, commercetools, Salesforce B2C Commerce,…”
   • [claimed-docs] “If your data is in one of these platforms, use an [integration](/doc/integration): Shopify, Adobe Commerce, BigCommerce, commercetools, Sale…”
   • [claimed-docs] “If your content is only web pages, and you don't have an API or database export, use the Crawler. The Crawler extracts content from your pag…”
   • [claimed-docs] “If your content is only web pages, and you don't have an API or database export, use the [Crawler](/doc/tools/crawler/getting-started/overvi…”

   proof ↗⚑ flag

   Typesense~partialclaimed6/10

   Typesense docs describe pushing data from a primary database or CSV/JSON files into collections, and public demos index millions of records (2.2M recipes, 32M songs) showing bulk ingestion is a core supported workflow. However, the evidence pack lacks explicit documentation of a bulk import/export API (batch create/update/delete endpoints), rate-limit behavior at scale, or AI-agent-specific tooling for issuing bulk operations. missing for 10: explicit bulk import/export API docs, batch update/delete semantics, and evidence of AI-agent-driven bulk operation workflows.

   • [claimed-docs] “you'd push data that you already have - in your primary database (or CSV/JSON file) or you've crawled using a scraper - into Typesense”
   • [claimed-docs] “you'd push data that you already have - in your primary database (or CSV/JSON file) or you've crawled using a scraper - into Typesense and t…”
   • [claimed-docs] “Creating a "books" collection ... Adding books to the collection ... Searching for books ... Filtering results ... Faceting”
   • [claimed-docs] “Found 63 recipes out of 2,231,142 in ...ms”
   • [github] “Search a 32M songs dataset from MusicBrainz: songs-search.typesense.org”
   • [github] “Semantic / Hybrid search on 300K HN comments: hn-comments-search.typesense.org”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Algolia
   Algolia~partialclaimed5/10

   Algolia's Rules engine lets you define conditions (e.g., query patterns, time windows) that trigger actions (promote, hide, redirect, boost) automatically, matching the core of 'define rules that trigger actions on events' but scoped specifically to search relevance/merchandising rather than general-purpose event automation (e.g., data pipeline events, webhooks, external triggers). Missing for 10: evidence of rules triggering non-relevance actions (e.g., notifications, external API calls), broader event types beyond search queries, and independent/hands-on validation of the rules engine's automation depth.

   • [claimed-docs] “Use rules to override relevance in some situations. For example, for seasonal product promotions.”
   • [claimed-docs] “Use **rules** to override relevance in some situations. For example, for seasonal product promotions.”
   • [claimed-docs] “Use [**rules**](/doc/guides/managing-results/rules/rules-overview) to override relevance in some situations. For example, for seasonal produ…”
   • [claimed-docs] “If one of your products isn’t appearing where you want it to in your search results, you can reposition it. Rules let you make precise and (…”

   proof ↗⚑ flag

   Typesense~partialclaimed4/10

   Typesense's curation/ranking system lets you define rules (e.g., pinning, hiding, promoting, boosting/burying results) that automatically trigger when certain query conditions are met, which is a narrow form of rule-based automation tied to search-time events. However, there is no evidence of a general event-driven automation engine (e.g., triggers on data changes, webhooks, scheduled actions) beyond search-query curation. Missing for 10: broader event types (data ingestion, index changes, external triggers), documented action types beyond result ranking/merchandising, and any workflow/automation API outside search curation.

   • [claimed-docs] “Boosting / Burying sets of records ... Promoting or Hiding Results (Merchandising) ... Tuning Typo Tolerance”
   • [claimed-docs] “Promoting or Hiding Results (Merchandising)”
   • [claimed-docs] “Boosting / Burying sets of records”
   • [claimed-docs] “Copy Markdown”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Algolia
   Algolia~partialclaimed5/10

   Algolia documents scheduled recurring data-sync jobs via its connectors ('Algolia keeps the schedule, the retries, and the transformations. Configure them in the Algolia dashboard without deploying code'), which covers automated recurring ingestion pipelines but not general-purpose recurring 'workflows' or agent task scheduling beyond data sync. Missing for 10: evidence of scheduling arbitrary/agentic workflows (not just data ingestion), a general cron/trigger API, and independent confirmation of recurring job reliability.

   • [claimed-docs] “Algolia keeps the schedule, the retries, and the transformations. Configure them in the Algolia dashboard without deploying code.”
   • [claimed-docs] “If your data is in one of these platforms, use an [integration](/doc/integration): Shopify, Adobe Commerce, BigCommerce, commercetools, Sale…”
   • [claimed-docs] “If your data is in one of these platforms, use an integration: Shopify, Adobe Commerce, BigCommerce, commercetools, Salesforce B2C Commerce,…”

   proof ↗⚑ flag

   Typesense—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Onboarding

1. developerCreate an index, add documents, and run my first search within minutes of starting the quickstart

   weight 3 · round to Algolia
   Algolia✓fullcommunity8/10

   Algolia's quickstart docs explicitly walk through indexing sample data, creating a React app with search, filtering, and pagination — the exact create-index/add-documents/first-search flow — and community feedback corroborates strong developer experience ('very impressed with their developer experience,' 'documentation is great,' easy setup vs ElasticSearch). Official CLI, API clients, and InstantSearch libraries further support rapid onboarding. Missing for 10: a hands-on timed account of completing the quickstart 'within minutes' and no first-party benchmark of setup time.

   • [claimed-docs] “Set up a React app, index sample data in Algolia, and build a search interface with React InstantSearch.”
   • [claimed-docs] “This quickstart builds a React app that searches a sample product catalog, filters by product type, and paginates results.”
   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [claimed-docs] “Official clients for JavaScript, Python, PHP, Ruby, Go, Java, Swift, Kotlin, .NET”
   • [community] “'Using them for a side project. Very impressed with their developer experience. Their React instant-search plugin is great, and very easy to…”
   • [community] “'If you've ever tried installing ElasticSearch and then switched to Algolia you'll understand how great of a product it is.'”
   • [community] “'We're using Algolia (the free version) for all Facebook open source project websites (React, GraphQL, Yarn...) and it's been nothing short …”

   proof ↗⚑ flag

   Typesense✓fullclaimed7/10

   Docs explicitly walk through creating a collection, adding documents, searching, filtering, and faceting as a guided quickstart, plus install instructions across many platforms (Docker, Homebrew, binaries) to get started fast. However, there's no independent/hands-on confirmation of how quickly this can actually be completed, and community commentary focuses on other aspects (memory usage, comparisons) rather than onboarding speed. Missing for 10: independent timing/hands-on validation of the 'minutes' claim, community testimonials specifically about first-search experience.

   • [claimed-docs] “Creating a "books" collection ... Adding books to the collection ... Searching for books ... Filtering results ... Faceting”
   • [claimed-docs] “Creating a "books" collection”
   • [claimed-docs] “Filtering results”
   • [claimed-docs] “Docker, Docker Compose, Kubernetes, Mac via Homebrew, Mac Binary, DEB package on Ubuntu/Debian, RPM package on CentOS/RHEL, Linux Binary”
   • [claimed-docs] “Docker Docker Compose Kubernetes Mac via Homebrew Mac Binary DEB package on Ubuntu/Debian RPM package on CentOS/RHEL Linux Binary Windows (W…”

   proof ↗⚑ flag

Sdks

1. developerOfficial SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more

   weight 2 · round to Algolia
   Algolia✓fullcommunity9/10

   Algolia explicitly lists official clients for JavaScript, Python, PHP, Ruby, Go, Java, Swift, Kotlin, and .NET, backed by SLA coverage, and community evidence corroborates strong SDK-based DX (React InstantSearch, other framework bindings). missing for 10: independent verification of update cadence/currency across all listed languages beyond vendor docs.

   • [claimed-docs] “Official clients for JavaScript, Python, PHP, Ruby, Go, Java, Swift, Kotlin, .NET”
   • [claimed-docs] “The official API clients are covered by Algolia’s Service Level Agreement”
   • [claimed-docs] “InstantSearch.js is an open source UI library for vanilla JS that lets you build a search interface in your frontend app.”
   • [community] “'Using them for a side project. Very impressed with their developer experience. Their React instant-search plugin is great, and very easy to…”
   • [community] “Comparing to Typesense, a user noted 'One of Algolia's strongest features is InstantSearch for vanilla JS, React, Vue, Angular, iOS and Andr…”

   proof ↗⚑ flag

   Typesense—none0/10

   The evidence pack contains no documentation, GitHub, or community references to official SDKs for JavaScript, Python, PHP, Ruby, Go, or other languages, nor any mention of SDK maintenance cadence. One community comment even suggests Typesense's Ruby/Rails integration lags a competitor's, but there is no confirmation of an official SDK ecosystem at all in the provided evidence.

   • [community] “I love Jason Bosco (the typesense guy). I love Ruby on Rails. But I've been using Meilisearch more and more over the past year on client pro…”

   proof ↗⚑ flag

Ui libraries

1. developerOfficial UI component libraries let me assemble a full search interface — box, results, facets, pagination — without building it from scratch

   weight 2 · round to Algolia
   Algolia✓fullcommunity9/10

   Algolia ships InstantSearch libraries (JS, React, Vue, Angular, iOS, Android) with predefined widgets for search box, results, facets/refinementList, and pagination, letting developers assemble a full UI without building from scratch, and this is corroborated by hands-on community praise for the React InstantSearch plugin and DX. Missing for 10: no independent audit of every widget type (e.g., pagination widget explicitly) beyond docs, and some community comments focus more on relevance/pricing than UI assembly specifics.

   • [claimed-docs] “InstantSearch.js is an open source UI library for vanilla JS that lets you build a search interface in your frontend app.”
   • [claimed-docs] “This quickstart builds a React app that searches a sample product catalog, filters by product type, and paginates results.”
   • [claimed-docs] “add the [`refinementList`](/doc/api-reference/widgets/refinement-list/js)` widget and ask it to show a list of brands, so your users can ref…”
   • [claimed-docs] “InstantSearch offers three levels of increasing control over your UI: Start with a predefined widget... customize a predefined widget... cre…”
   • [claimed-docs] “To change its render output (DOM or Native), **customize a predefined widget** to render what you want.”
   • [claimed-docs] “To implement something that doesn't exist, create a **custom widget**.”
   • [community] “'Using them for a side project. Very impressed with their developer experience. Their React instant-search plugin is great, and very easy to…”
   • [community] “Comparing to Typesense, a user noted 'One of Algolia's strongest features is InstantSearch for vanilla JS, React, Vue, Angular, iOS and Andr…”

   proof ↗⚑ flag

   Typesense~partialclaimed5/10

   Typesense's install docs list a 'Search UI Components' section, indicating an official UI library ecosystem exists, but the evidence pack gives no detail on what components are provided (search box, results list, facets, pagination) or how they compose into a full interface. Missing for 10: concrete documentation of specific component names/APIs (e.g., InstantSearch adapter, React/Vue components), code examples assembling a full search UI, and independent/hands-on confirmation that these components work end-to-end.

   • [claimed-docs] “Search UI Components”

   proof ↗⚑ flag

Connectors

1. founderIngest content with an official crawler or connectors instead of writing my own indexing pipeline

   weight 1 · round to Algolia
   Algolia✓fullclaimed8/10

   Algolia offers an official web Crawler for sites without an API/database export, plus pre-built connectors/integrations for Shopify, Adobe Commerce, BigCommerce, commercetools, Salesforce B2C Commerce, and Zendesk, and dashboard-configurable scheduling/retries/transformations without custom code — directly matching the founder's need to avoid building a custom indexing pipeline. Missing for 10: independent hands-on evidence specifically about crawler/connector reliability at scale (community evidence is about search relevance/pricing, not ingestion pipelines).

   • [claimed-docs] “If your content is only web pages, and you don't have an API or database export, use the Crawler. The Crawler extracts content from your pag…”
   • [claimed-docs] “If your content is only web pages, and you don't have an API or database export, use the [Crawler](/doc/tools/crawler/getting-started/overvi…”
   • [claimed-docs] “If your content is only web pages, and you don’t have an API or database export, use the Crawler. The Crawler extracts content from your pag…”
   • [claimed-docs] “If your data is in one of these platforms, use an integration: Shopify, Adobe Commerce, BigCommerce, commercetools, Salesforce B2C Commerce,…”
   • [claimed-docs] “If your data is in one of these platforms, use an [integration](/doc/integration): Shopify, Adobe Commerce, BigCommerce, commercetools, Sale…”
   • [claimed-docs] “Algolia keeps the schedule, the retries, and the transformations. Configure them in the Algolia dashboard without deploying code.”
   • [claimed-docs] “`algolia-crawler` Crawl web pages or whole sites into a RAG-optimized index with the Algolia Crawler”

   proof ↗⚑ flag

   Typesense—none0/10

   Docs explicitly describe pushing data you already have or 'crawled using a scraper' into Typesense, meaning founders must build or bring their own scraper/pipeline rather than use an official Typesense-branded crawler or connector like Algolia's Crawler or Elastic connectors; no such official tool is mentioned anywhere in the evidence.

   • [claimed-docs] “you'd push data that you already have - in your primary database (or CSV/JSON file) or you've crawled using a scraper - into Typesense”
   • [claimed-docs] “you'd push data that you already have - in your primary database (or CSV/JSON file) or you've crawled using a scraper - into Typesense and t…”

   proof ↗⚑ flag

Ingestion

1. platform-engineerBulk-import millions of documents quickly, with async task tracking to know when indexing completes

   weight 2 · round to Typesense
   Algolia—none0/10

   Evidence covers general data-ingestion methods (integrations, Crawler, scheduled dashboard-configured transformations) but never mentions bulk-import at millions-of-records scale nor any async task/job ID tracking mechanism for confirming indexing completion — the core of this story.

   • [claimed-docs] “Algolia keeps the schedule, the retries, and the transformations. Configure them in the Algolia dashboard without deploying code.”
   • [claimed-docs] “If your data is in one of these platforms, use an integration: Shopify, Adobe Commerce, BigCommerce, commercetools, Salesforce B2C Commerce,…”
   • [claimed-docs] “If your content is only web pages, and you don't have an API or database export, use the Crawler. The Crawler extracts content from your pag…”
   • [claimed-docs] “Algolia doesn’t query your database. It searches a copy of your data, stored as in an . After you’ve structured your data into records, choo…”

   proof ↗⚑ flag

   Typesense~partialclaimed4/10

   Evidence confirms Typesense supports pushing/importing bulk data at large scale (millions of records, e.g. 2.2M recipes, 32M songs dataset) and provides indexing/search functionality, but there is no evidence of an async task-tracking mechanism (e.g. job IDs, polling for import completion status) that platform engineers could use to monitor long-running bulk imports. Missing for 10: documentation of async import job status/tracking API, evidence of import progress polling, and any independent benchmark of import throughput at scale.

   • [claimed-docs] “you'd push data that you already have - in your primary database (or CSV/JSON file) or you've crawled using a scraper - into Typesense”
   • [claimed-docs] “Found 63 recipes out of 2,231,142 in ...ms”
   • [github] “Search a 32M songs dataset from MusicBrainz: songs-search.typesense.org”
   • [claimed-docs] “you'd push data that you already have - in your primary database (or CSV/JSON file) or you've crawled using a scraper - into Typesense and t…”
   • [claimed-docs] “Creating a "books" collection ... Adding books to the collection ... Searching for books ... Filtering results ... Faceting”

   proof ↗⚑ flag

2. developerDocument adds, updates, and deletes become searchable in near real time without a full reindex

   weight 2 · round drawn
   Algolia~partialclaimed4/10

   The Search API lets you 'manage your indices and records' (docs-4) and Algolia stores records as a searchable copy of your data that you send via API (docs-54), implying individual record adds/updates/deletes rather than requiring a full reindex, and docs-48 mentions scheduled/retry-managed transformations. However, the evidence pack never explicitly states near-real-time indexing latency, partial/incremental update semantics, or provides hands-on confirmation of update speed after single-record changes. Missing for 10: explicit documentation of near-real-time indexing latency, partialUpdateObject/incremental update API details, and independent evidence confirming updates appear searchable quickly without full reindex.

   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [claimed-docs] “Algolia doesn’t query your database. It searches a copy of your data, stored as in an . After you’ve structured your data into records, choo…”
   • [claimed-docs] “Algolia keeps the schedule, the retries, and the transformations. Configure them in the Algolia dashboard without deploying code.”

   proof ↗⚑ flag

   Typesense~partialclaimed4/10

   Docs show a document-add workflow ('Adding books to the collection') and instant sub-50ms search claims, implying documents become searchable quickly after being pushed, but the evidence pack never explicitly documents update/delete operations, incremental indexing mechanics, or benchmarks showing changes are searchable in near real time without full reindex. Missing for 10: explicit docs/benchmarks on document update and delete APIs, confirmation of incremental (non-full-reindex) indexing, and independent verification of update/delete latency.

   • [claimed-docs] “Creating a "books" collection ... Adding books to the collection ... Searching for books ... Filtering results ... Faceting”
   • [claimed-docs] “Creating a "books" collection”
   • [claimed-docs] “Typesense is an open-source, typo-tolerant search engine optimized for instant (typically sub-50ms) search-as-you-type experiences and devel…”
   • [claimed-docs] “you'd push data that you already have - in your primary database (or CSV/JSON file) or you've crawled using a scraper - into Typesense”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Algolia~partialprobed6/10

   Algolia's Search REST API and CLI expose index management, rules, ranking, typo tolerance and synonyms (algolia-docs-4, algolia-docs-31, algolia-docs-33), and the CLI explicitly wraps the API for scripting/CI (algolia-docs-2, algolia-docs-43). However several capabilities are documented as dashboard/UI-centric with no evidence of an equivalent API path — e.g. visual Merchandising Studio (algolia-docs-27, algolia-docs-59), analytics CSV/XLSX export and comparison mode (algolia-docs-10, algolia-docs-36, algolia-docs-47), and Data Sources 'Configure them in the Algolia dashboard without deploying code' (algolia-docs-48). No OpenAPI spec was found (algolia-probe-3), making full API-vs-UI parity hard to verify from docs alone. Missing for 10: explicit API endpoints for analytics export/comparison, Merchandising Studio visual curation, and Agent Studio setup, plus independent confirmation that dashboard-only features have API equivalents.

   • [claimed-docs] “The Algolia Search API lets you search, configure, and manage your indices and records”
   • [claimed-docs] “The Algolia CLI lets you work with Algolia's APIs from your terminal. It's great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “The Algolia CLI lets you work with Algolia’s APIs from your terminal. It’s great for interactive commands, scripts, and continuous integrati…”
   • [claimed-docs] “Add these headers to authenticate requests: * `x-algolia-application-id`. Your Algolia application ID. * `x-algolia-api-key`.”
   • [claimed-docs] “Use [**rules**](/doc/guides/managing-results/rules/rules-overview) to override relevance in some situations. For example, for seasonal produ…”
   • [claimed-docs] “Merchandising Studio - Visual tools for curating, pinning, and boosting search results”
   • [claimed-docs] “Visual tools for curating, pinning, and boosting search results”
   • [claimed-docs] “You can export and download your analytics data as CSV or XLSX files.”
   • [claimed-docs] “To compare the performance of your metrics between different periods, click **Comparison mode** and select the date ranges you want to compa…”
   • [claimed-docs] “To export any of the metrics from the Algolia dashboard, click Download. You can export and download your analytics data as CSV or XLSX file…”
   • [claimed-docs] “Algolia keeps the schedule, the retries, and the transformations. Configure them in the Algolia dashboard without deploying code.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.algolia.com/openapi.json, https://www.algolia.com/swagger.json, https://www.algolia.com/…”

   proof ↗⚑ flag

   Typesense~partialprobed6/10

   Typesense is fundamentally API-first: collections, indexing, search, filtering, faceting, ranking, curation, and even cluster management (via Typesense Cloud API/MCP) are documented as API operations, and the product ships without a mandatory admin UI, implying the API is the primary/complete interface. However, the evidence pack lacks a direct statement enumerating UI-only features and confirming 1:1 parity, and there's no OpenAPI spec discoverable (probe shows 404s), which weakens verifiable completeness. Missing for 10: an explicit UI feature inventory compared against API capabilities, a published OpenAPI/spec artifact, and independent confirmation that no admin/dashboard-only actions exist outside the API.

   • [claimed-docs] “Creating a "books" collection ... Adding books to the collection ... Searching for books ... Filtering results ... Faceting”
   • [claimed-docs] “Filtering results”
   • [claimed-docs] “Promoting or Hiding Results (Merchandising)”
   • [claimed-docs] “Boosting / Burying sets of records”
   • [claimed-docs] “Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://typesense.org/openapi.json, https://typesense.org/swagger.json, https://typesense.org/api/op…”
   • [claimed-docs] “Typesense **Cloud** is the hosted SaaS version of our **Open Source** product.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Typesense
   Algolia~partialclaimed3/10

   Algolia documents exporting analytics data (CSV/XLSX) via the dashboard, but there is no evidence of a documented bulk export path for the actual indexed records/search data in an open format, which is what 'all of my data' would require for a full exit. Missing for 10: documented bulk/records export tooling (e.g., API-based full index dump), explicit open-format (JSON/CSV) export of search records, and any migration/export guide for leaving the platform.

   • [claimed-docs] “Search analytics offer insights into what your users search and which results they select through metrics such as popular searches, no resul…”
   • [claimed-docs] “You can export and download your analytics data as CSV or XLSX files.”
   • [claimed-docs] “To export any of the metrics from the Algolia dashboard, click Download. You can export and download your analytics data as CSV or XLSX file…”
   • [claimed-docs] “Algolia doesn’t query your database. It searches a copy of your data, stored as in an . After you’ve structured your data into records, choo…”

   proof ↗⚑ flag

   Typesense~partialclaimed4/10

   Typesense is documented as fully open-source and self-hostable (Docker, binaries, Homebrew, etc.), which supports the ability to run your own instance and avoid lock-in, and migration guides exist for moving *into* Typesense from Postgres/Algolia. However, the evidence pack contains no explicit documentation of a bulk data export feature/API or an open interchange format (e.g., JSONL) for extracting your indexed data back out. missing for 10: explicit documentation of a data export API/CLI command, confirmation of an open export format (JSON/JSONL), and any guide on migrating *away from* Typesense to another system.

   • [claimed-docs] “An open source alternative to Algolia, with some key quirks solved”
   • [claimed-docs] “Typesense is an open source search engine that can be downloaded and run from your computer locally or from any server.”
   • [claimed-docs] “Docker, Docker Compose, Kubernetes, Mac via Homebrew, Mac Binary, DEB package on Ubuntu/Debian, RPM package on CentOS/RHEL, Linux Binary”
   • [claimed-docs] “Migrating from Postgres for Full-Text Search”
   • [claimed-docs] “Migrating from Algolia”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Typesense
   Algolia—none0/10

   Algolia's core search platform is a closed-source hosted SaaS; community evidence explicitly cites 'closed source license' as a reason customers left (algolia-comm-5, algolia-comm-6). While peripheral tools like InstantSearch.js and CLI skills are open source (algolia-docs-8, algolia-docs-50), the core product source is not available under an open license, so an AI-native user cannot read the product's source.

   • [community] “Company switched from Algolia to ElasticSearch: 'Algolia is great to get started but it doesn't make sense at scale. If you have large index…”
   • [community] “'It's easy to use and setup. If pricing and closed source is OK with you then it's worth it.' Compared to pre-docker Heroku.”
   • [claimed-docs] “InstantSearch.js is an open source UI library for vanilla JS that lets you build a search interface in your frontend app.”

   proof ↗⚑ flag

   Typesense✓fullprobed8/10

   Typesense is repeatedly documented and confirmed via GitHub/community as an open-source project (GPL-3.0 style OSS repo with public source), with docs explicitly stating 'open source search engine' and code publicly hosted and inspected by a community member ('written in C++, code is simple enough to skim'). missing for 10: explicit license name/text citation and a first-party statement of the specific OSI license terms.

   • [claimed-docs] “Typesense is an open-source, typo-tolerant search engine optimized for instant (typically sub-50ms) search-as-you-type experiences and devel…”
   • [github] “An Open Source Algolia Alternative & An Easier-to-Use ElasticSearch Alternative”
   • [claimed-docs] “Typesense is an open source search engine that can be downloaded and run from your computer locally or from any server.”
   • [community] “It's written in C++, and the code is simple enough to skim. I would expect this to be some hefty Java thing.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://typesense.org/llms.txt # Typesense > Typesense is an open source search engine for developers and AI ag…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Typesense
   Algolia—none0/10

   Algolia is explicitly a hosted, closed-source SaaS platform (community evidence repeatedly cites 'closed source' as a reason for switching away), with no documentation, download, or Docker/on-prem package for self-hosting the core search engine anywhere in the evidence pack.

   • [community] “Company switched from Algolia to ElasticSearch: 'Algolia is great to get started but it doesn't make sense at scale. If you have large index…”
   • [community] “'It's easy to use and setup. If pricing and closed source is OK with you then it's worth it.' Compared to pre-docker Heroku.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.algolia.com/llms.txt Algolia > Algolia is a search-and-discovery platform providing hosted APIs for…”

   proof ↗⚑ flag

   Typesense✓fullcommunity9/10

   Typesense is explicitly open source and provides extensive self-hosting install paths (Docker, Docker Compose, Kubernetes, Homebrew, DEB/RPM packages, Linux binaries, Terraform module) plus a downloads page stating it 'can be downloaded and run from your computer locally or from any server,' distinct from the separately offered hosted Cloud SaaS. Community comments corroborate real-world self-hosted deployments (memory footprint, running in docker-compose). Missing for 10: independent hands-on production self-hosting case studies at scale and more detail on self-hosted operational parity with Cloud features.

   • [claimed-docs] “Docker, Docker Compose, Kubernetes, Mac via Homebrew, Mac Binary, DEB package on Ubuntu/Debian, RPM package on CentOS/RHEL, Linux Binary”
   • [claimed-docs] “Docker Docker Compose Kubernetes Mac via Homebrew Mac Binary DEB package on Ubuntu/Debian RPM package on CentOS/RHEL Linux Binary Windows (W…”
   • [claimed-docs] “Docker Compose Kubernetes Mac via Homebrew Mac Binary DEB package on Ubuntu/Debian RPM package on CentOS/RHEL Linux Binary Windows (WSL) Ter…”
   • [claimed-docs] “Typesense is an open source search engine that can be downloaded and run from your computer locally or from any server.”
   • [claimed-docs] “Typesense **Cloud** is the hosted SaaS version of our **Open Source** product.”
   • [community] “good to know the memory efficiency !! when 1 million Hacker News titles are indexed along with their points, Typesense consumes 165 MB of me…”
   • [community] “I previously used Opensearch for my Rails project, it was quite heavy piece of service to run in the docker compose environment. I said to m…”

   proof ↗⚑ flag

Analytics

1. founderBuilt-in analytics show top queries, no-result queries, and click-through so I know what users search for and miss

   weight 2 · round to Algolia
   Algolia✓fullcommunity9/10

   Algolia's docs explicitly describe built-in Search Analytics covering popular searches, no-results queries, and click-through rates, plus comparison mode and CSV/XLSX export, and community feedback corroborates that Algolia analytics let users tie queries to business outcomes without heavy engineering. Missing for 10: independent hands-on verification of the analytics dashboard UI itself (only docs + indirect community praise, no screenshots or detailed review of the analytics feature specifically).

   • [claimed-docs] “Search analytics offer insights into what your users search and which results they select through metrics such as popular searches, no resul…”
   • [claimed-docs] “You can export and download your analytics data as CSV or XLSX files.”
   • [claimed-docs] “To compare the performance of your metrics between different periods, click **Comparison mode** and select the date ranges you want to compa…”
   • [claimed-docs] “To export any of the metrics from the Algolia dashboard, click Download. You can export and download your analytics data as CSV or XLSX file…”
   • [community] “Algolia has great analytics, so you can measure business value from search queries: tie a query to a purchase and run further analysis, powe…”

   proof ↗⚑ flag

   Typesense—none0/10

   The evidence pack covers installation, ranking/relevance tuning, production best practices, and monitoring, but contains no mention of built-in analytics dashboards for top queries, no-result queries, or click-through tracking. This is a fair capability to expect from a search engine product, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Production Best Practices ... Configuration ... Monitoring ... Search Relevance ... Security ... Schema Management”
   • [claimed-docs] “Production Best Practices ... Monitoring ... Search Relevance ... Security ... Schema Management”
   • [claimed-docs] “Production Best Practices”

   proof ↗⚑ flag

Scale

1. platform-engineerDocumented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents

   weight 2 · round to Typesense
   Algolia!disputedcontradicted4/10

   Algolia documents high availability via a 99.999% uptime SLA and API retry-fallback strategy (algolia-docs-40, algolia-docs-44), but there is no documented clustering/replication architecture guidance for scaling to hundreds of millions of documents — Algolia abstracts this as a managed SaaS rather than exposing an operational scaling playbook. Community hands-on evidence directly contradicts the 'prototype to hundreds of millions' claim: one company reports 'Algolia is great to get started but it doesn't make sense at scale... too expensive' and switched to Elasticsearch (algolia-comm-5), a Typesense maintainer notes frequent switch-aways due to cost 'at even moderate scale' (algolia-comm-7), and another user cites index duplication requirements exploding record counts as a scale-limiting factor (algolia-comm-19). missing for 10: documented clustering/sharding architecture, replication guidance, published benchmarks for hundred-million-document indices, and resolution of community cost/scale complaints.

   • [claimed-docs] “SLA (99.999% uptime SLA)”
   • [claimed-docs] “To guarantee high availability, implement a retry strategy for all API requests using the URLs of your servers as fallbacks”
   • [community] “Company switched from Algolia to ElasticSearch: 'Algolia is great to get started but it doesn't make sense at scale. If you have large index…”
   • [community] “Typesense maintainer: 'Algolia is a great product but can get quite expensive at even moderate scale. If I had a dollar for every time I've …”
   • [community] “'We're currently A/B testing TypeSense and Algolia, but the pricing model difference alone makes me almost want to skip the whole process an…”
   • [community] “'Algolia is an amazing service and an absolute joy to use... However, it's easy to exceed their record limits, especially since you need to …”

   proof ↗⚑ flag

   Typesense~partialcommunity5/10

   Typesense docs mention built-in high availability, automatic Raft leader election, Kubernetes/Docker Swarm deployment, and a 'Production Best Practices' guide, plus a Cloud tier with dedicated clusters and HA add-ons — suggesting a genuine clustering/HA story. However, there's no documented scaling playbook that walks from prototype to hundreds of millions of documents (sharding strategy, replica scaling guidance, capacity benchmarks at that scale), and demo datasets shown top out around 32M records. A community comment even flags that Elasticsearch is seen as better suited when you 'want to store billions of documents,' and another worries about memory-hog scaling — concrete caveats rather than full confidence. Missing for 10: documented multi-hundred-million-doc scaling benchmarks/case studies, explicit sharding guidance, and stronger independent corroboration of HA/clustering at that scale.

   • [claimed-docs] “High Availability Recommended for Production Envs”
   • [claimed-docs] “Typesense includes built-in high availability and the freedom to self-host or use a dedicated Typesense Cloud cluster.”
   • [claimed-docs] “Typesense is more battle-tested in high-scale production environments, and includes automatic Raft leader election in its open-source server…”
   • [claimed-docs] “Typesense is more battle-tested in high-scale production environments, and includes automatic Raft leader election in its open-source server”
   • [claimed-docs] “You get a dedicated cluster, with no limits on records or operations.”
   • [claimed-docs] “Production Best Practices ... Configuration ... Monitoring ... Search Relevance ... Security ... Schema Management”
   • [github] “Search a 32M songs dataset from MusicBrainz: songs-search.typesense.org”
   • [community] “Storing everything in memory seems fast, but seems like it'd be quite the resource hog on a server -- is that a normal approach to take? ...…”
   • [community] “We wanted a simple search engine that was fast, handled typographic errors out-of-the-box and was also simple to run and manage... Elasticse…”

   proof ↗⚑ flag

Self host

1. platform-engineerSelf-host the full engine — same features as the hosted product — on my own infrastructure

   weight 3 · round to Typesense
   Algolia—none0/10

   Algolia is explicitly a hosted SaaS search platform ('hosted APIs for full-text search'); there is no evidence of a self-hostable engine binary or on-prem deployment option, and community comments explicitly discuss it as closed-source ('closed source license') and hosted-only, with users switching away precisely because it's not self-hostable at scale.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.algolia.com/llms.txt Algolia > Algolia is a search-and-discovery platform providing hosted APIs for…”
   • [community] “Company switched from Algolia to ElasticSearch: 'Algolia is great to get started but it doesn't make sense at scale. If you have large index…”
   • [community] “'It's easy to use and setup. If pricing and closed source is OK with you then it's worth it.' Compared to pre-docker Heroku.”

   proof ↗⚑ flag

   Typesense✓fullclaimed8/10

   Typesense is explicitly open-source and self-hostable via Docker, Docker Compose, Kubernetes, Homebrew, binaries, DEB/RPM packages, and Terraform modules, with the same core feature set (search, filtering, faceting, ranking, semantic/hybrid search) documented for self-hosted use, and Typesense Cloud is described as 'the hosted SaaS version of our Open Source product,' implying feature parity. missing for 10: independent/hands-on confirmation that self-hosted clusters achieve full parity with Cloud-only operational features (e.g., Search Delivery Network, GPU acceleration, HA tooling) rather than just vendor claims.

   • [claimed-docs] “Docker, Docker Compose, Kubernetes, Mac via Homebrew, Mac Binary, DEB package on Ubuntu/Debian, RPM package on CentOS/RHEL, Linux Binary”
   • [claimed-docs] “Terraform Module”
   • [claimed-docs] “Typesense **Cloud** is the hosted SaaS version of our **Open Source** product.”
   • [claimed-docs] “Typesense is an open source search engine that can be downloaded and run from your computer locally or from any server.”
   • [claimed-docs] “Typesense includes built-in high availability and the freedom to self-host or use a dedicated Typesense Cloud cluster.”
   • [claimed-docs] “Production Best Practices ... Configuration ... Monitoring ... Search Relevance ... Security ... Schema Management”
   • [claimed-docs] “High Availability Recommended for Production Envs”
   • [claimed-docs] “GPU Acceleration Use GPUs for embedding generation”

   proof ↗⚑ flag

Pricing

1. founderCosts stay predictable as records and query volume grow — no surprise per-request cliffs

   weight 2 · round to Typesense
   Algolia—none0/10

   No vendor documentation in the evidence pack addresses predictable pricing, record-based cost caps, or protections against per-request cost cliffs. In fact, independent community reports describe the opposite experience — costs 'get expensive at scale,' a 'price per search model' criticized as 'ridiculous,' and users unexpectedly multiplying record usage (30K→150K) via duplicate indexes for sorting, leading companies to switch providers over cost surprises.

   • [community] “Company switched from Algolia to ElasticSearch: 'Algolia is great to get started but it doesn't make sense at scale. If you have large index…”
   • [community] “Typesense maintainer: 'Algolia is a great product but can get quite expensive at even moderate scale. If I had a dollar for every time I've …”
   • [community] “'We're currently A/B testing TypeSense and Algolia, but the pricing model difference alone makes me almost want to skip the whole process an…”
   • [community] “'Algolia is an amazing service and an absolute joy to use... However, it's easy to exceed their record limits, especially since you need to …”

   proof ↗⚑ flag

   Typesense~partialclaimed6/10

   Typesense Cloud pricing is based on dedicated cluster resources with 'no limits on records or operations' rather than per-request metering, and the open-source self-host option lets founders avoid cloud billing entirely, both of which support predictable, non-cliff cost growth. However, there's no independent evidence or founder testimony validating actual cost predictability at scale, and no detail on how cluster upgrade/resizing costs behave as usage grows. Missing for 10: independent case studies of cost scaling, detail on tier-upgrade pricing mechanics, and community confirmation of no surprise billing.

   • [claimed-docs] “Typesense **Cloud** is the hosted SaaS version of our **Open Source** product.”
   • [claimed-docs] “You get a dedicated cluster, with no limits on records or operations.”
   • [claimed-docs] “Typesense is an open source search engine that can be downloaded and run from your computer locally or from any server.”

   proof ↗⚑ flag

2. founderPublished per-unit pricing (searches, records, or nodes) lets me predict what search will cost before committing

   weight 3 · round to Typesense
   Algolia—none0/10

   The evidence pack contains no docs or pages describing Algolia's actual pricing tiers or per-unit costs (searches, records, nodes); only community anecdotes mention a 'price per search' model and general expense complaints (algolia-comm-11, algolia-comm-5, algolia-comm-7), with no concrete published rate card or calculator cited. Without a documented pricing page, a founder cannot predict costs from this evidence.

   • [community] “'We're currently A/B testing TypeSense and Algolia, but the pricing model difference alone makes me almost want to skip the whole process an…”
   • [community] “Company switched from Algolia to ElasticSearch: 'Algolia is great to get started but it doesn't make sense at scale. If you have large index…”
   • [community] “Typesense maintainer: 'Algolia is a great product but can get quite expensive at even moderate scale. If I had a dollar for every time I've …”

   proof ↗⚑ flag

   Typesense~partialclaimed4/10

   Typesense Cloud has a public pricing calculator page referencing dedicated clusters, HA, GPU acceleration, and SDN features, implying some cost transparency, but the evidence never shows actual published per-unit rates (e.g., $/search, $/record, $/node) that a founder could use to predict costs precisely. missing for 10: explicit published unit prices, cost breakdown examples, self-host vs cloud cost comparison, independent confirmation that the calculator yields predictable pricing.

   • [claimed-docs] “Typesense **Cloud** is the hosted SaaS version of our **Open Source** product.”
   • [claimed-docs] “You get a dedicated cluster, with no limits on records or operations.”
   • [claimed-docs] “Search Delivery Network Like a CDN, but for search”
   • [claimed-docs] “High Availability Recommended for Production Envs”
   • [claimed-docs] “GPU Acceleration Use GPUs for embedding generation”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Typesense
   Algolia—none0/10

   No evidence in the pack discusses data residency, regional storage options, or data location controls for Algolia; nothing addresses this axis at all.

   ⚑ flag

   Typesense~partialclaimed6/10

   Typesense is open-source and explicitly self-hostable ('run from your computer locally or from any server', 'freedom to self-host or use a dedicated Typesense Cloud cluster'), which lets an AI-native user fully control where data physically resides by choosing their own hosting location. However, there is no evidence of an explicit region/data-residency selector or documented list of Typesense Cloud regions for users who prefer the managed SaaS option. Missing for 10: documented Typesense Cloud region selection UI/list, explicit data-residency/compliance statements (e.g., GDPR region guarantees).

   • [claimed-docs] “Typesense is an open source search engine that can be downloaded and run from your computer locally or from any server.”
   • [claimed-docs] “Typesense includes built-in high availability and the freedom to self-host or use a dedicated Typesense Cloud cluster.”
   • [claimed-docs] “Typesense **Cloud** is the hosted SaaS version of our **Open Source** product.”

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Algolia—none0/10

   The evidence pack covers search features, indexing, analytics, CLI, and AI agent tooling, but contains no documentation about data retention policies, deletion controls, GDPR/CCPA compliance mechanisms, or record deletion APIs/settings specifically for privacy governance. No mention of data retention periods, right-to-be-forgotten workflows, or deletion audit trails.

   ⚑ flag

   Typesense—none0/10

   No evidence pack citation documents data retention or deletion controls (e.g., TTL policies, document/collection deletion APIs, data export/purge tools) for Typesense; the pack only covers indexing, ranking, install options, and cloud pricing. Since Typesense is a data store for search, deletion/retention controls are a fair axis, but the evidence provides none.

   ⚑ flag

3. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Algolia—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for Algolia's tools/CLI/SDKs; this is an applicable privacy-posture axis for a developer platform but no documentation or community report confirms an opt-out exists.

   ⚑ flag

   Typesense—none0/10

   No evidence pack item mentions telemetry, usage tracking, or an opt-out mechanism; Typesense is self-hostable open source, but no explicit privacy/telemetry documentation is provided here.

   ⚑ flag

Curation

1. developerDefine synonyms and curate results — pin, boost, or hide specific hits for specific queries

   weight 2 · round to Algolia
   Algolia✓fullcommunity9/10

   Algolia's docs explicitly cover Rules for overriding relevance (pin, boost, hide, reposition results) and a dedicated Merchandising Studio with visual tools for curating, pinning, and boosting results, plus CLI support for managing rules and synonyms. Community evidence corroborates real-world use of these tuning tools alongside typo tolerance and analytics for measuring impact. Missing for 10: independent hands-on verification specifically of synonym/pin workflows (most community commentary focuses on general relevance/pricing rather than curation feature usage).

   • [claimed-docs] “Use rules to override relevance in some situations. For example, for seasonal product promotions.”
   • [claimed-docs] “Use **rules** to override relevance in some situations. For example, for seasonal product promotions.”
   • [claimed-docs] “Use [**rules**](/doc/guides/managing-results/rules/rules-overview) to override relevance in some situations. For example, for seasonal produ…”
   • [claimed-docs] “If one of your products isn’t appearing where you want it to in your search results, you can reposition it. Rules let you make precise and (…”
   • [claimed-docs] “Merchandising Studio - Visual tools for curating, pinning, and boosting search results”
   • [claimed-docs] “Visual tools for curating, pinning, and boosting search results”
   • [claimed-docs] “`algolia-cli` Manage indices, settings, rules, and synonyms via the Algolia CLI”
   • [community] “Competitor (Loop54) claim: customers switch from Algolia because 'Algolia requires a bit of hand-holding and it still doesn't quite seem to …”

   proof ↗⚑ flag

   Typesense✓fullclaimed8/10

   Typesense docs explicitly cover a dedicated Ranking & Relevance guide with sections on Boosting/Burying sets of records, Promoting or Hiding Results (Merchandising), and a dedicated Curation API endpoint for pinning/hiding specific hits per query, plus synonyms are a standard documented feature referenced within the relevance-tuning guide set. Missing for 10: independent hands-on developer accounts specifically validating curation/pinning behavior in production, and no direct synonym-API citation in the pack (only implied via ranking-and-relevance guide).

   • [claimed-docs] “Boosting / Burying sets of records ... Promoting or Hiding Results (Merchandising) ... Tuning Typo Tolerance”
   • [claimed-docs] “Promoting or Hiding Results (Merchandising)”
   • [claimed-docs] “Boosting / Burying sets of records”
   • [claimed-docs] “Copy Markdown”

   proof ↗⚑ flag

Ranking

1. developerShape relevance with custom ranking rules and business signals (popularity, recency, margin) beyond textual matching

   weight 2 · round drawn
   Algolia✓fullcommunity8/10

   Docs explicitly describe custom ranking, rules to override relevance (e.g., for promotions), Merchandising Studio for curating/pinning/boosting, Personalization for user-level ranking affinity, and Recommend for popularity/trending signals—directly covering business-signal-based relevance beyond text match. Community feedback corroborates heavy use of custom ranking/rules in production, though some complain relevance still needs tuning for edge queries, which is a general quality caveat rather than a contradiction of the capability itself. missing for 10: independent hands-on benchmark showing recency/margin-based ranking specifically working well, and no explicit mention of 'margin' as a ranking field example.

   • [claimed-docs] “Choose a good set of searchable attributes. Apply custom ranking to adapt Algolia to your needs.”
   • [claimed-docs] “Use rules to override relevance in some situations. For example, for seasonal product promotions.”
   • [claimed-docs] “Choose a good set of **searchable attributes**. Apply **custom ranking** to adapt Algolia to your needs.”
   • [claimed-docs] “Use **rules** to override relevance in some situations. For example, for seasonal product promotions.”
   • [claimed-docs] “Merchandising Studio - Visual tools for curating, pinning, and boosting search results”
   • [claimed-docs] “Personalization - User-level affinity profiles for personalized ranking”
   • [claimed-docs] “Recommend - ML-based product recommendations (frequently bought together, related items, trending)”
   • [claimed-docs] “If one of your products isn’t appearing where you want it to in your search results, you can reposition it. Rules let you make precise and (…”
   • [community] “Algolia has great analytics, so you can measure business value from search queries: tie a query to a purchase and run further analysis, powe…”
   • [community] “Competitor (Loop54) claim: customers switch from Algolia because 'Algolia requires a bit of hand-holding and it still doesn't quite seem to …”

   proof ↗⚑ flag

   Typesense✓fullcommunity8/10

   Typesense docs explicitly cover boosting/burying, promoting/hiding (curation), ranking based on relevance+popularity, ranking based on relevance+recency, and text match score tuning, and a default_sorting_field mechanism lets any numeric business signal (popularity, recency, margin, etc.) be blended with textual relevance — corroborated by a community post confirming the default_sorting_field behavior in practice. Missing for 10: no independent hands-on benchmark specifically testing margin/business-metric ranking, and no third-party review validating complex multi-signal tuning at scale.

   • [claimed-docs] “Boosting / Burying sets of records ... Promoting or Hiding Results (Merchandising) ... Tuning Typo Tolerance”
   • [claimed-docs] “Ranking based on Relevance and Popularity ... Ranking based on Relevance and Recency”
   • [claimed-docs] “Promoting or Hiding Results (Merchandising)”
   • [claimed-docs] “Boosting / Burying sets of records”
   • [claimed-docs] “Ranking based on Relevance and Popularity”
   • [claimed-docs] “Text Match Score & Type”
   • [community] “Typesense use a default_sorting_field on each document, meaning before indexing you need to compute a relevancy score for Typesense to sort …”

   proof ↗⚑ flag

2. platform-engineerInspect ranking scores or explanations to understand exactly why a result ranked where it did

   weight 1 · round to Typesense
   Algolia—none0/10

   Docs describe configuring custom ranking, rules, and relevance settings, but there is no evidence of a feature that surfaces per-result ranking scores or an 'explain' breakdown showing why a specific result ranked where it did. This is a reasonable ask for a search relevance platform, so the axis applies, but no such inspection/debugging capability is documented.

   • [claimed-docs] “Choose a good set of searchable attributes. Apply custom ranking to adapt Algolia to your needs.”
   • [claimed-docs] “Use rules to override relevance in some situations. For example, for seasonal product promotions.”
   • [claimed-docs] “Choose a good set of **searchable attributes**. Apply **custom ranking** to adapt Algolia to your needs.”
   • [claimed-docs] “Use **rules** to override relevance in some situations. For example, for seasonal product promotions.”
   • [claimed-docs] “Apply [**custom ranking**](/doc/guides/managing-results/must-do/custom-ranking) to adapt Algolia to your needs.”
   • [claimed-docs] “Use [**rules**](/doc/guides/managing-results/rules/rules-overview) to override relevance in some situations. For example, for seasonal produ…”
   • [claimed-docs] “If one of your products isn’t appearing where you want it to in your search results, you can reposition it. Rules let you make precise and (…”

   proof ↗⚑ flag

   Typesense~partialclaimed5/10

   Typesense docs reference a 'Text Match Score & Type' feature in the ranking-and-relevance guide, indicating some visibility into how text matching contributed to a result's rank, but there is no evidence of a full explain-style breakdown covering all ranking factors (popularity, recency, custom boosts) or independent confirmation of its usefulness for debugging rank order. missing for 10: full ranking explanation covering all scoring factors (boosts, sort_by fields, popularity), hands-on/independent validation of the explain feature's usefulness for platform engineers.

   • [claimed-docs] “Text Match Score & Type”
   • [claimed-docs] “Boosting / Burying sets of records ... Promoting or Hiding Results (Merchandising) ... Tuning Typo Tolerance”
   • [claimed-docs] “Ranking based on Relevance and Popularity ... Ranking based on Relevance and Recency”

   proof ↗⚑ flag

Experience

1. developerServe query suggestions and autocomplete backed by real search traffic or a suggestions index

   weight 2 · round drawn
   Algolia—none0/10

   The evidence pack covers Algolia's search relevance, InstantSearch UI widgets, analytics on popular searches, and ML-based Recommend, but nowhere documents a dedicated Query Suggestions feature or autocomplete backed by a suggestions index derived from real search traffic — the specific capability the story asks about is unevidenced even though it's a fair question for a search platform.

   ⚑ flag

   Typesense—none0/10

   Evidence shows Typesense supports fast search-as-you-type and typo-tolerant querying, but there is no documentation of a dedicated suggestions/autocomplete feature driven by search-traffic analytics or a separate suggestions index (unlike Algolia's Query Suggestions). Curation/promotion features (typesense-docs-45, docs-27/28) address merchandising, not traffic-based suggestion indexing.

   ⚑ flag

2. developerDeliver as-you-type instant search with millisecond responses so results update on every keystroke

   weight 3 · round drawn
   Algolia✓fullcommunity9/10

   Algolia's InstantSearch libraries (JS, React, Vue, Android/iOS) are explicitly built for as-you-type search UIs with typo tolerance and custom ranking, and multiple independent HN comments corroborate millisecond, keystroke-fast search-as-you-type performance (RAM-first index beating ES/Solr) and praise the React InstantSearch DX. Missing for 10: a first-party documented latency benchmark/SLA number for keystroke response time.

   • [claimed-docs] “Set up a React app, index sample data in Algolia, and build a search interface with React InstantSearch.”
   • [claimed-docs] “InstantSearch.js is an open source UI library for vanilla JS that lets you build a search interface in your frontend app.”
   • [claimed-docs] “InstantSearch offers three levels of increasing control over your UI: Start with a predefined widget... customize a predefined widget... cre…”
   • [claimed-docs] “Algolia provides typo tolerance out-of-the-box, along with some important ways to customize just how tolerant a search experience should be.”
   • [community] “'We moved to Algolia mainly because of this [speed]. Elastic Search and Solr could not compete.' Algolia's RAM-first index approach cited as…”
   • [community] “'Using them for a side project. Very impressed with their developer experience. Their React instant-search plugin is great, and very easy to…”
   • [community] “'I definitely love the hn search which is powered by algolia. Fast and instant. I wish it was possible to turn off fuzzy matching in some ca…”
   • [community] “'Just their typo acceptance alone makes Algolia, imo, the best 3rd party search service available currently.'”

   proof ↗⚑ flag

   Typesense✓fullcommunity9/10

   Typesense's docs explicitly position it as optimized for sub-50ms search-as-you-type experiences with typo tolerance, and this is corroborated by community praise for instant search/fuzzy matching and demos (e.g., 32M song dataset search) and the live search-with-latency example on typesense.org showing millisecond result counts. Independent HN commenters confirm real-world instant-search behavior and performance characteristics (memory/speed tradeoffs), reinforcing the vendor claims. Missing for 10: independently benchmarked keystroke-level latency numbers from a third party beyond anecdotal community praise.

   • [claimed-docs] “optimized for instant (typically sub-50ms) search-as-you-type experiences and developer productivity”
   • [claimed-docs] “Typesense is an open-source, typo-tolerant search engine optimized for instant (typically sub-50ms) search-as-you-type experiences and devel…”
   • [claimed-docs] “Found 63 recipes out of 2,231,142 in ...ms”
   • [github] “Search a 32M songs dataset from MusicBrainz: songs-search.typesense.org”
   • [community] “Congrats on shipping! Love the instant search queries and the fuzzy text matching.”
   • [community] “I'm going to give Typesense a try today... went from Meilisearch (which is great) to Elastic for some more complex aggregation queries but t…”

   proof ↗⚑ flag

3. developerSearches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching applies

   weight 3 · round to Algolia
   Algolia✓fullcommunity9/10

   Algolia's docs explicitly state typo tolerance is built-in and customizable ('important ways to customize just how tolerant a search experience should be'), and community comments independently praise typo acceptance as a standout feature. Missing for 10: deeper documentation of specific tunable parameters (e.g., per-attribute typo settings, min word size for typos) beyond the overview page, and third-party technical validation of edge-case tuning.

   • [claimed-docs] “Algolia provides typo tolerance out-of-the-box, along with some important ways to customize just how tolerant a search experience should be.”
   • [claimed-docs] “Typo tolerance lets users make mistakes while typing but still find the they’re looking for.”
   • [community] “'Just their typo acceptance alone makes Algolia, imo, the best 3rd party search service available currently.'”
   • [community] “'I definitely love the hn search which is powered by algolia. Fast and instant. I wish it was possible to turn off fuzzy matching in some ca…”

   proof ↗⚑ flag

   Typesense✓fullcommunity8/10

   Typesense is documented as 'typo-tolerant search engine' out-of-the-box, and docs include a dedicated 'Tuning Typo Tolerance' section for controlling fuzzy matching behavior, plus community feedback praising built-in fuzzy text matching. missing for 10: no independent benchmark of typo-tolerance accuracy/edge-cases and no detail in evidence on exact configurable parameters (num_typos, per-field settings) beyond the section title.

   • [claimed-docs] “Typesense is an open-source, typo-tolerant search engine optimized for instant (typically sub-50ms) search-as-you-type experiences and devel…”
   • [claimed-docs] “Boosting / Burying sets of records ... Promoting or Hiding Results (Merchandising) ... Tuning Typo Tolerance”
   • [community] “Congrats on shipping! Love the instant search queries and the fuzzy text matching.”
   • [community] “We wanted a simple search engine that was fast, handled typographic errors out-of-the-box and was also simple to run and manage... Elasticse…”

   proof ↗⚑ flag

Filtering

1. developerBuild faceted navigation — filters with live counts across categories, ranges, and attributes — from a single query

   weight 2 · round to Algolia
   Algolia✓fullcommunity9/10

   Algolia's docs explicitly cover faceted navigation: the refinementList widget for filtering by attributes (facets), InstantSearch widgets for building UI with live counts, quickstart building filter-by-product-type UI, and dedicated 'Browse & Navigation - Category pages, filtering, and faceted navigation' feature listing. This is backed by first-party docs on InstantSearch and REST API for a single query returning facet counts, plus community corroboration of InstantSearch UI quality. Missing for 10: no independent hands-on confirmation specifically of live facet counts rendering or range-filter widgets in the evidence.

   • [claimed-docs] “add the [`refinementList`](/doc/api-reference/widgets/refinement-list/js)` widget and ask it to show a list of brands, so your users can ref…”
   • [claimed-docs] “Browse & Navigation - Category pages, filtering, and faceted navigation”
   • [claimed-docs] “This quickstart builds a React app that searches a sample product catalog, filters by product type, and paginates results.”
   • [claimed-docs] “InstantSearch offers three levels of increasing control over your UI: Start with a predefined widget... customize a predefined widget... cre…”
   • [claimed-docs] “InstantSearch.js is an open source UI library for vanilla JS that lets you build a search interface in your frontend app.”
   • [community] “Comparing to Typesense, a user noted 'One of Algolia's strongest features is InstantSearch for vanilla JS, React, Vue, Angular, iOS and Andr…”

   proof ↗⚑ flag

   Typesense✓fullcommunity7/10

   Typesense's official docs walk through building faceted search ("Faceting" step alongside "Filtering results" in the same query workflow), and community commentary independently confirms it "handles faceted search already," supporting single-query filter+facet delivery. Missing for 10: explicit documentation/example of range facets and live facet counts syntax, and independent hands-on verification of facet count accuracy at scale.

   • [claimed-docs] “Creating a "books" collection ... Adding books to the collection ... Searching for books ... Filtering results ... Faceting”
   • [claimed-docs] “Filtering results”
   • [community] “As of now, my project uses ElasticSearch — it works fine, but it wants lots of RAM which I find slightly annoying... I suggest you use Types…”

   proof ↗⚑ flag

Tenancy

1. developerScoped or tenant tokens restrict each end user's searches to their own documents without separate indexes per user

   weight 2 · round drawn
   Algolia—none0/10

   The evidence pack only shows generic API-key authentication headers (x-algolia-application-id/x-algolia-api-key) with no mention of scoped/secured API keys, tenant restrictions, or per-user filtering that Algolia's real secured-API-key feature provides. Missing for 10: any documentation of secured/scoped API keys, tenant token generation, or per-user query restriction mechanisms.

   • [claimed-docs] “Add these headers to authenticate requests: * `x-algolia-application-id`. Your Algolia application ID. * `x-algolia-api-key`.”

   proof ↗⚑ flag

   Typesense—none0/10

   The evidence pack only references a generic 'Security' doc heading without any mention of scoped/tenant API keys, per-user search restrictions, or multitenancy mechanisms. Missing for 10: any mention of scoped search API keys, tenant-based filtering, or documentation on restricting a token's search scope to a subset of documents.

   • [claimed-docs] “Production Best Practices ... Configuration ... Monitoring ... Search Relevance ... Security ... Schema Management”
   • [claimed-docs] “Production Best Practices ... Monitoring ... Search Relevance ... Security ... Schema Management”

   proof ↗⚑ flag