Algolia vs Meilisearch

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

   Meilisearch✓fullprobed8/10

   Meilisearch provides a full REST API, official SDKs/CLI-style tooling, and a documented official MCP server that explicitly supports creating indexes, adding documents, configuring settings, and performing searches via natural-language prompts — enabling an agent to do the whole workflow without a dashboard. This is corroborated by a dedicated MCP integration page and probe confirming its existence. Missing for 10: independent/hands-on validation of the MCP server specifically (community evidence covers API/self-hosting but not MCP end-to-end), and no explicit standalone CLI tool for index/document CRUD beyond the API.

   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”
   • [claimed-docs] “you can create indexes, add documents, configure settings, and perform searches using natural language prompts”
   • [claimed-docs] “Update ranking rules, searchable attributes, and faceting through natural-language prompts.”
   • [claimed-docs] “Index documents, tune ranking rules, and search Meilisearch through natural conversation in the AI client you already use.”
   • [probe] “official MCP server documented at https://www.meilisearch.com/docs/getting_started/integrations/mcp”
   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Typed SDKs for JavaScript, Python, Ruby, PHP, Go, Rust, Java, Swift, Dart, and .NET.”

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

   Meilisearch✓fullprobed8/10

   Meilisearch documents an official MCP server (integrations/mcp) that lets agents create indexes, add documents, configure settings, update ranking rules/searchable attributes/faceting, and perform searches using natural-language prompts, confirmed independently via probe evidence of the documented integration page. Analytics tracking (queries, clicks, conversions) is also exposed as a core capability, though not explicitly confirmed as callable via the MCP surface itself. Missing for 10: independent/hands-on confirmation of the MCP server in actual agent use, and explicit evidence that analytics endpoints are exposed through the MCP tool-calling surface specifically (vs. just the general API).

   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”
   • [claimed-docs] “you can create indexes, add documents, configure settings, and perform searches using natural language prompts”
   • [claimed-docs] “Update ranking rules, searchable attributes, and faceting through natural-language prompts.”
   • [claimed-docs] “Index documents, tune ranking rules, and search Meilisearch through natural conversation in the AI client you already use.”
   • [claimed-docs] “Track search queries, click events, and conversions to measure search quality and identify opportunities for improvement.”
   • [claimed-docs] “Meilisearch analytics helps you understand how users interact with your search. Track search queries, click events, and conversions to measu…”
   • [probe] “official MCP server documented at https://www.meilisearch.com/docs/getting_started/integrations/mcp”

   proof ↗⚑ flag

Agent access

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

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

   Meilisearch✓fullprobed9/10

   Meilisearch serves an llms.txt at the root (HTTP 200) and provides .md versions of docs pages that explicitly point agents to a documentation index at /docs/llms.txt, confirming agent-oriented doc discovery is actively supported. missing for 10: no independent/community confirmation that agents actually consume these successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.meilisearch.com/llms.txt # Meilisearch — Official Information (llms.txt) This file is maintained by…”
   • [probe] “PROBE docs-md: HTTP 200 at https://www.meilisearch.com/docs/getting_started/overview.md > ## Documentation Index > Fetch the complete docume…”

   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

   Meilisearch~partialclaimed6/10

   Meilisearch is a single binary/Docker image with official SDKs, cURL-installable, and no external dependencies, making it straightforward to run headlessly in CI/automation pipelines (docs-11, docs-12, docs-18, docs-44, docs-73). However, there is no explicit documentation or examples specifically addressing CI usage, headless test automation, or scripted startup/health-check patterns for pipelines. missing for 10: explicit CI/CD examples or guides, headless-mode automation docs, community evidence of running Meilisearch in CI pipelines.

   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “curl -L https://install.meilisearch.com | sh”
   • [claimed-docs] “Install Meilisearch locally on Linux, macOS, or Windows using cURL, Docker, Homebrew, APT, or from source.”
   • [claimed-docs] “Official Meilisearch Docker images for easy deployment and development.”
   • [claimed-docs] “For production deployments, you will also need: A reverse proxy (Nginx or Caddy) for HTTPS termination A process manager (systemd)... A mast…”

   proof ↗⚑ flag

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

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

   Meilisearch✓fullprobed8/10

   Meilisearch publishes an official MCP server integration allowing AI agents/clients to create indexes, add documents, configure settings, and search using natural-language prompts, confirmed via docs and a dedicated integrations page and probe. missing for 10: independent/hands-on community verification of the MCP server's real-world reliability.

   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”
   • [claimed-docs] “you can create indexes, add documents, configure settings, and perform searches using natural language prompts”
   • [claimed-docs] “Update ranking rules, searchable attributes, and faceting through natural-language prompts.”
   • [claimed-docs] “Index documents, tune ranking rules, and search Meilisearch through natural conversation in the AI client you already use.”
   • [probe] “official MCP server documented at https://www.meilisearch.com/docs/getting_started/integrations/mcp”

   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

   Meilisearch—none0/10

   The evidence pack shows a self-hosted single binary, SDKs, Docker/Kubernetes integrations, and an official MCP server for natural-language interaction, but there is no mention of a dedicated official CLI tool for AI-native workflows (e.g., a `meilisearch-cli` package or command-line client distinct from the server binary itself).

   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “Install Meilisearch locally on Linux, macOS, or Windows using cURL, Docker, Homebrew, APT, or from source.”
   • [claimed-docs] “Official Meilisearch Docker images for easy deployment and development.”
   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”

   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

   Meilisearch✓fullprobed8/10

   Meilisearch is API-first: full REST API documented for creating indexes, adding documents, searching, and configuring settings, plus typed SDKs for 10+ languages and llms.txt/markdown-doc endpoints explicitly aimed at AI assistants. This gives an AI-native user a clear, documented public API surface to drive the product programmatically. Missing for 10: a discoverable machine-readable OpenAPI/Swagger spec (candidate URLs all returned 404), and independent hands-on confirmation of API completeness beyond vendor docs.

   • [claimed-docs] “creating a project and an index, adding documents to it, and performing your first search with the default web interface”
   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Typed SDKs for JavaScript, Python, Ruby, PHP, Go, Rust, Java, Swift, Dart, and .NET.”
   • [claimed-docs] “Integrate powerful search into your mobile and web applications with our easy-to-use APIs and SDKs for every major language.”
   • [claimed-docs] “The official JavaScript client for Meilisearch, with full TypeScript support for Node.js and browser environments.”
   • [claimed-docs] “The official Python client for Meilisearch with async support and type hints.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.meilisearch.com/llms.txt # Meilisearch — Official Information (llms.txt) This file is maintained by…”
   • [probe] “PROBE docs-md: HTTP 200 at https://www.meilisearch.com/docs/getting_started/overview.md > ## Documentation Index > Fetch the complete docume…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.meilisearch.com/openapi.json, https://www.meilisearch.com/swagger.json, https://www.meil…”

   proof ↗⚑ flag

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

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

   Meilisearch✓fullclaimed7/10

   Meilisearch documents tenant tokens as short-lived, scoped API credentials generated from an API key that embed search rules (filters) restricting data visibility per tenant/user — a direct mechanism for least-privilege scoped credentials suitable for an agent. Combined with API keys controlling permissions, this directly enables issuing scoped credentials for an AI agent (e.g. for its MCP integration). Missing for 10: explicit documentation tying tenant tokens/API key scoping specifically to AI agent use cases, and independent/hands-on validation of scoped-token behavior in agentic workflows.

   • [claimed-docs] “Tenant tokens are short-lived, scoped credentials generated from an API key. They embed search rules (filters) that automatically apply to e…”
   • [claimed-docs] “Tenant tokens are short-lived, scoped credentials generated from an API key. They embed search rules (filters) that automatically apply to e…”
   • [claimed-docs] “tenant tokens serve a similar purpose to Algolia's secured API keys or PostgreSQL's row-level security (RLS)”
   • [claimed-docs] “Meilisearch uses API keys and tenant tokens to control access to your data.”
   • [claimed-docs] “API keys authenticate requests, while tenant tokens restrict what data each user can see within a shared index.”
   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Algolia
   Algolia✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   Meilisearch✓fullcommunity8/10

   Meilisearch documents official typed SDKs for JavaScript, Python, Ruby, PHP, Go, Rust, Java, Swift, Dart, and .NET, with dedicated first-party client pages for JS and Python, plus Docker/Kubernetes/Laravel integrations. Community evidence (comm-5) confirms real-world usage of official language clients (e.g., Rails gem) though notes occasional version-compatibility friction. Missing for 10: independent hands-on corroboration for the full SDK matrix beyond JS/Python and no explicit versioning/maintenance cadence details.

   • [claimed-docs] “Typed SDKs for JavaScript, Python, Ruby, PHP, Go, Rust, Java, Swift, Dart, and .NET.”
   • [claimed-docs] “Integrate powerful search into your mobile and web applications with our easy-to-use APIs and SDKs for every major language.”
   • [claimed-docs] “The official JavaScript client for Meilisearch, with full TypeScript support for Node.js and browser environments.”
   • [claimed-docs] “The official Python client for Meilisearch with async support and type hints.”
   • [claimed-docs] “First-party Meilisearch driver for Laravel Scout, the official Laravel search package.”
   • [claimed-docs] “Official Meilisearch Docker images for easy deployment and development.”
   • [community] “The other issue we faced is their Rails gems falling out of step with the server, and when fixes came out, the Rails gem was incompatible fo…”

   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

   Meilisearch—none0/10

   No evidence in the pack mentions webhooks or event subscription mechanisms; only search, indexing, security, analytics, and MCP integration capabilities are documented. Absence of evidence for this applicable axis (a search engine could plausibly emit indexing/task webhooks) means verdict is none.

   ⚑ 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

   Meilisearch~partialclaimed4/10

   Meilisearch ships a 'conversational search' product that lets end users ask questions and get answers grounded in indexed data, plus a RAG-focused retrieval product and personalization that adapts results to user behavior — these are AI-generated, data-grounded outputs. However, these are building-block APIs for developers to embed in their own apps rather than an in-product AI insights/suggestions experience for the Meilisearch user themselves, and there is no evidence of a dashboard or admin-facing AI-generated insights feature. Missing for 10: an in-product AI insight/analytics dashboard for the Meilisearch operator, independent evidence of conversational search quality/accuracy, and clarity that this is end-user-facing rather than developer-embedded.

   • [claimed-docs] “Let users ask questions and get real answers, grounded in your own content. No hallucinations, no guessing.”
   • [claimed-docs] “The retrieval layer your AI applications need. Give your models accurate, current context from your own data.”
   • [claimed-docs] “Three users search for "laptop". Each sees results ranked by their unique preferences, no extra configuration needed.”
   • [claimed-docs] “Tailor every search to every user. Surface what is most relevant to each person based on their preferences and behavior.”
   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”

   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

   Meilisearch—none0/10

   Evidence shows Meilisearch offers an MCP integration for interactive natural-language configuration and search (meilisearch-docs-13, meilisearch-docs-57), but nothing describes scheduled jobs, triggers, or autonomous background automations that run without a user driving them. missing for 10: any scheduler/automation engine, background trigger system, or autonomous agent workflow capability.

   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”
   • [claimed-docs] “Index documents, tune ranking rules, and search Meilisearch through natural conversation in the AI client you already use.”
   • [probe] “official MCP server documented at https://www.meilisearch.com/docs/getting_started/integrations/mcp”

   proof ↗⚑ flag

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

   weight 3 · round to Algolia
   Algolia~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Meilisearch~partialprobed4/10

   Meilisearch doesn't ship a built-in AI assistant inside its own UI, but it does offer an official MCP server that lets external AI clients (Claude, etc.) index documents, tune settings, and search 'through natural conversation,' effectively delegating admin tasks via natural language. This is delegation via an external AI client connecting to Meilisearch, not an assistant built into the product itself. Missing for 10: an in-product/embedded assistant UI, evidence of task delegation happening natively inside Meilisearch's own interface rather than through a third-party AI client, and independent hands-on confirmation of the MCP workflow.

   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”
   • [claimed-docs] “you can create indexes, add documents, configure settings, and perform searches using natural language prompts”
   • [claimed-docs] “Update ranking rules, searchable attributes, and faceting through natural-language prompts.”
   • [claimed-docs] “Index documents, tune ranking rules, and search Meilisearch through natural conversation in the AI client you already use.”
   • [probe] “official MCP server documented at https://www.meilisearch.com/docs/getting_started/integrations/mcp”

   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

   Meilisearch~partialprobed6/10

   Meilisearch offers an official MCP server that lets users create indexes, add documents, configure settings, and perform searches via natural-language prompts in an AI client, which is strong first-party evidence of natural-language operability. However this is scoped to an external MCP integration rather than a native NL interface built into the core product, and there's no independent/hands-on corroboration of this specific MCP workflow beyond vendor docs. missing for 10: independent/hands-on validation of the MCP natural-language workflow, evidence of natural-language support outside the MCP integration (e.g., built-in NL query parsing in core API), and detail on reliability/limitations of the NL command interface.

   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”
   • [claimed-docs] “you can create indexes, add documents, configure settings, and perform searches using natural language prompts”
   • [claimed-docs] “Update ranking rules, searchable attributes, and faceting through natural-language prompts.”
   • [claimed-docs] “Index documents, tune ranking rules, and search Meilisearch through natural conversation in the AI client you already use.”
   • [probe] “official MCP server documented at https://www.meilisearch.com/docs/getting_started/integrations/mcp”

   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

   Meilisearch—none0/10

   The evidence pack shows no interactive API reference or runnable-example playground; the openapi probe explicitly found all candidate OpenAPI/Swagger endpoints returning 404, and docs pages described are static markdown guides, not runnable interactive references.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.meilisearch.com/openapi.json, https://www.meilisearch.com/swagger.json, https://www.meil…”
   • [probe] “PROBE docs-md: HTTP 200 at https://www.meilisearch.com/docs/getting_started/overview.md > ## Documentation Index > Fetch the complete docume…”

   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

   Meilisearch—none0/10

   The evidence pack explicitly shows a probe for OpenAPI/swagger specs at all common paths returning 404, and no documentation item mentions a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.meilisearch.com/openapi.json, https://www.meilisearch.com/swagger.json, https://www.meil…”

   proof ↗⚑ flag

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

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

   Meilisearch~partialclaimed4/10

   Meilisearch's single-binary self-hosting model and simple local install (curl/Docker) let a developer spin up an isolated instance to test with sample data separate from production, and Meilisearch Cloud offers a 14-day free trial. However, there is no explicit 'sandbox' or staging-environment feature, no documented way to clone/mirror production data safely, and no AI-native tooling specifically for sandbox testing. missing for 10: a dedicated sandbox/staging mode, data-masking or safe-copy tooling for production data, and explicit AI-native sandbox workflow documentation.

   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “curl -L https://install.meilisearch.com | sh”
   • [claimed-docs] “Install Meilisearch locally on Linux, macOS, or Windows using cURL, Docker, Homebrew, APT, or from source.”
   • [claimed-docs] “14-day free trial, no credit card required”

   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

   Meilisearch—none0/10

   The evidence pack contains no mention of API versioning scheme, version headers, or a documented deprecation policy anywhere in Meilisearch's docs, product pages, or community discussion. This is a fair axis for an API-first product like Meilisearch, but nothing in the pack substantiates it.

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

   Meilisearch✓fullclaimed8/10

   Docs explicitly state that configuring an embedder makes Meilisearch auto-generate embeddings for documents (and by extension queries via hybrid search) so developers don't need to compute/manage embeddings themselves, and hybrid search combining full-text and semantic search is a first-class documented capability. Missing for 10: no explicit listing of which embedder providers/models are supported (OpenAI, HuggingFace, etc.) or independent hands-on confirmation of embedder setup ease.

   • [claimed-docs] “When you configure an embedder, Meilisearch automatically generates vector embeddings for every document in your index. You don't need to co…”
   • [claimed-docs] “Hybrid search combines two search strategies: full-text search (matching keywords) and semantic search (matching meaning).”
   • [claimed-docs] “Hybrid search combines two search strategies: full-text search (matching keywords) and semantic search (matching meaning). This gives users …”
   • [claimed-docs] “Match how people actually search. Combine keyword precision with AI that understands meaning and intent.”

   proof ↗⚑ flag

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

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

   Meilisearch✓fullclaimed9/10

   Meilisearch's docs explicitly describe hybrid search as combining full-text (keyword) and semantic (vector) search in a single query, with automatic embedding generation and no manual embedding management, and a dedicated product page reiterates this capability. Community evidence corroborates general production reliability of Meilisearch's search features, though no independent hands-on report specifically validates hybrid search quality. Missing for 10: independent/hands-on verification specifically of hybrid search fusion behavior (most corroboration covers full-text/indexing performance, not hybrid semantic fusion).

   • [claimed-docs] “When you configure an embedder, Meilisearch automatically generates vector embeddings for every document in your index. You don't need to co…”
   • [claimed-docs] “Hybrid search combines two search strategies: full-text search (matching keywords) and semantic search (matching meaning).”
   • [claimed-docs] “Hybrid search combines two search strategies: full-text search (matching keywords) and semantic search (matching meaning). This gives users …”
   • [claimed-docs] “Match how people actually search. Combine keyword precision with AI that understands meaning and intent.”

   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

   Meilisearch~partialclaimed6/10

   Meilisearch documents a dedicated 'conversational search' and 'RAG' product ('Let users ask questions and get real answers, grounded in your own content'; 'The retrieval layer your AI applications need') plus hybrid/semantic search with automatic embedding generation, which together form the retrieval backbone for RAG. However, the evidence pack only shows marketing-style product pages rather than technical API reference docs for a chat/answer endpoint, and there is no independent/hands-on confirmation that the conversational-answer feature works as described in production. Missing for 10: concrete API/endpoint documentation for the answer/chat capability, and independent corroboration of RAG/conversational-answer quality in real use.

   • [claimed-docs] “It stores your documents and embeddings, then exposes them through fast full-text search, semantic search, and conversational interfaces, al…”
   • [claimed-docs] “Let users ask questions and get real answers, grounded in your own content. No hallucinations, no guessing.”
   • [claimed-docs] “The retrieval layer your AI applications need. Give your models accurate, current context from your own data.”
   • [claimed-docs] “Hybrid search combines two search strategies: full-text search (matching keywords) and semantic search (matching meaning).”
   • [claimed-docs] “When you configure an embedder, Meilisearch automatically generates vector embeddings for every document in your index. You don't need to co…”

   proof ↗⚑ flag

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

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

   Meilisearch~partialcommunity5/10

   Meilisearch supports adding/indexing large document sets (community reports of importing millions of records and batch indexing working well), and its MCP integration lets an AI agent create indexes, add documents, and configure settings via natural language, implying bulk workflows. However, there's no explicit vendor documentation of a dedicated bulk API for large-scale updates/deletes, and independent reports show real limits: unpredictable RAM under heavy write/search load and indexing falling behind for hours with fast-changing datasets. missing for 10: explicit vendor-documented bulk add/update/delete API semantics, AI-driven bulk operation examples, and consistent independent confirmation of reliable bulk performance at scale.

   • [claimed-docs] “creating a project and an index, adding documents to it, and performing your first search with the default web interface”
   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”
   • [community] “Running Meilisearch on a Hetzner AX52 (64GB RAM) with ~80,000,000 documents across 13 indexes; searches are fast and it's 'bored' at idle lo…”
   • [community] “We needed a 16GB machine to import all the data into Meilisearch, as batch indexing is quite memory intensive, but once it's all indexed we …”
   • [community] “I installed coolify on a VM and it had a one-click Meilisearch docker install. I sent 1,000,000 records to it and it 'just worked' on a litt…”
   • [community] “My team tried to use Meilisearch for large datasets; it's impossible to plan RAM usage. With little search traffic it used little RAM, but w…”
   • [community] “We've used Meilisearch in production and it is the closest thing to self hosted Algolia you can get. Unfortunately indexing performance for …”

   proof ↗⚑ flag

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

   weight 3 · round to Algolia
   Algolia~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Meilisearch—none0/10

   Meilisearch's evidence describes ranking/relevancy rules (typo tolerance, ranking rules, dynamic search rules for boosting/pinning results) and tenant tokens applied per search request, but none of this constitutes user-defined rules that trigger automated actions in response to events (e.g., webhooks, event-driven workflows). No evidence of an events/triggers/actions automation system exists in the pack.

   • [claimed-docs] “Dynamic Search Rules ... Boost, pin, or bury results based on the context of each request”
   • [claimed-docs] “Personalization Adapt search results for each user based on their preferences and behavior ... Dynamic Search Rules Boost, pin, or bury resu…”
   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order: ["words", "typo", "proximity", "attributeRank", "sort", "wordPosit…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Algolia
   Algolia~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Meilisearch—none0/10

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

   ⚑ flag

Onboarding

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

   weight 3 · round to Algolia
   Algolia✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Meilisearch!disputedcontradicted6/10

   Meilisearch's docs include a dedicated quickstart (first_project.md) that walks through creating an index, adding documents, and running a first search via the web UI, plus a one-line curl install that gets a server running in seconds (docs-2, docs-12, docs-18, docs-44). Multiple community reports corroborate quick setup ('zero config', 'just worked', 'very easy' — comm-10, comm-17, comm-18), but at least one hands-on account explicitly contradicts the 'minutes' framing, saying creating an index, uploading documents, and changing settings took 'a week's worth of coding' (comm-8). missing for 10: independent hands-on confirmation of the exact quickstart flow timing, and resolution of the conflicting community report on setup effort.

   • [claimed-docs] “creating a project and an index, adding documents to it, and performing your first search with the default web interface”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “curl -L https://install.meilisearch.com | sh”
   • [claimed-docs] “Install Meilisearch locally on Linux, macOS, or Windows using cURL, Docker, Homebrew, APT, or from source.”
   • [community] “I'm impressed. Blazing fast to index, like 10x more performant than using ElasticSearch/Searchkick; Blazing fast to search, at least 3x fast…”
   • [community] “Tested Meilisearch recently, was a great experience, getting a multi-index search running in our frontend was very easy. Just wish they had …”
   • [community] “I installed coolify on a VM and it had a one-click Meilisearch docker install. I sent 1,000,000 records to it and it 'just worked' on a litt…”
   • [community] “1. The rules for text searches are too strict by default and if the order of words is different, will result in no matches. 2. Creating an i…”

   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

   Meilisearch!disputedcontradicted6/10

   Meilisearch documents official typed SDKs for JavaScript, Python, PHP, Ruby, Go, Rust, Java, Swift, Dart, and .NET, with dedicated integration pages for JS/Python clients and a Laravel Scout driver, matching the story's core language list. However, community hands-on reports concretely contradict the 'kept current' claim: users reported the official Ruby/Rails gem falling out of sync with server releases, becoming incompatible for a period after server updates. Missing for 10: independent confirmation of SDK freshness across all listed languages, evidence of consistent release cadence/versioning parity, and no counter-examples for other languages besides the documented Ruby gem lag.

   • [claimed-docs] “Typed SDKs for JavaScript, Python, Ruby, PHP, Go, Rust, Java, Swift, Dart, and .NET.”
   • [claimed-docs] “The official JavaScript client for Meilisearch, with full TypeScript support for Node.js and browser environments.”
   • [claimed-docs] “The official Python client for Meilisearch with async support and type hints.”
   • [claimed-docs] “First-party Meilisearch driver for Laravel Scout, the official Laravel search package.”
   • [community] “The other issue we faced is their Rails gems falling out of step with the server, and when fixes came out, the Rails gem was incompatible fo…”

   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

   Meilisearch~partialclaimed6/10

   Meilisearch documents an official integration pairing it with React InstantSearch to 'build performant, responsive search interfaces,' which is a UI component library that supplies box, results, facets, and pagination widgets out of the box. However, the evidence pack only gives a single line about this integration with no detail on the specific components, customization, or coverage for other frameworks (Vue, Angular, vanilla JS widgets). missing for 10: broader multi-framework UI library docs, concrete examples of facet/pagination components, independent hands-on confirmation of assembling a full UI without custom code.

   • [claimed-docs] “Build performant, responsive search interfaces by pairing Meilisearch with React InstantSearch.”

   proof ↗⚑ flag

Connectors

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

   weight 1 · round to Algolia
   Algolia✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Meilisearch~partialclaimed4/10

   Meilisearch lists official-looking connectors (meilisync for DB syncing, a Laravel Scout driver, various SDKs) that reduce custom pipeline work, but there is no evidence of an official web crawler (unlike Algolia's Crawler product) for ingesting arbitrary site/content, so founders would still need custom ingestion code for many content sources. missing for 10: an official website/content crawler, broader first-party connectors (CMS, cloud storage, SaaS apps) beyond meilisync and Laravel Scout, and independent evidence these connectors work reliably at scale.

   • [claimed-docs] “Sync databases with Meilisearch automatically.”
   • [claimed-docs] “First-party Meilisearch driver for Laravel Scout, the official Laravel search package.”
   • [claimed-docs] “The official JavaScript client for Meilisearch, with full TypeScript support for Node.js and browser environments.”
   • [claimed-docs] “The official Python client for Meilisearch with async support and type hints.”
   • [claimed-docs] “Official Meilisearch Docker images for easy deployment and development.”

   proof ↗⚑ flag

Ingestion

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

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

   Meilisearch~partialcommunity6/10

   Community evidence strongly supports bulk-importing millions of documents (7M-article corpus, 80M-document deployment, 1M-record imports that 'just worked') and confirms Meilisearch uses batch indexing for large imports, but none of the evidence explicitly documents the async task/status API that lets a platform engineer poll for indexing completion. One report also notes indexing can fall behind for hours under heavy write load, showing throughput is not always guaranteed at scale. Missing for 10: explicit documentation/evidence of the task-status endpoint or webhook mechanism for tracking async indexing completion, and stronger evidence reconciling the indexing-lag report.

   • [community] “We use Meilisearch in production with a 7 million article corpus - it works really well.”
   • [community] “Running Meilisearch on a Hetzner AX52 (64GB RAM) with ~80,000,000 documents across 13 indexes; searches are fast and it's 'bored' at idle lo…”
   • [community] “We needed a 16GB machine to import all the data into Meilisearch, as batch indexing is quite memory intensive, but once it's all indexed we …”
   • [community] “I installed coolify on a VM and it had a one-click Meilisearch docker install. I sent 1,000,000 records to it and it 'just worked' on a litt…”
   • [community] “We've used Meilisearch in production and it is the closest thing to self hosted Algolia you can get. Unfortunately indexing performance for …”
   • [community] “I'm impressed. Blazing fast to index, like 10x more performant than using ElasticSearch/Searchkick; Blazing fast to search, at least 3x fast…”

   proof ↗⚑ flag

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

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

   Meilisearch!disputedcontradicted5/10

   Meilisearch's docs describe adding/updating documents to an index and instant search, implying near-real-time indexing, and some users report blazing-fast indexing (meilisearch-comm-10, meilisearch-comm-6). However, hands-on production reports concretely contradict this for high-churn workloads: one team says 'indexing performance for constantly changing records wasn't great and Meilisearch would fall behind on indexing for hours' (meilisearch-comm-4), and others report unpredictable resource usage and write-scaling issues under heavy load (meilisearch-comm-3, meilisearch-comm-13). missing for 10: explicit vendor documentation of update latency/consistency guarantees, and resolution of the conflicting production reports on indexing lag under heavy write traffic.

   • [claimed-docs] “creating a project and an index, adding documents to it, and performing your first search with the default web interface”
   • [community] “I'm impressed. Blazing fast to index, like 10x more performant than using ElasticSearch/Searchkick; Blazing fast to search, at least 3x fast…”
   • [community] “We've used Meilisearch in production and it is the closest thing to self hosted Algolia you can get. Unfortunately indexing performance for …”
   • [community] “My team tried to use Meilisearch for large datasets; it's impossible to plan RAM usage. With little search traffic it used little RAM, but w…”
   • [community] “I've had issues scaling writes to it. You can get around it, but maybe this would be better in a high write environment.”
   • [community] “We needed a 16GB machine to import all the data into Meilisearch, as batch indexing is quite memory intensive, but once it's all indexed we …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Algolia~partialprobed6/10

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

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

   proof ↗⚑ flag

   Meilisearch~partialprobed6/10

   Meilisearch is fundamentally API-first — indexes, documents, settings, ranking rules, facets, embeddings, and search are all configured and queried through the API, with only a thin default web interface for a first search (docs-2) and a Cloud dashboard for hosted features. This strongly implies API/UI parity by design, but there is no explicit documentation stating full feature parity, and a probe for a public OpenAPI spec returned 404s, so exhaustive API coverage isn't independently verifiable. Missing for 10: an explicit statement or audit confirming every UI-exposed action (e.g., Cloud dashboard features like clusterization, analytics dashboards) has a documented API equivalent, and a public OpenAPI/reference spec.

   • [claimed-docs] “creating a project and an index, adding documents to it, and performing your first search with the default web interface”
   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Once configured, you can create indexes, add documents, configure settings, and perform searches using natural language prompts.”
   • [claimed-docs] “Guarantees the Read High Availability of the service with native support for clusterization.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.meilisearch.com/openapi.json, https://www.meilisearch.com/swagger.json, https://www.meil…”

   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

   Meilisearch—none0/10

   The evidence covers self-hosting, installation, and various search capabilities, but nowhere documents a data export/dump feature or open-format data portability mechanism that would let a user extract all their indexed documents and leave. Self-hosting (docs-11,12,44) implies data resides locally, but this is not the same as an explicit export tool or open-format guarantee.

   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “Install Meilisearch locally on Linux, macOS, or Windows using cURL, Docker, Homebrew, APT, or from source.”

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

   Meilisearch—none0/10

   The evidence pack contains no mention of Meilisearch's source code repository, license type, or any open-source claim; only docs, integrations, and community sentiment about performance are present. Since an open-source license is a plausible and common attribute for a self-hosted database/search product, the axis applies, but no evidence supports it here.

   ⚑ flag

4. ai-native userSelf-host the core product

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

   Meilisearch✓fullcommunity9/10

   Docs clearly describe self-hosting as a single dependency-free binary runnable via cURL, Docker, Homebrew, APT, or source on Linux/macOS/Windows, plus production guidance (reverse proxy, process manager, master key) and Kubernetes Helm charts/Docker images, and community reports confirm real-world self-hosted deployments at scale. Missing for 10: no independent audit of open-source license terms or feature parity vs. cloud version in the evidence pack.

   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “curl -L https://install.meilisearch.com | sh”
   • [claimed-docs] “For production deployments, you will also need: A reverse proxy (Nginx or Caddy) for HTTPS termination A process manager (systemd)... A mast…”
   • [claimed-docs] “Install Meilisearch locally on Linux, macOS, or Windows using cURL, Docker, Homebrew, APT, or from source.”
   • [claimed-docs] “Helm charts for deploying Meilisearch on Kubernetes.”
   • [claimed-docs] “Official Meilisearch Docker images for easy deployment and development.”
   • [community] “Running Meilisearch on a Hetzner AX52 (64GB RAM) with ~80,000,000 documents across 13 indexes; searches are fast and it's 'bored' at idle lo…”
   • [community] “I installed coolify on a VM and it had a one-click Meilisearch docker install. I sent 1,000,000 records to it and it 'just worked' on a litt…”
   • [community] “I recently stood up the server in our k8s cluster and that part was also pretty easy, at least compared to elastic.”

   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

   Meilisearch~partialclaimed6/10

   Meilisearch docs explicitly describe a built-in analytics capability tracking search queries, click events, and conversions to measure search quality (docs-9, docs-29, docs-54), which covers query tracking and click-through, but there is no explicit mention of a dedicated 'no-result queries' report/dashboard and no independent/hands-on corroboration of the analytics feature's UI or accuracy. missing for 10: explicit no-result-query reporting, a documented dashboard/UI view of these metrics, independent user confirmation of the analytics feature in practice.

   • [claimed-docs] “Track search queries, click events, and conversions to measure search quality and identify opportunities for improvement.”
   • [claimed-docs] “Meilisearch analytics helps you understand how users interact with your search. Track search queries, click events, and conversions to measu…”
   • [claimed-docs] “Track search events, user clicks, and conversions to measure and improve your search relevancy.”

   proof ↗⚑ flag

Scale

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

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

   Meilisearch~partialcommunity4/10

   Meilisearch Cloud advertises 'Read High Availability' with 'native support for clusterization' (meilisearch-docs-14), and there are Kubernetes Helm charts and Docker images for deployment (meilisearch-docs-69, meilisearch-docs-73), but the self-hosted OSS docs describe only a single-binary, no-external-dependency model with production notes limited to reverse proxy, systemd, and master keys (meilisearch-docs-11, meilisearch-docs-36) — no documented replication, sharding, or multi-node clustering path for self-managed deployments. Community reports are mixed on true large-scale operation: some reached tens of millions of documents successfully (meilisearch-comm-15, meilisearch-comm-14), but others report unpredictable RAM usage under heavy traffic and indexing falling behind for fast-changing datasets, forcing migration away (meilisearch-comm-3, meilisearch-comm-4, meilisearch-comm-13). Missing for 10: documented self-hosted clustering/sharding architecture, replication configuration guide, and independent validation of stable operation at 'hundreds of millions of documents' scale.

   • [claimed-docs] “Guarantees the Read High Availability of the service with native support for clusterization.”
   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “For production deployments, you will also need: A reverse proxy (Nginx or Caddy) for HTTPS termination A process manager (systemd)... A mast…”
   • [claimed-docs] “Helm charts for deploying Meilisearch on Kubernetes.”
   • [community] “Running Meilisearch on a Hetzner AX52 (64GB RAM) with ~80,000,000 documents across 13 indexes; searches are fast and it's 'bored' at idle lo…”
   • [community] “We use Meilisearch in production with a 7 million article corpus - it works really well.”
   • [community] “My team tried to use Meilisearch for large datasets; it's impossible to plan RAM usage. With little search traffic it used little RAM, but w…”
   • [community] “We've used Meilisearch in production and it is the closest thing to self hosted Algolia you can get. Unfortunately indexing performance for …”
   • [community] “I've had issues scaling writes to it. You can get around it, but maybe this would be better in a high write environment.”

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

   Meilisearch~partialcommunity6/10

   Meilisearch is explicitly built to self-host as a single binary with no external dependencies (Docker, Kubernetes/Helm, systemd, reverse proxy guidance), and community reports confirm large-scale self-hosted production deployments (7M-100M+ document corpora, k8s clusters). However, some capabilities referenced in the docs — read high-availability/clusterization, and features like Analytics, Personalization and Dynamic Search Rules — are described on the Cloud/pricing pages rather than the self-hosting docs, suggesting these are not identical to the self-hosted OSS engine. Missing for 10: explicit confirmation that clustering/HA, analytics, and personalization are available (not cloud-exclusive) in the self-hosted binary, and independent verification of full feature parity between Cloud and self-hosted editions.

   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine”
   • [claimed-docs] “For production deployments, you will also need: A reverse proxy (Nginx or Caddy) for HTTPS termination A process manager (systemd)... A mast…”
   • [claimed-docs] “Install Meilisearch locally on Linux, macOS, or Windows using cURL, Docker, Homebrew, APT, or from source.”
   • [claimed-docs] “Helm charts for deploying Meilisearch on Kubernetes.”
   • [claimed-docs] “Guarantees the Read High Availability of the service with native support for clusterization.”
   • [claimed-docs] “Personalization Adapt search results for each user based on their preferences and behavior ... Dynamic Search Rules Boost, pin, or bury resu…”
   • [community] “Running Meilisearch on a Hetzner AX52 (64GB RAM) with ~80,000,000 documents across 13 indexes; searches are fast and it's 'bored' at idle lo…”
   • [community] “I recently stood up the server in our k8s cluster and that part was also pretty easy, at least compared to elastic.”

   proof ↗⚑ flag

Pricing

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

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

   Meilisearch!disputedcontradicted3/10

   Docs describe self-hosting as a single binary you control (implying predictable infra costs) and reference a pricing page, but they never explicitly address predictable per-request/query pricing at scale. Concrete community evidence directly contradicts predictability: one team found RAM usage 'impossible to plan' and unpredictably expensive under heavy search traffic (comm-3), and another flags a steep jump from a free tier to $1200/month on Meilisearch Cloud (comm-2), i.e. real cost cliffs and unpredictable resource scaling. Missing for 10: first-party pricing documentation addressing predictability/no-cliff guarantees, and independent confirmation that costs scale linearly/predictably with volume.

   • [claimed-docs] “Dynamic Search Rules ... Boost, pin, or bury results based on the context of each request”
   • [claimed-docs] “Personalization Adapt search results for each user based on their preferences and behavior ... Dynamic Search Rules Boost, pin, or bury resu…”
   • [claimed-docs] “14-day free trial, no credit card required”
   • [community] “I was hoping the cloud version would be more appealing, granted there seems to be a generous free tier but the next option is $1200 a month?…”
   • [community] “My team tried to use Meilisearch for large datasets; it's impossible to plan RAM usage. With little search traffic it used little RAM, but w…”

   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

   Meilisearch—none0/10

   The evidence pack shows a pricing page exists (mentioning feature tiers like 'Dynamic Search Rules' and a '14-day free trial') but never publishes concrete per-unit rates for searches, records, or nodes that a founder could use to forecast costs. Community comments actually highlight unpredictability (a jump to '$1200/month' with no visible per-unit basis, and RAM/cost unpredictability under load), reinforcing that no transparent per-unit pricing model is documented.

   • [claimed-docs] “Dynamic Search Rules ... Boost, pin, or bury results based on the context of each request”
   • [claimed-docs] “Personalization Adapt search results for each user based on their preferences and behavior ... Dynamic Search Rules Boost, pin, or bury resu…”
   • [claimed-docs] “14-day free trial, no credit card required”
   • [community] “I was hoping the cloud version would be more appealing, granted there seems to be a generous free tier but the next option is $1200 a month?…”
   • [community] “My team tried to use Meilisearch for large datasets; it's impossible to plan RAM usage. With little search traffic it used little RAM, but w…”

   proof ↗⚑ flag

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

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

   Meilisearch~partialcommunity6/10

   Meilisearch ships as a self-hostable single binary/Docker/Kubernetes deployment, which lets an AI-native user run it in any jurisdiction of their choosing, satisfying the residency need via self-hosting rather than a built-in region picker. However, for the managed Meilisearch Cloud offering there's no documented list of selectable regions, and one community report notes only a Singapore region was available with no Australian option, suggesting limited choice for cloud users. Missing for 10: explicit multi-region selection UI/API for Meilisearch Cloud, first-party documentation listing available cloud regions, and confirmation that self-hosted deployments meet formal residency/compliance requirements.

   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine”
   • [claimed-docs] “For production deployments, you will also need: A reverse proxy (Nginx or Caddy) for HTTPS termination A process manager (systemd)... A mast…”
   • [claimed-docs] “Install Meilisearch locally on Linux, macOS, or Windows using cURL, Docker, Homebrew, APT, or from source.”
   • [claimed-docs] “Helm charts for deploying Meilisearch on Kubernetes.”
   • [community] “Tested Meilisearch recently, was a great experience, getting a multi-index search running in our frontend was very easy. Just wish they had …”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Algolia—none0/10

   No evidence in the pack addresses data usage for AI model training, opt-out controls, or any privacy policy regarding training data; this is an applicable axis (an AI-adjacent SaaS could plausibly document such a policy) but absent from the evidence.

   ⚑ flag

   Meilisearch—none0/10

   No evidence pack material addresses AI-training data usage, opt-out controls, or any privacy policy statement about whether user data/queries feed model training. Meilisearch is a self-hosted/cloud search engine and such a policy statement is plausible for it to publish, but nothing here confirms or denies it. Community notes mention on-by-default analytics concerns, but this is about telemetry, not AI training data use. missing for 10: explicit privacy policy or docs statement on AI/model training data usage, opt-out mechanism, or contractual guarantee.

   ⚑ flag

3. 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

   Meilisearch—none0/10

   The evidence pack never documents any explicit data-retention or document/index-deletion controls (e.g., delete-document API, TTL, data export/erasure tooling). Self-hosting evidence (meilisearch-docs-11/12/18/19) implies a user could control their own infrastructure, but this is indirect and not a documented retention/deletion feature; community evidence (meilisearch-comm-12) even flags on-by-default analytics tracking with no clear opt-out as a privacy concern rather than showing a retention control. Missing for 10: explicit documentation of deletion APIs, retention policies, TTLs, or data-export/erasure tooling.

   • [claimed-docs] “Meilisearch is a single binary with no external dependencies. You can run it on any Linux, macOS, or Windows machine, on bare metal or in co…”
   • [claimed-docs] “Download the latest stable release of Meilisearch with cURL. Launch Meilisearch to start the server.”
   • [claimed-docs] “Track search queries, click events, and conversions to measure search quality and identify opportunities for improvement.”
   • [community] “The practice itself is malignant [on-by-default analytics]; either explicitly ask upon first run or require an env variable to enable it.”

   proof ↗⚑ flag

4. 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

   Meilisearch—none0/10

   No documentation in the evidence pack describes a telemetry/analytics opt-out mechanism. A community comment explicitly criticizes Meilisearch's on-by-default analytics as a practice needing improvement ('either explicitly ask upon first run or require an env variable to enable it'), indicating no clear, documented way to opt out is evidenced here.

   • [community] “The practice itself is malignant [on-by-default analytics]; either explicitly ask upon first run or require an env variable to enable it.”

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

   Meilisearch✓fullclaimed8/10

   Meilisearch documents synonym configuration directly (synonyms.md) and offers editable ranking rules for relevance tuning, plus paid "Dynamic Search Rules" that explicitly boost, pin, or bury results per query context. Community evidence corroborates general relevancy/production use, though no independent hands-on confirmation specifically of pin/boost/hide curation exists. Missing for 10: independent/community validation specifically of the pin/boost/hide curation feature (only vendor pricing page mentions it) and detail on the 'hide' mechanism beyond bury.

   • [claimed-docs] “If multiple words have an equivalent meaning in your dataset, you can create a list of synonyms. This will make your search results more rel…”
   • [claimed-docs] “you can create a list of synonyms. This will make your search results more relevant.”
   • [claimed-docs] “If multiple words have an equivalent meaning in your dataset, you can create a list of synonyms”
   • [claimed-docs] “Dynamic Search Rules ... Boost, pin, or bury results based on the context of each request”
   • [claimed-docs] “Personalization Adapt search results for each user based on their preferences and behavior ... Dynamic Search Rules Boost, pin, or bury resu…”
   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order: ["words", "typo", "proximity", "attributeRank", "sort", "wordPosit…”
   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order... Depending on your needs, you might want to change this order.”

   proof ↗⚑ flag

Ranking

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

   weight 2 · round drawn
   Algolia✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Meilisearch✓fullclaimed8/10

   Meilisearch documents customizable ranking rules (including sort and attributeRank) that can be reordered, plus sortable attributes for popularity/recency/margin-style business signals, and Cloud-tier features like Dynamic Search Rules to boost/pin/bury results by context. Missing for 10: independent hands-on evidence of complex multi-signal ranking tuning in production, and the boost/pin/bury 'Dynamic Search Rules' feature is only documented on the pricing page (Cloud-only) rather than core docs.

   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order: ["words", "typo", "proximity", "attributeRank", "sort", "wordPosit…”
   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order... Depending on your needs, you might want to change this order.”
   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order: words, typo, proximity, attributeRank, sort, wordPosition, exactne…”
   • [claimed-docs] “Depending on your needs, you might want to change this order.”
   • [claimed-docs] “Dynamic Search Rules ... Boost, pin, or bury results based on the context of each request”
   • [claimed-docs] “Personalization Adapt search results for each user based on their preferences and behavior ... Dynamic Search Rules Boost, pin, or bury resu…”

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

   Meilisearch—none0/10

   The evidence describes the seven built-in ranking rules and that their order can be customized, but nothing in the pack shows a mechanism for inspecting per-result ranking scores or a detailed ranking explanation for why a specific document ranked where it did. missing for 10: any documentation of a ranking-score/explain API or debug output, independent confirmation of such a feature being used for relevance tuning.

   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order: ["words", "typo", "proximity", "attributeRank", "sort", "wordPosit…”
   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order... Depending on your needs, you might want to change this order.”
   • [claimed-docs] “Depending on your needs, you might want to change this order.”
   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order”

   proof ↗⚑ flag

Experience

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

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

   Meilisearch~partialclaimed5/10

   Meilisearch documents facet search explicitly for powering autocomplete/type-ahead interfaces, and its analytics feature tracks search queries, clicks, and conversions that could inform a suggestions strategy, but there is no documented dedicated 'suggestions index' or query-log-driven autocomplete feature (e.g., popular/trending query suggestions) — only facet-value autocomplete and general query analytics. missing for 10: a first-party suggestions/autocomplete-from-search-traffic feature, documentation on building a suggestions index from query logs, and independent evidence of this pattern being used in production.

   • [claimed-docs] “It is typically used to power auto-complete and type-ahead interfaces on top of filter menus, especially when a facet has too many distinct …”
   • [claimed-docs] “Facet search is a dedicated endpoint for searching through the values of a single facet. It is typically used to power auto-complete and typ…”
   • [claimed-docs] “Facet search is a dedicated endpoint for searching through the values of a single facet.”
   • [claimed-docs] “Track search queries, click events, and conversions to measure search quality and identify opportunities for improvement.”
   • [claimed-docs] “Meilisearch analytics helps you understand how users interact with your search. Track search queries, click events, and conversions to measu…”
   • [claimed-docs] “Track search events, user clicks, and conversions to measure and improve your search relevancy.”

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

   Meilisearch✓fullcommunity8/10

   Meilisearch is purpose-built for instant, typo-tolerant, millisecond full-text search with ranking rules, and community reports corroborate real-world speed (10x faster indexing/search than Elasticsearch, sub-second at scale) even though some users note RAM/write scaling issues under heavy load. Docs explicitly market 'instant' typo-tolerant search with no tuning required, and hands-on reports confirm fast search at production scale. missing for 10: no explicit documented millisecond latency benchmark or as-you-type debounce guidance, and some community reports of indexing lag/RAM unpredictability under heavy write load temper full confidence.

   • [claimed-docs] “Typo tolerance helps users find relevant results even when their search queries contain spelling mistakes or typos, for example, typing `phn…”
   • [claimed-docs] “Meilisearch contains seven built-in ranking rules in the following order: ["words", "typo", "proximity", "attributeRank", "sort", "wordPosit…”
   • [claimed-docs] “Help users find what they want instantly, even when they misspell or only remember part of it. No tuning required.”
   • [community] “I'm impressed. Blazing fast to index, like 10x more performant than using ElasticSearch/Searchkick; Blazing fast to search, at least 3x fast…”
   • [community] “We use Meilisearch in production with a 7 million article corpus - it works really well.”
   • [community] “Running Meilisearch on a Hetzner AX52 (64GB RAM) with ~80,000,000 documents across 13 indexes; searches are fast and it's 'bored' at idle lo…”
   • [community] “My team tried to use Meilisearch for large datasets; it's impossible to plan RAM usage. With little search traffic it used little RAM, but w…”
   • [community] “We've used Meilisearch in production and it is the closest thing to self hosted Algolia you can get. Unfortunately indexing performance for …”

   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

   Meilisearch✓fullcommunity8/10

   Docs confirm typo tolerance is enabled by default (docs-3, docs-37, docs-60) and is tunable per index via minWordSizeForTypos and other settings (docs-22, docs-31), giving developers control over when/how fuzzy matching applies. Community feedback (comm-10) corroborates a 'zero config' experience, though no independent test specifically stresses typo-matching edge cases. Missing for 10: independent hands-on verification of typo-tolerance accuracy/limits and more detail on advanced tuning knobs beyond minWordSizeForTypos.

   • [claimed-docs] “Typo tolerance helps users find relevant results even when their search queries contain spelling mistakes or typos, for example, typing `phn…”
   • [claimed-docs] “You can override these default settings using the minWordSizeForTypos object.”
   • [claimed-docs] “You can configure the typo tolerance feature for each index”
   • [claimed-docs] “Typo tolerance helps users find relevant results even when their search queries contain spelling mistakes or typos”
   • [claimed-docs] “Help users find what they want instantly, even when they misspell or only remember part of it. No tuning required.”
   • [community] “I'm impressed. Blazing fast to index, like 10x more performant than using ElasticSearch/Searchkick; Blazing fast to search, at least 3x fast…”

   proof ↗⚑ flag

Filtering

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

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

   Meilisearch✓fullcommunity9/10

   Meilisearch's docs directly describe faceted navigation with live counts (e.g., 'Color: Red (12), Blue (8)'), filtering by categories/ranges/attributes (brand, color, size, price range), a dedicated facet search endpoint for large facet lists, and this all being returned from a single query/API call alongside search results. Community evidence corroborates real-world use of filtering/faceting features at scale. missing for 10: independent hands-on benchmark specifically validating live facet counts performance/accuracy at scale.

   • [claimed-docs] “E-commerce faceted navigation: Let shoppers narrow products by brand, color, size, and price range while displaying counts for each option.”
   • [claimed-docs] “"Color: Red (12), Blue (8)"”
   • [claimed-docs] “Faceting returns aggregated counts for field values, powering category navigation in your UI”
   • [claimed-docs] “Facet search is a dedicated endpoint for searching through the values of a single facet. It is typically used to power auto-complete and typ…”
   • [claimed-docs] “Facets are filters that also return distribution data. Use them together to build interactive, ecommerce-style navigation.”
   • [claimed-docs] “Filtering, sorting, and faceting are three complementary tools for refining search results”
   • [claimed-docs] “Facet search is a dedicated endpoint for searching through the values of a single facet.”
   • [claimed-docs] “Filters, ranges, and refinements that turn a long list of results into the right answer.”
   • [community] “Tested Meilisearch recently, was a great experience, getting a multi-index search running in our frontend was very easy. Just wish they had …”

   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 to Meilisearch
   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

   Meilisearch✓fullclaimed8/10

   Meilisearch's docs explicitly describe tenant tokens as short-lived, scoped credentials that embed filters/search rules to restrict each user to their own data without needing separate indexes per tenant, directly matching the story (e.g., 'No need for separate indexes or infrastructure per customer', 'Each tenant gets isolated access through secure tokens'). This is a well-documented first-party feature analogous to Algolia secured keys / Postgres RLS. Missing for 10: independent/hands-on community verification specifically of tenant token security in production multi-tenant setups (community evidence covers performance/RAM/indexing issues, not this security feature).

   • [claimed-docs] “Tenant tokens are short-lived, scoped credentials generated from an API key. They embed search rules (filters) that automatically apply to e…”
   • [claimed-docs] “Tenant tokens are short-lived, scoped credentials generated from an API key. They embed search rules (filters) that automatically apply to e…”
   • [claimed-docs] “tenant tokens serve a similar purpose to Algolia's secured API keys or PostgreSQL's row-level security (RLS)”
   • [claimed-docs] “Tenant tokens... embed search rules (filters) that automatically apply to every search request, ensuring users only see their own data.”
   • [claimed-docs] “Tenant tokens restrict search results to a specific tenant. Documents are filtered at query time. No data ever crosses boundaries.”
   • [claimed-docs] “API keys authenticate requests, while tenant tokens restrict what data each user can see within a shared index.”
   • [claimed-docs] “Meilisearch handles multi-tenancy at the search level. Each tenant gets isolated access through secure tokens. No need for separate indexes …”

   proof ↗⚑ flag