Milvus
Vector database for similarity search and retrieval over embedding collections.
3 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements.
Runs in
Documented customer environment
Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Milvus deployment on Amazon EKS ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Milvus deployment on Azure Kubernetes Service ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Milvus deployment on Google Kubernetes Engine ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements. |
|---|---|
| Infrastructure | Servers / containers Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. |
| Licensing model | Open Source / Open Core Apache License 2.0 for upstream Milvus. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms. |
| License | Apache License 2.0 for upstream Milvus. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The current core authentication guide uses username/password credentials and SDK token fields with explicitly enabled authorization. It does not establish native SAML/OIDC federation or automatic IdP/group mapping. Hosted Zilliz console SSO is a different deployment; confirm an upstream integration before relying on it.
Self-hosted Milvus core user authentication; federation unresolved · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official standalone Docker guide links a script fetched from master. Its image selection moves and its upgrade command does not validate arbitrary version transitions; inspect the script and use matching versioned Compose when required.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (master script (moving; inspect its selected image)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The standalone requirements specify 8 GB RAM, recommend 16 GB and recommend at least 4 CPU cores with a supported SIMD instruction set. Dataset/index size and storage performance govern actual resources; distributed requirements differ.
Milvus 3.0.x standalone requirements as reviewed · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate.
Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was v3.0.6, published 2026-11-11. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream milvus-io/milvus release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Current installation scripts can track a different image than a selected stable release; use versioned configurations for reproducibility. Model inference and embedding generation are separate workloads. Managed Zilliz offerings are outside this listing.
Community & maintenance
Milvus documents governance under the LF AI & Data Foundation with Zilliz as a major contributor. Its public release stream records continuing October 2026 maintenance.
Category fit
- Databases & vector
- Vector database for approximate nearest-neighbor retrieval over embeddings and associated metadata.
- AI tools & infrastructure
- Embedding storage and vector retrieval infrastructure for AI search and RAG applications.
Compare within Databases & vector
- Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
- AWS
- Azure
- Alibaba Cloud
- ClickHouse BYOCManaged analytical database with its data plane in your cloud account.
- AWS
- Azure
- Google Cloud
- CockroachDB BYOCVendor-managed CockroachDB service deployed into the customer's AWS, Azure or Google Cloud account.
- AWS
- Azure
- Google Cloud
- Couchbase Server Enterprise EditionSelf-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.
- AWS
- Azure
- Google Cloud
- Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
- Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
- Meilisearch Community EditionSelf-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.
- AWS
- Google Cloud
- DigitalOcean
- Neo4j Self-ManagedSelf-managed graph database available in open-source Community and commercial Enterprise editions.
- AWS
- Azure
- Google Cloud
Showing 8 of 18 other listings in Databases & vector. These products address related workflows; read their category-fit notes before comparing scope. See all of Databases & vector →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation and runtime ↗milvus.io
- Upstream project and capabilities ↗github.com
- Current upstream license ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Milvus deployment on Amazon EKS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Official instructions provision Amazon EKS and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
- Milvus deployment on Azure Kubernetes Service ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Official instructions provision Azure Kubernetes Service and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
- Milvus deployment on Google Kubernetes Engine ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
- Milvus deployment on Amazon EKS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Foundation and contributing community ↗github.com
- Current release maintenance ↗github.com