Neon
Serverless Postgres — a cloud-native PostgreSQL that scales to zero, branches like Git, and separates storage from compute. Neon is Postgres-compatible with instant provisioning, branching, and autoscaling. The modern way to run Postgres.
Nikita Shamgunov · Founded Neon in 2021
- Serverless Postgres.
- Dev/test environments (branching).
- Variable-traffic apps (scale to zero).
- When you want Postgres without ops.
- Constant high traffic (traditional Postgres may be cheaper).
- When you need exotic Postgres extensions.
- When you need full control.
Definition
Neon is serverless PostgreSQL. Storage and compute are separated — compute scales to zero when idle, storage scales automatically. Database branching (instant copy for dev/test). Point-in-time restore. Standard Postgres protocol (works with any Postgres driver/ORM).
Why it exists
Traditional Postgres runs 24/7 (paying for idle time) and can't branch. Neon's architecture separates compute/storage — scale to zero, branch instantly, autoscale — a modern Postgres for serverless and dev workflows.
How it works
Create a project → get a Postgres endpoint. Compute scales automatically (including to zero). Branch your database for dev/test (instant, no copy). Point-in-time restore. Connect via standard Postgres drivers. Works with Supabase, Vercel, etc.
Scaling limits
Cold starts (compute wakes up). Free tier limits. Some Postgres extensions not supported. Vendor lock-in to Neon's architecture.
Cost shape
Free tier (0.5GB storage, some compute). Paid plans for more. Pay for storage + compute.
Alternatives
- Supabase — More features (auth, real-time), less focused on serverless scaling.
- PlanetScale — MySQL, different DB.
- RDS Postgres — Standard Postgres, no branching, more ops.
Failure modes
- Cold starts.
- Extension limitations.
- Free tier limits.
- Vendor architecture lock-in.