Milvus vs Chroma

These two split on where the work lands. Milvus is an Apache-2.0 project built to scale out across Kubernetes for very large collections, and the person installing it carries the operations. Chroma starts as a pip package on a laptop and later points the same code at a usage-billed cloud, which suits prototypes and mid-sized apps better than billion-vector jobs. Chroma Inc. is a San Francisco company, while the Milvus pages we read name no country, so the ownership question differs too.

Vendors can pay for more visibility on this website, for example a higher place in a ranking or more room on a page. Commercial relationships can also affect which products we feature and how prominently. Every vendor link is marked the same, whatever the arrangement behind it. How that works.

01

Milvus and Chroma side by side

MilvusChroma
Our vector databases rank#6 of 12#3 of 12
Established inNot stated by the vendorUnited States
List price, 10 November 2026Software free under Apache-2.0 to self-host; hosted version bought separately as Zilliz CloudStarter at $0 a month with $5 credits, then metered per GiB written, stored and returned and per TiB queried; Team flat fee plus usage; Enterprise custom
Free tierYesYes
Open sourceYesYes
Self-hostableYesYes
Built forPlatform teams running very large collections on their own KubernetesDevelopers who want to prototype locally and move to a hosted database later
Not forSmall teams without anyone to run Kubernetes servicesTeams planning billions of vectors with strict uptime commitments

Both are reviewed in full in our vector databases ranking: Milvus and Chroma.

02

Where they differ

Milvus 1 · Chroma 3 · open 2
  1. 01

    From pip install to Kubernetes cluster

    Chroma installs with pip install chromadb, runs as a local database, and offers a client-server mode through chroma run. Milvus also has a pip route, called Milvus Lite, plus a Standalone mode for modest jobs. Its full distributed form is Kubernetes-native, and our fit notes call that real operational work. For a first afternoon with a vector store, Chroma asks for much less setup, while Milvus asks more in exchange for a heavier path later.

    Edge: Chroma

  2. 02

    Index types and the billion-vector ceiling

    The Milvus README lists HNSW, IVF, FLAT, SCANN and DiskANN indexes, GPU indexing, metadata filtering and hybrid search with sparse vectors. It describes separated compute and storage with horizontal scaling, and the project tagline targets billions of vectors. Chroma offers serverless vector, hybrid and full-text search in its cloud, but our notes say it fits prototypes and mid-sized apps rather than billion-vector workloads. On sheer scale and index variety, Milvus is the stronger pick on paper.

    Edge: Milvus

  3. 03

    Chroma Cloud's three meters and the $5 start

    Chroma's Starter plan costs nothing per month and includes $5 of free credits, then bills usage per GiB written, per GiB stored each month, per TiB queried and per GiB of network returned. Team adds a flat monthly fee plus usage, with $100 of credits. The Team fee itself is not in the facts we captured, so confirm it before budgeting. Milvus itself costs nothing to run yourself, but the servers, upgrades and staff time are yours to fund.

    Depends on the buyer

  4. 04

    Who holds the Milvus roadmap

    Milvus sits under the LF AI & Data Foundation under an Apache-2.0 licence, with Zilliz named as the major contributor. Zilliz also sells the managed service, Zilliz Cloud, in Serverless, Dedicated and BYOC options. Our own notes flag that roadmap pull comes from the company that sells the hosted version. Chroma's repository is also Apache-2.0, but Chroma Inc. both writes the library and sells Chroma Cloud, so the two share this trade-off and neither is a neutral community product.

    Depends on the buyer

  5. 05

    Starter caps and Enterprise-only isolation

    Chroma's Starter plan allows 10 databases and 10 team members with community Slack, and Team lifts that to 100 databases and 30 members with Slack support and SOC II. Single-tenant clusters, bring-your-own-cloud clusters and SLAs sit on Enterprise, which is custom priced. Milvus has no plan caps because you run it, and BYOC appears only through Zilliz Cloud. Chroma is clearer about what each tier includes, and the caps are real limits to plan around.

    Edge: Chroma

  6. 06

    Named company and country

    Chroma's terms of service name Chroma Inc. at 2261 Market Street #4728, San Francisco, CA 94114, and the privacy policy repeats that address. For Milvus, neither the repository nor the README states a company address or country, because a foundation hosts the project. That leaves country as not stated for the project, with Zilliz as a separate vendor for hosting. Buyers who need a named contracting party for a contract get one from Chroma straight away.

    Edge: Chroma

03

When neither fits

If you want a vector database with a managed European-hosted path or tighter integration with a relational store, neither is the obvious fit. Qdrant and pgvector are the two alternatives in our vector databases category worth checking first.

04

Milvus or Chroma: questions

3 answers
Can Milvus run without Kubernetes at all?

Yes, for smaller jobs. The README describes Standalone mode and Milvus Lite, which installs with pip. The full distributed architecture is the part that is Kubernetes-native.

What does leaving Chroma's free tier cost in practice?

The Starter plan has $5 of free credits, after which usage is billed per GiB written, stored and returned and per TiB queried.

Team adds a flat monthly fee and $100 of credits. The exact Team fee is not in our captured facts, so check the pricing page.

Is the Milvus managed service made by the same people as the database?

Zilliz is named as the major contributor to Milvus and sells Zilliz Cloud as the managed service. The project itself sits under the LF AI & Data Foundation. So the hosted product and the project are separate, but closely linked.

—

Sources

Checked 10 November 2026
  • Milvus GitHub repository: Apache-2.0 licence, foundation hosting, Zilliz as major contributor, no stated company address.
  • Milvus project site: project home of the open-source vector database and its managed counterpart.
  • Milvus README: index types, GPU indexing, hybrid search and the Zilliz Cloud deployment options.
  • Chroma pricing page: credits, usage meters, database and member caps, Team features, Enterprise isolation options.
  • Chroma README: pip install, chroma run server mode, Chroma Cloud search types.
  • Chroma terms of service: Chroma Inc. as contracting party with San Francisco address.
—

More comparisons