Chroma vs Qdrant
Of the 107 makers' products we know the vector database of, 18 chose Qdrant (17%) and 12 Chroma (11%); 1 uses both. Among the 42 launched in 2025, Chroma is in 17% and Qdrant in 19%. They're different kinds of tool, embedded / local-first and open-source vector store, so the counts don't measure the same choice. Chroma is the more common pick among Next.js products (6 vs 5). At our calculator's default usage, Chroma comes to $51 a month and Qdrant $103, at list prices. On GitHub, 4 public pull requests moved projects from Chroma to Qdrant, and 0 the other way.
Two sides of the vector database decision: embedded / local-first and open-source vector store. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- You're prototyping retrieval on your laptop, or want vectors in files with no server
Use it whenYou're still figuring out whether retrieval works for your use case.
Trade-offFor production you either run its server yourself or move to Chroma Cloud.
- You need an open-source store with heavy filtering or hybrid search, self-hosted or managed
Use it whenYour queries combine similarity with many filters, such as tenant, date and category.
Trade-offOne more service to deploy and keep in sync with your main database.
At a glance
| Used by | 12 makers' products · 87 open-source projects | 18 makers' products · 94 open-source projects |
|---|---|---|
| Cost at default usagevectors stored 1 million vectors, queries 1 million queries, vectors written or updated 500k writes | $51/mo Starter | $103/mo Standard (3 nodes, 0.5 vCPU / 4 GiB each) |
| Moved to it on GitHubpull requests since Oct 2024 | fewer than 3 | 4 from Chroma |
| Downloads | 257.3k/wk−4% vs npm | 810.5k/wk−13% vs npm |
| Pricing | Free and open source to self-host (Apache-2.0); Chroma Cloud is usage-based with free starting credits. · paid from Usage-based | Free and open source to self-host; Qdrant Cloud has a free tier plus usage-based paid plans. · paid from Usage-based, no minimum |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes · self-hostable |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for vector database.
| Framework | |||
|---|---|---|---|
| 6 | 5 | All 38 Next.js products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the vector database decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2024 | 4% 1 | 25% 7 | 28 |
| 2025 | 17% 7 | 19% 8 | 42 |
Cost as you grow
At 100k vectors Qdrant costs less ($0 vs $1.32); from about 500k vectors Chroma does ($15 vs $68); from about 5M vectors Qdrant does ($410 vs $1,093). They're different kinds of tool — embedded / local-first and open-source vector store — so the prices don't buy the same thing.
The numbers, plan by plan
| Vectors stored (1,536 dimensions, about 6 GB per million) | Chroma | Qdrant |
|---|---|---|
| 0.1 | $1.32 Starter | $0 Free |
| 0.5 | $15 Starter | $68 Standard (1 node, 1 vCPU / 8 GiB) |
| 1 | $51 Starter | $103 Standard (3 nodes, 0.5 vCPU / 4 GiB each) |
| 5 | $1,093 Starter | $410 Standard (3 nodes, 2 vCPU / 16 GiB each) |
| 10 | $4,281 Starter | $820 Standard (3 nodes, 4 vCPU / 32 GiB each) |
| 50 | $105,226 Starter | $4,374 Standard (2 nodes, 32 vCPU / 256 GiB each) |
| 100 | $419,999 Starter | $8,747 Standard (4 nodes, 32 vCPU / 256 GiB each) |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Chroma to Qdrant" or the reverse — real code changes, by developers in general rather than makers only.
- feat(rag_core): switch retriever backend from Chroma to Qdrant financ…Xeoyeon/Whyfi-v2 · 2026-08-14
- Migrate RAG vector storage from local Chroma to Qdrantseethygerald/myfinancialapp · 2026-05-24
- feat: migrate chroma to qdrantrobbypambudi/RAGforge · 2025-10-08
- Add Chroma DB support as an alternative to Qdranthadv/wisdomforge · 2025-03-27
What makers say
Makers on using it for vector database, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
Chroma makes it super easy to manage embeddings for AI apps. We love the open-source focus and how quickly it integrates into RAG pipelines.
Jeff (the founder) is incredible - super knowledgeable and I'm super bullish on the direction of the product. Let's go!
Blazing fast Vector Database, easy to implement, and stack it up especially for Docuspark.
After evaluating a bunch of Vector DBs to be our internal vector DB, we finally closed on QDrant because it was the one that scaled the best and had the best price performance ratio
Thanks to Qdrant, we utilize it as a vector database to store our knowledge base and uploaded file data. Our RAG would not be possible without it.
We evaluated a bunch of vector DBs—and Qdrant stood out for its blazing speed, filtering, and hybrid search. It's the unsung hero that lets our AI agents recall and reason across docs, CRMs, and conversations in milliseconds.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Open source and easy to self-host, with a simple API that gets embeddings stored quickly. PHHN
- Full-text and regex search sit alongside vector search, and collection forking suits changing code. trychroma.comHNHN 2HN 3
- Plugs quickly into RAG pipelines and local-first tools built on LangChain or Ollama. PHHNHN 2HN 3
Who uses each
What makers pair each with
Neither quite right?
See the whole vector database decision →Questions
Chroma or Qdrant: which do makers choose?
Of the 107 makers' products we know the vector database of, 18 chose Qdrant (17%) and 12 Chroma (11%); 1 uses both. Among the 42 launched in 2025, Chroma is in 17% and Qdrant in 19%. They're different kinds of tool, embedded / local-first and open-source vector store, so the counts don't measure the same choice. Chroma is the more common pick among Next.js products (6 vs 5). At our calculator's default usage, Chroma comes to $51 a month and Qdrant $103, at list prices. On GitHub, 4 public pull requests moved projects from Chroma to Qdrant, and 0 the other way. Choose Chroma if you're prototyping retrieval on your laptop, or want vectors in files with no server; choose Qdrant if you need an open-source store with heavy filtering or hybrid search, self-hosted or managed.
When should I pick Chroma over Qdrant?
Pick Chroma if: You're prototyping retrieval on your laptop, or want vectors in files with no server.
When should I pick Qdrant over Chroma?
Pick Qdrant if: You need an open-source store with heavy filtering or hybrid search, self-hosted or managed.
Which is cheaper, Chroma or Qdrant?
At vectors stored 1 million vectors, queries 1 million queries, vectors written or updated 500k writes: Chroma $51/mo (Starter), Qdrant $103/mo (Standard (3 nodes, 0.5 vCPU / 4 GiB each)), at list prices.
How do Chroma and Qdrant compare in cost as you grow?
At 100k vectors Qdrant costs less ($0 vs $1.32); from about 500k vectors Chroma does ($15 vs $68); from about 5M vectors Qdrant does ($410 vs $1,093). Cheapest usable plan at each scale, at list prices.
Are people switching from Chroma to Qdrant?
Public GitHub pull requests since 2024-10-02: 4 from Chroma to Qdrant.

