Neon vs Turso

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.

Turso takes SQLite and makes it work as a cloud database. Its design goal is many small databases rather than one big one: you can give every user, workspace or AI agent its own isolated database, and idle ones cost only storage. Embedded replication lets the same database run inside your app or on a user’s device, reading and writing locally and syncing with the cloud. Turso no longer offers edge replicas in multiple regions to new users.

The free tier gives you 5 GB of storage, 100 databases, 500 million row reads and 10 million row writes a month. Paid plans start with Developer at $4.99 a month billed yearly ($5.99 monthly) and Scaler at $24.92 billed yearly ($29 monthly). On 2 October 2026 Turso announced that it is being acquired by Supabase. It says the service keeps running as before and the open-source engine stays in active development; the announcement does not mention plan or price changes. If your app is read-heavy or naturally split per tenant, Turso is fast and cheap. If you need complex relational queries or heavy write throughput, Postgres on Neon or Supabase is a better foundation.