Milvus
Milvus is an open-source vector database built for GenAI applications. Install with pip, perform high-speed searches, and scale to tens of billions of vectors.
Start with the strongest matches, then expand or search the complete category.
Milvus is an open-source vector database built for GenAI applications. Install with pip, perform high-speed searches, and scale to tens of billions of vectors.
Search through billions of items for similar matches to any object, in milliseconds. It’s the next generation of search, an API call away.
Bring AI-native applications to life with less hallucination, data leakage, and vendor lock-in
Open-source PostgreSQL extension for vector similarity search and embeddings storage.
Build fast, reliable RAG, agents, and search engines with LanceDB— a multimodal vector database with native versioning and S3-compatible object storage.
The AI-native open-source embedding database for LLM applications
Native vector search in MongoDB Atlas — store embeddings alongside operational data, build RAG applications with $vectorSearch aggregation pipeline.
Build 10x faster with the first fully native Graph-Vector Database combining the power of graph and vector types natively in Rust to build RAG and AI applications easily
Vector similarity search built into Redis — HNSW and FLAT indexing, hybrid queries combining vector search with Redis data structures, sub-millisecond latency.
serverless vector and full-text search built on object storage: fast, 10x cheaper, and extremely scalable
Highly scalable distributed vector search engine for approximate nearest neighbor search, designed for Kubernetes deployments.
Qdrant is an Open-Source Vector Search Engine written in Rust. It provides fast and scalable vector similarity search service with convenient API.
Zilliz Cloud is a fully managed vector database and data service for AI applications. Its product page describes vector storage, indexing, and management for embeddings generated by machine-learning models, with deployment through AWS, GCP, or Azure Marketplace. The platform supports hybrid search across multiple vector fields, including multimodal, sparse-dense, and dense-text combinations. It also lists cosine, Euclidean, and inner-product similarity metrics, plus multiple consistency levels.
For buyers assessing deployment and operating-model options, Zilliz Cloud offers fully managed clusters and an opt-in Bring Your Own Cloud (BYOC) option. The pricing page presents Free, Standard, Enterprise, and Business Critical plans, alongside on-demand compute for lake-scale search and indexing jobs on zero-copy external data. The Free plan includes 5 GB of storage, 2.5 million vCUs per month, and up to five collections. Plan selection should account for the intended deployment model, cluster type, cloud provider, workload scale, and required security controls.
A useful evaluation starts by separating managed-service requirements from vector-search requirements. Zilliz Cloud is a managed offering built around vector search, with managed clusters, backup and restore, basic monitoring, and encryption for data in transit and at rest on its Standard plan. Its product page also describes AutoIndex, a Cardinal Search Engine, automated algorithm selection, tiered storage, and component-based horizontal scaling.
For workloads that need hybrid retrieval, Zilliz Cloud supports queries across multiple vector fields and combinations of multimodal, sparse-dense, and dense-text search. It lists filtered search, range search, grouping search, full-text search, text match, and query capabilities in its plan feature details. Buyers should verify which of these capabilities, support arrangements, and deployment controls are available for the exact plan and cluster configuration under consideration.
The vendor lists Free as a starting point for learning and personal projects. Standard is positioned for prototypes and testing environments; Enterprise for production applications; and Business Critical for regulated, mission-critical systems. These stated use cases are a practical starting point for comparing a managed platform with any alternative whose deployment, support, or governance model differs.
Zilliz Cloud describes itself as a cloud-native vector database with distributed architecture and on-demand scalability. Its managed-cluster offering is available on AWS, Google Cloud, and Azure, while BYOC is presented for organizations that prioritize custom infrastructure, data protection, or compliance. Dedicated deployment uses isolated, reserved environments and compute units (CUs), which Zilliz defines as a measure of computational resources for data processing.
The pricing page identifies three dedicated cluster types. Performance-optimized clusters are described for real-time applications with high concurrent traffic; Zilliz lists 2 million 768-dimensional vectors per CU, 500–1,500 search QPS, and 10 ms search latency. Capacity-optimized clusters list 8 million vectors per CU, 100–300 QPS, and 50–100 ms latency. Tiered-storage clusters list 40 million vectors per CU, 10–50 QPS, and 100–1,000 ms latency. These figures are based on evaluations of 768-dimensional vectors.
Architecture assessment should also cover scaling and availability. The plan table lists system-managed auto-scaling for serverless, manual scaling to 32 CUs for Standard Dedicated, and configurable auto-scaling for higher dedicated plans. Enterprise lists a 99.95% uptime SLA and multi-replica elastic scaling; the detailed table also lists 99.99% when multi-replica is enabled. Requirements for private networking, VPC peering, audit logs, SAML 2.0 SSO, granular RBAC, CMEK, or a global cluster should be checked against the selected plan.
Zilliz Cloud publishes several plan starting points and usage-based cluster references. The Free plan is listed at $0 and includes 5 GB of storage, 2.5 million vCUs per month, and up to five collections. Standard is listed from $0 per month for Serverless and from $126 per month for Dedicated. The page describes Standard as managed essentials for non-critical workloads, including core APIs, backup and restore, basic monitoring, and encryption in transit and at rest.
Enterprise Dedicated is listed from $197 per month. Zilliz associates this plan with a 99.95% uptime SLA, audit logs, SAML 2.0-based SSO, granular RBAC, multi-replica and elastic scaling, private endpoints, VPC peering, and included on-demand compute. Business Critical is shown as “Let’s Talk,” rather than with a public price; the pricing page describes a global cluster, high-level availability and disaster recovery, CMEK, full-path in-transit encryption, HIPAA-eligible features, and rapid incident response. A buyer considering that plan should confirm its quote, contract terms, included services, and applicable cloud configuration.
Dedicated list-price references are expressed per million vectors per month: from $63 for Performance-optimized, from $16 for Capacity-optimized, and from $5 for Tiered-storage. Zilliz ties those capacity figures to 768-dimensional-vector evaluations and advises that calculator estimates can differ from actual costs. The calculator asks for cloud provider, region, plan, cluster type, entity count, vector dimensions, vector data type, and mmap selection; it also offers $200 in free credits for evaluation. Annual-plan commitments can receive additional credits based on usage. Buyers should use the calculator and validate cost and performance with a proof of concept for their own vector dimensions, scalar fields, and workload.
Consider a different deployment approach when the capabilities required by the workload do not align with Zilliz Cloud’s managed plans. Zilliz positions Free for learning and personal projects, Standard for prototypes and testing environments, Enterprise for production applications, and Business Critical for regulated and mission-critical systems. A team needing a different operating model should compare how it will provide deployment, scaling, backup, monitoring, security, and incident support.
Zilliz Cloud may fit workloads that need managed vector-search infrastructure, hybrid search across sparse-dense or dense-text combinations, or cloud deployment on AWS, Google Cloud, or Azure. Its dedicated options provide performance-, capacity-, and tiered-storage configurations, while its BYOC option is intended for organizations prioritizing custom infrastructure, enhanced data protection, and compliance.
A change in platform or plan is also worth considering when requirements grow beyond the current configuration: for example, private networking, multi-replica availability, SAML 2.0 SSO, audit logs, CMEK, or a global cluster. The vendor’s plan table distinguishes these controls across plans, so buyers should map the exact requirement to the selected plan rather than assuming availability across all deployments.
Zilliz Cloud’s plan feature details list cross-cluster migration, including migration from free and serverless clusters, zero-downtime migration, migration from external sources, volume support, and high-speed data import. The page does not publish a general migration duration, data-format conversion procedure, or a supported compatibility guarantee for a particular destination. Those details should be confirmed for the source, destination, dataset size, and target plan.
Migration planning should include the collection design, vector dimensions, scalar fields, expected query patterns, required search modes, cloud region, and operational controls. Zilliz notes that cluster capacity estimates are based on vectors with primary keys only and that additional scalar fields such as IDs or labels can reduce capacity. Its calculator also collects vector dimensions and data type, which reinforces the need to validate the final configuration against the actual workload.
For a planned move within Zilliz Cloud, verify whether the chosen plan provides the needed migration path and availability controls. For a move to another system, confirm export and import methods, index and metadata mapping, validation criteria, downtime approach, and rollback process with the relevant vendors. Zilliz’s pricing page recommends a proof of concept using free credits to validate costs and performance; that can also help establish workload-specific acceptance criteria before a production change.
Zilliz Cloud is presented as a fully managed vector database and data service. Its Standard plan lists core APIs, backup and restore, basic monitoring, and encryption in transit and at rest. The product page also describes elastic managed clusters, automated upgrades, scaling, and monitoring. A self-managed option may have a different operating model, but this page does not establish its features, cost, licensing, or operational responsibilities.
A like-for-like price comparison cannot be made from Zilliz’s pricing page alone because it does not list another provider’s prices, usage units, plans, or contract terms. Zilliz lists Free at $0 with 5 GB storage and 2.5 million monthly vCUs; Standard from $0 per month for Serverless and from $126 per month for Dedicated; and Enterprise Dedicated from $197 per month. Compare the same vector dimensions, entity count, cloud region, cluster type, usage profile, and required controls before drawing a cost conclusion.
Yes. Zilliz Cloud describes hybrid search as querying across multiple vector fields and supporting multimodal, sparse-dense, and dense-text combinations. Its plan details also list vector search, filtered search, range search, grouping search, hybrid search, full-text search, text match, and query capabilities. Availability should be verified for the selected plan and deployment configuration.
Zilliz Cloud can be subscribed to through AWS, GCP, or Azure Marketplace. The pricing page lists AWS and Google Cloud for Free and Serverless, and AWS, Google Cloud, and Azure for dedicated plans. It also offers BYOC for organizations that prioritize custom infrastructure, enhanced data protection, and compliance, with the same features and experience as SaaS Dedicated clusters according to the vendor.
Zilliz’s calculator asks for cloud provider, region, pricing plan, cluster type, number of entities, vector dimensions, vector data type, and mmap selection. Dedicated reference capacities are based on 768-dimensional vectors: 2 million per CU for Performance-optimized, 8 million for Capacity-optimized, and 40 million for Tiered-storage. Zilliz notes that additional scalar fields can reduce capacity and that estimates may differ from actual costs, so workload-specific validation is appropriate.