CockroachDB vs Neon

CockroachDB is a distributed SQL database that speaks the Postgres wire protocol. Your existing Postgres drivers, ORMs, and queries work without changes. The key selling point is resilience — data is automatically replicated across nodes, so a zone going down does not take your database offline. The Serverless free tier gives you 10 GiB of storage and 50 million request units, which covers a moderate production workload.

For most solo founders, CockroachDB is more database than you need. The distributed architecture adds write latency (each write requires consensus across nodes), and you are paying that cost even if your app runs in a single region. Where it makes sense is if you are building something that genuinely needs multi-region availability or you want to avoid ever dealing with database failovers. For simpler use cases, Neon or Supabase give you standard Postgres with less overhead.

Neon is Postgres that disappears when you are not using it. On the free tier, your database scales to zero during quiet periods and wakes up when a request comes in. This means a side project that gets occasional traffic costs nothing, not $39/month like PlanetScale.

The tradeoff is cold starts — that first query after a period of inactivity takes a second or two while the database wakes up. For APIs and web apps, this is usually fine. For real-time applications, it might matter. The branching feature is great for testing migrations safely. If you want Postgres without paying for idle time, Neon is the best option right now.