CockroachDB

What CockroachDB Cloud actually is

CockroachDB Cloud is the managed service around CockroachDB, the distributed SQL database built by Cockroach Labs — a New York company founded in 2015 by ex-Googlers Spencer Kimball, Peter Mattis and Ben Darnell, with roughly $633 million raised and a customer list that reads like a payments and infrastructure roll call (Nvidia, OpenAI, DoorDash, JP Morgan, Netflix, Rivian, Bose, Cisco). The pitch has not changed much since the Spanner-inspired beginnings: PostgreSQL-compatible SQL that keeps transactional correctness while replicating data across nodes, regions and clouds, so that losing a node — or a whole region — causes a dip on a graph rather than a war room. Clusters scale horizontally by adding machines, and the wire protocol compatibility means a lot of existing Postgres applications can move without a rewrite.

The managed offering runs in three flavors (historically called Serverless and Dedicated; the current names are Basic, Standard and Advanced), plus a Bring-Your-Own-Cloud model where CockroachDB Cloud runs inside your own cloud account. Basic is usage-based and scales to zero; Standard bills provisioned compute with usage-based storage; Advanced provisions compute and storage with the full security and compliance stack (customer-managed encryption keys, egress controls, PCI DSS and HIPAA postures) and adds Azure to the AWS/GCP mix. Since 15 September 2026, new organizations land on "Cockroach Continuum", a repositioned agentic-database cloud with its own Standard and Mission Critical editions; existing customers keep their plans until renewal. That transition is the most confusing thing about the product right now, and we untangle it below.

In our view this is genuinely one of the serious databases in the market — the interesting question is not whether it works, but what it costs once you leave the free tier, and whether you need its guarantees at all.

Pricing: what you really pay

Under the current CockroachDB Cloud plans, Basic starts at $0 per month and includes 50 million Request Units and 10 GiB of storage free each month (the docs describe that as the first $15 of monthly consumption credited back, with a payment method on file), with compute that scales to zero and ceilings around 30K RU/sec. Standard starts at $0.18 per hour for 2 vCPUs — provisioned compute up to 200 vCPUs with on-demand storage — and Advanced starts at $0.60 per hour for 4 vCPUs with provisioned compute and storage, unlimited scaling and multi-region support on AWS, GCP and Azure. Every new organization gets $400 in trial credits, and Basic and Standard require no credit card to start.

The Continuum pricing that applies to new organizations from 15 September 2026 is published with unusual candor: Standard from $0.057 per vCPU-hour (one worked example quotes $0.092 per vCPU-hour, about $203 per month for 2 vCPU and 100 GB) and Mission Critical from $0.162 per vCPU-hour — the vendor's own calculator shows $1,528 per month for 12 vCPUs and 100 GB, broken down as $1,420 of compute (12 vCPUs at $0.162 per vCPU-hour), $70 of storage (100 GiB at 4.5x durability multiplier = 450 GiB billed at $0.155 per GiB-month) and $38 for a default hourly backup policy with 30-day retention. Read that storage line twice: the durability multiplier means you pay for 4.5 times your logical data.

Where the money surprises people: data transfer is billed separately and excluded from the calculator, backups are metered, and change data capture is a per-GiB-month add-on with tiers that escalate as watched data grows. The pricing pages are honest about all of this — the docs' cost page walks through each component — but the number of billable surfaces (RUs or vCPU-hours, storage with multipliers, backups, CDC, egress, add-ons) means you should model your workload before committing. Compared with running a single managed Postgres, this is expensive; compared with engineering your own multi-region consistent database, it is not.

Performance & infrastructure

CockroachDB Cloud runs on AWS and GCP across single- and multi-region configurations, with Azure available on Advanced (and on Mission Critical under Continuum). Availability targets are contractual: 99.99% on Basic and Standard, up to 99.999% for multi-region Advanced deployments, and support response targets of one hour for P1 on Standard versus 30 minutes on Mission Critical. Private connectivity, IP allowlists, metrics and log export to Datadog, row-level security, column-level encryption and distributed vector indexing (with MCP server, CLI and agent skills for AI tooling) round out the operational surface. Storage limits run to 3 TiB on Basic and Standard and effectively per-node (up to 10 TiB per node) on Advanced.

The engineering substance is what you are paying for: serializable transactions with automatic replication across failure domains, consistent reads after region loss, and an upgrade story (automatic or manual version control depending on edition) that database teams do not have to babysit. The database is trusted for payments, banking, identity and gaming infrastructure at large scale, which is the strongest reliability evidence any vendor can offer short of your own testing. We have not benchmarked CockroachDB ourselves — our own runs on /benchmarks cover compute providers, not database services — so we will not attach numbers to its latency profile.

The operational trade-offs are real, though. CockroachDB is not Postgres internally: the query planner has different characteristics, some Postgres features and extensions are missing or behave differently, and the Request Unit model on Basic takes learning. Multi-region correctness has latency costs — writes that must commit across regions are bound by the speed of light, and schema changes on large tables require the platform's own tooling. Teams that adopt it for one feature (surviving a region outage) often discover they have adopted a distributed-systems lifestyle.

Where it falls short

Price and complexity dominate. The step from the free tier to production is steep: a 2 vCPU Standard cluster with real storage, backups and egress quickly reaches three figures per month, and the Mission Critical class runs into four. The 4.5x storage durability multiplier, separately billed backups and egress, and CDC add-on pricing make bills hard to forecast without the calculator and discipline. And the September 2026 pricing transition — new "Continuum" organizations on different rate cards than pre-September customers — means much of the advice and tooling floating around the internet describes a plan you cannot buy.

Second: you may not need it. If your availability target fits one region with a read replica, a managed Postgres with automated failover is an order of magnitude cheaper and simpler. CockroachDB earns its keep when correctness and availability must survive losing a region — everything else is overbuying. Third: it is a proprietary service around an open-core database; self-hosting is possible and cheaper but moves operational burden back to you, and the managed plane's features (CMEK, compliance posture, private connectivity) live on the higher tiers. Finally, the vendor is a venture-backed company whose pricing and product naming have shifted more than once — long-term buyers should pin terms in contracts.

Who should pick this

Our pick for applications where the database cannot go down and cannot lose a transaction: payments, ledger systems, identity platforms, multi-region SaaS with strong consistency requirements, and gaming backends with global player bases. Startups validating a product should start on Basic — the $15 of monthly free usage and $400 in trial credits make it one of the more generous evaluation offers in databases — and move to Standard when traffic steadies. Enterprises with PCI/HIPAA obligations have a clean path through Advanced or Mission Critical with CMEK.

We would not pick this for simple CRUD applications, content sites, or anything a single-region managed Postgres handles comfortably — the cost and conceptual overhead are not justified there. If your team has no distributed-systems experience, budget for the learning curve, not just the invoice.

Key takeaways

• Managed distributed SQL from Cockroach Labs (founded 2015, New York; ~$633M raised) with Postgres wire compatibility and true multi-region consistency
• Free tier that actually works: Basic at $0/month with 50 million RUs and 10 GiB free monthly, plus $400 in trial credits and no credit card required
• Contractual availability: 99.99% on Basic/Standard, up to 99.999% multi-region on Advanced; 1-hour P1 support on Standard, 30 minutes on Mission Critical
• Pricing is multi-surface — vCPU-hours or RUs, storage with a 4.5x durability multiplier, backups, CDC and egress billed separately; model before committing
• Since 15 September 2026 new organizations land on "Cockroach Continuum" (Standard from $0.057/vCPU-hr, Mission Critical from $0.162/vCPU-hr) while existing customers keep legacy plans until renewal

Sources

• https://www.cockroachlabs.com/cockroachdb/pricing/
• https://www.cockroachlabs.com/pricing/
• https://docs.cockroachlabs.com/docs/cockroachcloud
• https://docs.cockroachlabs.com/docs/cockroachcloud/costs
• https://docs.cockroachlabs.com/docs/cockroachcloud/free-trial
• https://en.wikipedia.org/wiki/Cockroach_Labs
• https://yespress.io/cockroach-labs
• https://www.linkedin.com/company/cockroach-labs