Weaviate vs Milvus

Agent access

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

   weight 2 · round drawn
   Weaviate✓fullprobed9/10

   A probe confirms Weaviate hosts a working llms.txt at docs.weaviate.io/llms.txt returning HTTP 200 with structured summary content, and Weaviate also documents an official MCP server for agent/IDE integration, directly supporting agent-oriented docs consumption. Missing for 10: independent third-party confirmation that agents actually consume and act on this llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.weaviate.io/llms.txt # Weaviate ## TL;DR Weaviate is an open-source vector database (Go) that sto…”
   • [probe] “official MCP server documented at https://github.com/weaviate/mcp-server-weaviate”
   • [claimed-docs] “Enable and configure the Weaviate MCP server so LLMs and IDE assistants can interact with your Weaviate instance.”

   proof ↗⚑ flag

   Milvus✓fullprobed9/10

   A probe confirms Milvus hosts a working llms.txt at https://milvus.io/llms.txt (HTTP 200) with a proper agent-oriented summary, directly satisfying the story of pointing an agent at llms.txt. Missing for 10: no independent/community corroboration of agents actually consuming this file in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://milvus.io/llms.txt # Milvus > Milvus is an open-source, high-performance vector database designed for s…”

   proof ↗⚑ flag

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

   weight 2 · round to Milvus
   Weaviate~partialclaimed6/10

   Weaviate ships as a headless server deployable via Docker/Kubernetes with official client libraries (Python, JS, Go, Java) for programmatic access, which supports scripted/CI automation (weaviate-gh-2, weaviate-gh-3, weaviate-docs-21). However, there is no explicit documentation or example of running Weaviate specifically within a CI pipeline or automated test/deploy workflow. Missing for 10: explicit CI/CD integration guides, non-interactive automation examples, and independent confirmation of headless CI usage.

   • [github] “You can easily start Weaviate and a local vector embedding model with Docker.”
   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”
   • [claimed-docs] “Follow the instructions below to install one of the official client libraries, available in Python, JavaScript/TypeScript, Go, and Java.”

   proof ↗⚑ flag

   Milvus✓fullclaimed7/10

   Milvus is API/SDK-driven (pymilvus MilvusClient) and documented to run identically as Milvus Lite, Standalone in Docker, or Distributed on Kubernetes with the same client code, which is inherently headless and scriptable for CI/automation pipelines. Missing for 10: explicit CI/CD pipeline examples, GitHub Actions/test automation docs, or independent reports confirming headless CI usage in practice.

   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”
   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”
   • [claimed-docs] “from pymilvus import MilvusClient client = MilvusClient("milvus_demo.db")”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Weaviate✓fullprobed8/10

   Weaviate documents an official MCP server that lets LLMs/IDE assistants interact with a Weaviate instance, with both docs and a dedicated GitHub repo confirming it. Missing for 10: independent hands-on validation/community corroboration of the MCP server's reliability and depth of tool coverage.

   • [claimed-docs] “Enable and configure the Weaviate MCP server so LLMs and IDE assistants can interact with your Weaviate instance.”
   • [probe] “official MCP server documented at https://github.com/weaviate/mcp-server-weaviate”

   proof ↗⚑ flag

   Milvus✓fullprobed8/10

   Milvus documents an official MCP server integration tutorial (milvus_and_mcp.md) and a dedicated repo (zilliztech/mcp-server-milvus) allowing AI agents to perform vector search, manage collections, and retrieve data via natural language commands. Missing for 10: independent hands-on validation of the MCP server in production and details on maintenance/versioning of the mcp-server-milvus repo.

   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “This tutorial walks you through setting up an MCP server for Milvus, allowing AI applications to perform vector searches, manage collections…”
   • [probe] “official MCP server documented at https://github.com/zilliztech/mcp-server-milvus”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Weaviate—none0/10

   Evidence lists official client libraries (Python, JS/TS, Go, Java) and an MCP server, but no mention anywhere of an official CLI tool for interacting with or managing Weaviate.

   • [claimed-docs] “Follow the instructions below to install one of the official client libraries, available in Python, JavaScript/TypeScript, Go, and Java.”
   • [probe] “official MCP server documented at https://github.com/weaviate/mcp-server-weaviate”

   proof ↗⚑ flag

   Milvus—none0/10

   The evidence pack shows Python SDK usage (pymilvus/MilvusClient), MCP server integration, and Milvus Lite, but nowhere describes an official standalone CLI tool for interacting with Milvus. missing for 10: any mention of a dedicated Milvus CLI, its command set, installation, or documentation.

   ⚑ flag

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

   weight 3 · round drawn
   Weaviate✓fullprobed8/10

   Weaviate exposes official documented client libraries (Python, JS/TS, Go, Java) and REST/GraphQL APIs for driving all core operations (collections, hybrid search, RAG, multi-tenancy), plus a documented official MCP server enabling LLMs/IDE assistants to interact with instances, confirming programmatic, agent-friendly access. missing for 10: independent hands-on validation of API completeness/stability and no direct evidence of OpenAPI/REST spec docs beyond client libraries.

   • [claimed-docs] “Follow the instructions below to install one of the official client libraries, available in Python, JavaScript/TypeScript, Go, and Java.”
   • [claimed-docs] “Enable and configure the Weaviate MCP server so LLMs and IDE assistants can interact with your Weaviate instance.”
   • [probe] “official MCP server documented at https://github.com/weaviate/mcp-server-weaviate”
   • [github] “Weaviate supports two approaches to store vectors: automatic vectorization at import using integrated models ... or direct import of pre-com…”
   • [claimed-docs] “Import objects directly into Weaviate without having to manually specify embeddings”

   proof ↗⚑ flag

   Milvus✓fullprobed8/10

   Milvus ships a documented public API via pymilvus SDK (MilvusClient) with clear docs for search, filtering, multi-vector, RBAC, and collection management, plus a Python SDK and REST/gRPC access implied by client libraries; an official MCP server further exposes this API for natural-language/agentic driving. Missing for 10: a discoverable OpenAPI/swagger spec (probe found only 404s) and independent hands-on confirmation of API stability/versioning.

   • [claimed-docs] “To create a local Milvus vector database, simply instantiate a `MilvusClient` by specifying a file name to store all data”
   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”
   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”
   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “This tutorial walks you through setting up an MCP server for Milvus, allowing AI applications to perform vector searches, manage collections…”
   • [probe] “official MCP server documented at https://github.com/zilliztech/mcp-server-milvus”
   • [probe] “PROBE openapi: all candidate paths 404 (https://milvus.io/openapi.json, https://milvus.io/swagger.json, https://milvus.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 2 · round to Milvus
   Weaviate—none0/10

   No evidence of scoped/least-privilege API key or credential issuance for agents; docs cover multi-tenancy, RBAC-adjacent isolation, and MCP server setup but nothing about generating restricted-scope API credentials specifically for agent use. Missing for 10: any mention of API key scoping, role-based permission grants, or credential minting workflow for agents.

   • [claimed-docs] “Enable and configure the Weaviate MCP server so LLMs and IDE assistants can interact with your Weaviate instance.”
   • [probe] “official MCP server documented at https://github.com/weaviate/mcp-server-weaviate”
   • [claimed-docs] “Multi-tenancy provides data isolation. Each tenant is stored on a separate shard. Data stored in one tenant is not visible to another tenant…”

   proof ↗⚑ flag

   Milvus~partialprobed5/10

   Milvus documents RBAC that lets admins finely control operations at the collection, database, and instance level, which is the underlying mechanism needed to create least-privilege credentials that could be handed to an agent. However, there is no documented workflow for issuing scoped API keys/tokens specifically for AI agents, no mention of short-lived or agent-specific credential issuance, and the MCP server integration docs don't describe any credential-scoping step. Missing for 10: agent-specific credential/token issuance workflow, examples of scoping RBAC roles to an agent's MCP session, and any independent verification that RBAC-scoped keys are used in agentic contexts.

   • [claimed-docs] “With RBAC, you can finely control the operations users can perform at the collection, database, and instance levels, enhancing data security”
   • [claimed-docs] “With RBAC, you can finely control the operations users can perform at the collection, database, and instance levels, enhancing data security…”
   • [claimed-docs] “This tutorial walks you through setting up an MCP server for Milvus, allowing AI applications to perform vector searches, manage collections…”
   • [probe] “official MCP server documented at https://github.com/zilliztech/mcp-server-milvus”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Milvus
   Weaviate✓fullcommunity8/10

   Weaviate documents official client libraries in Python, JavaScript/TypeScript, Go, and Java, which are the primary SDKs for building AI-native applications against the database. Missing for 10: independent hands-on corroboration of SDK quality/completeness and explicit coverage of async support issues raised by a community user.

   • [claimed-docs] “Follow the instructions below to install one of the official client libraries, available in Python, JavaScript/TypeScript, Go, and Java.”
   • [community] “Just migrated from Supabase + pgvector to Weaviate hoping to take advantage of langchain.retrievers.weaviate_hybrid_search.WeaviateHybridSea…”

   proof ↗⚑ flag

   Milvus✓fullcommunity9/10

   Milvus provides official SDKs (PyMilvus/MilvusClient) with documented client code for both Milvus Lite and full deployments, consistent APIs across scale, and community/hands-on corroboration of SDK usage (search, insert, collection management). Missing for 10: broader multi-language SDK evidence (e.g., Java/Go/Node official SDK docs) beyond Python.

   • [claimed-docs] “To create a local Milvus vector database, simply instantiate a `MilvusClient` by specifying a file name to store all data”
   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”
   • [community] “I recently used Milvus for the first time - it made sense because it was quick to implement, purpose built, and worked exactly as intended.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Weaviate—none0/10

   No evidence in the pack mentions webhooks or event subscription mechanisms; Weaviate's documented features cover search, RAG, multi-tenancy, replication, backups, and MCP integration but nothing about webhook-based event subscriptions.

   ⚑ flag

   Milvus—none0/10

   No evidence anywhere in the pack of Milvus offering webhooks or an event subscription mechanism; it's a vector database with client SDKs, MCP integration, and RBAC, but nothing about outbound event notifications or webhook subscriptions.

   ⚑ flag

Agentic features

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

   weight 2 · round to Weaviate
   Weaviate~partialclaimed6/10

   Weaviate's docs show generative/RAG features that produce natural-language answers from data (docs-6/23), a dedicated agentic 'Query Agent' for agentic search over collections (docs-27), and RAG-oriented backend claims (docs-3, gh-4) plus agent integrations leveraging semantic insights (docs-4) — this directly matches 'AI-generated insights from data'. However the natural-language Q&A feature is explicitly marked 'Cloud only' (docs-23), and there is no independent/hands-on evidence validating quality or reliability of these generated insights, only vendor docs. Missing for 10: independent corroboration of generated-insight quality, self-hosted parity for the Q&A/insights feature, and concrete examples of Query Agent output.

   • [claimed-docs] “Weaviate can serve as a robust backend for RAG workflows, where vector search is used to retrieve context that enhances the output of genera…”
   • [claimed-docs] “These agents can leverage semantic insights to make decisions or trigger actions based on the data stored in Weaviate.”
   • [claimed-docs] “Get answers from your data by using a natural language prompt/question.”
   • [claimed-docs] “Get answers from your data by using a natural language prompt/question. Cloud only”
   • [claimed-docs] “Query Agent: Run agentic search over your Weaviate Cloud collections”
   • [github] “It combines vector similarity search with keyword filtering, retrieval-augmented generation (RAG), and reranking in a single query interface…”

   proof ↗⚑ flag

   Milvus—none0/10

   Milvus documentation shows it as a vector search/database engine with MCP-based natural-language query access, but there is no evidence of Milvus itself generating insights, summaries, or suggestions from stored data — it only enables external AI apps to query it, not to produce insights inside the product.

   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “This tutorial walks you through setting up an MCP server for Milvus, allowing AI applications to perform vector searches, manage collections…”
   • [probe] “official MCP server documented at https://github.com/zilliztech/mcp-server-milvus”

   proof ↗⚑ flag

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

   weight 3 · round to Weaviate
   Weaviate~partialclaimed5/10

   Weaviate Cloud ships a 'Query Agent' described as agentic search that can be delegated over your collections, and docs mention agents leveraging semantic insights to trigger actions, which is a form of built-in AI delegation. However this is narrow (search-only, Cloud-only) rather than a general-purpose in-product assistant, and there's no independent/hands-on corroboration of its use. Missing for 10: broader task delegation beyond search, self-hosted availability, and third-party validation of the Query Agent's real-world behavior.

   • [claimed-docs] “Query Agent: Run agentic search over your Weaviate Cloud collections”
   • [claimed-docs] “These agents can leverage semantic insights to make decisions or trigger actions based on the data stored in Weaviate.”
   • [claimed-docs] “Get answers from your data by using a natural language prompt/question. Cloud only”

   proof ↗⚑ flag

   Milvus—none0/10

   The evidence shows Milvus exposes an MCP server so external AI agents can query it, but this is the reverse of the story — there is no evidence of a built-in AI assistant inside Milvus itself that a user can delegate tasks to.

   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “This tutorial walks you through setting up an MCP server for Milvus, allowing AI applications to perform vector searches, manage collections…”
   • [probe] “official MCP server documented at https://github.com/zilliztech/mcp-server-milvus”

   proof ↗⚑ flag

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

   weight 2 · round to Weaviate
   Weaviate✓fullprobed7/10

   Weaviate documents both natural-language query answering ("Get answers from your data by using a natural language prompt/question") and an official MCP server enabling LLMs/IDE assistants to interact with a Weaviate instance, plus a 'Query Agent' for agentic search over collections — together these let an AI-native user operate the DB via natural-language commands rather than only structured queries. Missing for 10: independent/hands-on verification that NL commands reliably drive full CRUD/admin operations (not just search), and no community corroboration of MCP/Query Agent quality in practice.

   • [claimed-docs] “Get answers from your data by using a natural language prompt/question.”
   • [claimed-docs] “Get answers from your data by using a natural language prompt/question. Cloud only”
   • [claimed-docs] “Enable and configure the Weaviate MCP server so LLMs and IDE assistants can interact with your Weaviate instance.”
   • [claimed-docs] “Query Agent: Run agentic search over your Weaviate Cloud collections”
   • [probe] “official MCP server documented at https://github.com/weaviate/mcp-server-weaviate”

   proof ↗⚑ flag

   Milvus~partialprobed6/10

   Milvus documents an official MCP server integration that lets AI applications perform vector search, manage collections, and retrieve data via natural-language commands without writing queries, and this MCP server is corroborated by a separate GitHub repo (zilliztech/mcp-server-milvus). However, this NL capability is delivered through a bolt-on MCP layer rather than a built-in Milvus interface, and there is no independent/hands-on evidence validating real-world reliability of the NL command translation. Missing for 10: independent/hands-on validation of the MCP-based NL commands, and native (non-MCP) NL support within core Milvus.

   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “This tutorial walks you through setting up an MCP server for Milvus, allowing AI applications to perform vector searches, manage collections…”
   • [probe] “official MCP server documented at https://github.com/zilliztech/mcp-server-milvus”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Weaviate—none0/10

   The evidence pack covers client libraries, quickstart guides, and an MCP server, but there is no mention of an interactive API reference (e.g., Swagger/OpenAPI console) with runnable, in-browser examples. missing for 10: interactive API explorer/playground, runnable code snippets embedded in docs, evidence of live query execution from documentation.

   ⚑ flag

   Milvus—none0/10

   There is no evidence of an interactive API reference (e.g., Swagger/OpenAPI explorer, runnable code sandbox) — the openapi probe explicitly returned 404s at all candidate paths, and documentation consists of static markdown code snippets rather than an interactive, runnable reference. Docs show code examples (milvus-docs-22, milvus-gh-3) but nothing interactive or executable in-browser.

   • [probe] “PROBE openapi: all candidate paths 404 (https://milvus.io/openapi.json, https://milvus.io/swagger.json, https://milvus.io/api/openapi.json, …”
   • [claimed-docs] “from pymilvus import MilvusClient client = MilvusClient("milvus_demo.db")”
   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Weaviate—none0/10

   The evidence pack contains no mention of an OpenAPI spec, Swagger docs, or any machine-readable API specification being available for download; it only covers client libraries, MCP server, and quickstart guides. Since Weaviate exposes a REST/GraphQL API, this axis clearly applies to the product category, but no evidence confirms a downloadable spec.

   ⚑ flag

   Milvus—none0/10

   The evidence pack shows explicit probes for an OpenAPI/swagger spec on Milvus's site returning 404 for all candidate paths, and no documentation snippet references a downloadable machine-readable API spec (Milvus docs focus on SDK usage, MCP server, RBAC, multi-tenancy, etc.). No evidence of a published OpenAPI file or equivalent machine-readable spec.

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

   proof ↗⚑ flag

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

   weight 1 · round to Milvus
   Weaviate~partialclaimed4/10

   Weaviate supports self-hosted local deployments (Docker, Kubernetes) and a free cloud cluster tier, which a user could stand up as an isolated dev/test environment separate from production, and multi-tenancy provides data isolation between tenants. However, there is no explicit documented 'sandbox' feature or guidance for testing against a non-production environment without affecting live data. missing for 10: dedicated sandbox/staging environment documentation, guidance on test-vs-prod separation workflows, independent confirmation that local/free-tier usage is treated as a true sandbox.

   • [github] “You can easily start Weaviate and a local vector embedding model with Docker.”
   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”
   • [claimed-docs] “Always free — 1 cluster per user, upgrade to paid anytime.”
   • [claimed-docs] “Multi-tenancy provides data isolation. Each tenant is stored on a separate shard. Data stored in one tenant is not visible to another tenant…”

   proof ↗⚑ flag

   Milvus✓fullclaimed7/10

   Milvus Lite lets users spin up a local, file-based Milvus instance (e.g. `MilvusClient("milvus_demo.db")`) with the same client API as Standalone/Distributed production deployments, enabling prototyping and testing entirely separate from production data (milvus-docs-1, milvus-docs-8, milvus-docs-17, milvus-docs-19, milvus-gh-1). This is explicitly positioned for quick prototyping in Jupyter notebooks/edge devices before scaling to production. Missing for 10: no explicit 'sandbox' terminology or guidance on safely testing against a shared non-prod environment (e.g. staging cluster), and no independent/community confirmation of this specific workflow.

   • [claimed-docs] “To create a local Milvus vector database, simply instantiate a `MilvusClient` by specifying a file name to store all data”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [claimed-docs] “Milvus Lite is a Python library that can be easily integrated into your applications. As a lightweight version of Milvus, it’s ideal for qui…”
   • [claimed-docs] “from pymilvus import MilvusClient client = MilvusClient("milvus_demo.db")”
   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Weaviate—none0/10

   No evidence pack item mentions API versioning scheme or a documented deprecation policy for Weaviate's APIs; all evidence covers search, RAG, multi-tenancy, backups, and MCP integration instead. Missing for 10: any mention of API version numbers, changelog/deprecation notices, or a stability/support policy document.

   ⚑ flag

   Milvus—none0/10

   No evidence pack item documents API versioning practices or a deprecation policy for Milvus's SDKs/APIs; the OpenAPI probe returned 404s and no versioning/deprecation docs are cited, so this applicable axis is unmet. missing for 10: documented API versioning scheme, explicit deprecation policy, changelog/migration guides for breaking changes.

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

   proof ↗⚑ flag

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

   weight 2 · round to Milvus
   Weaviate~partialclaimed3/10

   Evidence only shows generic references to 'importing data' and 'creating collections' (e.g., weaviate-docs-5, weaviate-docs-12, weaviate-gh-1) without any explicit mention of a batch/bulk API for importing, updating, or deleting many objects at once. Bulk operations are a standard vector-DB capability, so the axis applies, but the pack lacks concrete documentation of batch size limits, bulk delete, or batch import endpoints. missing for 10: explicit batch import/delete API docs, performance/throughput claims for bulk operations, independent confirmation of bulk operation reliability.

   • [claimed-docs] “Set up a collection - Create a collection and import data into it.”
   • [claimed-docs] “Import objects directly into Weaviate without having to manually specify embeddings”
   • [github] “Weaviate supports two approaches to store vectors: automatic vectorization at import using integrated models ... or direct import of pre-com…”

   proof ↗⚑ flag

   Milvus~partialcommunity6/10

   Evidence shows batch support for search (client.search accepts a list of query vectors) and scale claims for billions of vectors, indicating operations designed for bulk workloads, but there is no direct documentation of bulk insert/delete/update APIs or a dedicated bulk-import tool in the pack. missing for 10: explicit bulk insert/delete/update API docs, bulk-import tool documentation, independent benchmark of bulk throughput.

   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”
   • [claimed-docs] “In 2022, Milvus supported billion-scale vectors, and in 2023, it scaled up to tens of billions with consistent stability”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [community] “Milvus allows appending vectors, stored across multiple file slices; when a slice hits a threshold, Milvus builds the index for it and new d…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Weaviate—none0/10

   Weaviate is a vector database with search, RAG, multi-tenancy, backup and agent-integration features, but there is no evidence of an event-driven rules/triggers system that automatically fires actions based on defined conditions or data events. The closest mentions (agentic search, Query Agent, MCP server) describe query/retrieval capabilities, not rule-based automation triggers.

   ⚑ flag

   Milvus—none0/10

   The evidence pack covers Milvus's vector search, indexing, multi-tenancy, RBAC, and MCP integration for natural-language queries, but there is no mention of any rule/trigger system that automatically fires actions on data or system events (e.g., triggers, webhooks, event subscriptions). Missing for 10: any documentation of event-driven triggers, webhook/callback mechanisms, or rule-based automation tied to database events.

   ⚑ flag

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

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

   Milvus—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

Backup

1. platform-engineerBack up collections with snapshots and restore them

   weight 2 · round to Weaviate
   Weaviate✓fullclaimed8/10

   Docs explicitly cover backup/restore functionality including cloud blob storage integration (S3/GCS/Azure), cross-provider restore, incremental backups, and choice of backing up entire instance or selected collections. missing for 10: independent/hands-on corroboration of restore success, detail on snapshot scheduling/automation, and recovery time/consistency guarantees.

   • [claimed-docs] “Seamless integration with widely-used cloud blob storage, such as AWS S3, GCS, or Azure Storage”
   • [claimed-docs] “Backup and Restore between different storage providers”
   • [claimed-docs] “Incremental backups that only store changed data, reducing backup and speeding up backup times”
   • [claimed-docs] “Choice of backing up an entire instance, or selected collections only”

   proof ↗⚑ flag

   Milvus—none0/10

   No evidence in the pack mentions backup/snapshot/restore functionality for collections; the docs cover search, RBAC, multi-tenancy, deployment modes, and MCP integration but nothing about data-lifecycle backup/restore tooling.

   ⚑ flag

Freshness

1. developerUpsert and delete records continuously and have changes reflected in search results quickly, with documented freshness/consistency behavior

   weight 2 · round to Weaviate
   Weaviate~partialclaimed3/10

   Docs confirm CRUD-style data import and replication factor settings (weaviate-docs-9/17) but there is no explicit documentation of freshness/consistency guarantees after upsert/delete, nor any consistency-level or read-after-write behavior described in the evidence pack. missing for 10: documented consistency levels/tunable consistency, read-after-write freshness guarantees, benchmarks or docs on indexing latency for updates/deletes.

   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1. This enables a variety of benefits such as…”
   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1.”
   • [claimed-docs] “Set up a collection - Create a collection and import data into it.”

   proof ↗⚑ flag

   Milvus—none0/10

   Evidence only vaguely mentions 'vector CRUD operations' as a supported feature (milvus-docs-17) but contains no documentation of consistency levels, freshness guarantees, or how quickly upserts/deletes are reflected in search results. The only concrete signal on this topic is a dated community report noting that deletion was 'not yet supported' at the time and that newly inserted vectors are queried via brute force until indexed (milvus-comm-2, milvus-comm-3), which is not corroborating current documented behavior. No first-party consistency-model documentation (e.g., strong/bounded/eventual consistency levels) is present in the pack.

   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [community] “Milvus allows appending vectors, stored across multiple file slices; when a slice hits a threshold, Milvus builds the index for it and new d…”
   • [community] “From reading the docs, newly inserted vectors seem to be queried using brute force until indexed - an interesting design, but insertion docs…”

   proof ↗⚑ flag

Portability

1. developerBulk-import and bulk-export vectors plus metadata in documented formats

   weight 2 · round to Weaviate
   Weaviate~partialclaimed6/10

   Bulk import of objects with either auto-vectorization or pre-computed vector embeddings is well documented (weaviate-docs-12, -15, -24, -28, weaviate-gh-1), and client libraries support this at scale. Export-side evidence is limited to backup/restore to cloud blob storage (S3/GCS/Azure) with incremental and selective backups (weaviate-docs-10, -11, -18, -19), which covers whole-instance/collection portability but is not explicitly documented as a per-object bulk vector+metadata export format (e.g., CSV/JSON dump) for developer-level data lifecycle use. Missing for 10: explicit documented bulk-export API/format for vectors+metadata (vs. binary backup snapshots), and independent/hands-on confirmation of round-trip import/export fidelity.

   • [claimed-docs] “Import objects directly into Weaviate without having to manually specify embeddings”
   • [claimed-docs] “Import objects and vectorize them with the Weaviate Embeddings service. ](/weaviate/quickstart?import=vectorization#create-a-collection)[ …”
   • [claimed-docs] “Import objects and vectorize them with the Weaviate Embeddings service. Import pre-computed vector embeddings along with your data.”
   • [claimed-docs] “Import vectors: Import pre-computed vector embeddings along with your data.”
   • [github] “Weaviate supports two approaches to store vectors: automatic vectorization at import using integrated models ... or direct import of pre-com…”
   • [claimed-docs] “Seamless integration with widely-used cloud blob storage, such as AWS S3, GCS, or Azure Storage”
   • [claimed-docs] “Backup and Restore between different storage providers”
   • [claimed-docs] “Incremental backups that only store changed data, reducing backup and speeding up backup times”
   • [claimed-docs] “Choice of backing up an entire instance, or selected collections only”

   proof ↗⚑ flag

   Milvus—none0/10

   The evidence pack covers Milvus's search, multi-tenancy, RBAC, MCP integration, and deployment modes, but contains no documentation or mention of bulk-import/bulk-export tooling, supported file formats (e.g., Parquet/JSON/NumPy), or a bulkinsert API/CLI for moving vectors plus metadata in and out of Milvus. Missing for 10: bulk-import API/CLI documentation, supported import/export file formats, evidence of export functionality, any hands-on or community confirmation of bulk data lifecycle operations.

   ⚑ flag

Local dev

1. developerRun the database embedded in-process or as a lightweight local instance for development and small workloads

   weight 2 · round to Milvus
   Weaviate~partialcommunity5/10

   Weaviate is well documented for lightweight local deployment via Docker (weaviate-gh-2, weaviate-gh-3), and a community report confirms an embedded Python package mode exists as an alternative to running a separate process (weaviate-comm-1), but the evidence pack contains no first-party documentation describing or supporting embedded in-process operation as an official deployment mode. Missing for 10: first-party docs on embedded mode, language coverage beyond Python, and guidance on limitations of embedded/local instances for production-like dev workloads.

   • [github] “You can easily start Weaviate and a local vector embedding model with Docker.”
   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”
   • [community] “Weaviate is pretty cool IMO. It is open source and fairly easy to get running locally... You can even run Weaviate as an embedded python pac…”

   proof ↗⚑ flag

   Milvus✓fullcommunity9/10

   Milvus Lite provides an embedded, file-based local instance instantiated via a single MilvusClient("file.db") call, sharing the same API/client code as Standalone/Distributed and covering most core features (CRUD, search, filtering, hybrid search), explicitly targeted at laptops/Jupyter notebooks for prototyping. Community mentions corroborate real-world lightweight usage. Missing for 10: independent hands-on benchmarking or confirmation of Milvus Lite's limitations/edge cases beyond vendor docs.

   • [claimed-docs] “To create a local Milvus vector database, simply instantiate a `MilvusClient` by specifying a file name to store all data”
   • [claimed-docs] “from pymilvus import MilvusClient client = MilvusClient("milvus_demo.db")”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [claimed-docs] “Milvus Lite is a Python library that can be easily integrated into your applications. As a lightweight version of Milvus, it’s ideal for qui…”
   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”
   • [community] “I recently used Milvus for the first time - it made sense because it was quick to implement, purpose built, and worked exactly as intended.”

   proof ↗⚑ flag

Managed cloud

1. developerUse a fully managed cloud version of the database with programmatic provisioning

   weight 2 · round to Weaviate
   Weaviate~partialclaimed5/10

   Evidence confirms a fully managed offering (Weaviate Cloud) with a free tier and upgrade path, and lists Weaviate Cloud as one of the deployment options alongside Docker/Kubernetes, but there is no documentation of a provisioning API, CLI, or Terraform-style IaC tool for creating/managing cloud clusters programmatically. Missing for 10: explicit programmatic provisioning API/CLI/IaC support, independent confirmation of automated cluster creation workflows.

   • [claimed-docs] “Always free — 1 cluster per user, upgrade to paid anytime.”
   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”
   • [claimed-docs] “Follow the instructions below to install one of the official client libraries, available in Python, JavaScript/TypeScript, Go, and Java.”

   proof ↗⚑ flag

   Milvus—none0/10

   The evidence pack documents only self-hosted deployment modes (Milvus Lite, Standalone, Distributed/Kubernetes) and open-source SDK usage; a fully managed cloud offering (Zilliz Cloud) is only obliquely referenced in a community complaint about being pushed toward 'their Zilliz SaaS', with no documentation of programmatic provisioning (API/Terraform/CLI cluster creation) for any managed cloud tier. missing for 10: first-party docs on a managed cloud product, API/CLI/Terraform provisioning workflow, evidence of automated cluster lifecycle management.

   • [community] “We regularly do tens of thousands of QPS on pgvector fine on massive data stores. We dropped Milvus after they started trying to force their…”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”

   proof ↗⚑ flag

Self managed

1. platform-engineerDeploy to production on Kubernetes with an official Helm chart or operator

   weight 1 · round to Weaviate
   Weaviate~partialclaimed4/10

   Evidence confirms Kubernetes is a supported deployment option (weaviate-gh-3), which implies K8s-native deployment tooling exists, but no citation explicitly mentions an official Helm chart or Kubernetes operator. Missing for 10: explicit documentation of the Helm chart repo, operator CRDs, or production-grade K8s deployment guide.

   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”

   proof ↗⚑ flag

   Milvus—none0/10

   Evidence only shows that Milvus Distributed can run 'on massive scale Kubernetes cluster' (milvus-docs-8/20), but there is no mention of an official Helm chart, Kubernetes Operator, or any production K8s deployment tooling/documentation. Missing for 10: evidence of an official Helm chart, a Kubernetes Operator (e.g. milvus-operator), and production deployment guides referencing them.

   ⚑ flag

Embeddings

1. ml-engineerHave the database generate embeddings at ingest and query time using built-in or configured model providers, instead of running a separate embedding pipeline

   weight 3 · round to Weaviate
   Weaviate✓fullclaimed8/10

   Weaviate documents built-in vectorization at import (automatic vectorization via integrated models, including its own Embeddings service) and integration with many self-hosted/API model providers, avoiding a separate embedding pipeline; it also supports natural-language query-time search that uses these configured providers. Missing for 10: independent hands-on verification of query-time embedding generation quality/reliability and broader corroboration beyond vendor docs.

   • [claimed-docs] “Import objects directly into Weaviate without having to manually specify embeddings”
   • [claimed-docs] “Import objects and vectorize them with the Weaviate Embeddings service. ](/weaviate/quickstart?import=vectorization#create-a-collection)[ …”
   • [claimed-docs] “Weaviate integrates with a variety of self-hosted and API-based models from a range of providers.”
   • [github] “Weaviate supports two approaches to store vectors: automatic vectorization at import using integrated models ... or direct import of pre-com…”
   • [github] “You can easily start Weaviate and a local vector embedding model with Docker.”
   • [claimed-docs] “Import objects and vectorize them with the Weaviate Embeddings service. Import pre-computed vector embeddings along with your data.”

   proof ↗⚑ flag

   Milvus~partialclaimed5/10

   Evidence shows Milvus can auto-generate sparse embeddings from raw text for full-text search (BM25-style) without manual embedding generation, but there is no evidence of built-in dense embedding generation via configured model providers (e.g., OpenAI, HuggingFace) at both ingest and query time, which is the core of the story. missing for 10: documentation of configurable embedding model providers/functions for dense embeddings, evidence of embedding generation at both ingest and query time beyond sparse/full-text search, independent confirmation of this workflow in practice.

   • [claimed-docs] “it simplifies vector searches by accepting raw text input, automatically converting your text data into sparse embeddings without the need t…”
   • [claimed-docs] “it simplifies vector searches by accepting raw text input, automatically converting your text data into sparse embeddings without the need t…”

   proof ↗⚑ flag

Filtering

1. developerFilter vector search by structured metadata conditions without wrecking recall or latency

   weight 3 · round to Milvus
   Weaviate~partialprobed3/10

   Evidence only hints at filtering capability via 'keyword filtering' combined with vector search (weaviate-gh-4) and mentions of inverted indexes for structured data (weaviate-probe-1), but there is no documentation addressing how structured metadata filters interact with vector search to preserve recall or latency. missing for 10: explicit docs on pre-filtering/post-filtering strategy, benchmarks or claims about recall/latency impact of combined filter+vector queries, and independent corroboration of filter performance.

   • [github] “It combines vector similarity search with keyword filtering, retrieval-augmented generation (RAG), and reranking in a single query interface…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.weaviate.io/llms.txt # Weaviate ## TL;DR Weaviate is an open-source vector database (Go) that sto…”

   proof ↗⚑ flag

   Milvus✓fullclaimed7/10

   Milvus docs explicitly describe pre-filtering: filtering conditions are applied before the ANN search so the search scope is reduced to matching entities, and Milvus Lite confirms metadata filtering is a supported feature across deployment modes. This directly matches the story of combining structured filters with vector search without a separate post-filter step. missing for 10: independent benchmarks or community evidence quantifying recall/latency impact of filtered search, and documentation detail on filter expression complexity/performance trade-offs.

   • [claimed-docs] “You can include filtering conditions in a search request so that Milvus conducts metadata filtering before conducting ANN searches, reducing…”
   • [claimed-docs] “You can include filtering conditions in a search request so that Milvus conducts metadata filtering before conducting ANN searches, reducing…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”

   proof ↗⚑ flag

2. developerExpress rich filter conditions (ranges, geo, nested boolean logic, array membership) in queries

   weight 2 · round to Milvus
   Weaviate—none0/10

   The evidence pack covers hybrid search, RAG, multi-tenancy, replication, backups, and model integrations, but contains no mention of Weaviate's filter operators (e.g., range, GeoRange, nested And/Or, ContainsAny/ContainsAll for arrays) despite these being real, documented Weaviate capabilities. Without citations describing filter syntax or examples, this story cannot be credited as delivered from this evidence pack alone.

   ⚑ flag

   Milvus~partialclaimed5/10

   Docs confirm Milvus supports metadata filtering conditions in search/query requests (scalar filtering reduces search scope), but the evidence pack never details the specific expression capabilities like range operators, geo-spatial predicates, nested boolean logic, or array membership operators. missing for 10: explicit examples of range queries, geo-spatial filters, nested AND/OR/NOT boolean expressions, and array 'contains'/'in' membership filters.

   • [claimed-docs] “You can include filtering conditions in a search request so that Milvus conducts metadata filtering before conducting ANN searches, reducing…”
   • [claimed-docs] “You can include filtering conditions in a search request so that Milvus conducts metadata filtering before conducting ANN searches, reducing…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”

   proof ↗⚑ flag

Scaling

1. platform-engineerScale beyond one node with sharding or distributed deployment

   weight 2 · round drawn
   Weaviate✓fullclaimed8/10

   Docs confirm multi-node distributed deployment with replication factor >1 for high availability, sharding via multi-tenancy (each tenant on a separate shard), and multiple deployment options including Kubernetes for cluster scaling. First-party documentation is strong but lacks independent hands-on validation of multi-node scaling specifically. Missing for 10: independent/community corroboration of production multi-node cluster scaling behavior, benchmarks on distributed performance.

   • [claimed-docs] “Multi-tenancy provides data isolation. Each tenant is stored on a separate shard. Data stored in one tenant is not visible to another tenant…”
   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1. This enables a variety of benefits such as…”
   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1.”
   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”

   proof ↗⚑ flag

   Milvus✓fullcommunity8/10

   Docs explicitly describe Milvus Distributed running on Kubernetes clusters serving billions of vectors, with the same client API as Standalone/Lite, and community evidence corroborates real-world use at billion-scale/thousands of QPS. missing for 10: detailed sharding architecture/query-node scaling docs and independent hands-on verification of distributed cluster setup steps.

   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “In 2022, Milvus supported billion-scale vectors, and in 2023, it scaled up to tens of billions with consistent stability”
   • [claimed-docs] “In 2022, Milvus supported billion-scale vectors, and in 2023, it scaled up to tens of billions with consistent stability, powering large-sca…”
   • [community] “For people who run thousands of QPS on billions of vectors, Milvus is a solid choice... I've seen many builders migrate from pgvector to Mil…”
   • [community] “pgVector is great and so is FAISS, but those are just a subset of what you get from Milvus - if you want hybrid search, different IVF varian…”
   • [github] “Milvus also supports Standalone mode for single machine deployment.”

   proof ↗⚑ flag

2. platform-engineerReplicate data across nodes or zones for high availability with a documented consistency model

   weight 2 · round to Weaviate
   Weaviate~partialclaimed5/10

   Docs confirm Weaviate replicates data across multi-node clusters via a replication factor >1 for high availability, but the evidence pack does not cite specifics of a documented consistency model (e.g., tunable consistency levels, quorum reads/writes) beyond the general HA claim. Missing for 10: explicit documentation of consistency levels/tunable consistency, cross-zone replication guarantees, and independent verification of HA behavior in production.

   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1. This enables a variety of benefits such as…”
   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1.”

   proof ↗⚑ flag

   Milvus—none0/10

   The evidence pack covers multi-tenancy isolation strategies and RBAC, but contains no mention of cross-node/zone replication, replica configuration, or a documented consistency model (e.g., strong/bounded staleness/eventual) that Milvus is known to offer elsewhere. Since this axis clearly applies to a distributed vector database, absence of evidence yields 'none'.

   • [claimed-docs] “Milvus supports four multi-tenancy strategies, each offering a different trade-off between scalability, data isolation, and flexibility”
   • [claimed-docs] “In 2022, Milvus supported billion-scale vectors, and in 2023, it scaled up to tens of billions with consistent stability”

   proof ↗⚑ flag

Tenancy

1. platform-engineerEnforce granular access control (API keys, roles, per-collection permissions) on database operations

   weight 2 · round to Milvus
   Weaviate—none0/10

   The evidence pack covers multi-tenancy data isolation, replication, and backups but contains no mention of API keys, RBAC, roles, or per-collection permission enforcement — an applicable but unevidenced capability for a platform-engineer persona.

   ⚑ flag

   Milvus✓fullclaimed7/10

   Milvus docs explicitly describe RBAC that lets admins control operations at the collection, database, and instance levels, and separately document four multi-tenancy isolation strategies for tenant/collection separation, directly matching the story's ask for granular per-collection/role access control. Missing for 10: explicit documentation of API-key-based auth mechanics, and independent/hands-on community verification that RBAC/multi-tenancy works as described in production.

   • [claimed-docs] “With RBAC, you can finely control the operations users can perform at the collection, database, and instance levels, enhancing data security”
   • [claimed-docs] “With RBAC, you can finely control the operations users can perform at the collection, database, and instance levels, enhancing data security…”
   • [claimed-docs] “Milvus supports four multi-tenancy strategies, each offering a different trade-off between scalability, data isolation, and flexibility”
   • [claimed-docs] “Milvus supports four multi-tenancy strategies, each offering a different trade-off between scalability, data isolation, and flexibility.”

   proof ↗⚑ flag

2. platform-engineerIsolate many tenants cheaply using namespaces, partitions, or per-tenant collections with documented limits

   weight 3 · round drawn
   Weaviate~partialclaimed6/10

   Docs confirm per-tenant isolation via separate shards, auto-tenant creation, and replication for HA, which directly supports cheap multi-tenant isolation via per-tenant collections/shards (weaviate-docs-7, weaviate-docs-8, weaviate-docs-16, weaviate-docs-9, weaviate-docs-17). However, no evidence cites concrete documented limits (e.g., max tenants per node/cluster, cost/scale ceilings) that a platform engineer would need to plan capacity. missing for 10: explicit documented tenant-count limits or scaling guidance, independent benchmarks/case studies of large tenant counts.

   • [claimed-docs] “Multi-tenancy provides data isolation. Each tenant is stored on a separate shard. Data stored in one tenant is not visible to another tenant…”
   • [claimed-docs] “To change this behavior so Weaviate creates a new tenant, set `autoTenantCreation` to `true` in the collection definition.”
   • [claimed-docs] “By default, Weaviate returns an error if you try to insert an object into a non-existent tenant. To change this behavior so Weaviate creates…”
   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1. This enables a variety of benefits such as…”
   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1.”

   proof ↗⚑ flag

   Milvus~partialclaimed6/10

   Milvus documents four distinct multi-tenancy strategies (databases, collections, partitions, partition-key based) with tradeoffs on scalability/isolation/flexibility, and RBAC for fine-grained per-collection/database/instance access control, directly supporting tenant isolation patterns. However, the evidence pack lacks documented hard limits/quotas per tenant strategy (e.g., max collections/partitions per cluster, resource-cost guidance) or independent validation of cost-efficiency at scale for many tenants. Missing for 10: explicit documented numeric limits per strategy, cost/resource benchmarks for many-tenant scenarios, and independent/hands-on confirmation of isolation guarantees at scale.

   • [claimed-docs] “Milvus supports four multi-tenancy strategies, each offering a different trade-off between scalability, data isolation, and flexibility”
   • [claimed-docs] “Milvus supports four multi-tenancy strategies, each offering a different trade-off between scalability, data isolation, and flexibility.”
   • [claimed-docs] “With RBAC, you can finely control the operations users can perform at the collection, database, and instance levels, enhancing data security”
   • [claimed-docs] “With RBAC, you can finely control the operations users can perform at the collection, database, and instance levels, enhancing data security…”

   proof ↗⚑ flag

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

   weight 2 · round to Milvus
   Weaviate—none0/10

   The evidence pack documents Weaviate's API/client libraries, hybrid search, RAG, and MCP server, but never compares API capabilities against a separate UI (e.g., Weaviate Cloud console) or claims feature parity between the two. Missing for 10: any explicit statement or example that every UI-console action (e.g., cluster management, monitoring, schema editing) can be replicated via the REST/GraphQL/gRPC API, and any independent confirmation of this parity.

   ⚑ flag

   Milvus✓fullprobed8/10

   Milvus is fundamentally API/SDK-first (PyMilvus/MilvusClient), with no distinct GUI that offers capabilities beyond the API — all core operations (collection management, CRUD, ANN search, filtering, multi-vector, RBAC, multi-tenancy) are documented as API/SDK operations, and Milvus Lite/Standalone/Distributed share the same client-side API surface. missing for 10: no explicit comparison against the Attu GUI to confirm 1:1 parity, and no published OpenAPI/REST spec (probe shows 404s) confirming a fully documented REST surface alongside the SDK.

   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [claimed-docs] “from pymilvus import MilvusClient client = MilvusClient("milvus_demo.db")”
   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”
   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://milvus.io/openapi.json, https://milvus.io/swagger.json, https://milvus.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 3 · round to Weaviate
   Weaviate~partialcommunity5/10

   Weaviate offers backup/restore across cloud storage providers and open client libraries (Python/JS/Go/Java) that could be used to pull data out, and the product itself is open-source, supporting a 'leave without lock-in' narrative. However there is no explicit documentation of a bulk data export feature or open interchange format (e.g., JSON/parquet dump) — backups are described as instance restores rather than portable exports. Missing for 10: explicit bulk-export/dump-to-open-format documentation, evidence of exporting vectors+metadata in a standard interchange format, and independent confirmation of successful full-data migration out of Weaviate.

   • [claimed-docs] “Seamless integration with widely-used cloud blob storage, such as AWS S3, GCS, or Azure Storage”
   • [claimed-docs] “Backup and Restore between different storage providers”
   • [claimed-docs] “Incremental backups that only store changed data, reducing backup and speeding up backup times”
   • [claimed-docs] “Choice of backing up an entire instance, or selected collections only”
   • [claimed-docs] “Follow the instructions below to install one of the official client libraries, available in Python, JavaScript/TypeScript, Go, and Java.”
   • [community] “Weaviate is pretty cool IMO. It is open source and fairly easy to get running locally... You can even run Weaviate as an embedded python pac…”

   proof ↗⚑ flag

   Milvus~partialclaimed4/10

   Milvus is fully open-source and self-hostable, and Milvus Lite stores all data in a single local file (e.g. milvus_demo.db) that the user directly controls, which implies inherent data portability without vendor lock-in. However, the evidence pack contains no explicit documentation of a bulk export/backup feature or supported open export formats (e.g. Parquet, JSON dump, migration tooling) for standalone/distributed deployments. Missing for 10: explicit export/backup documentation, supported open data formats for bulk export, and any hands-on confirmation that a user can fully extract and leave with their data.

   • [claimed-docs] “To create a local Milvus vector database, simply instantiate a `MilvusClient` by specifying a file name to store all data”
   • [claimed-docs] “from pymilvus import MilvusClient client = MilvusClient("milvus_demo.db")”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [github] “Milvus also supports Standalone mode for single machine deployment.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Weaviate✓fullprobed7/10

   Weaviate's GitHub repo and docs explicitly describe it as an open-source vector database, and a community comment independently corroborates that it is open source and can be run locally. missing for 10: explicit citation of the specific open-source license name (e.g., BSD-3-Clause) and confirmation that the full source (not just parts) is publicly available under that license.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.weaviate.io/llms.txt # Weaviate ## TL;DR Weaviate is an open-source vector database (Go) that sto…”
   • [community] “Weaviate is pretty cool IMO. It is open source and fairly easy to get running locally... You can even run Weaviate as an embedded python pac…”
   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”

   proof ↗⚑ flag

   Milvus✓fullprobed7/10

   Milvus is repeatedly described as an 'open-source vector database' in its own docs, and its source code is publicly hosted on GitHub (milvus-io/milvus), which the evidence cites directly for code snippets and installation instructions. This confirms the source is readable and publicly available under an open-source model. Missing for 10: explicit license name/badge (e.g., Apache-2.0) in the evidence, and independent third-party confirmation of licensing terms.

   • [claimed-docs] “Milvus is an open-source vector database that suits AI applications of every size from running a demo chatbot in Jupyter notebook to buildin…”
   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”
   • [github] “Milvus also supports Standalone mode for single machine deployment.”
   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://milvus.io/llms.txt # Milvus > Milvus is an open-source, high-performance vector database designed for s…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Weaviate✓fullprobed9/10

   Weaviate is explicitly open-source (Go) and offers self-hosted deployment via Docker/Kubernetes in addition to Weaviate Cloud, with community confirmation of easy local/self-hosted setup including an embedded mode. Missing for 10: no independent audit of self-hosted feature parity with the managed cloud offering (some features like Query Agent are noted cloud-only).

   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.weaviate.io/llms.txt # Weaviate ## TL;DR Weaviate is an open-source vector database (Go) that sto…”
   • [community] “Weaviate is pretty cool IMO. It is open source and fairly easy to get running locally... You can even run Weaviate as an embedded python pac…”
   • [claimed-docs] “Get answers from your data by using a natural language prompt/question. Cloud only”
   • [github] “You can easily start Weaviate and a local vector embedding model with Docker.”

   proof ↗⚑ flag

   Milvus✓fullcommunity9/10

   Milvus is open-source and explicitly documented to run fully self-hosted across deployment modes (Milvus Lite for local/laptop, Standalone via Docker, Distributed via Kubernetes), all sharing the same client API, with community evidence confirming real-world self-hosted use at scale. Minor gap - missing for 10: independent hands-on benchmarking of the full self-hosted distributed setup beyond community anecdotes.

   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [github] “Milvus also supports Standalone mode for single machine deployment.”
   • [community] “For people who run thousands of QPS on billions of vectors, Milvus is a solid choice... I've seen many builders migrate from pgvector to Mil…”
   • [community] “pgVector is great and so is FAISS, but those are just a subset of what you get from Milvus - if you want hybrid search, different IVF varian…”
   • [claimed-docs] “In 2022, Milvus supported billion-scale vectors, and in 2023, it scaled up to tens of billions with consistent stability”

   proof ↗⚑ flag

Benchmarks

1. platform-engineerSee published benchmarks or measured latency/recall numbers backing the database's performance claims

   weight 2 · round to Milvus
   Weaviate—none0/10

   No evidence pack items contain published benchmarks, latency numbers, recall metrics, or any quantitative performance comparisons; the docs focus on feature descriptions (hybrid search, multi-tenancy, backups, replication) without measured performance data. missing for 10: benchmark reports, latency/recall figures, third-party performance evaluations.

   ⚑ flag

   Milvus!disputedcontradicted3/10

   Milvus docs make a vague vendor claim of '30%-70% better performance' vs FAISS/HNSWLib with no methodology, recall curves, latency tables, or dataset details (milvus-docs-18), and no independent benchmark corroborates it. Community hands-on feedback contradicts this blanket claim, noting that Milvus's IVF indices are literally FAISS-based and 'performance is the same as Faiss' (milvus-comm-1), undercutting the specific performance-superiority claim. Missing for 10: published benchmark report/methodology, recall@k figures, latency percentiles under specified QPS/hardware, and independent reproduction of the claimed 30-70% gain.

   • [claimed-docs] “Compared to popular implementations like FAISS and HNSWLib, Milvus delivers 30%-70% better performance.”
   • [community] “At this moment, the IVF indices are based on FAISS, so performance is the same as Faiss. IVF_SQ8H reconstructs Faiss IVF SQ8 with much bette…”
   • [community] “We regularly do tens of thousands of QPS on pgvector fine on massive data stores. We dropped Milvus after they started trying to force their…”

   proof ↗⚑ flag

Index tuning

1. ml-engineerTune index parameters (HNSW graph settings, index types) to trade recall against latency and memory

   weight 2 · round to Milvus
   Weaviate—none0/10

   The evidence pack contains no mention of HNSW parameters (ef, efConstruction, maxConnections), index type selection (flat vs HNSW vs dynamic), or any recall/latency/memory tuning guidance — only general search, multi-tenancy, replication, and backup features are covered. Missing for 10: any documentation of HNSW graph parameter configuration, index type trade-off guidance, or benchmarks showing recall/latency/memory tuning.

   ⚑ flag

   Milvus~partialcommunity3/10

   Evidence only indirectly touches on index type variety (IVF variants, IVF_SQ8H GPU-optimized index, disk-based search) via community commentary, but there is no documentation in the pack of HNSW-specific parameters (M, efConstruction, ef) or explicit recall/latency/memory trade-off guidance for tuning. Missing for 10: HNSW parameter docs, index-type comparison guide, recall-vs-latency benchmarking guidance, first-party tuning tutorial.

   • [community] “At this moment, the IVF indices are based on FAISS, so performance is the same as Faiss. IVF_SQ8H reconstructs Faiss IVF SQ8 with much bette…”
   • [community] “pgVector is great and so is FAISS, but those are just a subset of what you get from Milvus - if you want hybrid search, different IVF varian…”

   proof ↗⚑ flag

2. ml-engineerEnable vector quantization or compression to cut memory and storage cost with a documented accuracy trade-off

   weight 2 · round drawn
   Weaviate—none0/10

   The evidence pack contains no mention of vector quantization (PQ, BQ, SQ) or compression features, nor any documented accuracy/memory trade-offs, despite Weaviate actually shipping such features in reality; based solely on this evidence pack, there is no support. Missing for 10: any mention of quantization/compression config options, memory/storage savings benchmarks, or documented recall/accuracy trade-off data.

   ⚑ flag

   Milvus—none0/10

   No evidence pack item documents Milvus's quantization/compression index types (e.g., IVF_SQ8, PQ, scalar/product quantization) with a stated accuracy/memory trade-off. Only a tangential community comment mentions IVF_SQ8H performance vs FAISS, but it doesn't address accuracy trade-offs or documented guidance. missing for 10: official docs on index types (IVF_SQ8, PQ, BIN, etc.), memory/storage savings figures, recall/accuracy trade-off benchmarks, configuration guidance.

   • [community] “At this moment, the IVF indices are based on FAISS, so performance is the same as Faiss. IVF_SQ8H reconstructs Faiss IVF SQ8 with much bette…”

   proof ↗⚑ flag

Pricing

1. developerPrototype on a meaningful free tier before paying anything

   weight 1 · round to Milvus
   Weaviate~partialclaimed5/10

   Weaviate Cloud offers an 'Always free' 1 cluster tier per user that upgrades to paid anytime, which supports prototyping without payment. However, evidence doesn't detail the free tier's resource limits, duration, or whether it's sufficient for meaningful real-world prototyping, and self-hosted open-source use (free but requiring infra) is a separate path not tied to this pricing claim. missing for 10: details on free tier limits/quotas, independent user confirmation of the free tier being 'meaningful' for real prototyping, comparison to competitor free tiers.

   • [claimed-docs] “Always free — 1 cluster per user, upgrade to paid anytime.”

   proof ↗⚑ flag

   Milvus✓fullclaimed8/10

   Milvus Lite is documented as a free, open-source, lightweight Python library explicitly positioned for 'quick prototyping in Jupyter Notebooks or edge devices,' with the same API as Standalone/Distributed, so a developer can prototype fully before any payment. Missing for 10: explicit documentation of a hosted/managed free tier (e.g., Zilliz Cloud) with limits, and independent confirmation that prototyping never requires payment beyond self-hosting.

   • [claimed-docs] “Milvus Lite is a Python library that can be easily integrated into your applications. As a lightweight version of Milvus, it’s ideal for qui…”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [claimed-docs] “from pymilvus import MilvusClient client = MilvusClient("milvus_demo.db")”
   • [github] “Milvus also supports Standalone mode for single machine deployment.”

   proof ↗⚑ flag

2. developerPay serverless usage-based pricing with transparent per-unit costs instead of provisioning fixed clusters

   weight 2 · round drawn
   Weaviate—none0/10

   The only pricing evidence describes a free tier as '1 cluster per user, upgrade to paid anytime,' implying cluster-based provisioning rather than serverless usage-based per-unit billing; no evidence of transparent per-unit consumption pricing is present.

   • [claimed-docs] “Always free — 1 cluster per user, upgrade to paid anytime.”

   proof ↗⚑ flag

   Milvus—none0/10

   Milvus is documented as open-source software deployable as Milvus Lite, Standalone, or Distributed; none of the evidence describes a serverless usage-based pricing model or transparent per-unit costs — the only pricing-adjacent mention is a community complaint about being pushed toward 'Zilliz SaaS' with no cost details. Missing for 10: any documentation of usage-based billing, per-unit pricing, or a serverless managed tier with transparent costs.

   • [community] “We regularly do tens of thousands of QPS on pgvector fine on massive data stores. We dropped Milvus after they started trying to force their…”

   proof ↗⚑ flag

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

   weight 2 · round to Milvus
   Weaviate~partialclaimed3/10

   Weaviate can be self-hosted via Docker/Kubernetes or run in Weaviate Cloud, which implicitly gives users control over where their data physically resides, but there is no explicit documentation of region-selection or data-residency features for Weaviate Cloud. missing for 10: explicit region/data-residency configuration options, compliance certifications (e.g., GDPR region pinning), and any documentation on choosing a cloud region for hosted deployments.

   • [github] “Weaviate offers multiple installation and deployment options: Docker, Kubernetes, Weaviate Cloud”

   proof ↗⚑ flag

   Milvus~partialclaimed5/10

   Milvus is open-source and self-hostable in multiple modes (Milvus Lite on a laptop, Standalone via Docker, Distributed on Kubernetes), which implicitly lets users control exactly where their data physically resides by choosing their own deployment location. However, there is no explicit documentation of region/residency selection features (e.g., cloud region picker, data-residency compliance controls) — that capability would live in a managed offering like Zilliz Cloud, which isn't covered here. Missing for 10: explicit region/residency configuration options, documented compliance/data-residency guarantees, and any managed-cloud region selection UI or API.

   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “With the same client-side code, you can run GenAI apps with Milvus Lite on a laptop or Jupyter Notebook, or Milvus Standalone on Docker cont…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [github] “Milvus also supports Standalone mode for single machine deployment.”

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round to Milvus
   Weaviate—none0/10

   The evidence pack covers hybrid search, RAG, multi-tenancy, replication, and backups, but contains no documentation of object/collection deletion APIs, TTL-based expiration, or data retention policies that would let an AI-native user control how long data persists or ensure deletion. Multi-tenancy (isolation) and backups (durability) are adjacent but do not address retention/deletion controls.

   • [claimed-docs] “Multi-tenancy provides data isolation. Each tenant is stored on a separate shard. Data stored in one tenant is not visible to another tenant…”
   • [claimed-docs] “Weaviate allows data replication across a multi-node cluster by setting a replication factor > 1. This enables a variety of benefits such as…”
   • [claimed-docs] “Seamless integration with widely-used cloud blob storage, such as AWS S3, GCS, or Azure Storage”

   proof ↗⚑ flag

   Milvus~partialcommunity4/10

   Milvus Lite/Standalone docs mention 'vector CRUD operations' as a core feature, implying users can delete entities/collections, and RBAC/multi-tenancy docs show some data-governance controls, but the evidence pack has no explicit documentation of deletion APIs, TTL/expiry, purge/compaction policies, or retention controls. An older community comment even notes vector deletion was unsupported in early versions, though this predates current CRUD claims and isn't a concrete current-version contradiction. missing for 10: explicit delete/drop API docs, data retention/TTL policy documentation, compliance-oriented deletion guarantees, independent confirmation of deletion behavior.

   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”
   • [claimed-docs] “With RBAC, you can finely control the operations users can perform at the collection, database, and instance levels, enhancing data security”
   • [claimed-docs] “Milvus supports four multi-tenancy strategies, each offering a different trade-off between scalability, data isolation, and flexibility”
   • [community] “Milvus allows appending vectors, stored across multiple file slices; when a slice hits a threshold, Milvus builds the index for it and new d…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Weaviate—none0/10

   No evidence pack item mentions telemetry, usage tracking, opt-out settings, or privacy configuration options for Weaviate; the axis applies to any self-hostable database product but no supporting documentation is provided.

   ⚑ flag

   Milvus—none0/10

   The evidence pack contains no mention of telemetry, usage tracking, or opt-out settings for Milvus; this is a fair question for an open-source database (e.g., anonymized usage stats) but no documentation addresses it.

   ⚑ flag

Integrations

1. ml-engineerPlug the database into RAG and agent frameworks (LangChain, LlamaIndex, etc.) through maintained first-class integrations

   weight 2 · round to Weaviate
   Weaviate~partialcommunity4/10

   Evidence confirms Weaviate is usable as a RAG backend with official client libraries and an MCP server, and a community report shows it being used with a LangChain retriever (WeaviateHybridSearchRetriever) in practice, but that same report flags a concrete functional gap (can't get it to work asynchronously). There is no first-party documentation in the pack of maintained LangChain/LlamaIndex integration pages, and LlamaIndex is not mentioned at all. Missing for 10: official docs/changelog for LangChain and LlamaIndex integrations, confirmation the async issue is resolved, and any first-party integration-maintenance statement.

   • [claimed-docs] “Weaviate can serve as a robust backend for RAG workflows, where vector search is used to retrieve context that enhances the output of genera…”
   • [claimed-docs] “These agents can leverage semantic insights to make decisions or trigger actions based on the data stored in Weaviate.”
   • [claimed-docs] “Follow the instructions below to install one of the official client libraries, available in Python, JavaScript/TypeScript, Go, and Java.”
   • [community] “Just migrated from Supabase + pgvector to Weaviate hoping to take advantage of langchain.retrievers.weaviate_hybrid_search.WeaviateHybridSea…”
   • [github] “It combines vector similarity search with keyword filtering, retrieval-augmented generation (RAG), and reranking in a single query interface…”

   proof ↗⚑ flag

   Milvus~partialprobed3/10

   Evidence shows Milvus ships a Python SDK (pymilvus) and an official MCP server that lets AI agents query the database via natural language, which is a form of agent-framework connectivity, but no evidence pack item explicitly documents maintained first-class connectors for LangChain, LlamaIndex, or similar RAG frameworks. Missing for 10: explicit documentation of LangChain/LlamaIndex integration modules, versioning/maintenance status of those connectors, and any hands-on confirmation they work as advertised.

   • [claimed-docs] “allowing AI applications to perform vector searches, manage collections, and retrieve data using natural language commands—without writing c…”
   • [claimed-docs] “This tutorial walks you through setting up an MCP server for Milvus, allowing AI applications to perform vector searches, manage collections…”
   • [probe] “official MCP server documented at https://github.com/zilliztech/mcp-server-milvus”
   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”

   proof ↗⚑ flag

Sdks

1. developerBuild against official SDKs in the major languages (Python, TypeScript, Go, Java)

   weight 2 · round to Weaviate
   Weaviate✓fullclaimed8/10

   Official docs explicitly state client libraries are available in Python, JavaScript/TypeScript, Go, and Java, matching the story's exact language list. missing for 10: independent hands-on corroboration of each SDK's parity/quality, and no mention of versioning or release cadence across languages.

   • [claimed-docs] “Follow the instructions below to install one of the official client libraries, available in Python, JavaScript/TypeScript, Go, and Java.”

   proof ↗⚑ flag

   Milvus~partialclaimed4/10

   Evidence strongly documents the official Python SDK (pymilvus/MilvusClient) with quickstart code and API examples, but the pack contains no mention of TypeScript, Go, or Java SDKs, their docs, or usage examples. Missing for 10: documentation or references confirming official TypeScript, Go, and Java SDK support/parity with the Python client.

   • [github] “This installs `pymilvus`, the Python SDK for Milvus. Use `MilvusClient` to create a client”
   • [claimed-docs] “To create a local Milvus vector database, simply instantiate a `MilvusClient` by specifying a file name to store all data”
   • [claimed-docs] “from pymilvus import MilvusClient client = MilvusClient("milvus_demo.db")”
   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”

   proof ↗⚑ flag

Core search

1. developerRun approximate nearest-neighbor similarity search over embeddings with configurable distance metrics

   weight 3 · round to Milvus
   Weaviate~partialprobed5/10

   Weaviate's core function as a vector database with semantic/vector similarity search is well evidenced (docs-22, docs-26, gh-4, probe-1 confirm it stores vectors and runs ANN-style similarity search, often combined with keyword search), but the evidence pack never explicitly documents configurable distance metrics (e.g., cosine, dot product, L2) or ANN indexing parameters like HNSW settings. Missing for 10: explicit documentation of selectable distance metrics, HNSW/ANN index configuration options, and independent hands-on confirmation of metric selection working as expected.

   • [claimed-docs] “By indexing data with vectors, Weaviate supports searches based on both semantic similarity and keywords.”
   • [claimed-docs] “Weaviate supports searches based on both semantic similarity and keywords. This allows for more relevant results even when the query terms d…”
   • [github] “It combines vector similarity search with keyword filtering, retrieval-augmented generation (RAG), and reranking in a single query interface…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.weaviate.io/llms.txt # Weaviate ## TL;DR Weaviate is an open-source vector database (Go) that sto…”
   • [github] “Weaviate supports two approaches to store vectors: automatic vectorization at import using integrated models ... or direct import of pre-com…”

   proof ↗⚑ flag

   Milvus✓fullcommunity8/10

   Milvus is fundamentally an ANN vector search engine, with docs showing search APIs, filtered/multi-vector ANN search, and index tuning (IVF variants), plus community confirmation of real-world QPS/scale performance. Missing for 10: explicit documentation snippet listing configurable distance metric options (L2/IP/cosine) in this evidence pack, and independent benchmarking of metric-specific accuracy.

   • [claimed-docs] “Milvus supports this by allowing search on multiple vector fields, conducting several Approximate Nearest Neighbor (ANN) searches simultaneo…”
   • [claimed-docs] “You can include filtering conditions in a search request so that Milvus conducts metadata filtering before conducting ANN searches, reducing…”
   • [github] “res = client.search( collection_name="demo_collection", # target collection data=query_vectors, # a list of one or more query vect…”
   • [community] “At this moment, the IVF indices are based on FAISS, so performance is the same as Faiss. IVF_SQ8H reconstructs Faiss IVF SQ8 with much bette…”
   • [community] “For people who run thousands of QPS on billions of vectors, Milvus is a solid choice... I've seen many builders migrate from pgvector to Mil…”
   • [community] “pgVector is great and so is FAISS, but those are just a subset of what you get from Milvus - if you want hybrid search, different IVF varian…”

   proof ↗⚑ flag

Hybrid

1. developerRun keyword/full-text search over documents inside the database without bolting on a separate search engine

   weight 2 · round to Weaviate
   Weaviate✓fullclaimed8/10

   Weaviate natively supports BM25 keyword search combined with vector search via hybrid search (fusion algorithms), built directly into the database without needing a separate search engine like Elasticsearch. missing for 10: independent hands-on benchmarking of BM25-only relevance/performance, and clearer documentation on pure keyword-only query mode without vector component.

   • [claimed-docs] “Hybrid search combines vector search and keyword search (BM25) to leverage the strengths of both approaches.”
   • [claimed-docs] “Weaviate supports two strategies (`relativeScoreFusion` and `rankedFusion`) for combining vector and keyword search scores”
   • [claimed-docs] “A hybrid search runs both search types in parallel and combines their scores to produce a final ranking of results.”
   • [claimed-docs] “By indexing data with vectors, Weaviate supports searches based on both semantic similarity and keywords.”
   • [claimed-docs] “Weaviate supports searches based on both semantic similarity and keywords. This allows for more relevant results even when the query terms d…”
   • [github] “It combines vector similarity search with keyword filtering, retrieval-augmented generation (RAG), and reranking in a single query interface…”

   proof ↗⚑ flag

   Milvus✓fullclaimed7/10

   Milvus docs explicitly describe native full-text search that converts raw text into sparse embeddings automatically (BM25-style keyword search) without requiring a separate search engine or manual embedding generation, and Milvus Lite/Standalone/Distributed all share this feature per docs-17. This is a first-party documented capability integrated into the same client API used for vector search. Missing for 10: independent/hands-on validation of full-text search quality or relevance benchmarks, and community evidence specifically confirming it replaces dedicated search engines like Elasticsearch in production.

   • [claimed-docs] “it simplifies vector searches by accepting raw text input, automatically converting your text data into sparse embeddings without the need t…”
   • [claimed-docs] “it simplifies vector searches by accepting raw text input, automatically converting your text data into sparse embeddings without the need t…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”

   proof ↗⚑ flag

2. developerCombine dense vector search with keyword or sparse (BM25-style) signals in one hybrid query with fusion ranking

   weight 3 · round to Weaviate
   Weaviate✓fullcommunity9/10

   Weaviate's docs explicitly describe hybrid search combining vector and BM25 keyword search with two fusion algorithms (relativeScoreFusion, rankedFusion) run in parallel and merged into a final ranking, matching the story precisely. Community discussion confirms real-world usage of hybrid search fusion (with minor confusion over fusion algorithm internals, not a failure). Missing for 10: no independent benchmark or hands-on quality comparison of fusion ranking accuracy.

   • [claimed-docs] “Hybrid search combines vector search and keyword search (BM25) to leverage the strengths of both approaches.”
   • [claimed-docs] “Weaviate supports two strategies (`relativeScoreFusion` and `rankedFusion`) for combining vector and keyword search scores”
   • [claimed-docs] “A hybrid search runs both search types in parallel and combines their scores to produce a final ranking of results.”
   • [github] “It combines vector similarity search with keyword filtering, retrieval-augmented generation (RAG), and reranking in a single query interface…”
   • [community] “I feel like small formulas could clarify better these 2 fusion algorithms. I have read the article twice and checked some of the references …”

   proof ↗⚑ flag

   Milvus✓fullclaimed7/10

   Milvus docs explicitly describe full-text search that auto-converts text to sparse (BM25-style) embeddings, multi-vector search that runs multiple ANN searches simultaneously, and Milvus Lite covering 'sparse and dense vector search... multi-vector and hybrid_search,' confirming a combined dense+sparse hybrid query capability. Missing for 10: explicit documentation of fusion ranking strategies (e.g., RRF/weighted ranker names) and independent/hands-on corroboration of hybrid_search quality in practice.

   • [claimed-docs] “it simplifies vector searches by accepting raw text input, automatically converting your text data into sparse embeddings without the need t…”
   • [claimed-docs] “Milvus supports this by allowing search on multiple vector fields, conducting several Approximate Nearest Neighbor (ANN) searches simultaneo…”
   • [claimed-docs] “Milvus Lite shares the same API with Milvus Standalone and Distributed, and covers most of the features such as vector data persistence and …”

   proof ↗⚑ flag

Reranking

1. ml-engineerRerank search results with built-in or first-party-integrated reranking models

   weight 2 · round to Weaviate
   Weaviate~partialclaimed5/10

   Weaviate's GitHub README explicitly states it combines vector search, keyword filtering, RAG, and reranking in a single query interface, indicating built-in reranking support, but the evidence pack lacks first-party docs detailing specific reranker modules (e.g., Cohere, transformers) or configuration guidance. missing for 10: dedicated reranker-module docs, list of supported reranking providers, hands-on validation of reranking quality/behavior.

   • [github] “It combines vector similarity search with keyword filtering, retrieval-augmented generation (RAG), and reranking in a single query interface…”

   proof ↗⚑ flag

   Milvus—none0/10

   The evidence pack covers full-text/sparse search, multi-vector search, filtering, multi-tenancy, RBAC, and MCP integration, but contains no mention of reranking models—neither a built-in reranker nor a first-party reranking integration (e.g., cross-encoder or BGE-reranker support). Missing for 10: any documentation of a reranking API, built-in rerank function, or first-party reranker model integration and evidence of its use in search pipelines.

   ⚑ flag