Chroma · FinOps Profile

Chroma Db Finops

FinOps view of Chroma spend. Chroma's core vector database is open source (Apache 2.0) and free to self-host - in that model the cost is your own compute, storage, and network for running the Chroma server, with no vendor invoice. Chroma Cloud is the managed, serverless offering billed on usage, metered primarily on data written, data stored, data queried, and network egress, above free credits. Enterprise agreements cover single-tenant clusters and negotiated terms.

Chroma Db Finops is the FinOps profile for Chroma on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 5 billable meters, billed in USD, on a monthly cycle, and pricing category usage-based.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Vector Database, Embeddings, Vector Search, Open Source, and FinOps.

Category: AI and Machine Learning Pricing: Usage-Based Billing: Monthly FOCUS v1.3
Vector DatabaseEmbeddingsVector SearchOpen SourceFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchaseAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
Chroma
PricingCategory
Usage-Based
ProviderName
Chroma
PublisherName
Chroma
ServiceCategory
AI and Machine Learning
ServiceName
Chroma Cloud

Meters

data_written
Unit: bytes
Data written into collections on Chroma Cloud, billed per GiB (observed ~$2.50/GiB).
data_stored
Unit: bytes
Data stored in Chroma Cloud, billed per GiB per month (observed ~$0.33/GiB-month).
data_queried
Unit: bytes
Data scanned by vector queries on Chroma Cloud (observed ~$0.0075/TiB queried).
network_egress
Unit: bytes
Data returned over the network from Chroma Cloud (observed ~$0.09/GiB).
self_hosted_compute
Unit: hours
Infrastructure cost of running the self-hosted Chroma server (no Chroma invoice).

Sources