All companies
technology

Chroma pricing

trychroma.com facts checked analysis reviewed
Quick summary
In this page
AI Summary
  • Chroma's core database is open-source (Apache-2.0) and free to self-host with pip install; the company monetizes the managed Chroma Cloud.
  • Chroma Cloud is true serverless: $0/month base on the Starter plan, $5 in free credits, then 100% usage-based pricing with no minimum spend and scale-to-zero.
  • Four usage dimensions: $2.50 per GiB written, $0.33 per GiB-month stored, $0.0075 per TiB queried, and $0.09 per GiB of network egress returned.
  • The Team plan adds $250/month (with $100 of included credits that do not roll over) for 100 databases, 30 seats, Slack support, SOC II and volume discounts; Enterprise is custom with single-tenant/BYOC clusters and SLAs.
  • Chroma Cloud separates storage and compute over S3 object storage (the Rust-based 'Chroma Distributed' engine), which is what lets pricing start at $0 and scale linearly rather than charging for an always-on pod.
Pricing summary
Chroma 2026 — Pricing overview
Open-source self-host is free; Chroma Cloud Starter is $0/mo + usage; Team adds a $250/mo platform fee; Enterprise is sales-led.
Open source (self-host)
Free
Teams running their own infrastructure
Cloud — Team
$250 /mo + usage
Production teams that need support & compliance
Cloud — Enterprise
Custom
Large orgs prioritizing security & scale
Usage dimensions (all plans): $2.50/GiB written · $0.33/GiB-mo stored · $0.0075/TiB queried · $0.09/GiB egress. Verified June 2026 from trychroma.com/pricing.

About

Chroma is the open-source search and retrieval database for AI applications — the storage layer behind RAG pipelines, agents, and semantic search. Founded in 2022 by Anton Troynikov and Jeff Huber, it became one of the most-adopted open-source vector databases during the 2023 LLM wave (~27k GitHub stars), spread largely through a pip install chromadb developer-first distribution and deep LangChain/LlamaIndex integration.

The company raised an $18M seed in April 2023 (led by Quiet Capital, ~$75M valuation) and spent over a year building a managed counterpart. Chroma Cloud — a fully-managed, serverless version backed by a Rust engine called Chroma Distributed running on S3 object storage — entered private preview in 2024 and reached general availability in August 2025. The open-source engine remains free under Apache-2.0; the cloud is how Chroma monetizes.

For the most current information on Chroma’s pricing and market position, visit Chroma.


Pricing summary : How Chroma’s pricing model works

Chroma runs a two-track model. The open-source database is free — you pip install chromadb, run it embedded or self-hosted, and pay only for your own infrastructure, with no feature gating. Chroma Cloud is pure usage-based: the Starter plan has a $0/month base with $5 in free credits, after which you pay only for what you consume across four dimensions — data written, data stored, data queried, and network egress. There is no per-seat fee, no provisioned-cluster fee, and no minimum spend.

The four metered dimensions are flat and published:

DimensionRate
Write$2.50 per GiB written
Storage$0.33 per GiB per month
Query$0.0075 per TiB queried
Network$0.09 per GiB returned (egress)

Above the free Starter tier, the Team plan adds a $250/month platform fee (with $100 of included usage credits that do not roll over) for higher limits, Slack support, SOC II and volume discounts. Enterprise is custom — single-tenant or BYOC clusters, dedicated support, and SLAs.

What makes this different: Chroma bills on data movement and footprint, not on a provisioned pod or per-query unit alone. Because storage and compute are separated over S3, idle databases scale to zero and cost effectively nothing — so a prototype can live inside the $5 credit while a heavy workload scales linearly. That “start at $0, no minimum” stance is the explicit contrast to the fifty-dollar-a-month minimum Pinecone introduced in September 2025.


Pricing by product

TierPriceIncludedKey mechanics
Open source (self-host)Free (Apache-2.0)Full engine, no gatingYou run it; pay your own compute
Cloud — Starter$0/mo + usage$5 credits · 10 DBs · 10 seatsPure usage, no minimum, scale-to-zero
Cloud — Team$250/mo + usage$100 credits (no rollover) · 100 DBs · 30 seatsSlack support, SOC II, volume discounts
Cloud — EnterpriseCustomUnlimited DBs & seatsSingle-tenant/BYOC clusters, SLAs

Sales motions across products: open source and Starter are fully self-serve / PLG; Team is self-serve with a higher platform fee; Enterprise is sales-led (“Get in touch”). The same four usage rates apply across every paid tier.


Hidden costs : What Chroma users actually pay

The headline is “$0/month,” but real-world cost is the sum of four usage meters — and the one buyers underestimate is network egress ($0.09/GiB returned), which scales with how much data your queries return, not just how many queries you run. Chroma’s own calculator illustrates a mid-size workload (1M docs written ≈ 13 GiB, 6M docs stored ≈ 80 GiB, 10M queries) landing around $79/month.

Line itemExample monthly cost
Write — 1M docs (~13 GiB) @ $2.50/GiB~$34
Storage — 6M docs (~80 GiB) @ $0.33/GiB-mo~$27
Query + egress — 10M queries @ $0.0075/TiB + $0.09/GiB~$19
Estimated total~$79

Things to watch: the Team plan’s $250/month is a platform fee on top of usage, and its $100 included credit does not roll over month to month. The free $5 (Starter) and most other credits do not expire. There are no per-seat charges within a plan’s seat cap, and exporting your data out is explicitly easy (it’s open source) — Chroma leans on that to argue against lock-in.

Want to estimate your own Chroma bill? Use the Chroma pricing calculator to model your costs based on usage patterns.


Pricing evolution : Chroma pricing history and changes

Cadence

PeriodPrice changesProduct / SKU additionsNotes
202300OSS only; $18M seed, no commercial product
20240+1 (Cloud private preview)Managed serverless cloud waitlisted
2025 H10+1 (usage pricing published)Four-dimension rates go live, $0 + $5 credits
2025 H20 (rates held)+2 (Team, Enterprise at GA)Cloud GA; tiering added on top of stable rates
202600Rates unchanged through mid-2026

Tracked range: 2023–present, via Wayback Machine snapshots (earliest pricing snapshot April 2025) plus the August 2025 Show HN launch.

Notable changes

  • 2023-04 — $18M seed (Quiet Capital, ~$75M valuation). Chroma is free OSS; no paid product.
  • 2024 — Chroma Cloud enters waitlisted private preview (managed serverless).
  • 2025-04 — Usage-based pricing published: $2.50/GiB write, $0.33/GiB-mo storage, $0.0075/TiB query, $0.09/GiB egress, at $0/mo + $5 credits. These rates have not changed since.
  • 2025-08 — Chroma Cloud GA (Show HN). Team ($250/mo) and Enterprise tiers added; Starter usage rates held constant.

What’s unique : Chroma’s distinctive pricing mechanics

1. True $0 floor, no minimum. Starter has no platform fee and no minimum spend — idle databases scale to zero on S3. This is the deliberate antithesis of the fifty-dollar-a-month minimum Pinecone introduced in September 2025, and Chroma markets it directly to small and bursty workloads.

2. Four-dimension data metering instead of a provisioned pod. Rather than charging for an always-on cluster or a flat per-query rate, Chroma meters writes, storage, queries and network egress separately. Cost tracks the actual data lifecycle, which is unusually granular and transparent — but means egress is a real line item, not an afterthought.

3. Open-source escape hatch as a pricing lever. Because the full engine is Apache-2.0 and “egressing your data is easy,” Chroma’s pricing is implicitly capped by the credibility of self-hosting. The cloud has to stay cheap enough that the convenience beats running it yourself — a discipline most closed vector DBs don’t face.


Strengths & weaknesses

StrengthsWeaknesses
True $0 floor with $5 credits — friendliest for prototypes and bursty appsFour meters (esp. egress) make the bill harder to predict than a flat pod price
Fully published flat rates + interactive calculator — no opaque quotes (Starter/Team)Team plan’s $250/mo platform fee + non-rolling $100 credit is a real step-up cost
Open-source engine caps lock-in and keeps cloud pricing honestPer-dimension rates can add up at very large steady scale vs a provisioned competitor
Scale-to-zero over S3 means idle workloads cost ~nothingCloud is young (GA Aug 2025); less battle-tested at extreme scale than Pinecone

Billing UX : Chroma billing controls and transparency

  • Billing controls — Plans can be changed mid-cycle with pro-rated adjustments; you can upgrade, downgrade, or export and leave at any time. Self-hosting is always an exit ramp.
  • Usage visibility — The pricing page ships an interactive calculator (vectors, doc size, collections, query volume) that estimates the monthly bill before you commit; the dashboard exposes data, search, API keys and collaborators.
  • Payment options — Card-based self-serve for Starter/Team; Enterprise is invoiced. Free $5 (Starter) credit and most credits do not expire, but the Team plan’s included $100 credit does not roll over month to month.

Strategic wins : Why Chroma’s pricing decisions worked

1. OSS-led distribution, then monetize the managed layer

Chroma grew to ~27k GitHub stars as free Apache-2.0 software embedded in LangChain/LlamaIndex tutorials before ever charging. By the time Chroma Cloud launched, the funnel already existed — the company monetizes convenience, not access. See how AI companies structure pricing.

2. “$0 and no minimum” as competitive positioning

Launching a true scale-from-zero serverless model just as Pinecone added a fifty-dollar-a-month minimum gave Chroma a clean wedge for the long tail of small projects — the exact buyers a minimum-fee model pushes away. Related: outcome-based pricing trends.

3. Storage/compute separation makes the pricing model possible

The Rust “Chroma Distributed” engine on S3 is what lets idle databases cost nothing, which in turn is what makes “$0/month + usage” honest rather than a teaser. The architecture and the pricing reinforce each other. See choosing the right usage metric.


Areas to improve : Gaps in Chroma’s pricing approach

1. Bill predictability across four meters

Metering writes, storage, queries and egress separately is transparent but cognitively heavy — buyers have to model four numbers, and egress in particular surprises people. A single blended “per-query, all-in” estimate or spend alerts would reduce bill-shock risk. See bill shock and cost unpredictability.

2. The Team-plan cliff

Jumping from Starter ($0 base) to Team ($250/month + a non-rolling $100 credit) is a hard step. There’s little visible middle ground for a team that has outgrown Starter limits but isn’t ready for a $250 platform fee.

3. Enterprise opacity

Single-tenant/BYOC and SLA pricing is fully sales-led with no public anchor, which is conventional but contrasts with the otherwise-transparent self-serve tiers — a published “starting from” would keep the transparency story consistent.


Key takeaways

  1. Two tracks: free OSS, paid cloud. The Apache-2.0 engine is free to self-host; Chroma Cloud is the commercial product and the only thing you pay Chroma for.
  2. Pure usage, $0 floor. Starter is $0/month + $5 credits with no minimum — among the most prototype-friendly entry points in the vector-DB market.
  3. Four meters define the bill. $2.50/GiB written, $0.33/GiB-mo stored, $0.0075/TiB queried, $0.09/GiB egress — watch egress and storage growth most.
  4. Tiers layer on stable rates. Team ($250/mo + $100 non-rolling credit) and Enterprise (custom) add support/compliance/scale without changing the underlying usage rates.
  5. Architecture is the pricing. Storage/compute separation on S3 is what makes scale-to-zero and “$0 + usage” credible — the technical and commercial stories are the same story.

UBP implications

  1. Let the architecture set the floor. Chroma can credibly offer $0 + scale-to-zero only because storage and compute are decoupled over object storage — usage pricing is downstream of the system design.
  2. A true zero minimum is a positioning weapon. When a dominant competitor adds a minimum fee, “no minimum, scale from $0” becomes a concrete acquisition message for the long tail, not just a nicety. See introduction to usage-based pricing.
  3. Granular metering trades predictability for fairness. Billing on four distinct data dimensions is precise and defensible, but practitioners should pair it with calculators and spend alerts so buyers aren’t surprised by egress.

Sources


Bottom line

Chroma turned one of the most-adopted open-source vector databases into a true serverless cloud with the friendliest possible on-ramp: $0/month, $5 in free credits, no minimum, and four published usage rates. Self-hosting stays free and keeps the cloud honest. The model rewards small and bursty workloads and is explicitly positioned against minimum-fee competitors — buyers at scale should still model the four meters, especially egress. Browse the pricing blueprint for fully-researched company profiles.

Want to compare Chroma against other Infrastructure, Compute & MLOps companies? Browse the pricing blueprint.

Pricing timeline : Major events on a vertical axis

Each milestone below corresponds to a public pricing change, product launch, or material adjustment. Major events use a filled marker; minor adjustments use a faded one.

Chroma Cloud general availability

Show HN launch: Chroma Cloud exits private beta to GA, backed by the Rust 'Chroma Distributed' engine on S3. Team ($250/mo) and Enterprise tiers added alongside the unchanged Starter usage rates.

Usage-based pricing published

Chroma Cloud's pricing page goes live with the four-dimension usage model — $2.50/GiB written, $0.33/GiB-mo stored, $0.0075/TiB queried, $0.09/GiB egress — at $0/mo + $5 credits.

Chroma Cloud private preview

Chroma opens a waitlisted private preview of its managed serverless cloud, layering a hosted offering on top of the Apache-2.0 engine.

Chroma raises $18M seed

Quiet Capital-led seed round (~$75M valuation) funds the open-source embedding database; Chroma is free OSS with no commercial product yet.

Trivia
  • · Chroma Cloud charges a $0 base with no minimum spend — its key pitch against Pinecone, which imposed a flat fifty-dollar monthly minimum on all users in September 2025.
  • · The managed service runs on 'Chroma Distributed', a Rust engine that keeps data on S3 object storage and separates storage from compute, enabling true scale-to-zero for idle databases.
  • · Chroma is among the most-starred open-source vector databases on GitHub (~27k stars), and the cloud is billed purely on usage rather than gating features behind the paid tier.

Questions & answers

Is Chroma free?
The Chroma database is open-source under Apache-2.0 and free to self-host — you just pip install chromadb and run it locally or on your own infrastructure, paying only for your own compute. The managed Chroma Cloud also starts at $0/month on the Starter plan with $5 of free credits, after which you pay purely for usage.
How does Chroma Cloud pricing work?
Chroma Cloud is pure usage-based with no per-seat or always-on cluster fee. You pay across four dimensions: $2.50 per GiB written, $0.33 per GiB stored per month, $0.0075 per TiB queried, and $0.09 per GiB of network egress returned. The Starter plan has a $0 base; the Team plan adds a $250/month platform fee with $100 of included usage credits.
How much does Chroma Cloud cost per month?
It depends entirely on your data and query volume since there is no minimum. Chroma's own pricing calculator illustrates a workload of ~1M docs written (13 GiB), 6M docs stored (80 GiB) and 10M queries landing around $79/month. A small prototype that writes little and queries occasionally can sit inside the $5 free credit and effectively cost $0.
Is Chroma Cloud cheaper than Pinecone?
For small and bursty workloads, often yes — Chroma Cloud has no minimum and scales from $0, whereas Pinecone introduced a flat fifty-dollar monthly minimum for all users in September 2025. Because Chroma bills on data written, stored, queried and egressed rather than a provisioned pod, low-usage projects pay only for what they use; very large steady workloads should model both since the per-dimension rates add up.
What is the difference between Chroma open source and Chroma Cloud?
Chroma open source is a single-node, embeddable vector database you run yourself (pip install, Docker, or your own server) — free under Apache-2.0. Chroma Cloud is the fully-managed, serverless version backed by 'Chroma Distributed', a Rust engine that stores data on S3 object storage and separates storage from compute, giving zero-ops scaling, scale-to-zero, and usage-based billing.