CockroachDB review

CockroachDB is a distributed SQL database server, not an application framework or a standalone API wrapper. Applications connect to it over the PostgreSQL wire protocol, using PostgreSQL-compatible drivers and ORMs. It can run as a fully managed service, in your own cloud account, or as software you operate yourself, including on Kubernetes, on-premises or in a hybrid setup.

The database distributes data across nodes and uses Raft consensus to keep copies in step across nodes, zones and regions. Every node can accept reads and writes; adding nodes increases capacity, while data rebalances automatically. Hotspot detection adjusts data distribution as load grows. This is aimed at applications that need to scale across regions and withstand infrastructure failures without building a sharding layer themselves. It is not a default replacement for every PostgreSQL deployment: the distributed architecture has different behavior, and Cockroach Labs documents PostgreSQL features that behave differently.

The primary integration surface is SQL over the PostgreSQL wire protocol. CockroachDB supports most PostgreSQL syntax, data types, drivers and ORMs, so existing applications may connect with little or no code change. Cockroach Labs does not name particular programming languages or SDKs on the vendor's site; confirm support for your language, driver and ORM in its documentation before committing to a stack.

This is a database connection, not a REST API or webhook integration. The vendor's site does not describe a CLI, so check Cockroach Labs’ current docs for the command-line tools and operational workflows your team needs. The vendor says a few PostgreSQL features behave differently in a distributed system and are documented. That compatibility detail matters: validate your SQL patterns, transaction behavior and migration tooling against those documented differences. For managed deployments, Cockroach Labs operates the database; customer-cloud and self-hosted options put more operational work on your team.

CockroachDB has no free plan. The pricing page lists a 30-day trial with $400 in credit. Standard is priced by usage: one example is $203 per month for 2 vCPU and 100 GB, and a pricing card lists $0.092 per vCPU-hour. A separate feature table lists Standard from $0.057 per vCPU-hour, so confirm the applicable rate and estimate with Cockroach Labs. The Standard example includes shared infrastructure and a 99.99% availability SLA.

Mission Critical is aimed at production needing higher availability. The listed example is $1,528 per month for 12 vCPU and 100 GB, at $0.162 per vCPU-hour, with dedicated infrastructure and a 99.999% multi-region SLA. Storage, backups and data transfer are billed separately based on usage. Change data capture costs $0.006 per vCPU-hour on Standard and $0.023 on Mission Critical; physical cluster replication and cluster virtualization are listed at $0.023 on Mission Critical. Usage is metered by the minute and billed monthly; pay-as-you-go is billed in arrears.

CockroachDB can be self-hosted, including on Kubernetes, on-premises and in hybrid environments. That does not settle whether a particular use is permitted by the current license. A Reddit thread about a Cockroach Labs license announcement describes a move to a fully proprietary license and notes that the Core code previously moved from Apache 2.0 to the Business Source License in 2019. Confirm the current license and your intended deployment rights directly with Cockroach Labs before choosing self-hosting.

CockroachDB’s PostgreSQL wire protocol and SQL interface give applications a familiar integration point, but they do not guarantee a drop-in migration to another database. Cockroach Labs documents differences from PostgreSQL. The vendor's site does not set out export formats or a complete migration-away process; ask the vendor about data export, schema and transaction compatibility, and exit planning before production adoption.

CockroachDB’s main production case is resilience and scale across nodes, zones and regions. The vendor describes Raft consensus, automatic rebalancing and hotspot detection, and lists a 99.99% availability SLA for Standard and a 99.999% multi-region SLA for Mission Critical. Those SLAs are plan-specific; review their terms, deployment requirements and support coverage before relying on them. The vendor's site does not list request-rate limits, security certifications or detailed compliance controls, so ask Cockroach Labs to confirm the requirements that apply to your workload.

Distributed SQL is a trade-off, not a universal upgrade. In a Reddit database discussion, commenters describe distributed databases as niche and point to added latency and workload-specific fit. A separate thread raises concerns about self-hosted per-vCPU pricing and the cost of maintaining a fork under license changes. These are user reports, not measured comparisons, but they identify concrete issues to evaluate: latency across regions, workload shape, license terms, operational staffing and total cost at your expected capacity.