Neon

What it is

Neon is serverless Postgres with branching. The big selling point vs. competitors: the free tier doesn't pause your database after inactivity. For serious projects, that's a dealbreaker for alternatives.

Who it's for

• Developers who want Postgres without managing a server
• Projects using serverless compute (Vercel, Cloudflare) where a persistent DB connection isn't viable
• Anyone burned by Supabase free tier pausing on them
• NOT for: teams who need auth, storage, and realtime bundled — use Supabase instead
• NOT for: apps requiring always-on read replicas without budget for Scale tier

The good

The free tier is honest. 0.5GB storage, compute that scales to zero but wakes fast. No pausing. You can build and launch a real product on the free tier.

Database branching actually matters. Create a branch per PR for isolated test environments. Merge or discard when done. This is the feature that separates Neon from commodity Postgres hosting.

The serverless driver is purpose-built. The @neondatabase/serverless driver works in edge runtimes where pg can't. Zero latency penalty on Vercel Edge or Cloudflare Workers.

Drizzle ORM integration is tight. The Drizzle adapter just works. Type-safe queries with no overhead.

The bad

Cold starts are real at scale-to-zero. Typically under 100ms, but pay for always-on compute in latency-sensitive production.

No read replicas on lower tiers. You need Scale tier ($69/mo) for that. Launch ($19/mo) is single-region, single-instance.

Storage costs aren't obvious. Archival vs. active storage pricing needs a careful read if you have large datasets.

Onboarding experience

Dashboard project creation takes 2 minutes. Connection string is ready immediately. Serverless driver setup is 3 lines of code. There's no local database to configure. Neon branches serve as per-developer and per-PR isolated environments. Drizzle and Prisma adapter docs are accurate with working examples. Self-serve from signup to first query in under 10 minutes.

Support reality

Free tier gets Discord community with active participation from the Neon team. Launch tier adds email support. The Discord is responsive. Most connection pooling and cold start questions resolve within hours. The core team regularly posts about upcoming changes and known issues. Technical blog posts often preempt common support questions.

Migration and lock-in

Near-zero lock-in. Neon is standard Postgres, so pg_dump and pg_restore work as expected. The @neondatabase/serverless driver is Neon-specific but standard pg is a drop-in fallback on any Postgres host. Database branching is a Neon primitive; losing it doesn't break your app, it just removes a workflow advantage. Leaving Neon requires an afternoon, not a project.

Pricing reality

Free: real for side projects and this site. Launch at $19/mo: correct for production. Scale at $69/mo: for serious workloads. Dramatically cheaper than Supabase Pro ($25/mo) for pure Postgres needs. Comparing Launch to Pro, you're saving $6/mo and not paying for features you don't use.

Vendor signals

• Series B funded; actively investing in the product
• Public roadmap and consistent changelog
• Technical blog is genuinely worth reading. Architecture decisions explained openly.
• No pricing surprises since launch; free tier terms have been stable
• OSS community contributions accepted and acknowledged on GitHub

Verdict

Neon is the right database if you want serverless Postgres without the bells and whistles. The free tier holds, branching pays dividends in development workflows, and the driver was built for edge runtimes before most alternatives thought about it.

If you need pure Postgres with a serverless-friendly driver: Neon. If you need auth, storage, and realtime alongside your database: Supabase is a better bundle, even though it costs $6/mo more. If you're building a latency-sensitive global app, combine Neon with Fly.io or PlanetScale.

Would I recommend a colleague start here? Yes, without qualification.