Neon

Neon is serverless Postgres without compromise. PlanetScale was the original plan, but they killed their free tier. And honestly, I wanted real Postgres — not MySQL with branching bolted on. Drizzle ORM plus Postgres is the cleanest DX I've worked with. Upstash is great for Redis and edge use cases, but DwellRecord needs relational data — homes, rooms, assets, improvements, photos, sessions, users. That's a relational schema, not key-value. Forcing that into Upstash would have been fighting the tool. Render's managed Postgres works fine, but it's always-on pricing and no serverless scaling. Neon scales to zero when nobody's using the app and wakes up instantly on the first query. For an early-stage SaaS where traffic is unpredictable, that's the difference between paying for idle compute and paying for actual usage. The killer feature for me was Neon's connection pooling out of the box. Railway runs Node containers, Cloudflare sits in front — I didn't want to think about connection limits. Neon just handles it. I pointed Drizzle at the connection string and never thought about the database layer again.

Neon is serverless Postgres without compromise. PlanetScale was the original plan, but they killed their free tier. And honestly, I wanted real Postgres — not MySQL with branching bolted on. Drizzle ORM plus Postgres is the cleanest DX I've worked with. Upstash is great for Redis and edge use cases, but DwellRecord needs relational data — homes, rooms, assets, improvements, photos, sessions, users. That's a relational schema, not key-value. Forcing that into Upstash would have been fighting the tool. Render's managed Postgres works fine, but it's always-on pricing and no serverless scaling. Neon scales to zero when nobody's using the app and wakes up instantly on the first query. For an early-stage SaaS where traffic is unpredictable, that's the difference between paying for idle compute and paying for actual usage. The killer feature for me was Neon's connection pooling out of the box. Railway runs Node containers, Cloudflare sits in front — I didn't want to think about connection limits. Neon just handles it. I pointed Drizzle at the connection string and never thought about the database layer again.

Waldium is multi-tenant, thousands of blogs and posts posts, all in one Postgres database. Neon's serverless Postgres scales instantly without us thinking about it. We like the Database branching. Every time we test a migration or new feature, we branch production data and test safely. No more "hope this migration works in prod." Connection pooling is built-in. Cold starts are sub-100ms. The free tier is absurdly generous for early stage. If you're building on Postgres and haven't tried Neon, you're missing out

Waldium is multi-tenant, thousands of blogs and posts posts, all in one Postgres database. Neon's serverless Postgres scales instantly without us thinking about it. We like the Database branching. Every time we test a migration or new feature, we branch production data and test safely. No more "hope this migration works in prod." Connection pooling is built-in. Cold starts are sub-100ms. The free tier is absurdly generous for early stage. If you're building on Postgres and haven't tried Neon, you're missing out

I knew I needed a robust Postgres database for WriteRush's user accounts and subscription data. As a solo dev, the idea of managing a traditional database was daunting. Neon's serverless Postgres was great! The setup took literally 5 minutes. It scales automatically, the developer experience is fantastic, and the ability to branch my database like I branch my code is awesome. Neon gave WriteRush a production-grade database with zero overhead, letting me focus on building the app itself.