Softwr

Databases · head to head

Chroma vs Turso

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
Turso logo

Turso

Databases

SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.

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.; Turso sQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option.
  • They diverge on capability: Chroma covers Embedded mode, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Chroma and Turso actually diverge.

Attributes where Chroma and Turso differ
AttributeChromaTurso
Pricing modelusage-basedfreemium

Identical on both: starting price (Free), free tier (Yes), platforms (Web), 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 Turso

  • Per-tenant databases
  • MIT licence
  • Embedded replicas
  • SQLite compatibility
  • HTTP access
  • Branching
  • Point-in-time restore
  • In-process engine

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

Turso

  • Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot Chroma
  • Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot Chroma
  • Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot Chroma
  • Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot 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.

Turso

  • SQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option.
  • Per-tenant databases mean per-tenant migrations, so every schema change becomes a fan-out job that must be idempotent and resumable, and multi-database schemas, the feature meant to solve this, is deprecated.
  • There are no cross-database queries; ATTACH is deprecated on the cloud, so any report or analytic spanning tenants must be assembled in your application or in a separate warehouse you also operate.
  • Data Edge, the multi-region edge replication that was Turso's original positioning, is deprecated, so a large share of the tutorials and articles describing Turso as an edge database describe behaviour you can no longer rely on.
  • Three engine lineages share the name, SQLite, the libSQL fork and the Rust rewrite, and the Rust engine is still maturing, so SQLite compatibility needs verifying against your specific pragmas, extensions and query patterns; the cloud already restricts journal_mode and busy_timeout and makes user_version read-only.

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

Turso

Free
  • FreeFree
    • 100 databases
    • 5 GB storage
    • 500M monthly rows read
  • Developer$4.99/month
    • Unlimited databases
    • 9 GB storage
    • 2.5B monthly rows read
  • Scaler$24.92/month
    • Unlimited databases
    • 24 GB storage
    • 100B monthly rows read
  • Pro$416.58/month
    • Unlimited databases
    • 50 GB storage
    • 250B monthly rows read

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 Turso if

  • You need per-tenant databases.
  • You want to start without paying.
  • You also want mit licence.
Turso review

Questions people ask

Is Chroma or Turso better?
Neither clearly leads. Chroma starts at Free and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Chroma or Turso?
Chroma starts at Free and Turso at Free.
Does Chroma or Turso run on more platforms?
Both run on Web, so platform support will not decide this one for you.
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 Turso is typically brought in for.
What can Chroma do that Turso cannot?
Chroma covers Embedded mode, Single-node server, Distributed architecture, Vector search. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

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.

Turso: Is Turso just hosted SQLite?

Not exactly. It hosts databases built on the SQLite lineage: libSQL, an MIT fork of SQLite, and Turso Database, a newer Rust rewrite. The platform adds branching, backups, an HTTP API and programmatic database creation.

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.

Turso: Can I really run a million databases?

That is the design goal and the platform API exists to make provisioning and deletion programmatic. The practical constraints are the ones that come with it: migrations fan out, and nothing can query across databases.

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.

Turso: How do embedded replicas handle read-after-write?

Reads come from the local replica and writes go to the primary, so a read immediately after a write can return stale data unless you wait for a sync. Application code has to account for that rather than assume it.

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.

Turso: What licence is it under?

libSQL and Turso Database are both MIT. Turso Cloud is a commercial managed service built on them, so the engine is genuinely open even though the platform is not.

Chroma: What licence is it under?

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

Turso: Is Turso still an edge database?

No. Data Edge, the multi-region edge replication feature, is deprecated. The current positioning is per-tenant and embedded databases, and older material describing edge replication is out of date.

Share

Related pages

More on Chroma

More on Turso

Keep looking

Other head to heads