Softwr

Databases · head to head

Cockroach Labs vs TiDB

Cockroach Labs logo

Cockroach Labs

Databases

The cloud-native distributed SQL database

From
Free
Rated
-
Full reviewWebsite
TiDB logo

TiDB

Databases

Apache 2.0 distributed SQL database with MySQL wire compatibility and a separate columnar replica for analytical queries.

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); TiDB a production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
  • They diverge on capability: Cockroach Labs covers Distributed SQL, TiDB covers MySQL wire compatibility.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

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

Attributes where Cockroach Labs and TiDB differ
AttributeCockroach LabsTiDB
PlatformsAWS, GCP, AzureCloud, AWS, Azure, Google Cloud Platform, Self-managed

Identical on both: starting price (Free), pricing model (freemium), free tier (Yes), user rating (Not yet rated), category (Databases), founded (2015).

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 TiDB

  • MySQL wire compatibility
  • Horizontal write scaling
  • Distributed ACID transactions
  • TiFlash columnar replica
  • Automatic rebalancing
  • Raft replication
  • Apache 2.0 licence
  • Online schema change

What people use each for

The jobs each tool is most often brought in to do.

Cockroach Labs

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

TiDB

  • A MySQL workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layernot Cockroach Labs
  • Reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an ETL pipelinenot Cockroach Labs
  • Multi-region deployments needing a single logical database with automatic failover rather than manual primary promotionnot Cockroach Labs
  • Migrating off a sharded MySQL estate where the sharding logic in the application has become the main source of bugs and operational toilnot 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

TiDB

  • A production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
  • Every transaction takes a timestamp from the placement driver and crosses the network to storage nodes, so simple point queries are slower than on single-node MySQL and latency-sensitive paths need to be measured, not assumed.
  • MySQL compatibility is at the wire and dialect level but not complete; stored procedures, triggers and events are not supported, so an application that pushed logic into the database cannot simply be repointed.
  • The columnar replica is an extra full copy of the data on its own nodes, so hybrid analytics roughly doubles storage and adds hardware that must be sized and paid for separately.
  • Operating it well requires cluster-specific expertise in TiUP or the Kubernetes operator, region hot spots, and rebalancing behaviour, so the licence is free but the running cost includes an engineer who understands distributed storage.

Pricing, plan by plan

Cockroach Labs

Free

No published plan breakdown. See the Cockroach Labs review.

TiDB

Free
  • ServerlessFree
    • 5GB storage
    • 50M request units
    • Free forever tier
  • Dedicated$250/month
    • Dedicated resources
    • SLA guarantees
    • Enterprise support

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

  • You need mysql wire compatibility.
  • You want to start without paying.
  • You work on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
  • You also want horizontal write scaling.
TiDB review

Questions people ask

Is Cockroach Labs or TiDB better?
Neither clearly leads. Cockroach Labs starts at Free and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cockroach Labs or TiDB?
Cockroach Labs starts at Free and TiDB at Free.
Does Cockroach Labs or TiDB run on more platforms?
Cockroach Labs runs on AWS, GCP, Azure. TiDB runs on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
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 TiDB is typically brought in for.
What can Cockroach Labs do that TiDB cannot?
Cockroach Labs covers Distributed SQL, Automatic Sharding, Multi-region Replication, Geo-partitioning. TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica.

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
TiDB: Is TiDB a drop-in replacement for MySQL?

At the protocol and dialect level it is close, and most applications connect unchanged. Stored procedures, triggers and events are not supported, and latency characteristics differ, so it needs testing rather than assumption.

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
TiDB: What licence is it under?

Apache 2.0, for both TiDB and the underlying TiKV storage engine. TiKV is a graduated CNCF project, which is a meaningful governance signal in a market where several competitors moved to source-available licences.

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
TiDB: Do I need TiFlash?

Only for analytical queries. It is an optional columnar replica; without it TiDB is a distributed transactional database. With it you get analytics on live data at the cost of an additional full copy.

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
TiDB: Is the managed cloud the same software?

TiDB Cloud runs the same engine, with the control plane, scaling and operational tooling provided as a service. The entry tier is metered differently from a dedicated cluster, so the cost model rather than the engine is what changes.

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
TiDB: When is TiDB the wrong choice?

When the database is small enough for one server, when latency on single-row lookups is the primary constraint, or when the application depends on MySQL stored procedures and triggers.

Share

Related pages

More on Cockroach Labs

More on TiDB

Keep looking

Other head to heads