CockroachDB review

CockroachDB is a distributed SQL database for applications that need to run across regions and keep serving through infrastructure failures. Instead of relying on one database server, it spreads data across nodes. The homepage says every node can read and write, and that data rebalances automatically as a cluster changes.

The product is designed to work with PostgreSQL applications: CockroachDB supports the PostgreSQL wire protocol and most PostgreSQL syntax, data types, drivers and ORMs. That may reduce migration work, but “most” is not the same as complete compatibility; the homepage describes little or no code change, not a guarantee that every application will run unchanged.

Teams can use CockroachDB as a managed service, run it in their own cloud account, or self-host it, including on Kubernetes, on-premises or in a hybrid setup. The trade-off is a more distributed architecture to operate in exchange for scaling and resilience features that a single-node database does not provide by itself.

CockroachDB’s main case is reducing the work of building a distributed database out of separate parts. The product description says teams can add nodes to increase capacity without manual sharding, while data rebalances automatically and hotspot detection adjusts distribution as load grows. That is useful when a workload genuinely needs to spread across machines or regions—not a reason by itself to replace a database that already fits on one server.

The docs describe Raft consensus as keeping data copies in step across nodes, zones and regions. The homepage also emphasizes that every node can read and write. Together, these are aimed at applications that need distributed availability rather than a primary server with replicas and custom failover logic. PostgreSQL wire-protocol support and compatibility with most syntax, types, drivers and ORMs may also make an existing application easier to adapt, though compatibility should be checked against its actual queries and dependencies.

Deployment options cover managed service, customer cloud accounts and self-hosting. The pricing page lists a 99.99% availability SLA for Standard on shared infrastructure, and a 99.999% multi-region SLA for Mission Critical on dedicated infrastructure. Those are plan-specific commitments, not a blanket promise across every deployment.

Price is usage-based, not a simple fixed license. The pricing page lists a Standard example at $203 a month for 2 vCPU and 100 GB, and Mission Critical at $1,528 a month for 12 vCPU and 100 GB. Those are examples, not universal quotes. Standard’s pricing card says $0.092 per vCPU-hour, while a separate feature table says pricing starts at $0.057 per vCPU-hour; confirm the applicable rate before budgeting. Storage, backups and data transfer are billed separately. There is no free plan; the listed trial is 30 days with $400 credit. Usage is metered by the minute, and pay-as-you-go is billed in arrears.

Some capabilities cost extra: change data capture is listed at $0.006 per vCPU-hour on Standard and $0.023 on Mission Critical. Physical cluster replication and cluster virtualization are listed at $0.023 per vCPU-hour on Mission Critical; virtualization is in preview, and replication has limited access.

Licensing also needs review. One Reddit thread discusses CockroachDB’s move to a fully proprietary license; commenters note the earlier shift from Apache 2.0 to Business Source License. Separately, a Reddit commenter reports a self-hosted enterprise quote in the tens of millions, an individual account rather than published pricing. Reddit users also argue distributed databases can be unnecessary for workloads a conventional database can handle.

CockroachDB lists Standard at $203/month in an example configuration (2 vCPU, 100 GB) and Mission Critical at $1,528/month (12 vCPU, 100 GB). That is about 7.5 times the example bill, but it is not a like-for-like tier comparison: Mission Critical adds dedicated infrastructure and a 99.999% multi-region SLA, versus shared infrastructure and 99.99% for Standard. Usage is billed by the minute. Pay-as-you-go bills in arrears; annual or committed-use contracts buy credits upfront.

Check the rates before budgeting: the Standard pricing details list $0.092 per vCPU-hour, while a separate feature table says “from $0.057.” Mission Critical lists $0.162 per vCPU-hour. Change data capture adds $0.006/vCPU-hour on Standard or $0.023 on Mission Critical. Physical cluster replication and preview cluster virtualization each list $0.023 on Mission Critical. Storage, backups and data transfer cost extra. A 30-day trial includes $400 in credit; there is no free plan.

CockroachDB supports the PostgreSQL wire protocol and most PostgreSQL syntax, data types, drivers and ORMs. The company says applications can connect with little or no code change, but “most” is not “all”: check your SQL and dependencies for compatibility before planning a migration.

For a move away, identify which parts of your setup depend on CockroachDB’s automatic rebalancing or distributed resilience. Replacing those capabilities may mean architectural or operational changes; that is a planning risk, not a published migration estimate. The published material does not specify data export tooling or formats, so confirm how you will export and validate data before committing. It also flags licensing certainty as a buyer concern, but gives no licensing details to assess here. We don’t have Reddit posts in the published material for this review, so we can’t responsibly say what users there most often cite when leaving.