Rank #2 of 7 in Vector Databases & Memory Stores
Access
Install
Try itExperimental
See what an agent can do with Milvus before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$python3 -c 'from pymilvus import MilvusClient; c = MilvusClient("/tmp/pa-milvus-probe.db"); c.create_collection("pa_probe", dimension=8); print("PA_PROBE_OK", c.list_collections())'recorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Data lifecycle — stories about data lifecycle in this arenaData lifecycleevidence →
Stories about data lifecycle in this arena
Deployment modes — stories about deployment modes in this arenaDeployment modesevidence →
Stories about deployment modes in this arena
Embeddings pipeline — stories about embeddings pipeline in this arenaEmbeddings pipelineevidence →
Stories about embeddings pipeline in this arena
Filtering metadata — stories about filtering metadata in this arenaFiltering metadataevidence →
Stories about filtering metadata in this arena
Multi tenancy scale — stories about multi tenancy scale in this arenaMulti tenancy scaleevidence →
Stories about multi tenancy scale in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Performance latency — stories about performance latency in this arenaPerformance latencyevidence →
Stories about performance latency in this arena
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Sdk integrations — stories about sdk integrations in this arenaSdk integrationsevidence →
Stories about sdk integrations in this arena
Search quality hybrid — stories about search quality hybrid in this arenaSearch quality hybridevidence →
Stories about search quality hybrid in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 2 free · 0 paid · 0 enterprise · 27 not stated in evidence
Follow the green: where the map greys out is where Milvus stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Machine-readable spec · Versioning policy · Official CLI
Subscribe to events via webhooks
—–
Build against official SDKs
✓9/10
Issue scoped/least-privilege API credentials for an agent
~5/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
✓7/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—0/10
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
—0/10
Set up automations that run autonomously in the background
n/an/a
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Data lifecycle — stories about data lifecycle in this arenaData lifecycle
Stories about data lifecycle in this arena
Deployment modes — stories about deployment modes in this arenaDeployment modes
Stories about deployment modes in this arena
Embeddings pipeline — stories about embeddings pipeline in this arenaEmbeddings pipeline
Stories about embeddings pipeline in this arena
Filtering metadata — stories about filtering metadata in this arenaFiltering metadata
Stories about filtering metadata in this arena
Multi tenancy scale — stories about multi tenancy scale in this arenaMulti tenancy scale
Stories about multi tenancy scale in this arena
Scaling
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Performance latency — stories about performance latency in this arenaPerformance latency
Stories about performance latency in this arena
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Sdk integrations — stories about sdk integrations in this arenaSdk integrations
Stories about sdk integrations in this arena
Search quality hybrid — stories about search quality hybrid in this arenaSearch quality hybrid
Stories about search quality hybrid in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Xcommunity | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 7/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | full | 9/10 | Xcommunity | |
Run approximate nearest-neighbor similarity search over embeddings with configurable distance metrics C Core search | developer | Search quality hybrid — stories about search quality hybrid in this arenaSearch quality hybrid | 3 | full | 8/10 | Xcommunity | |
Combine dense vector search with keyword or sparse (BM25-style) signals in one hybrid query with fusion ranking C Hybrid | developer | Search quality hybrid — stories about search quality hybrid in this arenaSearch quality hybrid | 3 | full | 7/10 | Cclaimed | |
Filter vector search by structured metadata conditions without wrecking recall or latency C Filtering | developer | Filtering metadata — stories about filtering metadata in this arenaFiltering metadata | 3 | full | 7/10 | Cclaimed | |
Isolate many tenants cheaply using namespaces, partitions, or per-tenant collections with documented limits C Tenancy | platform-engineer | Multi tenancy scale — stories about multi tenancy scale in this arenaMulti tenancy scale | 3 | partial | 6/10 | Cclaimed | |
Have the database generate embeddings at ingest and query time using built-in or configured model providers, instead of running a separate embedding pipeline C Embeddings | ml-engineer | Embeddings pipeline — stories about embeddings pipeline in this arenaEmbeddings pipeline | 3 | partial | 5/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 4/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Run the database embedded in-process or as a lightweight local instance for development and small workloads C Local dev | developer | Deployment modes — stories about deployment modes in this arenaDeployment modes | 2 | full | 9/10 | Xcommunity | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | full | 8/10 | Tprobed | |
Scale beyond one node with sharding or distributed deployment C Scaling | platform-engineer | Multi tenancy scale — stories about multi tenancy scale in this arenaMulti tenancy scale | 2 | full | 8/10 | Xcommunity | |
Enforce granular access control (API keys, roles, per-collection permissions) on database operations C Tenancy | platform-engineer | Multi tenancy scale — stories about multi tenancy scale in this arenaMulti tenancy scale | 2 | full | 7/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | fullfree | 7/10 | Tprobed | |
Run keyword/full-text search over documents inside the database without bolting on a separate search engine C Hybrid | developer | Search quality hybrid — stories about search quality hybrid in this arenaSearch quality hybrid | 2 | full | 7/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 6/10 | Xcommunity | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 5/10 | Cclaimed | |
Express rich filter conditions (ranges, geo, nested boolean logic, array membership) in queries C Filtering | developer | Filtering metadata — stories about filtering metadata in this arenaFiltering metadata | 2 | partial | 5/10 | Cclaimed | |
Build against official SDKs in the major languages (Python, TypeScript, Go, Java) G Sdks | developer | Sdk integrations — stories about sdk integrations in this arenaSdk integrations | 2 | partial | 4/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Xcommunity | |
Plug the database into RAG and agent frameworks (LangChain, LlamaIndex, etc.) through maintained first-class integrations C Integrations | ml-engineer | Sdk integrations — stories about sdk integrations in this arenaSdk integrations | 2 | partial | 3/10 | Tprobed | |
See published benchmarks or measured latency/recall numbers backing the database's performance claims C Benchmarks | platform-engineer | Performance latency — stories about performance latency in this arenaPerformance latency | 2 | disputed | 3/10 | Dcontradicted | |
Tune index parameters (HNSW graph settings, index types) to trade recall against latency and memory C Index tuning | ml-engineer | Performance latency — stories about performance latency in this arenaPerformance latency | 2 | partial | 3/10 | Xcommunity | |
Enable vector quantization or compression to cut memory and storage cost with a documented accuracy trade-off C Index tuning | ml-engineer | Performance latency — stories about performance latency in this arenaPerformance latency | 2 | none | 0/10 | ||
Pay serverless usage-based pricing with transparent per-unit costs instead of provisioning fixed clusters G Pricing | developer | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 2 | none | 0/10 | ||
Replicate data across nodes or zones for high availability with a documented consistency model C Scaling | platform-engineer | Multi tenancy scale — stories about multi tenancy scale in this arenaMulti tenancy scale | 2 | none | 0/10 | ||
Upsert and delete records continuously and have changes reflected in search results quickly, with documented freshness/consistency behavior C Freshness | developer | Data lifecycle — stories about data lifecycle in this arenaData lifecycle | 2 | none | 0/10 | ||
Use a fully managed cloud version of the database with programmatic provisioning C Managed cloud | developer | Deployment modes — stories about deployment modes in this arenaDeployment modes | 2 | none | 0/10 | ||
Back up collections with snapshots and restore them C Backup | platform-engineer | Data lifecycle — stories about data lifecycle in this arenaData lifecycle | 2 | none | untested | none yet | |
Bulk-import and bulk-export vectors plus metadata in documented formats C Portability | developer | Data lifecycle — stories about data lifecycle in this arenaData lifecycle | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Rerank search results with built-in or first-party-integrated reranking models C Reranking | ml-engineer | Search quality hybrid — stories about search quality hybrid in this arenaSearch quality hybrid | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Prototype on a meaningful free tier before paying anything G Pricing | developer | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 1 | fullfree | 8/10 | Cclaimed | |
Deploy to production on Kubernetes with an official Helm chart or operator C Self managed | platform-engineer | Deployment modes — stories about deployment modes in this arenaDeployment modes | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 32 stories with headroom
What would move Milvus’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
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.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Missing: any documentation of event-driven triggers, webhook/callback mechanisms, or rule-based automation tied to database events.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
The evidence pack contains no explicit privacy/data-usage policy addressing whether Milvus or its cloud offering (Zilliz) uses customer data to train AI models.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
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.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
Missing: any mention of a dedicated Milvus CLI, its command set, installation, or documentation.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
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.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
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.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
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.).
Showing the top 8 of 32 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map4 surfaces · 30 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
GitHub README28 stories
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Run the database embedded in-process or as a lightweight local instance for development and small workloads
- Have the database generate embeddings at ingest and query time using built-in or configured model providers, instead of running a separate embedding pipeline
- Filter vector search by structured metadata conditions without wrecking recall or latency
- Express rich filter conditions (ranges, geo, nested boolean logic, array membership) in queries
- Scale beyond one node with sharding or distributed deployment
- Enforce granular access control (API keys, roles, per-collection permissions) on database operations
- Isolate many tenants cheaply using namespaces, partitions, or per-tenant collections with documented limits
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- See published benchmarks or measured latency/recall numbers backing the database's performance claims
- Prototype on a meaningful free tier before paying anything
- Choose where my data is stored (region/residency)
- Control data retention and deletion
- Plug the database into RAG and agent frameworks (LangChain, LlamaIndex, etc.) through maintained first-class integrations
- Build against official SDKs in the major languages (Python, TypeScript, Go, Java)
- Run approximate nearest-neighbor similarity search over embeddings with configurable distance metrics
- Run keyword/full-text search over documents inside the database without bolting on a separate search engine
- Combine dense vector search with keyword or sparse (BM25-style) signals in one hybrid query with fusion ranking
Hacker News9 stories
- Build against official SDKs
- Perform bulk operations across many items at once
- Run the database embedded in-process or as a lightweight local instance for development and small workloads
- Scale beyond one node with sharding or distributed deployment
- Self-host the core product
- See published benchmarks or measured latency/recall numbers backing the database's performance claims
- Tune index parameters (HNSW graph settings, index types) to trade recall against latency and memory
- Control data retention and deletion
- Run approximate nearest-neighbor similarity search over embeddings with configurable distance metrics
llms.txt2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$python3 -c 'from pymilvus import MilvusClient; c = MilvusClient("/tmp/pa-milvus-probe.db"); c.create_collection("pa_probe", dimension=8); print("PA_PROBE_OK", c.list_collections())'reproduced$ python3 -c 'from pymilvus import MilvusClient; c = MilvusClient("/tmp/pa-milvus-probe.db"); c.create_collection("pa_probe", dimension=8); print("PA_PROBE_OK", c.list_collections())'
PA_PROBE_OK ['pa_probe']
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
7 of 14 testable claims verified · 2 contradicted → integrity 21/100
16 distinct capability claims found in Milvus’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
7
Verified
5
Unverified
2
Contradicted
17
Undersold
Verified (10)
“Milvus is an open-source vector database suitable for everything from a notebook demo to web-scale search”
“Milvus is an open-source vector database suitable for everything from a notebook demo to web-scale search”
“Create a local Milvus database instantly by instantiating a MilvusClient pointed at a local file”
Run the database embedded in-process or as a lightweight local instance for development and small workloadsfullproof ↗
“An MCP server lets AI apps run vector search, manage collections, and retrieve data via natural-language commands”
“Same client-side code runs Milvus Lite on a laptop, Standalone in Docker, or Distributed on Kubernetes at billion-scale”
Run the database embedded in-process or as a lightweight local instance for development and small workloadsfullproof ↗
“Milvus scaled from billion-scale vectors in 2022 to tens of billions in 2023 with consistent stability”
Scale beyond one node with sharding or distributed deploymentfullproof ↗
“Official pymilvus Python SDK provides a MilvusClient for building applications”
“Milvus Lite shares the same API as Standalone/Distributed and covers CRUD, sparse/dense search, filtering, and hybrid search”
Run the database embedded in-process or as a lightweight local instance for development and small workloadsfullproof ↗
“Milvus Lite is a lightweight Python library ideal for quick prototyping in notebooks or running on edge devices”
Run the database embedded in-process or as a lightweight local instance for development and small workloadsfullproof ↗
“Client search API accepts a batch of query vectors and a result limit for ANN search”
Run approximate nearest-neighbor similarity search over embeddings with configurable distance metricsfullproof ↗
Unverified (5)
“Accepts raw text input and automatically converts it to sparse embeddings without manual embedding generation”
Have the database generate embeddings at ingest and query time using built-in or configured model providers, instead of running a separate embedding pipelinepartialproof ↗
“Supports searching across multiple vector fields by running several ANN searches simultaneously”
Combine dense vector search with keyword or sparse (BM25-style) signals in one hybrid query with fusion rankingfullproof ↗
“Search requests can include metadata filters applied before ANN search to shrink the search scope”
Filter vector search by structured metadata conditions without wrecking recall or latencyfullproof ↗
“Offers four multi-tenancy strategies with different scalability/isolation/flexibility trade-offs”
Isolate many tenants cheaply using namespaces, partitions, or per-tenant collections with documented limitspartialproof ↗
“RBAC lets admins finely control user operations at collection, database, and instance levels”
Enforce granular access control (API keys, roles, per-collection permissions) on database operationsfullproof ↗
Contradicted (2)
“Same client-side code runs Milvus Lite on a laptop, Standalone in Docker, or Distributed on Kubernetes at billion-scale”
Deploy to production on Kubernetes with an official Helm chart or operatornone
“Milvus delivers 30%-70% better performance than FAISS and HNSWLib per vendor benchmarks”
See published benchmarks or measured latency/recall numbers backing the database's performance claimsdisputedproof ↗
Undersold (17)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIfullproof ↗
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Test against a sandbox environment without touching production datafullproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Express rich filter conditions (ranges, geo, nested boolean logic, array membership) in queriespartialproof ↗
Do everything through the API that I can do in the UIfullproof ↗
Export all of my data in open formats and leavepartialproof ↗
Tune index parameters (HNSW graph settings, index types) to trade recall against latency and memorypartialproof ↗
Prototype on a meaningful free tier before paying anythingfullproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Plug the database into RAG and agent frameworks (LangChain, LlamaIndex, etc.) through maintained first-class integrationspartialproof ↗
Build against official SDKs in the major languages (Python, TypeScript, Go, Java)partialproof ↗
Run keyword/full-text search over documents inside the database without bolting on a separate search enginefullproof ↗
Claims outside our story set (1)
Real capability claims found in Milvus’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Supports a Standalone deployment mode for single-machine setups”
source ↗
Pricing signals
- $63per 1M vectors/monthpay-as-you-goPerformance-optimized dedicated cluster ratesource ↗as of 2026-09-07
- $16per 1M vectors/monthpay-as-you-goCapacity-optimized dedicated cluster ratesource ↗as of 2026-09-07
- $5per 1M vectors/monthpay-as-you-goTiered-storage dedicated cluster ratesource ↗as of 2026-09-07
- $126per GB-monthpay-as-you-goStandard plan dedicated rate per GB of storagesource ↗as of 2026-09-07
- $197per month (entry plan)entry planEnterprise plan starting dedicated pricesource ↗as of 2026-09-07
- freeper GB-monthfree tierFree tier includes 5 GB storage and 2.5M vCUs per month at no costsource ↗as of 2026-09-07
Extracted verbatim from the vendor’s own pricing page — hover a figure for the exact quote.
Business model
Apache-2.0 open-source vector database under LF AI & Data, free to self-host from laptop (Milvus Lite) to cluster; Zilliz Cloud sells the managed version with free, serverless, and dedicated tiers.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
