Softwr

Databases · head to head

Chroma vs SurrealDB

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
Rated
-
Full reviewWebsite
SurrealDB logo

SurrealDB

Databases

Multi-model database combining documents, graphs, vectors and time-series

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; SurrealDB the listed $0.192/node/hr Scale pricing lacks transparent higher-tier rates, requiring a sales conversation for full production sizing.
  • They diverge on capability: Chroma covers Embedded mode, SurrealDB covers Multi-model engine.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Chroma and SurrealDB actually diverge.

Attributes where Chroma and SurrealDB differ
AttributeChromaSurrealDB
PlatformsWebweb, api, windows, mac, linux
FoundedUnknown2022

Identical on both: starting price (Free), pricing model (usage-based), free tier (Yes), user rating (Not yet rated), category (Databases).

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 SurrealDB

  • Multi-model engine
  • ACID transactions
  • Hybrid retrieval
  • Horizontal scaling
  • Multi-region disaster recovery
  • FIPS-compliant cryptography

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 SurrealDB
  • Agent memory in a single application process, where an embedded store avoids adding a network dependencynot SurrealDB
  • A departmental search application under roughly ten million records where one server is sufficient and simplicity is worth more than headroomnot SurrealDB
  • Local and CI testing of retrieval code with the same client library used in productionnot SurrealDB

SurrealDB

  • AI agent memory and retrieval-augmented generationnot Chroma
  • Applications needing documents, graphs and vectors in one databasenot Chroma
  • Knowledge graph construction from unstructured datanot Chroma
  • Regulated workloads requiring SOC2/ISO27001/HIPAA-eligible hostingnot 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.

SurrealDB

  • The listed $0.192/node/hr Scale pricing lacks transparent higher-tier rates, requiring a sales conversation for full production sizing.
  • As a newer multi-model database, it has a smaller ecosystem of drivers, ORMs and community tooling than established single-model databases.
  • HIPAA compliance is only available as an Enterprise add-on rather than included in standard paid tiers.
  • Combining multiple data models in one engine can add query-planning complexity compared to purpose-built single-model databases.

Pricing, plan by plan

Chroma

Free
  • StarterFree
    • 10 databases
    • 10 team members
    • Community Slack access
  • Team$250/month
    • 100 databases
    • 30 team members
    • $100 in included credits
  • Enterprise$null/month
    • Unlimited databases
    • Unlimited team members
    • Dedicated support

SurrealDB

Free
  • StartFree
    • 1 free instance, then from $0.021/hr
    • 1GB storage free forever
    • Vertical scaling to terabytes
  • Scale$0.192/month
    • $0.192/node/hr
    • Production-grade fault tolerance
    • Horizontal scaling to petabytes
  • Enterprise$undefined/month
    • Self-hosted, custom pricing
    • Clustered fault-tolerant deployments
    • FIPS-compliant cryptography

Which should you pick?

Choose Chroma if

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

Choose SurrealDB if

  • You need multi-model engine.
  • You want to start without paying.
  • You work on web, api, windows, mac, linux.
  • You also want acid transactions.
SurrealDB review

Questions people ask

Is Chroma or SurrealDB better?
Neither clearly leads. Chroma starts at Free and SurrealDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Chroma or SurrealDB?
Chroma starts at Free and SurrealDB at Free.
Does Chroma or SurrealDB run on more platforms?
Chroma runs on Web. SurrealDB runs on web, api, windows, mac, linux.
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 SurrealDB is typically brought in for.
What can Chroma do that SurrealDB cannot?
Chroma covers Embedded mode, Single-node server, Distributed architecture, Vector search. SurrealDB covers Multi-model engine, ACID transactions, Hybrid retrieval, Horizontal scaling.

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.

SurrealDB: What does SurrealDB cost?

SurrealDB Cloud's Start plan is free with one free instance (then from $0.021/hr), the Scale plan runs $0.192/node/hr for production workloads, and Enterprise self-hosted deployments use custom pricing.

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.

SurrealDB: Is there a free plan and what are its limits?

Yes, the Start plan includes one free instance with 1GB of storage free forever and 1GB of outbound data transfer per month, aimed at prototypes and development.

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.

SurrealDB: How is billing handled?

Customers are invoiced monthly based on actual usage in a pay-as-you-go model with no long-term commitments, though commitment-based discounts are available.

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

More on Chroma

More on SurrealDB

Keep looking

Other head to heads