
# Milvus

Vector database for similarity search and retrieval over embedding collections.

Canonical page: https://launchinyourcloud.com/directory/milvus/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Milvus

Vector database for similarity search and retrieval over embedding collections.

- Listing: https://launchinyourcloud.com/directory/milvus/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Milvus.
- Licensing model: open-source
- Installation: Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements.
- Architecture: Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services
- Operations: Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.
- Product website: https://milvus.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

Apache License 2.0 for upstream Milvus. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

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.


### Category fit

- databases-vector: Vector database for approximate nearest-neighbor retrieval over embeddings and associated metadata.

- ai-tools: Embedding storage and vector retrieval infrastructure for AI search and RAG applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/eks.md (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/azure.md (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://milvus.io/docs/gcp.md (checked 2026-11-12). 


### Cloud deployment evidence

- Milvus deployment on Amazon EKS (aws): https://milvus.io/docs/eks.md
  Official instructions provision Amazon EKS and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Milvus deployment on Azure Kubernetes Service (azure): https://milvus.io/docs/azure.md
  Official instructions provision Azure Kubernetes Service and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Milvus deployment on Google Kubernetes Engine (gcp): https://milvus.io/docs/gcp.md
  Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-10.

- Foundation and contributing community: https://github.com/milvus-io/milvus

- Current release maintenance: https://github.com/milvus-io/milvus/releases

### Sources

- Official installation and runtime: https://milvus.io/docs/install_standalone-docker.md

- Upstream project and capabilities: https://github.com/milvus-io/milvus

- Current upstream license: https://github.com/milvus-io/milvus/blob/master/LICENSE

### Licensing sources

- https://github.com/milvus-io/milvus/blob/master/LICENSE

### Infrastructure sources

- https://milvus.io/docs/install_standalone-docker.md


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. 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. Scope: Self-hosted Milvus core user authentication; federation unresolved. Source: https://milvus.io/docs/authenticate.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://milvus.io/docs/install_standalone-docker.md (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/milvus-io/milvus/master/scripts/standalone_embed.sh. Artifact reference: master script (moving; inspect its selected image).

- Minimum footprint / sizing: Documented. 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. Scope: Milvus 3.0.x standalone requirements as reviewed. Source: https://milvus.io/docs/prerequisite-docker.md (reviewed 2026-11-14).

- License pricing: Documented. 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/milvus-io/milvus/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream milvus-io/milvus release record; commercial editions and deployment packages may differ. Source: https://github.com/milvus-io/milvus/releases/tag/v3.0.6 (reviewed 2026-11-14).






