Cockroach
Labs.

A region goes dark. Nobody wakes up.

Somewhere right now, a cloud availability zone is failing. A power feed trips, a network partition splits a continent, a routine deploy goes sideways. For a lot of companies that is a war room, a status page, and a long apology. For the companies running CockroachDB, it is a graph that dips and recovers while everyone keeps working.

That is the business Cockroach Labs is in. Not flashy features, not the loudest demo at the conference - just the unglamorous promise that your data stays correct and online when the infrastructure underneath it does not. The product is a distributed SQL database. The pitch is older than software: things break, so build something that expects to be broken and keeps going anyway.

It is a strange thing to name a company after a pest. It is also the most honest branding in enterprise software. The whole proposition fits in the logo.

Databases were forcing a bad trade.

For decades you got to pick two virtues and live without the third. Traditional SQL databases gave you consistency and the language everyone knew, but they scaled by buying a bigger, more expensive single machine and praying it never fell over. The NoSQL wave gave you scale and survivability, but asked you to give up transactions, joins, and the comfortable certainty that your data was actually correct.

So teams did the thing teams do. They sharded by hand, bolted caches on top, wrote elaborate failover runbooks, and hired people whose entire job was to be awake when the database was not. It worked, in the way that holding your breath works. Eventually you need to breathe.

The founders had watched this movie from the best seat in the house. At Google, they saw AdWords data outgrow the relational tools meant to hold it, and they saw Google's answer - a globally distributed database called Spanner that delivered consistency and scale at once. Spanner solved the problem. It also lived inside Google, behind Google's hardware and Google's atomic clocks. Everyone else was still making the bad trade.

Three ex-Googlers, one stubborn idea.

In 2015, Spencer Kimball, Peter Mattis, and Ben Darnell bet that Spanner's ideas did not have to stay Google's secret. They would rebuild the concept in the open, on commodity hardware, for everyone. Kimball and Mattis had history - the two had collaborated years earlier on GIMP, the open-source image editor - and they leaned into open source again.

The bet had a name before it had customers. They called it CockroachDB, because the goal was a database that was, frankly, hard to kill. You can debate whether that is charming or off-putting. You cannot say it is unclear.

Benchmark led a $6.3M Series A that same year, with GV, Sequoia, and Index Ventures along for the ride. The open-source release followed in 2016. The idea, it turned out, had a market.

One database, written to expect failure.

CockroachDB automatically replicates your data across nodes, regions, and clouds. Lose a node and it reroutes. Lose a whole region and it keeps serving, consistent the entire time. You add capacity by adding machines, not by migrating to a bigger one at midnight. And because it speaks the PostgreSQL wire protocol, a lot of existing applications can move over without a rewrite.

There is a quieter feature that wins the regulated deals: data locality. Tell CockroachDB that European customer rows must physically live in Europe, and it pins them there by policy, no parallel database required. For banks and anyone living under data-residency law, that is the difference between a yes and a no.

The roach's paper trail.

Who bets their data on a bug.

The customer list answers the skeptic's first question. JP Morgan Chase runs it. Netflix deploys it inside its Device Management Platform. Rivian, DoorDash, Booking.com, FanDuel, and SumUp are in the fold. These are not companies that pick infrastructure for the cute name; they pick it for the part where the lights stay on.

Behind those rounds sits a who's-who of investors - Benchmark, GV, Index Ventures, Sequoia, Tiger Global, Altimeter, Coatue, Bond, Greenoaks. The 2025 IBM OEM partnership added a different kind of proof: a legacy giant choosing to ship CockroachDB inside its own stack.

Make downtime boring.

The mission reads simply: build the most resilient, scalable, consistent database so companies can run mission-critical applications without downtime, anywhere. Strip the adjectives and it is a promise to take a category of 3am emergencies and turn them into a footnote in a quarterly report.

Cockroach Labs decided that was a worthy enough fight to build a company around, then went and published an annual State of Resilience report to keep score for the whole industry. It is a clever move - the company selling resilience also defines what resilience means. Mildly self-serving, undeniably useful.

The lights, the bug, and 3am.

AI changed the size of the problem. Models and the products around them generate traffic and data at volumes that flatten systems which were fine a year ago, and they do it while regulators tighten the rules about where that data can live. Cockroach Labs is betting that resilience stops being an infrastructure footnote and becomes a board-level line item. Its 2026 momentum suggests the bet is landing.

So return to where we started. A region goes dark. The old story had a war room and an apology. The new story has a graph that dips and recovers, an on-call engineer who never gets paged, and a database quietly doing the thing it was named to do. The cockroach outlasts the catastrophe. That was the plan from the first line of code - and increasingly, it is the plan everyone else is copying.