Softwr

Databases · head to head

Cockroach Labs vs Turso

Cockroach Labs logo

Cockroach Labs

Databases

The cloud-native distributed SQL database

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: Cockroach Labs basic and Standard tiers limited to AWS and GCP (select regions only); 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: Cockroach Labs covers Distributed SQL, Turso covers Per-tenant databases.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Cockroach Labs and Turso actually diverge.

Attributes where Cockroach Labs and Turso differ
AttributeCockroach LabsTurso
PlatformsAWS, GCP, AzureWeb
Founded2015Unknown

Identical on both: starting price (Free), pricing model (freemium), 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 Cockroach Labs

  • Distributed SQL
  • Automatic Sharding
  • Multi-region Replication
  • Geo-partitioning
  • ACID Transactions
  • Horizontal Scaling
  • Survivability
  • PostgreSQL Compatibility

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.

Cockroach Labs

  • Distributed SQL database for scalable applicationsnot Turso
  • Multi-region deployment and failovernot Turso

Turso

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

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cockroach Labs

  • Basic and Standard tiers limited to AWS and GCP (select regions only)
  • Azure support restricted to Advanced tier only
  • Basic tier limited to 50 million RUs and 10 GiB storage per month
  • Advanced tier starts at $0.60/hour for 4 vCPUs minimum
  • 3 TiB maximum storage on Basic and Standard tiers, 10 TiB per node on Advanced

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

Cockroach Labs

Free

No published plan breakdown. See the Cockroach Labs review.

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 Cockroach Labs if

  • You need distributed sql.
  • You want to start without paying.
  • You work on AWS, GCP, Azure.
  • You also want automatic sharding.
Cockroach Labs 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 Cockroach Labs or Turso better?
Neither clearly leads. Cockroach Labs 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, Cockroach Labs or Turso?
Cockroach Labs starts at Free and Turso at Free.
Does Cockroach Labs or Turso run on more platforms?
Cockroach Labs runs on AWS, GCP, Azure. Turso runs on Web.
Can I use Cockroach Labs for free?
Both have a free tier, so you can try either at no cost before committing.
What is Cockroach Labs best used for?
Cockroach Labs is most often used for distributed sql database for scalable applications, multi-region deployment and failover. Of those, distributed sql database for scalable applications and multi-region deployment and failover are not what Turso is typically brought in for.
What can Cockroach Labs do that Turso cannot?
Cockroach Labs covers Distributed SQL, Automatic Sharding, Multi-region Replication, Geo-partitioning. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.

Answered from the vendors’ own pages

Cockroach Labs: What does the free Basic tier include?

The Basic tier is free and includes 50 million RUs and 10 GiB storage per month, with a maximum compute of 30K RU/sec. No credit card is required to start.

Source
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.

Cockroach Labs: How much do the paid tiers cost?

Standard tier starts at $0.18 per hour for 2 vCPUs, and Advanced tier starts at $0.60 per hour for 4 vCPUs. Both tiers support additional resources with higher costs for increased compute and storage.

Source
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.

Cockroach Labs: What are the storage limits for each tier?

Basic plan supports up to 3 TiB storage, Standard tier up to 3 TiB, and Advanced tier up to 10 TiB per node with unlimited total storage.

Source
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.

Cockroach Labs: Can I get trial credits before paying?

Yes, new users can try CockroachDB free with $400 in credits. The Basic and Standard plans do not require a credit card to start.

Source
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.

Cockroach Labs: Do legacy contracts have different pricing?

Customers with annual or multi-year contracts entered before December 1, 2024 can view legacy pricing terms on a separate page, which apply until their contract renewal date.

Source
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 Cockroach Labs

More on Turso

Keep looking

Other head to heads