Typesense vs Orama

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 Typesense
   Typesense~partialprobed7/10

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

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

   proof ↗⚑ flag

   Orama~partialprobed6/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 to Orama
   Typesense✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Orama✓fullprobed8/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

Agent access

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

   weight 2 · round drawn
   Typesense✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Orama✓fullprobed8/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
   Typesense~partialprobed6/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed6/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 to Orama
   Typesense~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Orama✓fullprobed8/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
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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

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

   weight 3 · round to Typesense
   Typesense✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Orama~partialprobed6/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

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

   weight 2 · round drawn
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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

7. ai-native userBuild against official SDKs

   weight 2 · round to Orama
   Typesense—none0/10

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

   ⚑ flag

   Orama✓fullprobed8/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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Typesense—none0/10

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

   ⚑ flag

   Orama—none0/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
   Typesense~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Orama✓fullclaimed7/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
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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

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

   weight 3 · round to Orama
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed4/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

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

   weight 2 · round to Typesense
   Typesense✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Orama~partialprobed7/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
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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 drawn
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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

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

   weight 2 · round drawn
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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

Hybrid

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

   weight 2 · round to Typesense
   Typesense~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed6/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 to Orama
   Typesense✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Orama✓fullclaimed9/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
   Typesense~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Orama✓fullprobed8/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

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

   weight 2 · round to Typesense
   Typesense~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed5/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 to Typesense
   Typesense~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Orama—none0/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
   Typesense—none0/10

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

   ⚑ flag

   Orama—none0/10

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

   ⚑ flag

Onboarding

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

   weight 3 · round to Typesense
   Typesense✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed6/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
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed4/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 Typesense
   Typesense~partialclaimed5/10

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

   • [claimed-docs] “Search UI Components”

   proof ↗⚑ flag

   Orama—none0/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

Connectors

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

   weight 1 · round to Orama
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed3/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 Typesense
   Typesense~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed3/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
   Typesense~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed5/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

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

   weight 2 · round to Typesense
   Typesense~partialprobed6/10

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

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

   proof ↗⚑ flag

   Orama~partialprobed5/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 to Typesense
   Typesense~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Orama—none0/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 Typesense
   Typesense✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Orama✓fullclaimed7/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

4. ai-native userSelf-host the core product

   weight 3 · round to Typesense
   Typesense✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   Orama✓fullclaimed7/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

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 drawn
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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 Typesense
   Typesense~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Orama—none0/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 to Typesense
   Typesense✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed6/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

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

   weight 2 · round to Typesense
   Typesense~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Orama—none0/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 to Typesense
   Typesense~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Orama—none0/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

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

   weight 2 · round to Typesense
   Typesense~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed5/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 userControl data retention and deletion

   weight 2 · round drawn
   Typesense—none0/10

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

   ⚑ flag

   Orama—none0/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

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

   weight 2 · round drawn
   Typesense—none0/10

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

   ⚑ flag

   Orama—none0/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

Curation

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

   weight 2 · round to Typesense
   Typesense✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed5/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 Typesense
   Typesense✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed5/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 to Typesense
   Typesense~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Orama—none0/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

Experience

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

   weight 2 · round drawn
   Typesense—none0/10

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

   ⚑ flag

   Orama—none0/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

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

   weight 3 · round to Typesense
   Typesense✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed5/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

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

   weight 3 · round to Typesense
   Typesense✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Orama~partialclaimed4/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 Orama
   Typesense✓fullcommunity7/10

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

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

   proof ↗⚑ flag

   Orama✓fullclaimed8/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

Tenancy

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

   weight 2 · round drawn
   Typesense—none0/10

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

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

   proof ↗⚑ flag

   Orama—none0/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