Softwr

Databases · head to head

Chroma vs Milvus

Chroma logo

Chroma

Databases

Apache 2.0 vector and full-text search engine that runs as an embedded library, a single server or a distributed cloud service.

From
Free
Free plan
Yes
Milvus logo

Milvus

Machine Learning

Open-source vector database for scalable similarity search

From
Free
Free plan
Yes

The short version

  • Milvus is an open-source vector database.
  • Milvus is free; Chroma starts at $250/mo.
  • Only Chroma lists embedded mode; only Milvus lists billion-scale vectors.
  • Where Milvus falls short: vector dimensions are capped at 32,768.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Chroma and Milvus actually diverge.

Attributes where Chroma and Milvus differ
AttributeChromaMilvus
Pricing modelUsage-basedFreemium
PlatformsWebLinux, macOS, Windows, Web
CategoryDatabasesMachine Learning

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Chroma.

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Chroma

  • Embedded mode
  • Single-node server
  • Distributed architecture
  • Vector search
  • Full-text search
  • Metadata filtering
  • Consistent API across modes
  • Multi-language clients

Only in Milvus

  • Billion-scale vectors
  • Multiple index types
  • GPU acceleration
  • Hybrid search
  • Data partitioning
  • PyTorch
  • TensorFlow
  • Hugging Face

What people use each for

The jobs each tool is most often brought in to do.

Chroma

  • Prototyping retrieval-augmented generation where the priority is having a working index in minutes rather than choosing a permanent storenot Milvus
  • Agent memory in a single application process, where an embedded store avoids adding a network dependencynot Milvus
  • A departmental search application under roughly ten million records where one server is sufficient and simplicity is worth more than headroomnot Milvus
  • Local and CI testing of retrieval code with the same client library used in productionnot Milvus

Milvus

  • Self hosting a vector database for semantic searchnot Chroma
  • Storing and querying embeddings for retrieval augmented generationnot Chroma
  • Similarity search over images, audio or text at scalenot Chroma

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Chroma

  • On a single node, available memory sets a hard upper bound on collection size, roughly 245,000 records per gigabyte of RAM at 1024 dimensions, so capacity planning is a memory purchase and the ceiling arrives without warning
  • Single-node queries parallelise only up to the number of vCPUs, after which requests queue and latency rises linearly with concurrency, so throughput problems appear as a slow application rather than as errors
  • The distributed deployment behind Chroma Cloud is a different architecture from the embedded library, so latency, consistency and failure behaviour observed in a local prototype do not predict production behaviour
  • The open source server has no built-in authentication or multi-tenancy worth relying on, so a self-hosted deployment needs its own auth proxy and network controls before anything untrusted can reach it
  • The project has moved quickly through major internal rewrites and version changes, so upgrades have historically involved data migrations and client changes, and pinning versions is necessary rather than cautious

Milvus

  • Vector dimensions are capped at 32,768
  • A collection is limited to 64 fields, 1,024 partitions and 16 shards
  • Only 1 index is allowed per field
  • Search returns at most 16,384 vectors as top-k, and nq is capped at 16,384
  • Input and output per RPC is capped at 64 MB for insert, search and query
  • VARCHAR values are limited to 65,535 characters
  • Data loaded into query nodes cannot exceed 90% of available memory
  • An instance supports at most 65,536 collections

Pricing, plan by plan

Chroma

Free
  • StarterFree
    • 10 databases
    • 10 team members
    • Community Slack access
  • Team$250/mo
    • 100 databases
    • 30 team members
    • $100 in included credits
  • EnterpriseOn request
    • Unlimited databases
    • Unlimited team members
    • Dedicated support

Milvus

Free
  • Open SourceFree
    • Full features
    • Self-hosted
    • Community support
  • Zilliz CloudFree
    • Managed service
    • Free tier available

Which should you pick?

Choose Chroma if

  • You need embedded mode.
  • You want to start without paying.
  • You also want single-node server.

Choose Milvus if

  • You need billion-scale vectors.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Web.
  • You also want multiple index types.

Questions people ask

Is Chroma or Milvus better?
Neither clearly leads. Chroma starts at Free and Milvus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Chroma or Milvus?
Chroma starts at Free and Milvus at Free.
Does Chroma or Milvus run on more platforms?
Chroma runs on Web. Milvus runs on Linux, macOS, Windows, Web.
Can I use Chroma for free?
Both have a free tier, so you can try either at no cost before committing.
What is Chroma best used for?
Chroma is most often used for prototyping retrieval-augmented generation where the priority is having a working index in minutes rather than choosing a permanent store, agent memory in a single application process, where an embedded store avoids adding a network dependency, a departmental search application under roughly ten million records where one server is sufficient and simplicity is worth more than headroom, local and ci testing of retrieval code with the same client library used in production. Of those, prototyping retrieval-augmented generation where the priority is having a working index in minutes rather than choosing a permanent store and agent memory in a single application process, where an embedded store avoids adding a network dependency are not what Milvus is typically brought in for.
What can Chroma do that Milvus cannot?
Chroma covers Embedded mode, Single-node server, Distributed architecture, Vector search. Milvus covers Billion-scale vectors, Multiple index types, GPU acceleration, Hybrid search.

Answered from the vendors’ own pages

Chroma: Do I need to run a server?

No. Chroma runs embedded in your process with persistence to a local directory, which is how most projects start. The server and distributed modes exist for when multiple clients or larger collections require them.

Milvus: How much does Milvus cost?

Milvus is open-source and free to use and modify. The self-hosted version has no licensing cost. Zilliz Cloud (the managed SaaS version) does not publish pricing on the website.

Source
Chroma: How large can a single node get?

The project puts single-node deployments at fewer than about ten million records across a handful of collections, with collection size bounded by system memory at roughly 245,000 records per gigabyte at 1024 dimensions.

Milvus: Is there a free or open-source version of Milvus?

Yes, Milvus is fully open-source and available for free. Milvus Lite is a lightweight option for learning and prototyping that can be installed via pip.

Source
Chroma: Is Chroma Cloud the same software?

It is the same API and project, but the distributed deployment is a different architecture, using independent services, object storage and SSD caches rather than a single process. Behaviour under load differs accordingly.

Milvus: Does Milvus offer a managed cloud service?

Yes, Zilliz Cloud is a fully managed Milvus cloud offering with serverless and dedicated cluster options. Pricing must be requested from the company as it is not listed on the public website.

Source
Chroma: How does it compare with pgvector?

pgvector keeps vectors in a Postgres database you already operate, with SQL, joins and transactions. Chroma is a dedicated retrieval engine with a lower setup cost and a retrieval-shaped API. If you already run Postgres, pgvector removes a system; if you do not, Chroma removes a decision.

Chroma: What licence is it under?

Apache 2.0, which permits self-hosting and embedding in commercial products without a competing-use restriction.

Share

Related pages

Other head to heads