Algolia vs Elasticsearch

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 drawn
   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

   Elasticsearch✓fullprobed8/10

   Elasticsearch exposes a full REST API for index creation, document ingestion, and querying (elastic-docs-4, elastic-docs-19), ships official client libraries (elastic-docs-6), provides an official MCP server (elastic-docs-28, elastic-probe-4) and 'skills' packages that teach coding agents to use the stack (elastic-docs-10) — all without requiring the Kibana dashboard. missing for 10: no dedicated first-party CLI tool distinct from curl/API calls, and no independent hands-on report confirming an agent completing the full create-index→add-docs→query loop via the MCP server.

   • [claimed-docs] “Elasticsearch can combine vector search with full-text search, structured filters, aggregations, and hybrid retrieval in one engine”
   • [claimed-docs] “Elasticsearch functions as a vector database when you store embeddings in `dense_vector` or `sparse_vector` fields and query them for simila…”
   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”
   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”
   • [probe] “official MCP server documented at https://github.com/elastic/mcp-server-elasticsearch”
   • [claimed-docs] “Install official skills that teach AI coding agents how to work with Elasticsearch, Kibana, Fleet, and the rest of the Elastic stack.”
   • [claimed-docs] “All you need to do is create an index mapping to start ingesting, embedding, and querying data. There is no need to define model-related set…”

   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

   Elasticsearch✓fullprobed7/10

   Elastic maintains and documents an official MCP server (elastic/mcp-server-elasticsearch) that exposes Elasticsearch to AI agents as a tool-calling surface, plus 'skills' docs for AI coding agents to work with the stack. Missing for 10: detailed documentation of exactly which operations (query, analytics, index management) the MCP server exposes, and independent/hands-on corroboration of its reliability.

   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”
   • [probe] “official MCP server documented at https://github.com/elastic/mcp-server-elasticsearch”
   • [claimed-docs] “Install official skills that teach AI coding agents how to work with Elasticsearch, Kibana, Fleet, and the rest of the Elastic stack.”

   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

   Elasticsearch~partialprobed3/10

   Elastic explicitly advertises 'official skills that teach AI coding agents how to work with Elasticsearch' (elastic-docs-10) and has an official MCP server (elastic-probe-4/elastic-docs-28), which are agent-oriented resources, but direct probes show no llms.txt or docs.md file exists (elastic-probe-1, elastic-probe-2), so the specific story of pointing an agent at llms.txt is not supported. Missing for 10: a working llms.txt/docs.md endpoint, and any first-party documentation detailing the 'skills' content or how an agent consumes it.

   • [claimed-docs] “Install official skills that teach AI coding agents how to work with Elasticsearch, Kibana, Fleet, and the rest of the Elastic stack.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.elastic.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.elastic.co/docs.md”
   • [probe] “official MCP server documented at https://github.com/elastic/mcp-server-elasticsearch”

   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

   Elasticsearch~partialclaimed6/10

   Elasticsearch ships a headless-friendly install path (curl one-liner, Docker quickstart) and REST API plus official clients in multiple languages, which supports scripted/CI automation, but there is no explicit CI/automation guide or documented CLI for pipeline integration in the evidence pack. missing for 10: dedicated CI/automation documentation, examples of running in pipelines, headless configuration flags/env-var setup guidance.

   • [claimed-docs] “curl -fsSL https://elastic.co/start-local | sh”
   • [claimed-docs] “Quickly set up Elasticsearch and Kibana in Docker for local development or testing, using this one-liner in the command line.”
   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”

   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

   Elasticsearch✓fullprobed7/10

   Elastic maintains an official MCP server repository (elastic/mcp-server-elasticsearch) confirmed both in docs listing and by direct probe, enabling AI agents to connect to Elasticsearch via MCP. Missing for 10: detailed setup/usage documentation for the MCP server and independent hands-on validation of its functionality.

   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”
   • [probe] “official MCP server documented at https://github.com/elastic/mcp-server-elasticsearch”

   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

   Elasticsearch—none0/10

   The evidence pack mentions official client libraries (elastic-docs-6) and an MCP server (elastic-docs-28), but no official CLI tool tailored for AI-native/agentic workflows is documented anywhere in the pack.

   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”
   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”

   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

   Elasticsearch~partialprobed6/10

   Elasticsearch's core interaction model is REST-API-driven, evidenced by client libraries (elastic-docs-6), inference/semantic_text APIs (elastic-docs-9,11,23), and explicit AI-agent enablement via an official MCP server (elastic-docs-28, elastic-probe-4) and 'skills' for coding agents (elastic-docs-10). However, automated probes found no llms.txt, no docs.md, and no discoverable OpenAPI/swagger spec at standard paths (elastic-probe-1,2,3), undercutting machine-readable API discoverability for AI-native tooling. Missing for 10: a verifiable OpenAPI/swagger spec or llms.txt, and independent hands-on evidence of an agent successfully driving the API end-to-end.

   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”
   • [claimed-docs] “The inference API workflow is more complex but offers greater control over the inference endpoint configuration.”
   • [claimed-docs] “Install official skills that teach AI coding agents how to work with Elasticsearch, Kibana, Fleet, and the rest of the Elastic stack.”
   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.elastic.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.elastic.co/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.elastic.co/openapi.json, https://www.elastic.co/swagger.json, https://www.elastic.co/api…”
   • [probe] “official MCP server documented at https://github.com/elastic/mcp-server-elasticsearch”

   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

   Elasticsearch—none0/10

   The evidence pack contains no mention of API key scoping, role-based access control, or least-privilege credential issuance for agents/service accounts in Elasticsearch; nothing addresses creating scoped API keys or restricting permissions for AI agent use. This is a plausible and well-known Elasticsearch capability (API keys with role descriptors exist in the product) but is simply absent from the provided evidence, so it must be judged 'none' rather than assumed.

   ⚑ 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

   Elasticsearch✓fullprobed8/10

   Elastic documents a wide range of official client libraries covering popular programming languages (elastic-docs-6), giving AI-native developers standard SDKs to build against, complementing official MCP server support for agentic integration (elastic-docs-28, elastic-probe-4). missing for 10: independent hands-on validation of SDK quality/coverage beyond first-party docs, and no explicit mention of language-specific AI/agent framework integrations within the SDKs themselves.

   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”
   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”
   • [probe] “official MCP server documented at https://github.com/elastic/mcp-server-elasticsearch”

   proof ↗⚑ 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

   Elasticsearch—none0/10

   Elasticsearch offers watchers/alerting internally but no evidence in the pack shows a webhook subscription mechanism for AI-native agents to receive events; no docs describe outbound webhooks for event subscription.

   ⚑ 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

   Elasticsearch~partialclaimed4/10

   Elasticsearch documents strong building blocks for AI-driven data work — automatic embedding generation via semantic_text, hybrid/vector search, and explicit support for RAG pipelines (elastic-docs-1, elastic-docs-11, elastic-docs-18, elastic-docs-19) — but these are infrastructure for developers to build their own AI insight layer, not a native in-product feature that surfaces AI-generated insights/suggestions to end users. Missing for 10: evidence of an actual built-in insights/summary/suggestion UI (e.g., Kibana AI Assistant narrative insights) generating analysis automatically, and independent confirmation that end users see such generated insights rather than just raw search results.

   • [claimed-docs] “When you index content into a `semantic_text` field, Elasticsearch automatically generates vector embeddings using a configured machine lear…”
   • [claimed-docs] “When you index content into a `semantic_text` field, Elasticsearch automatically generates vector embeddings using a configured machine lear…”
   • [claimed-docs] “RAG (Retrieval Augmented Generation) systems”
   • [claimed-docs] “Elasticsearch functions as a vector database when you store embeddings in `dense_vector` or `sparse_vector` fields and query them for simila…”
   • [claimed-docs] “All you need to do is create an index mapping to start ingesting, embedding, and querying data. There is no need to define model-related set…”

   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

   Elasticsearch—none0/10

   Elasticsearch is a search/data engine, not an automation/orchestration platform; the evidence covers indexing, vector search, hybrid search, serverless scaling, and an MCP server for connecting agents to ES data, but nothing about scheduling or running autonomous background automations/workflows. No watcher/alerting or agentic automation feature is documented in this pack.

   ⚑ 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

   Elasticsearch—none0/10

   The evidence pack shows Elasticsearch's search/vector/RAG capabilities and an external MCP server for connecting AI agents to Elasticsearch, but nothing describes a built-in AI assistant embedded in the product that a user can delegate tasks to. This is a fair capability to expect from a modern data platform (many now ship in-product AI assistants), so absence of evidence means 'none' rather than 'na'.

   • [claimed-docs] “Install official skills that teach AI coding agents how to work with Elasticsearch, Kibana, Fleet, and the rest of the Elastic stack.”
   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”
   • [probe] “official MCP server documented at https://github.com/elastic/mcp-server-elasticsearch”

   proof ↗⚑ flag

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

   weight 2 · round to Algolia
   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

   Elasticsearch~partialprobed6/10

   Elasticsearch itself is a query/DSL-based search engine, but it ships an official MCP server (elastic/mcp-server-elasticsearch) and documented 'skills' that teach AI coding agents how to operate Elasticsearch, Kibana, and Fleet — enabling natural-language-driven operation via an agent intermediary rather than a native NL interface. Missing for 10: first-party documentation of the MCP server's actual command coverage/reliability, independent hands-on validation of natural-language query results, and any built-in (non-MCP) NL query feature.

   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”
   • [probe] “official MCP server documented at https://github.com/elastic/mcp-server-elasticsearch”
   • [claimed-docs] “Install official skills that teach AI coding agents how to work with Elasticsearch, Kibana, Fleet, and the rest of the Elastic stack.”

   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

   Elasticsearch—none0/10

   The evidence pack contains no mention of an interactive API reference with runnable examples (e.g., a Swagger/OpenAPI console or embedded code sandbox); in fact, probes explicitly show that openapi.json, llms.txt, and docs.md endpoints all return 404, indicating no discoverable machine-readable or interactive API spec was found. Missing for 10: any documentation of an interactive API explorer, runnable code snippets, or a working OpenAPI/Swagger reference.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.elastic.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.elastic.co/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.elastic.co/openapi.json, https://www.elastic.co/swagger.json, https://www.elastic.co/api…”

   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

   Elasticsearch—none0/10

   The evidence pack's own probes checked for a machine-readable API spec (openapi.json, swagger.json, etc.) and found 404s at all candidate paths, and no docs item references a downloadable OpenAPI spec for Elasticsearch's REST API.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.elastic.co/openapi.json, https://www.elastic.co/swagger.json, https://www.elastic.co/api…”

   proof ↗⚑ flag

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

   weight 1 · round to Elasticsearch
   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

   Elasticsearch~partialclaimed5/10

   Elasticsearch docs show a one-line Docker quickstart for local development/testing and a free serverless trial project, both of which let a user spin up an isolated instance separate from production (elastic-docs-5, elastic-docs-17, elastic-docs-8, elastic-docs-13). However, there is no explicit 'sandbox mode', synthetic test-data seeding, or documented data-isolation guarantee marketed for AI-native testing workflows. Missing for 10: an explicit sandbox/test-environment feature, guidance on isolating test data from production indices, and independent confirmation that local/trial instances are fully safe substitutes for production testing.

   • [claimed-docs] “curl -fsSL https://elastic.co/start-local | sh”
   • [claimed-docs] “Quickly set up Elasticsearch and Kibana in Docker for local development or testing, using this one-liner in the command line.”
   • [claimed-docs] “If you are a new user, sign up for a free 14-day trial to create a serverless project.”
   • [claimed-docs] “Elastic provides several self-managed and Elastic-managed options.”

   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

   Elasticsearch—none0/10

   No evidence pack items address API versioning strategy, version compatibility guarantees, or a documented deprecation policy for Elasticsearch APIs; the pack focuses on search/vector features, serverless deployment, and community pricing/support complaints. Probes even show missing openapi.json and llms.txt, suggesting no discoverable machine-readable API spec, but nothing confirms or denies a deprecation policy.

   ⚑ 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 Elasticsearch
   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

   Elasticsearch✓fullclaimed9/10

   Elasticsearch's semantic_text field and inference API automatically generate embeddings via configured ML models (built-in or managed), with docs explicitly stating no need to define model settings or build inference pipelines, plus support for external/hosted embedding models. This directly matches the story of vectorization without a self-run embedding pipeline. Missing for 10: independent/hands-on developer corroboration beyond vendor docs.

   • [claimed-docs] “When you index content into a `semantic_text` field, Elasticsearch automatically generates vector embeddings using a configured machine lear…”
   • [claimed-docs] “When you index content into a `semantic_text` field, Elasticsearch automatically generates vector embeddings using a configured machine lear…”
   • [claimed-docs] “All you need to do is create an index mapping to start ingesting, embedding, and querying data. There is no need to define model-related set…”
   • [claimed-docs] “All you need to do is create an index mapping to start ingesting, embedding, and querying data. There is no need to define model-related set…”
   • [claimed-docs] “The inference API workflow is more complex but offers greater control over the inference endpoint configuration.”
   • [claimed-docs] “You can deploy external or hosted embedding models, or bring your own pre-computed vectors.”

   proof ↗⚑ flag

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

   weight 3 · round to Elasticsearch
   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

   Elasticsearch✓fullclaimed9/10

   Elastic's docs clearly describe hybrid search combining full-text and vector search in a single request, with RRF as the recommended fusion algorithm, plus semantic_text and dense_vector/sparse_vector support for embeddings. This is well-documented first-party capability directly matching the story; missing for 10: independent hands-on benchmark or third-party validation of the fused-query relevance quality.

   • [claimed-docs] “Hybrid search runs full-text search and vector search in one request.”
   • [claimed-docs] “We recommend implementing hybrid search with the reciprocal rank fusion (RRF) algorithm.”
   • [claimed-docs] “We recommend implementing hybrid search with the reciprocal rank fusion (RRF) algorithm. This approach merges rankings from the full-text an…”
   • [claimed-docs] “Hybrid search runs full-text search and vector search in one request... We recommend implementing hybrid search with the reciprocal rank fus…”
   • [claimed-docs] “We recommend implementing hybrid search with the [reciprocal rank fusion (RRF)](https://www.elastic.co/docs/reference/elasticsearch/rest-api…”
   • [claimed-docs] “Elasticsearch functions as a vector database when you store embeddings in `dense_vector` or `sparse_vector` fields and query them for simila…”
   • [claimed-docs] “When you index content into a `semantic_text` field, Elasticsearch automatically generates vector embeddings using a configured machine lear…”

   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

   Elasticsearch~partialclaimed7/10

   Elasticsearch documents strong retrieval-side building blocks for RAG—automatic embeddings via semantic_text, dense/sparse vector search, hybrid search with RRF, and an inference API for embedding/model integration, and explicitly references 'RAG (Retrieval Augmented Generation) systems' as a use case. However, the evidence shows no native 'answer' or completion API that generates conversational answers itself—Elasticsearch remains the retrieval layer, with answer generation implied to depend on external LLM integration (e.g., via the inference API to a hosted model) rather than a documented end-to-end answer endpoint. Missing for 10: a documented native answer/completion API or an explicit RAG pipeline tool (e.g., a 'Playground' or answer-generation endpoint) demonstrating conversational answer synthesis directly from Elasticsearch, plus independent hands-on confirmation of a full RAG flow.

   • [claimed-docs] “When you index content into a `semantic_text` field, Elasticsearch automatically generates vector embeddings using a configured machine lear…”
   • [claimed-docs] “Hybrid search runs full-text search and vector search in one request.”
   • [claimed-docs] “We recommend implementing hybrid search with the reciprocal rank fusion (RRF) algorithm.”
   • [claimed-docs] “The inference API workflow is more complex but offers greater control over the inference endpoint configuration.”
   • [claimed-docs] “RAG (Retrieval Augmented Generation) systems”
   • [claimed-docs] “Elasticsearch functions as a vector database when you store embeddings in `dense_vector` or `sparse_vector` fields and query them for simila…”
   • [claimed-docs] “All you need to do is create an index mapping to start ingesting, embedding, and querying data. There is no need to define model-related set…”

   proof ↗⚑ flag

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

   weight 2 · round to Algolia
   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

   Elasticsearch—none0/10

   The evidence pack contains no mention of Elasticsearch's bulk/batch APIs, batch indexing, multi-document updates, or any bulk-operation tooling for AI-native workflows — only single-document indexing (semantic_text), hybrid search, and serverless scaling are documented. Bulk operations are a plausible and expected capability for a search/database platform, so the axis applies, but no supporting evidence is present in this pack.

   ⚑ 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

   Elasticsearch—none0/10

   The evidence pack contains no mention of Elasticsearch/Kibana alerting, Watcher, or any rule-based trigger-action automation for events; only search, vector, and serverless-scaling features are documented. While such a capability (e.g., Kibana Alerting) is plausible for this product category, no evidence supports it here.

   ⚑ 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

   Elasticsearch—none0/10

   No evidence describes any scheduling, cron, or recurring workflow/job orchestration capability in Elasticsearch; the pack covers search, vector/hybrid retrieval, serverless scaling, and MCP integration, none of which address recurring job scheduling.

   ⚑ 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

   Elasticsearch~partialcommunity6/10

   Docs show a one-line local quickstart (curl install, Docker setup) and official client libraries, supporting fast setup, but no direct evidence of a documented end-to-end 'create index, add documents, search' walkthrough with actual commands, and community feedback notes documentation can be vague. missing for 10: explicit quickstart tutorial content showing index creation/document ingestion/search steps, independent hands-on confirmation of 'minutes' claim.

   • [claimed-docs] “curl -fsSL https://elastic.co/start-local | sh”
   • [claimed-docs] “Quickly set up Elasticsearch and Kibana in Docker for local development or testing, using this one-liner in the command line.”
   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”
   • [claimed-docs] “If you are a new user, sign up for a free 14-day trial to create a serverless project.”
   • [community] “Elastic.co is probably one of the worst websites that somehow gained popularity despite its crappy pricing model and support. Their document…”

   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

   Elasticsearch~partialclaimed5/10

   Docs confirm Elasticsearch ships 'a wide range of official libraries and developer tools' for popular languages, but the pack gives no specifics naming JavaScript, Python, PHP, Ruby, Go clients or evidence they are kept current/version-matched. Missing for 10: explicit list of supported official SDKs per language, versioning/release cadence details, and independent corroboration of SDK quality or maintenance.

   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”

   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

   Elasticsearch—none0/10

   Elasticsearch's evidence pack covers search/vector/hybrid features, serverless deployment, and clients, but contains no mention of official UI component libraries (search box, results, facets, pagination) for assembling a search interface. Search UI (Elastic's front-end library) is not referenced anywhere in the evidence.

   ⚑ 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

   Elasticsearch—none0/10

   The evidence pack contains no mention of Elastic's official web crawler or connectors for ingesting content (e.g., from S3, SharePoint, databases); it only covers semantic_text embedding generation, vector/hybrid search, and serverless deployment. Without documentation of a no-code ingestion pipeline via crawler/connectors, this story is unsupported by the given evidence.

   ⚑ flag

Ingestion

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

   weight 2 · round drawn
   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

   Elasticsearch—none0/10

   The evidence pack contains no mention of Elasticsearch's bulk API, async reindex/_reindex task API, or the Tasks API for tracking long-running indexing operations — all material specific to this story is absent; only unrelated search, vector, and serverless/pricing content is provided.

   ⚑ flag

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

   weight 2 · round to Elasticsearch
   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

   Elasticsearch~partialcommunity5/10

   Community evidence confirms Elasticsearch supports near-real-time search where indexed adds/updates/deletes become searchable after a refresh interval, and that this can be tuned to be 'practically real-time,' though with a performance trade-off ([elastic-comm-6]). However, none of the vendor documentation in this evidence pack explicitly describes the refresh_interval mechanism, versioning, or delete-visibility semantics that underlie this story, so the capability is only corroborated from a single community source rather than documented first-party. missing for 10: first-party docs on refresh_interval/NRT search semantics, documentation of update/delete visibility timing, independent benchmarks validating near-real-time latency under load.

   • [community] “The default refresh rate for ES is a minute or so... This means when you index a document, it won't be returned when you search for it until…”

   proof ↗⚑ flag

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

   weight 2 · round to Algolia
   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

   Elasticsearch—none0/10

   The evidence pack describes Elasticsearch's REST API capabilities (search, vector, hybrid search, clients) but never addresses whether every UI (e.g., Kibana) feature is exposed via the API, and probes show no OpenAPI/machine-readable spec confirming full API surface parity.

   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.elastic.co/openapi.json, https://www.elastic.co/swagger.json, https://www.elastic.co/api…”

   proof ↗⚑ flag

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

   weight 3 · round to Algolia
   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

   Elasticsearch—none0/10

   The evidence pack contains no documentation or community reports about exporting Elasticsearch data in open/portable formats (e.g., bulk export, snapshot/restore to open formats, or migration tooling); coverage is entirely about search, vector, and serverless features. Missing for 10: any mention of data export APIs, snapshot/restore in open formats, or migration/exit tooling.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Elasticsearch—none0/10

   The evidence pack contains no direct documentation of Elasticsearch's core source license or a link to its main source repository; the only GitHub reference is to the separate mcp-server-elasticsearch tool, not the Elasticsearch product itself. Community commentary even signals licensing churn (elastic-comm-2 calls it a 'formerly-OSS core'), but this doesn't rise to a concrete contradiction of a claimed capability—there's simply no evidence the story is fulfilled.

   • [claimed-docs] “elastic / mcp-server-elasticsearch Public”
   • [community] “Elastic.co has a lot of proprietary add-ons in their cloud and subscription tiers... Unfortunately for them a lot of users don't need any of…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Elasticsearch
   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

   Elasticsearch✓fullcommunity8/10

   Docs provide explicit self-managed deployment options, a local Docker/one-liner quickstart, and official client libraries, and community threads confirm real-world self-hosting (AWS ES, Elastic Cloud on Kubernetes, on-prem OSS core users) — clearly delivering self-hosting of the core product. Missing for 10: independent benchmark of self-hosted scaling/HA behavior and clearer distinction of which security/management features remain free vs paywalled in self-hosted mode.

   • [claimed-docs] “curl -fsSL https://elastic.co/start-local | sh”
   • [claimed-docs] “Quickly set up Elasticsearch and Kibana in Docker for local development or testing, using this one-liner in the command line.”
   • [claimed-docs] “Elastic provides several self-managed and Elastic-managed options.”
   • [claimed-docs] “Elasticsearch is easy to use from most popular programming languages, thanks to the wide range of official libraries and developer tools ava…”
   • [community] “Elastic.co has a lot of proprietary add-ons in their cloud and subscription tiers... Unfortunately for them a lot of users don't need any of…”
   • [community] “I found Elastic Cloud on K8s to be the best way to deploy and manage Elastic clusters on Kubernetes so far.”
   • [community] “For one, we don't have to pay for basic amenities like security and alerts. To heck with gouging the customer for basic feature sets. AWS ha…”

   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

   Elasticsearch—none0/10

   Elasticsearch is a search/data engine; the evidence covers vector search, hybrid search, serverless scaling, and clients, but there is no mention of a built-in analytics dashboard for top queries, no-result queries, or click-through tracking. This is a plausible axis for a search product (e.g., Algolia offers this), so absence of evidence means 'none' rather than 'na'.

   ⚑ 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 Elasticsearch
   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

   Elasticsearch~partialcommunity6/10

   Elastic documents serverless auto-scaling, separated search/index tiers, and Elastic Cloud on K8s (community-corroborated) as scaling paths, and community evidence confirms real production clustering use, but the pack lacks first-party detail on core self-managed clustering/replication mechanics (shard allocation, replica configuration, data tiers) and includes independent evidence of data-loss risk under network partitions (Jepsen) and default near-real-time refresh trade-offs that temper HA claims. missing for 10: explicit documented self-managed clustering/replica/shard-allocation guidance, resolution of the Jepsen partition-tolerance concern, and independent benchmarks validating scale to hundreds of millions of documents.

   • [claimed-docs] “instead of managing clusters, nodes, data tiers, and scaling, you create serverless projects that are fully managed and automatically scaled…”
   • [claimed-docs] “instead of managing clusters, nodes, data tiers, and scaling, you create serverless projects that are fully managed and automatically scaled…”
   • [claimed-docs] “Management free: Elastic manages the underlying Elastic cluster, so you can focus on your data... Autoscaled: To meet your performance requi…”
   • [claimed-docs] “Separating search and index tiers enables workloads to be scaled independently and reliably, with optimized hardware for each use case.”
   • [claimed-docs] “when you have a short-term spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the s…”
   • [community] “I found Elastic Cloud on K8s to be the best way to deploy and manage Elastic clusters on Kubernetes so far.”
   • [community] “Elastic is great as a search index, not as a primary database. [referencing Aphyr's Jepsen analysis showing Elasticsearch can lose indexed d…”
   • [community] “The default refresh rate for ES is a minute or so... This means when you index a document, it won't be returned when you search for it until…”

   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 Elasticsearch
   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

   Elasticsearch!disputedcontradicted4/10

   Elastic docs confirm self-managed/local deployment exists (elastic-docs-5, elastic-docs-13, elastic-docs-17), but Elastic Cloud Serverless — with auto-scaling, cross-project search, and independent scaling of search/index tiers — is explicitly described as a hosted-only model that removes manual cluster management (elastic-docs-21, elastic-docs-25, elastic-docs-27, elastic-docs-32), meaning self-hosted deployments do not get the same operational features. Community evidence also recalls basic security features being paywalled in self-managed versions historically (elastic-comm-3, elastic-comm-9), further undercutting the 'same features' claim. Missing for 10: documentation showing self-managed clusters can match serverless autoscaling/cross-project search, and confirmation that all licensed features are available identically on-prem.

   • [claimed-docs] “curl -fsSL https://elastic.co/start-local | sh”
   • [claimed-docs] “Elastic provides several self-managed and Elastic-managed options.”
   • [claimed-docs] “Quickly set up Elasticsearch and Kibana in Docker for local development or testing, using this one-liner in the command line.”
   • [claimed-docs] “instead of managing clusters, nodes, data tiers, and scaling, you create serverless projects that are fully managed and automatically scaled…”
   • [claimed-docs] “instead of managing clusters, nodes, data tiers, and scaling, you create serverless projects that are fully managed and automatically scaled…”
   • [claimed-docs] “Separating search and index tiers enables workloads to be scaled independently and reliably, with optimized hardware for each use case.”
   • [claimed-docs] “instead of managing clusters, nodes, data tiers, and scaling, you create **serverless projects** that are fully managed and automatically sc…”
   • [community] “I'll never forgive Elastic for locking basic security features behind their paid licence. Over the years probably millions of people had the…”
   • [community] “We were hit by this on Kibana 6.x as I didn't read the x-pack trial properly. I thought at least login would be there. My bad. We added Ngin…”

   proof ↗⚑ flag

Pricing

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

   weight 2 · round to Elasticsearch
   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

   Elasticsearch!disputedcontradicted4/10

   Elastic's serverless docs claim automatic, usage-based scaling that spins resources up for spikes and back down without user action (elastic-docs-33, elastic-docs-26), implying smooth cost scaling, but no pricing/cost caps or predictable-billing model is documented. Community evidence directly contradicts the 'no surprise cliffs' claim: teams report Elastic's licensing/subscription fees 'eat up significant portions of the project's profits' and describe its pricing as expensive and nickel-and-diming compared to alternatives (elastic-comm-4, elastic-comm-5, elastic-comm-10, elastic-comm-12, elastic-comm-13). Missing for 10: any first-party pricing/cost-predictability documentation, cost caps, or independent case studies showing stable costs at scale.

   • [claimed-docs] “when you have a short-term spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the s…”
   • [claimed-docs] “Management free: Elastic manages the underlying Elastic cluster, so you can focus on your data... Autoscaled: To meet your performance requi…”
   • [community] “Too late. We just deployed a new project with OpenSearch after learning from an Elastic salesperson that their licensing fees would eat up s…”
   • [community] “Elastic.co is probably one of the worst websites that somehow gained popularity despite its crappy pricing model and support. Their document…”
   • [community] “Elastic’s SaaS offering is incredibly expensive vs AWS Elasticsearch”
   • [community] “No one wants Elastic Search over Open Search. We're spending all our money on Open Search. Whenever I mention Elastic Search I may as well h…”
   • [community] “For one, we don't have to pay for basic amenities like security and alerts. To heck with gouging the customer for basic feature sets. AWS ha…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Elasticsearch—none0/10

   No evidence of published per-unit pricing (per search, record, or node) anywhere in the pack; only vague marketing claims ('30x faster... 50% cost of Datadog') and community complaints about opaque/expensive licensing, none of which constitute a transparent pricing calculator or rate card.

   • [claimed-docs] “Elasticsearch is 30x faster than Prom at 50% the cost of Datadog”
   • [community] “Elastic.co is probably one of the worst websites that somehow gained popularity despite its crappy pricing model and support. Their document…”
   • [community] “Elastic’s SaaS offering is incredibly expensive vs AWS Elasticsearch”
   • [community] “No one wants Elastic Search over Open Search. We're spending all our money on Open Search. Whenever I mention Elastic Search I may as well h…”

   proof ↗⚑ flag

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

   weight 2 · round to Elasticsearch
   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

   Elasticsearch~partialclaimed3/10

   Elastic offers both self-managed and Elastic-managed deployment options, which indirectly lets users control where their data physically resides (elastic-docs-13), and 'Cross-project search' claims data can stay in place without duplication (elastic-docs-34, elastic-docs-38). However, there is no explicit documentation of cloud region/residency selection controls for Elastic Cloud or Serverless projects. Missing for 10: explicit region-selection UI/API documentation, named regional data-residency guarantees, and independent confirmation of residency compliance.

   • [claimed-docs] “Elastic provides several self-managed and Elastic-managed options.”
   • [claimed-docs] “Cross-project search: Query isolated projects in-place. Unify global visibility without paying to move or duplicate your data.”
   • [claimed-docs] “CPS is GA: one unified view across your Serverless projects while data stays in place.”

   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

   Elasticsearch—none0/10

   The evidence pack contains no documentation of Elasticsearch's data retention or deletion controls (e.g., Index Lifecycle Management, TTL, delete-by-query APIs, or privacy/compliance tooling) — it focuses entirely on search, vector/embedding features, and serverless deployment. Since retention/deletion is a fair and applicable axis for a data platform like Elasticsearch, but no supporting evidence is present, this is 'none' rather than 'na'.

   ⚑ 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

   Elasticsearch—none0/10

   No evidence in the pack addresses telemetry opt-out or usage tracking controls for Elasticsearch; the docs/community items cover search features, deployment, pricing, and reliability, not privacy/telemetry settings. Missing for 10: any documentation of telemetry collection, opt-out mechanism, or privacy controls.

   ⚑ 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

   Elasticsearch—none0/10

   The evidence pack covers vector/hybrid search, serverless deployment, and pricing/community sentiment, but contains no mention of synonym definitions, curated results, pinning/boosting/hiding documents, or any relevance-tuning APIs (e.g., synonym API, query rules). No documentation or community evidence addresses this capability at all.

   ⚑ flag

Ranking

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

   weight 2 · round to Algolia
   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

   Elasticsearch—none0/10

   The evidence pack covers semantic/vector search, hybrid search with RRF, and serverless deployment, but contains no mention of Elasticsearch's ranking customization tools (e.g., function_score, script_score, boosting, decay functions) that would let a developer inject business signals like popularity, recency, or margin into relevance scoring. Missing for 10: any documentation of custom scoring functions, field/query boosting for non-textual signals, or examples combining business metrics with relevance ranking.

   ⚑ flag

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

   weight 1 · round drawn
   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

   Elasticsearch—none0/10

   Elasticsearch famously offers an Explain API and query profiling for ranking transparency, but none of the evidence pack mentions explain, _explain, profile API, or scoring breakdowns — the pack only covers hybrid search, RRF, vector search, serverless, and MCP topics. Absence of evidence for this applicable relevance-tuning capability means it cannot be credited here.

   ⚑ 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

   Elasticsearch—none0/10

   The evidence pack covers semantic/vector/hybrid search, serverless deployment, and MCP tooling, but contains no mention of Elasticsearch's suggestion/autocomplete-specific capabilities (e.g., completion suggester, search-as-you-type, edge n-grams) or any pattern for building suggestions from real query/traffic logs. Since autocomplete is a plausible axis for a search engine but no evidence supports it here, verdict is none.

   ⚑ flag

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

   weight 3 · round to Algolia
   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

   Elasticsearch—none0/10

   The evidence pack contains general marketing claims about speed ('unprecedented speed', '30x faster than Prom') and hybrid/vector search docs, but nothing describes autocomplete-style, keystroke-driven instant search (e.g. completion suggester, search-as-you-type field, edge n-gram) or millisecond query latency for typeahead use cases. Community notes even highlight refresh-interval delays affecting near-real-time indexing, but this doesn't establish the as-you-type capability itself.

   • [claimed-docs] “Get relevant results at unprecedented speed with open and flexible enterprise solutions.”
   • [claimed-docs] “Elasticsearch is 30x faster than Prom at 50% the cost of Datadog”
   • [community] “The default refresh rate for ES is a minute or so... This means when you index a document, it won't be returned when you search for it until…”

   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

   Elasticsearch—none0/10

   The evidence pack focuses on vector/semantic/hybrid search, serverless deployment, and pricing/support commentary, but contains no mention of fuzzy matching, typo tolerance, or edit-distance/fuzziness query parameters that would support this story.

   ⚑ 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

   Elasticsearch~partialclaimed4/10

   Elasticsearch's docs confirm it can combine full-text search, structured filters, and aggregations 'in one engine' (elastic-docs-4), which is the mechanism needed for faceted navigation, but the evidence pack contains no dedicated documentation, examples, or API references for building terms/range/histogram aggregations for facet counts, nor any walkthrough of a single query returning filtered results plus live facet counts. Missing for 10: explicit aggregations API docs/examples, terms/range/date-histogram facet examples, guidance on combining filters+aggs in one request, and independent/hands-on validation of facet performance.

   • [claimed-docs] “Elasticsearch can combine vector search with full-text search, structured filters, aggregations, and hybrid retrieval in one engine”

   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

   Elasticsearch—none0/10

   The evidence pack contains no mention of document-level security, field/document-level access control, API key privileges scoped to queries, or search templates restricting results per user — the actual mechanisms Elasticsearch offers for this use case are absent from the pack. Nothing here shows scoped/tenant tokens restricting per-user search results.

   ⚑ flag