Fazlur Rahman
Neon Postgres pricing in 2026 is built on three plans: Free $0/mo with 100 CU-hours, Launch pay-as-you-go at $0.106/CU-hour (typical small app ~$15/mo), and Scale pay-as-you-go at $0.222/CU-hour with autoscale up to 56 CU/224 GB RAM. Storage is $0.35/GB-month on both paid plans. Instant restore history is $0.20/GB-month. Egress past 500 GB included is $0.10/GB. Each additional branch past 10 is $1.50/branch-month. Scale-to-zero after 5 minutes of inactivity is the key cost control (Neon official, July 2026; BudgetForge, September 2026).
Last verified: Sep 16, 2026.
At a glance
- Free: $0/mo (100 CU-hours, 0.5 GB)
- Launch: $0.106/CU-hour + $0.35/GB storage
- Scale: $0.222/CU-hour (up to 56 CU/224 GB RAM)
- Instant restore: $0.20/GB-month
- Egress overage: $0.10/GB past 500 GB
- Extra branches: $1.50/branch-month past 10
- Scale-to-zero: After 5 min idle (free for dev)
- Typical Launch: ~$15/mo for small apps
The three Neon plans decoded
Neon pricing in 2026 is structured around three self-serve plans plus enterprise custom pricing. The Free plan at $0/mo is permanent (not a trial) with no credit card required, including 100 CU-hours, 0.5 GB storage, 5 GB egress, 6-hour history window with 1 GB limit, 1 collection, and 10 branches per project. The Launch plan is pay-as-you-go with no monthly minimum at $0.106/CU-hour, $0.35/GB-month storage, and 500 GB egress included. The Scale plan is also pay-as-you-go at $0.222/CU-hour with autoscale up to 56 CU (224 GB RAM), 30-day history window, SLA, HIPAA, and SOC 2 (Neon official, 2026).
Two rates do most of the damage on real workloads. First, the Scale compute rate ($0.222) is 2.1x the Launch rate ($0.106), so moving up a tier roughly doubles the cost of every awake hour. Second, extra items meter separately and quietly: instant restore history is $0.20 per GB-month, egress past 500 GB is $0.10 per GB, and each branch past your allowance is $1.50 per branch-month (BudgetForge, September 2026).
Why scale-to-zero changes everything
Neon's scale-to-zero is the key cost control: compute automatically suspends after 5 minutes of inactivity and resumes in a few hundred milliseconds on the next query. An always-on 1 CU database costs about $77/mo on Launch even with no real traffic (730 hours x $0.106). A database that sleeps 23 hours per day costs near zero (only the CU-hours it actually runs).
For spiky, branch-heavy development workloads with lots of previews and bursty traffic, Neon's scale-to-zero and branching earn their premium. For a single always-on database with steady load, a fixed VPS at $5-12/mo is cheaper and simpler than Neon. The break-even math against a flat $50/mo fixed Postgres box: Neon Launch breaks even at about 15.5 awake hours per day; on the Scale rate it breaks even at about 7.4 awake hours per day (BudgetForge, September 2026).
Side-by-side: Neon vs fixed instance economics
| Workload | Neon Plan | Compute/mo | Storage/mo | Restore/mo | Total |
|---|---|---|---|---|---|
| 0.5 CU floor awake 24/7 | Launch | $38.69 | $1.05 | - | ~$40 |
| Low-traffic small app | Launch | ~$10 | ~$2 | - | ~$15 |
| Always-on 2 CU (growth prod) | Scale | $324.12 | $17.50 | $6.00 | ~$347.62 |
| Always-on 2 CU on Launch | Launch | $154.76 | $17.50 | $6.00 | ~$178 |
| Scale-to-zero dev/preview | Launch | $0 (sleeps) | $2-5 | - | ~$5 |
CU-hours, branches, and hidden meters
The actual cost driver on Neon is awake-hours, not query count. Many teams underestimate how often their databases actually stay awake. A long-lived connection, a min autoscale size set too high, or a health check that pings more often than the 5-minute suspend window can keep the database awake 24/7. An always-on 1 CU database costs about $77/mo on Launch even with no real traffic (BudgetForge, September 2026).
Branching is genuinely useful and genuinely mis-budgeted. Branches share storage through copy-on-write, so 10 branches of a 10 GB database do not cost 10x storage. But each branch with an active compute endpoint bills its own CU-hours. 10 preview branches that wake 2 hours per day at 0.25 CU cost $15.90/mo on Launch. The same 10 branches kept warm 24/7 by a CI pipeline cost $193.45/mo (BudgetForge, September 2026).
Hidden costs and contract traps
Beyond the per-CU-hour rate, four cost lines determine Neon total cost of ownership. First, instant restore history at $0.20/GB-month can add up quickly for high-write workloads (each write is retained for the history window). Second, egress overage at $0.10/GB past 500 GB included is a real cost for data-heavy applications. Third, branches past plan allowance at $1.50/branch-month each. Fourth, spending notifications: Launch and Scale support spending limits and email alerts at 80% and 100% to prevent runaway bills (Neon official, 2026).
For applications where writes are sparse and reads dominate, instant restore costs are negligible. For high-write workloads, instant restore can be a meaningful line item. Always model your write rate and history window when budgeting Neon.
How Neon compares to alternatives
For serverless Postgres, Neon competes with Aurora Serverless v2, Supabase, and PlanetScale. Aurora Serverless v2 requires AWS-native IAM, Multi-AZ, and the wider AWS surface area — different cost model (ACU-hour) and different feature set. Supabase uses fixed monthly plan tiers plus compute add-ons — more predictable but less serverless. PlanetScale is provisioned rather than serverless — different cost model entirely. Neon's serverless approach with CU-hours and scale-to-zero is unique in the Postgres ecosystem (Neon official, 2026).
For workloads needing mobile SDKs and Google Analytics integration, Firebase remains the choice. For SQL-first teams wanting predictable monthly pricing, Supabase Pro at $25/mo is simpler. For workloads needing scale-to-zero and instant branching, Neon is the only Postgres option with both features (Neon official, 2026).
What enterprise buyers should do next
Three actions for organizations evaluating Neon Postgres in 2026.
- Model your awake-hours. Neon's pricing is dominated by compute time, not query count. Profile your application's traffic patterns to estimate average awake CU-hours per month.
- Set spending limits and alerts. Launch and Scale support spending limits. Always set a budget alert before deploying production.
- Audit branch usage. Branches past plan allowance cost $1.50/branch-month each. Delete unused branches or set TTL to prevent branch creep from inflating the bill.
What to watch next
Three near-term datapoints. First, Neon's continued Databricks integration — expect tighter serverless Postgres-to-Databricks analytics workflows. Second, Scale tier feature expansion — SLA, HIPAA, SOC 2, and 30-day history are increasingly included. Third, competitive pressure from Aurora Serverless v2, Supabase, and PlanetScale Postgres — all are positioning for serverless Postgres workloads in 2026 (Neon official, 2026).
