Skip to content
ProductArena

Search Infrastructure Arena

Meilisearch vs Orama

Meilisearch logo

Meilisearch

Meili SAS

Arena29/100AGENT-READY57/100BUILT-IN AI21/100
MCP✓CLI—API✓
open-source21/100 integrity
Orama logo

Orama

OramaSearch Inc.

Arena27/100AGENT-READY41/100BUILT-IN AI33/100
MCP✓CLI—API~
open-source25/100 integrity

Meilisearch wins · 22–7 (22 drawn)

Agent search — stories about agent search in this arenaAgent search

Stories about agent search in this arena

Agent ops

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

    weight 3 · round to Meilisearch
    Meilisearchfullprobed8/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
    Oramapartialprobed6/10

    Orama's JS/TS (and Python/Rust) APIs clearly support end-to-end create→insert→search workflows (orama-docs-1,2,15,16,24,32), and Orama Cloud ships an auto-configured MCP server for interacting with project data from AI clients like Cursor (orama-docs-9,20,30, orama-probe-3), satisfying the 'no dashboard' requirement for search/query. However, there's no evidence of a CLI, and the MCP server's documented scope emphasizes querying/interacting with existing data rather than confirmed index-creation or document-insertion operations, and OpenAPI/REST API docs could not be located (orama-probe-2). Missing for 10: dedicated CLI tool, explicit confirmation MCP server supports index creation and document insertion (not just querying), and a public REST/OpenAPI spec.

    • [claimed-docs] “Since version `1.2.0`, Orama supports vector search.”
    • [claimed-docs] “insertion in Orama is quick and intuitive”
    • [claimed-docs] “We can create a new instance (from now on database) with an **indexing `schema`**.”
    • [claimed-docs] “Inserting a large number of documents in a loop could potentially block the event loop. Instead `insertMultiple` handles this case better.”
    • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
    • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
    • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other.”
    • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
    • [probe] “PROBE openapi: all candidate paths 404 (https://docs.orama.com/openapi.json, https://docs.orama.com/swagger.json, https://docs.orama.com/api…”
    • [claimed-docs] “Orama Cloud officially supports the following SDKs: - JavaScript/TypeScript - Python - Rust”
    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
    Meilisearchfullprobed8/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
    Oramafullprobed8/10

    Orama Cloud ships an official, automatically-configured MCP server per project that lets AI interfaces (ChatGPT, Cursor, etc.) interact with indexed data, confirmed both in docs and via a live probe of the docs page. Missing for 10: independent/hands-on evidence of the MCP server's tool surface covering analytics and index-management operations (docs emphasize query/interaction but don't detail full CRUD/analytics tool coverage), and no third-party confirmation of real-world usage.

    • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
    • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
    • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other.”
    • [probe] “PROBE llms.txt: HTTP 200 at https://docs.orama.com/llms.txt # Docs ## cloud - [Introduction to Orama Cloud](/docs/cloud): Run Orama at sca…”
    • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
    proof ↗⚑ flag

Agenticness — how well agents can access and operate the productAgenticness

How well agents can access and operate the product

Agent access

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

    weight 2 · round to Meilisearch
    Meilisearchfullprobed9/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
    Oramafullprobed8/10

    Orama has a live llms.txt (HTTP 200) plus a full llms-full.txt content reference, confirmed by direct probe, and docs are structured for agent consumption. missing for 10: no independent/third-party confirmation that agents actually consume this successfully, and no explicit agent-onboarding guide beyond the llms.txt file itself.

    • [probe] “PROBE llms.txt: HTTP 200 at https://docs.orama.com/llms.txt # Docs ## cloud - [Introduction to Orama Cloud](/docs/cloud): Run Orama at sca…”
    • [claimed-docs] “A data source identifies a specific set of documents, ideally coming from a single origin.”
    • [claimed-docs] “you can put data that will be updated frequently in a single data source (let's call it `docs`), and put data that follows a different updat…”
    • [claimed-docs] “A project is a set of **data sources** that you want to use for RAG, search, or any other method of retrieval.”
    proof ↗⚑ flag

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

    weight 2 · round drawn
    Meilisearchpartialclaimed6/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
    Oramapartialclaimed6/10

    Orama ships as a JS/TS (and Rust/Python SDK) library with programmatic insert/search APIs and no UI dependency, meaning it can be embedded and run headlessly in scripts, servers, or automation pipelines (e.g. orama-docs-2, orama-docs-15, orama-docs-21). However, there is no explicit documentation of CI-specific workflows, CLI tooling, or headless automation examples. Missing for 10: explicit CI/CD integration guides, a dedicated CLI for automation, and independent evidence of headless CI usage.

    • [claimed-docs] “insertion in Orama is quick and intuitive”
    • [claimed-docs] “We can create a new instance (from now on database) with an **indexing `schema`**.”
    • [claimed-docs] “Orama Cloud officially supports the following SDKs: - JavaScript/TypeScript - Python - Rust”
    • [claimed-docs] “If you have a lot of records, we suggest using the `insertMultiple` function”
    • [claimed-docs] “The open-source search library. Add fast, relevant search to your own application at no cost.”
    proof ↗⚑ flag

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

    weight 3 · round drawn
    Meilisearchfullprobed8/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
    Oramafullprobed8/10

    Orama Cloud ships an official, automatically-configured MCP server per project, documented and confirmed via probe, enabling agents like ChatGPT and Cursor to connect to project data. Missing for 10: independent/hands-on third-party corroboration beyond vendor docs and probe confirmation.

    • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
    • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
    • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other.”
    • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
    proof ↗⚑ flag

  4. ai-native userUse an official CLI

    weight 2 · round drawn
    Meilisearchnone0/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
    Oramanone0/10

    Evidence covers SDKs (JS/TS, Python, Rust), an MCP server, and search features, but there is no mention of an official CLI tool anywhere in the docs or GitHub evidence. Missing for 10: any documented CLI command/tool, installation instructions for a CLI, or CLI usage examples.

      ⚑ flag

    • ai-native userDrive the product through a documented public API

      weight 3 · round to Meilisearch
      Meilisearchfullprobed8/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
      Oramapartialprobed6/10

      Orama documents SDK APIs (JS/TS, Python, Rust), a documented MCP server for Orama Cloud, and llms.txt for AI consumption, showing a documented public API surface usable by AI-native workflows. However, a direct OpenAPI/REST spec probe returned 404 on all candidate paths, indicating no discoverable formal REST API spec despite SDK/MCP documentation. missing for 10: a public OpenAPI/REST spec, independent/hands-on confirmation of API usage by AI agents beyond docs, and details on API completeness for non-JS/Python/Rust clients.

      • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
      • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
      • [claimed-docs] “Orama Cloud officially supports the following SDKs: - JavaScript/TypeScript - Python - Rust”
      • [probe] “PROBE llms.txt: HTTP 200 at https://docs.orama.com/llms.txt # Docs ## cloud - [Introduction to Orama Cloud](/docs/cloud): Run Orama at sca…”
      • [probe] “PROBE openapi: all candidate paths 404 (https://docs.orama.com/openapi.json, https://docs.orama.com/swagger.json, https://docs.orama.com/api…”
      • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
      proof ↗⚑ flag

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

      weight 2 · round to Meilisearch
      Meilisearchfullclaimed7/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
      Oramanone0/10

      The evidence pack shows no mention of issuing scoped or least-privilege API keys/credentials for agents — only generic API key proxying (Secure Proxy) to hide a key client-side, which is not the same as granular credential scoping. Missing for 10: any documentation of role-based or scoped API key generation, permission scopes, or agent-specific credential issuance.

      • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website. It uses a free feature from Orama Cloud called **Secure…”
      proof ↗⚑ flag

    • ai-native userBuild against official SDKs

      weight 2 · round drawn
      Meilisearchfullcommunity8/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
      Oramafullprobed8/10

      Orama officially documents and supports SDKs for JavaScript/TypeScript, Python, and Rust for Orama Cloud, with APIs designed to closely mirror across Cloud and open-source, easing AI-native integration; it also ships an official MCP server for AI interface interoperability. missing for 10: independent/community verification of SDK quality beyond first-party docs, and no explicit versioned SDK changelog/compatibility matrix.

      • [claimed-docs] “Orama Cloud officially supports the following SDKs: - JavaScript/TypeScript - Python - Rust”
      • [claimed-docs] “The APIs are designed to be as close as possible to the **Orama Cloud** APIs, so you can easily migrate your projects from **Orama Cloud** t…”
      • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
      • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
      • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
      proof ↗⚑ flag

    • ai-native userSubscribe to events via webhooks

      weight 2 · round drawn
      Meilisearchnone0/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
        Oramanone0/10

        No evidence of webhook subscription support anywhere in the docs or probes; Orama's event-driven integration is limited to an MCP server and SDKs, not webhooks.

          ⚑ flag

        Agentic features

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

          weight 2 · round to Orama
          Meilisearchpartialclaimed4/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
          Oramafullclaimed7/10

          Orama's AnswerSession feature explicitly delivers ChatGPT-like AI-generated answers with sources drawn from the user's own indexed data, and Orama Cloud extends this with AI-powered NLP search and RAG-oriented data sources/projects, directly matching the ask for in-product AI-generated insights. Missing for 10: independent/hands-on validation of answer quality, and no explicit evidence of proactive 'suggestions' beyond Q&A-style answers.

          • [claimed-docs] “turns a question into a straight answer with the sources behind it”
          • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website. It uses a free feature from Orama Cloud called **Secure…”
          • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website.”
          • [claimed-docs] “we introduced a new feature called **AnswerSession** that allows you to perform ChatGPT-like experiences on your website.”
          • [claimed-docs] “With Orama 3.0, we introduced a new feature called AnswerSession that allows you to perform ChatGPT-like experiences on your website.”
          • [claimed-docs] “Full-text search - Vector search - Hybrid search - AI-powered NLP search”
          • [claimed-docs] “A project is a set of **data sources** that you want to use for RAG, search, or any other method of retrieval.”
          • [claimed-docs] “A project is a set of data sources that you want to use for RAG, search, or any other method of retrieval.”
          proof ↗⚑ flag

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

          weight 2 · round drawn
          Meilisearchnone0/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
          Oramanone0/10

          No evidence in the pack shows Orama offering scheduled tasks, triggers, or autonomous background automations; its documented features are search, indexing, vector/hybrid search, and an MCP server for interactive querying, not self-running automation workflows.

            ⚑ flag

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

            weight 3 · round drawn
            Meilisearchpartialprobed4/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
            Oramapartialclaimed4/10

            Orama's 'AnswerSession'/Answer Engine feature provides a built-in, ChatGPT-like conversational AI assistant embedded directly in the product for querying data and getting answers with sources, which is a form of an in-product AI assistant. However, this is limited to answering questions over indexed data (RAG-style Q&A) rather than true task delegation — there's no evidence of the assistant performing multi-step actions, automations, or agentic workflows on the user's behalf. Missing for 10: evidence of task execution/automation capabilities beyond Q&A, evidence of the assistant taking actions (not just answering), and independent/hands-on validation of the assistant's real-world behavior.

            • [claimed-docs] “allows you to perform ChatGPT-like experiences on your website”
            • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website. It uses a free feature from Orama Cloud called **Secure…”
            • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website.”
            • [claimed-docs] “we introduced a new feature called **AnswerSession** that allows you to perform ChatGPT-like experiences on your website.”
            • [claimed-docs] “With Orama 3.0, we introduced a new feature called AnswerSession that allows you to perform ChatGPT-like experiences on your website.”
            • [claimed-docs] “turns a question into a straight answer with the sources behind it”
            proof ↗⚑ flag

          • ai-native userOperate the product with natural-language commands

            weight 2 · round to Orama
            Meilisearchpartialprobed6/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
            Oramapartialprobed7/10

            Orama's AnswerSession lets end-users pose natural-language questions and get synthesized answers with sources (docs-6, docs-13, docs-18, docs-28, docs-35), and its MCP server exposes Orama Cloud project data to AI interfaces like ChatGPT and Cursor for natural-language interaction (docs-9, docs-20, docs-30, orama-probe-3). This covers natural-language querying/retrieval well, but there's no evidence of natural-language commands for administrative/configuration operations (schema creation, data source management, indexing) — those remain API/SDK driven. Missing for 10: evidence of NL-driven configuration or management actions beyond querying, and independent/hands-on confirmation of AnswerSession or MCP usage quality.

            • [claimed-docs] “allows you to perform ChatGPT-like experiences on your website”
            • [claimed-docs] “turns a question into a straight answer with the sources behind it”
            • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website. It uses a free feature from Orama Cloud called **Secure…”
            • [claimed-docs] “we introduced a new feature called **AnswerSession** that allows you to perform ChatGPT-like experiences on your website.”
            • [claimed-docs] “With Orama 3.0, we introduced a new feature called AnswerSession that allows you to perform ChatGPT-like experiences on your website.”
            • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
            • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
            • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other.”
            • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
            proof ↗⚑ flag

          Api quality

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

            weight 2 · round drawn
            Meilisearchnone0/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
            Oramanone0/10

            Evidence shows only static markdown documentation (create.mdx, insert.mdx, facets.mdx, etc.) with no mention of an interactive API reference or runnable code examples; a probe for OpenAPI/Swagger specs at docs.orama.com returned 404 on all candidate paths, indicating no interactive API explorer exists.

            • [probe] “PROBE openapi: all candidate paths 404 (https://docs.orama.com/openapi.json, https://docs.orama.com/swagger.json, https://docs.orama.com/api…”
            • [claimed-docs] “A data source identifies a specific set of documents, ideally coming from a single origin.”
            • [claimed-docs] “Orama Cloud officially supports the following SDKs: - JavaScript/TypeScript - Python - Rust”
            proof ↗⚑ flag

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

            weight 2 · round drawn
            Meilisearchnone0/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
            Oramanone0/10

            A direct probe found no OpenAPI/Swagger spec at any standard path (all 404s), and no documentation references a downloadable machine-readable API spec; only an llms.txt for docs discovery exists, which is not an API spec.

            • [probe] “PROBE openapi: all candidate paths 404 (https://docs.orama.com/openapi.json, https://docs.orama.com/swagger.json, https://docs.orama.com/api…”
            • [probe] “PROBE llms.txt: HTTP 200 at https://docs.orama.com/llms.txt # Docs ## cloud - [Introduction to Orama Cloud](/docs/cloud): Run Orama at sca…”
            proof ↗⚑ flag

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

            weight 1 · round to Meilisearch
            Meilisearchpartialclaimed4/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
            Oramanone0/10

            No evidence of a sandbox/staging environment or test mode separate from production data; docs cover search features, MCP server, and cloud deployment but nothing about sandbox testing isolation.

              ⚑ flag

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

              weight 2 · round drawn
              Meilisearchnone0/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
                Oramanone0/10

                No evidence of API versioning scheme or a documented deprecation policy; version mentions (e.g., 1.2.0, 3.0) refer to product/feature releases, not API contract versioning. The OpenAPI probe even returned 404s, and no changelog or deprecation policy page is cited. Missing for 10: versioned API endpoints/spec, explicit deprecation policy/timeline documentation, changelog with breaking-change notices.

                • [probe] “PROBE openapi: all candidate paths 404 (https://docs.orama.com/openapi.json, https://docs.orama.com/swagger.json, https://docs.orama.com/api…”
                • [claimed-docs] “Since version `1.2.0`, Orama supports vector search.”
                proof ↗⚑ flag

              Ai search — stories about ai search in this arenaAi search

              Stories about ai search in this arena

              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
                Meilisearchfullclaimed8/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
                Oramapartialclaimed6/10

                Orama's official `plugin-embeddings` generates embeddings for documents automatically at insert and search time, letting developers add vector/hybrid search without building their own embedding pipeline [orama-docs-7], and Orama Cloud's Secure Proxy/AnswerSession similarly proxies embedding/LLM calls so API keys aren't exposed client-side [orama-docs-18]. However, the docs don't detail a fully built-in default embedder independent of an external provider (e.g., OpenAI) or give hands-on/independent proof of zero-setup vectorization. Missing for 10: details on a truly self-contained default embedding model vs. reliance on third-party API keys, and independent corroboration of the plugin's real-world use.

                • [claimed-docs] “This plugin generates embeddings for your documents at insert and search time, allowing you to perform vector and hybrid searches on your do…”
                • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website. It uses a free feature from Orama Cloud called **Secure…”
                • [claimed-docs] “Hybrid search is an Orama feature that allows you to perform full-text and vector search in one unique query, combining the results to get t…”
                • [claimed-docs] “Being a vector database, Orama allows you to perform vector search natively.”
                proof ↗⚑ flag

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

                weight 3 · round drawn
                Meilisearchfullclaimed9/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
                Oramafullclaimed9/10

                Orama's docs explicitly describe hybrid search as combining full-text and vector search in one unique query, and this is corroborated in both the OSS library (GitHub feature list) and Orama Cloud docs. missing for 10: independent hands-on benchmark or third-party validation of fusion quality/performance.

                • [claimed-docs] “Hybrid search is an Orama feature that allows you to perform full-text and vector search in one unique query, combining the results to get t…”
                • [claimed-docs] “Full-text search - Vector search - Hybrid search - AI-powered NLP search”
                • [github] “Full-Text search... Vector Search... Hybrid Search... Search Filters... Geosearch... Pinning Rules (Merchandising)... Facets... Typo Toleran…”
                • [claimed-docs] “This plugin generates embeddings for your documents at insert and search time, allowing you to perform vector and hybrid searches on your do…”
                proof ↗⚑ flag

              Rag

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

                weight 1 · round to Orama
                Meilisearchpartialclaimed6/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
                Oramafullprobed8/10

                Orama documents an AnswerSession API for ChatGPT-like conversational answers with sources, built on vector/hybrid search and Secure Proxy to OpenAI, plus Orama Cloud's data-source/project model explicitly framed for RAG and retrieval, and a documented MCP server for AI interface integration. Missing for 10: no independent/hands-on corroboration of RAG output quality and no formal OpenAPI/answer-API reference spec (openapi probe 404s).

                • [claimed-docs] “allows you to perform ChatGPT-like experiences on your website”
                • [claimed-docs] “turns a question into a straight answer with the sources behind it”
                • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website. It uses a free feature from Orama Cloud called **Secure…”
                • [claimed-docs] “AnswerSession** that allows you to perform ChatGPT-like experiences on your website.”
                • [claimed-docs] “we introduced a new feature called **AnswerSession** that allows you to perform ChatGPT-like experiences on your website.”
                • [claimed-docs] “A project is a set of **data sources** that you want to use for RAG, search, or any other method of retrieval.”
                • [claimed-docs] “A project is a set of data sources that you want to use for RAG, search, or any other method of retrieval.”
                • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
                • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
                • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
                proof ↗⚑ flag

              Automation depth — how much of the product can run unattendedAutomation depth

              How much of the product can run unattended

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

                weight 2 · round drawn
                Meilisearchpartialcommunity5/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
                Oramapartialclaimed5/10

                Orama documents `insertMultiple` explicitly for bulk-inserting large numbers of documents without blocking the event loop, which directly supports bulk operations for insertion. However, evidence does not show bulk update/delete operations or batch query/search operations across many items, so the story is only partially covered. Missing for 10: bulk update/delete APIs, batch search/query operations, and independent/hands-on verification of insertMultiple performance at scale.

                • [claimed-docs] “Inserting a large number of documents in a loop could potentially block the event loop. Instead `insertMultiple` handles this case better.”
                • [claimed-docs] “If you have a lot of records, we suggest using the `insertMultiple` function”
                • [claimed-docs] “Instead insertMultiple handles this case better.”
                proof ↗⚑ flag

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

                weight 3 · round drawn
                Meilisearchnone0/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
                Oramanone0/10

                Orama's evidence covers search, vector/hybrid search, facets, and an MCP server for AI interfaces, but nothing describes a rules/automation engine that triggers actions on events. The closest feature, 'Pinning Rules (Merchandising),' only affects search result ranking for specific queries, not general event-triggered automation. Missing for 10: any documentation of event listeners, triggers, webhooks, or conditional automation logic tied to data or search events.

                • [github] “Pinning Rules (Merchandising)”
                • [github] “Full-Text search... Vector Search... Hybrid Search... Search Filters... Geosearch... Pinning Rules (Merchandising)... Facets... Typo Toleran…”
                proof ↗⚑ flag

              3. ai-native userSchedule recurring jobs or workflows

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

                  Developer experience — stories about developer experience in this arenaDeveloper experience

                  Stories about developer experience in this arena

                  Onboarding

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

                    weight 3 · round to Orama
                    Meilisearchdisputedcontradicted6/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
                    Oramapartialclaimed6/10

                    Docs cover creating an instance with a schema, inserting documents (including insertMultiple for bulk), and running searches with filters/facets, which together map to a quickstart flow, but there is no single consolidated 'quickstart' walkthrough or independent hands-on confirmation of the end-to-end time-to-first-search experience. missing for 10: a dedicated quickstart guide/tutorial artifact, and independent/hands-on evidence confirming ease/time-to-first-search.

                    • [claimed-docs] “We can create a new instance (from now on database) with an **indexing `schema`**.”
                    • [claimed-docs] “Orama supports the following types: | Type | Description | Example | | ---------------- | ------------------------------------------------ |…”
                    • [claimed-docs] “The schema represents the searchable properties of the document to be inserted.”
                    • [claimed-docs] “insertion in Orama is quick and intuitive”
                    • [claimed-docs] “Inserting a large number of documents in a loop could potentially block the event loop. Instead `insertMultiple` handles this case better.”
                    • [claimed-docs] “If you have a lot of records, we suggest using the `insertMultiple` function”
                    • [claimed-docs] “users can filter their search results by various criteria, such as category, price range, or other attributes”
                    • [claimed-docs] “Facets are a powerful tool for filtering and narrowing down search results on the Orama search engine.”
                    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 Orama
                    Meilisearchdisputedcontradicted6/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
                    Oramapartialclaimed4/10

                    Orama Cloud officially supports only JavaScript/TypeScript, Python, and Rust SDKs; there is no evidence of official PHP, Ruby, or Go SDKs, nor of active maintenance/currency across all these languages. Missing for 10: PHP, Ruby, Go SDK evidence, and documentation of update cadence/parity across all listed languages.

                    • [claimed-docs] “Orama Cloud officially supports the following SDKs: - JavaScript/TypeScript - Python - Rust”
                    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 Meilisearch
                    Meilisearchpartialclaimed6/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
                    Oramanone0/10

                    The evidence pack covers Orama's search engine capabilities (facets, filters, vector/hybrid search, schema, insertion) and cloud/MCP integration, but contains no mention of any official prebuilt UI components (search box, results list, facet widgets, pagination) that a developer could assemble into a search interface. Missing for 10: any citation of a UI component library, widget, or pagination component from Orama.

                      ⚑ flag

                    Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines

                    Stories about indexing pipelines in this arena

                    Connectors

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

                      weight 1 · round to Meilisearch
                      Meilisearchpartialclaimed4/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
                      Oramapartialclaimed3/10

                      Orama Cloud documentation describes a 'data source' abstraction for ingesting sets of documents (implying some built-in ingestion mechanism beyond manual SDK calls), but the evidence pack never names an official crawler, sitemap importer, or specific third-party connectors (e.g., web crawler, CMS, Elasticsearch, etc.). The open-source library's actual indexing API (insert/insertMultiple) is manual, not connector-based. Missing for 10: explicit documentation of a website crawler or named connector integrations, hands-on/independent confirmation of connector usage.

                      • [claimed-docs] “A data source identifies a specific set of documents, ideally coming from a single origin.”
                      • [claimed-docs] “you can put data that will be updated frequently in a single data source (let's call it `docs`), and put data that follows a different updat…”
                      • [claimed-docs] “A project is a set of **data sources** that you want to use for RAG, search, or any other method of retrieval.”
                      • [claimed-docs] “A project is a set of data sources that you want to use for RAG, search, or any other method of retrieval.”
                      • [claimed-docs] “Inserting a large number of documents in a loop could potentially block the event loop. Instead `insertMultiple` handles this case better.”
                      • [claimed-docs] “If you have a lot of records, we suggest using the `insertMultiple` function”
                      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
                      Meilisearchpartialcommunity6/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
                      Oramapartialclaimed3/10

                      Orama's docs confirm a bulk-insert API (`insertMultiple`) recommended for large record counts, addressing the 'bulk import' half of the story, but there is no evidence of any async task/job tracking mechanism, status polling, or completion notification for indexing jobs, nor any documented performance/scale claims for millions of documents. missing for 10: async task/job ID tracking, indexing-completion signals, and millions-scale benchmarks or documentation.

                      • [claimed-docs] “Inserting a large number of documents in a loop could potentially block the event loop. Instead `insertMultiple` handles this case better.”
                      • [claimed-docs] “If you have a lot of records, we suggest using the `insertMultiple` function”
                      • [claimed-docs] “Instead insertMultiple handles this case better.”
                      proof ↗⚑ flag

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

                      weight 2 · round to Orama
                      Meilisearchdisputedcontradicted5/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
                      Oramapartialclaimed5/10

                      Orama documents insert/insertMultiple for adding documents and mentions data sources that can be updated frequently, implying documents become searchable quickly since it's an in-memory/JS index, but there is no explicit documentation of update/delete APIs, real-time reindex latency, or confirmation that deletes are reflected without a full reindex. missing for 10: explicit update/delete document API docs, evidence of near-real-time index refresh after writes, and any performance/latency data or independent confirmation of incremental indexing without full reindex.

                      • [claimed-docs] “insertion in Orama is quick and intuitive”
                      • [claimed-docs] “Inserting a large number of documents in a loop could potentially block the event loop. Instead `insertMultiple` handles this case better.”
                      • [claimed-docs] “If you have a lot of records, we suggest using the `insertMultiple` function”
                      • [claimed-docs] “you can put data that will be updated frequently in a single data source (let's call it `docs`), and put data that follows a different updat…”
                      • [claimed-docs] “A data source identifies a specific set of documents, ideally coming from a single origin.”
                      proof ↗⚑ flag

                    Openness — open source, data portability, and self-hosting storiesOpenness

                    Open source, data portability, and self-hosting stories

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

                      weight 2 · round to Meilisearch
                      Meilisearchpartialprobed6/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
                      Oramapartialprobed5/10

                      Orama's core search/insert/facet/vector/hybrid features are all exposed via JS SDK APIs and Orama Cloud APIs, and Cloud also ships an MCP server for AI interfaces, suggesting broad API parity with UI features. However, there is no discoverable OpenAPI spec (probe found 404s across candidate paths), and no evidence explicitly confirming that every UI-configurable capability (e.g., Cloud dashboard settings, on-premise deployment configuration, answer-engine/AnswerSession setup) has a fully documented API equivalent. missing for 10: a published OpenAPI/API reference proving full UI-API parity, explicit confirmation that all dashboard/UI-only settings are API-configurable, and independent/hands-on verification of API completeness.

                      • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
                      • [claimed-docs] “The APIs are designed to be as close as possible to the **Orama Cloud** APIs, so you can easily migrate your projects from **Orama Cloud** t…”
                      • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
                      • [claimed-docs] “Orama Cloud officially supports the following SDKs: - JavaScript/TypeScript - Python - Rust”
                      • [claimed-docs] “so you can easily migrate your projects from **Orama Cloud** to **Orama Open Source** and vice-versa”
                      • [probe] “PROBE openapi: all candidate paths 404 (https://docs.orama.com/openapi.json, https://docs.orama.com/swagger.json, https://docs.orama.com/api…”
                      • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
                      proof ↗⚑ flag

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

                      weight 3 · round drawn
                      Meilisearchnone0/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
                      Oramanone0/10

                      The evidence pack never documents an explicit data-export or persistence feature (no mention of exporting indexes/documents to JSON, CSV, or any open format); only vague notes about migrating between Orama Cloud and Orama OSS APIs (orama-docs-19/29) exist, which is not the same as user-initiated data export. Since Orama is a data-handling search/AI platform, this axis is fair to ask, but no evidence shows the capability being delivered.

                      • [claimed-docs] “The APIs are designed to be as close as possible to the **Orama Cloud** APIs, so you can easily migrate your projects from **Orama Cloud** t…”
                      • [claimed-docs] “so you can easily migrate your projects from **Orama Cloud** to **Orama Open Source** and vice-versa”
                      proof ↗⚑ flag

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

                      weight 2 · round to Orama
                      Meilisearchnone0/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
                        Oramafullclaimed7/10

                        Orama explicitly markets itself as 'the open-source search library' and maintains a public GitHub repository (oramasearch/orama) showcasing its full feature set, confirming the core engine's source is publicly available for inspection. Missing for 10: explicit citation of the specific open-source license (e.g., Apache-2.0/MIT) and independent third-party confirmation of license terms.

                        • [claimed-docs] “The open-source search library. Add fast, relevant search to your own application at no cost.”
                        • [github] “Stemming and tokenization in 30 languages”
                        • [github] “Full-Text search... Vector Search... Hybrid Search... Search Filters... Geosearch... Pinning Rules (Merchandising)... Facets... Typo Toleran…”
                        proof ↗⚑ flag

                      • ai-native userSelf-host the core product

                        weight 3 · round to Meilisearch
                        Meilisearchfullcommunity9/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
                        Oramafullclaimed7/10

                        Orama's core search library is explicitly open-source and free to self-host (orama-docs-12), and even the Cloud/RAG offering provides on-premise deployment of the context server on your own infrastructure (orama-docs-8), directly satisfying the self-hosting story for an AI-native user. Missing for 10: detailed self-hosting/deployment documentation (Docker/K8s instructions) and independent hands-on confirmation of a successful self-hosted setup.

                        • [claimed-docs] “The open-source search library. Add fast, relevant search to your own application at no cost.”
                        • [claimed-docs] “We offer on-premise support for Orama Cloud, allowing you to deploy the context server on your own infrastructure.”
                        • [claimed-docs] “The APIs are designed to be as close as possible to the **Orama Cloud** APIs, so you can easily migrate your projects from **Orama Cloud** t…”
                        proof ↗⚑ flag

                      Operations scale — stories about operations scale in this arenaOperations scale

                      Stories about operations scale in this arena

                      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 Meilisearch
                        Meilisearchpartialclaimed6/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
                        Oramanone0/10

                        Evidence covers search features (full-text, vector, hybrid, facets, MCP server) but no mention of built-in analytics dashboards for top queries, no-result queries, or click-through tracking. missing for 10: analytics dashboard docs, no-result query tracking, click-through rate reporting, any founder-facing insights UI.

                          ⚑ 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
                          Meilisearchpartialcommunity4/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
                          Oramanone0/10

                          No evidence pack items describe clustering, replication, or high-availability architecture, nor any documented path from prototype-scale to hundreds of millions of documents; Orama Cloud is described only as 'managed at scale' and offers on-premise deployment, but no operational scaling/HA/clustering documentation is present.

                          • [claimed-docs] “We offer on-premise support for Orama Cloud, allowing you to deploy the context server on your own infrastructure.”
                          • [probe] “PROBE llms.txt: HTTP 200 at https://docs.orama.com/llms.txt # Docs ## cloud - [Introduction to Orama Cloud](/docs/cloud): Run Orama at sca…”
                          proof ↗⚑ flag

                        Self host

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

                          weight 3 · round drawn
                          Meilisearchpartialcommunity6/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
                          Oramapartialclaimed6/10

                          Orama ships a free open-source library that can be self-hosted (orama-docs-12) and also explicitly offers on-premise deployment of the 'context server' for Orama Cloud (orama-docs-8), and notes its OSS APIs are designed to closely mirror Cloud APIs for easy migration (orama-docs-19/29). However, the docs never claim full feature parity — the OSS/self-host path and the on-prem 'context server' appear to be distinct offerings, and Cloud-specific capabilities (hosted MCP server, managed SDpossible, Secure Proxy for AnswerSession, project/data-source management) are not shown as available in the self-hosted engine. Missing for 10: explicit statement/documentation that all hosted-product features (MCP server, Secure Proxy, managed data-source pipeline, SDKs) are available in the self-hosted deployment, and independent/hands-on confirmation of feature parity.

                          • [claimed-docs] “We offer on-premise support for Orama Cloud, allowing you to deploy the context server on your own infrastructure.”
                          • [claimed-docs] “The open-source search library. Add fast, relevant search to your own application at no cost.”
                          • [claimed-docs] “The APIs are designed to be as close as possible to the **Orama Cloud** APIs, so you can easily migrate your projects from **Orama Cloud** t…”
                          • [claimed-docs] “so you can easily migrate your projects from **Orama Cloud** to **Orama Open Source** and vice-versa”
                          proof ↗⚑ flag

                        Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans

                        Plan structure and value — what each tier costs and what it unlocks

                        Pricing

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

                          weight 2 · round to Meilisearch
                          Meilisearchdisputedcontradicted3/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
                          Oramanone0/10

                          The evidence pack contains no pricing tiers, usage-based cost details, or discussion of per-request billing/predictability beyond the fact that the open-source library is free; there is no documentation of Orama Cloud's paid pricing structure or how costs scale with records/query volume. missing for 10: Orama Cloud pricing tiers, usage-based billing details, any statement about cost predictability at scale.

                          • [claimed-docs] “The open-source search library. Add fast, relevant search to your own application at no cost.”
                          proof ↗⚑ flag

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

                          weight 3 · round drawn
                          Meilisearchnone0/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
                          Oramanone0/10

                          The only pricing-related evidence is a single line noting the open-source library is free; there is no evidence of published per-unit pricing (e.g., cost per search, per record, or per node) for Orama Cloud that would let a founder predict costs before committing. Missing for 10: any documented pricing tiers, unit costs, or usage-based pricing calculator for Orama Cloud.

                          • [claimed-docs] “The open-source search library. Add fast, relevant search to your own application at no cost.”
                          proof ↗⚑ flag

                        Privacy posture — data-handling and privacy storiesPrivacy posture

                        Data-handling and privacy stories

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

                          weight 2 · round to Meilisearch
                          Meilisearchpartialcommunity6/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
                          Oramapartialclaimed5/10

                          Orama Cloud offers on-premise deployment, letting customers host the context server on their own infrastructure, and the open-source library can be self-hosted anywhere — both effectively let a user control data location. However there is no evidence of a formal multi-region selection feature (e.g., choosing EU/US Orama Cloud regions) or documented data-residency guarantees for the hosted Cloud offering. missing for 10: explicit region-selection UI/API for Orama Cloud, documented data residency/compliance certifications, independent confirmation of self-hosting meeting residency requirements.

                          • [claimed-docs] “We offer on-premise support for Orama Cloud, allowing you to deploy the context server on your own infrastructure.”
                          • [claimed-docs] “The open-source search library. Add fast, relevant search to your own application at no cost.”
                          proof ↗⚑ flag

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

                          weight 3 · round drawn
                          Meilisearchnone0/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
                            Oramanone0/10

                            The evidence pack covers Orama's search/vector/AI features and cloud/MCP capabilities but contains no explicit statement, policy, or documentation about preventing user data from being used to train AI models (e.g., no data-usage/training opt-out policy, no statement about third-party model providers not retaining data for training). On-premise deployment (orama-docs-8) hints at data control but does not address AI-training usage specifically.

                              ⚑ flag

                            • ai-native userControl data retention and deletion

                              weight 2 · round drawn
                              Meilisearchnone0/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
                              Oramanone0/10

                              No evidence in the pack addresses data retention policies, deletion controls, TTL/data lifecycle, or user-initiated deletion of indexed/embedded data; the docs cover search, indexing, and MCP features but say nothing about retention/deletion controls.

                                ⚑ flag

                              • ai-native userOpt out of telemetry and usage tracking

                                weight 2 · round drawn
                                Meilisearchnone0/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
                                Oramanone0/10

                                No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for Orama's open-source library or Cloud offering; this is an applicable axis for any AI-native tool but the pack provides no documentation of a telemetry policy or opt-out flag.

                                  ⚑ flag

                                Relevance tuning — stories about relevance tuning in this arenaRelevance tuning

                                Stories about relevance tuning in this arena

                                Curation

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

                                  weight 2 · round to Meilisearch
                                  Meilisearchfullclaimed8/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
                                  Oramapartialclaimed5/10

                                  Orama's GitHub README explicitly lists 'Pinning Rules (Merchandising)' as a feature, directly supporting query-specific result pinning/curation, but no evidence pack item documents synonym definition or explicit boost/hide controls beyond the general 'merchandising' label. missing for 10: synonym dictionary/configuration docs, explicit boost and hide mechanisms, and any hands-on or independent confirmation of pinning behavior in practice.

                                  • [github] “Pinning Rules (Merchandising)”
                                  • [github] “Full-Text search... Vector Search... Hybrid Search... Search Filters... Geosearch... Pinning Rules (Merchandising)... Facets... Typo Toleran…”
                                  proof ↗⚑ flag

                                Ranking

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

                                  weight 2 · round to Meilisearch
                                  Meilisearchfullclaimed8/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
                                  Oramapartialclaimed5/10

                                  Orama exposes 'Pinning Rules (Merchandising)' for boosting specific results and search filters/facets that can approximate business-signal filtering, but there is no documented support for custom ranking formulas incorporating popularity, recency, or margin as scoring signals beyond textual relevance. missing for 10: documented custom scoring/boost-by-field (e.g. recency decay, popularity weighting, margin-based ranking), configurable ranking function API, and evidence of combining multiple business signals into the relevance score.

                                  • [github] “Full-Text search... Vector Search... Hybrid Search... Search Filters... Geosearch... Pinning Rules (Merchandising)... Facets... Typo Toleran…”
                                  • [github] “Pinning Rules (Merchandising)”
                                  • [claimed-docs] “users can filter their search results by various criteria, such as category, price range, or other attributes”
                                  • [claimed-docs] “Facets are a powerful tool for filtering and narrowing down search results on the Orama search engine.”
                                  proof ↗⚑ flag

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

                                  weight 1 · round drawn
                                  Meilisearchnone0/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
                                  Oramanone0/10

                                  No evidence of score/relevance explanation, ranking debug tools, or explain-style APIs; documentation covers search features (facets, hybrid, vector) and algorithm selection but nothing about inspecting or explaining why a document ranked where it did. Missing for 10: score breakdown/explain API, ranking debug docs, any transparency into scoring internals.

                                  • [claimed-docs] “Orama Cloud gives you the flexibility to choose the search algorithm that best suits your needs.”
                                  • [claimed-docs] “Full-text search - Vector search - Hybrid search - AI-powered NLP search”
                                  proof ↗⚑ flag

                                Search experience — stories about search experience in this arenaSearch experience

                                Stories about search experience in this arena

                                Experience

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

                                  weight 2 · round to Meilisearch
                                  Meilisearchpartialclaimed5/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
                                  Oramanone0/10

                                  The evidence pack covers full-text/vector/hybrid search, facets, filters, and an AI answer engine, but nowhere mentions autocomplete, typeahead, or query-suggestion features driven by search traffic or a dedicated suggestions index.

                                    ⚑ flag

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

                                    weight 3 · round to Meilisearch
                                    Meilisearchfullcommunity8/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
                                    Oramapartialclaimed5/10

                                    Orama is documented as a fast, in-memory full-text search engine ('fast, relevant search', 'insertion is quick and intuitive') suitable for real-time query use cases, but the evidence never explicitly describes an as-you-type UI pattern or cites millisecond-level latency benchmarks. missing for 10: explicit as-you-type/keystroke-search documentation, published latency/benchmark numbers, hands-on confirmation of instant search UX.

                                    • [claimed-docs] “The open-source search library. Add fast, relevant search to your own application at no cost.”
                                    • [claimed-docs] “insertion in Orama is quick and intuitive”
                                    • [github] “Full-Text search... Vector Search... Hybrid Search... Search Filters... Geosearch... Pinning Rules (Merchandising)... Facets... Typo Toleran…”
                                    proof ↗⚑ flag

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

                                    weight 3 · round to Meilisearch
                                    Meilisearchfullcommunity8/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
                                    Oramapartialclaimed4/10

                                    GitHub feature list explicitly confirms Orama ships 'Typo Tolerance' out of the box, but no evidence details how it can be tuned (e.g., threshold, per-field settings, exact-match toggles). missing for 10: documentation on configurable tolerance levels, per-field fuzzy rules, and independent confirmation of tuning behavior.

                                    • [github] “Full-Text search... Vector Search... Hybrid Search... Search Filters... Geosearch... Pinning Rules (Merchandising)... Facets... Typo Toleran…”
                                    • [github] “Typo Tolerance”
                                    proof ↗⚑ flag

                                  Filtering

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

                                    weight 2 · round to Meilisearch
                                    Meilisearchfullcommunity9/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
                                    Oramafullclaimed8/10

                                    Orama's docs explicitly describe a dedicated Faceted Search API that generates facets at search-time based on schema, supporting filtering by category, price range, and other attributes in a single query (orama-docs-3, orama-docs-17, orama-docs-27, orama-docs-34), and this is listed as a core engine feature alongside filters/facets in the GitHub feature list (orama-gh-2). Missing for 10: explicit documentation/example showing live counts per facet value returned in the same response, and independent/hands-on corroboration beyond first-party docs.

                                    • [claimed-docs] “users can filter their search results by various criteria, such as category, price range, or other attributes”
                                    • [claimed-docs] “Orama will be able to generate facets at search-time based on the schema.”
                                    • [claimed-docs] “Facets are a powerful tool for filtering and narrowing down search results on the Orama search engine.”
                                    • [claimed-docs] “the Orama Faceted Search API is the perfect solution for adding faceted search functionality to your project”
                                    • [github] “Full-Text search... Vector Search... Hybrid Search... Search Filters... Geosearch... Pinning Rules (Merchandising)... Facets... Typo Toleran…”
                                    proof ↗⚑ flag

                                  Security multitenancy — stories about security multitenancy in this arenaSecurity multitenancy

                                  Stories about security multitenancy in this arena

                                  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
                                    Meilisearchfullclaimed8/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
                                    Oramanone0/10

                                    No evidence describes scoped/tenant-specific API keys or per-user document restriction; documentation covers filters, facets, and data sources but nothing about restricting an individual end user's search to only their own documents without separate indexes. Missing for 10: any mention of tenant/user-scoped tokens, per-user document access control, or multitenancy security guarantees.

                                      ⚑ flag

                                    Not comparable on these axes

                                    1. ai-native userPlug MCP servers into this product so it can use their tools

                                      weight 3 · not comparable
                                      Meilisearchn/a

                                      Meilisearch is a search/database backend, not an AI agent or assistant that itself consumes MCP tools; the evidence shows the reverse relationship — Meilisearch ships an official MCP *server* so AI clients (e.g., Claude) can call ITS search tools (meilisearch-docs-13, meilisearch-docs-57, meilisearch-probe-4), not that Meilisearch plugs in external MCP servers to gain their tools. Acting as an MCP client/host is outside this product's category.

                                      • [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
                                      Oraman/a

                                      Orama is a search/vector database and RAG data platform whose AI-facing integration is to expose its own data as an MCP *server* for other AI tools (ChatGPT, Cursor) to consume — the reverse of the story, which asks whether the product itself can plug in and use external MCP servers' tools. There is no evidence Orama acts as an MCP client, and its product category (search infrastructure, not an agent) makes 'consuming other tools via MCP' a mismatched axis rather than a gap.

                                      • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other”
                                      • [claimed-docs] “Every Orama Cloud project comes with an MCP server that is automatically configured to interact with your project's data.”
                                      • [claimed-docs] “you'll be able to interact with your data from different AI interfaces, including ChatGPT, Cursor, and many other.”
                                      • [probe] “official MCP server documented at https://docs.orama.com/docs/cloud/mcp-server”
                                      proof ↗⚑ flag

                                    2. ai-native userVersion, review, and roll back my automations

                                      weight 1 · not comparable
                                      Meilisearchn/a

                                      Meilisearch is a search engine/database product, not an automation/workflow tool; there is no concept of 'automations' to version, review, or roll back. This story targets automation platforms and does not apply to this product's category.

                                        ⚑ flag
                                        Oraman/a

                                        Orama is a search/vector database and RAG/answer engine product, not an automation/workflow tool; versioning, reviewing, and rolling back 'automations' is not a concept that applies to its category.

                                          ⚑ flag