Neon Pricing in 2026: What Serverless Postgres Really Costs

Neon's serverless Postgres has one number that decides your entire bill, and it is not on the pricing page: how many hours your database is actually awake. The same 1 CU database can cost you about $0/mo if it sleeps between requests, or roughly $81/mo if you keep it always-on. Neon's own docs put the same-sized workloads anywhere from a few dollars to hundreds. This teardown converts Neon's 2026 usage-based rates into three real 30-day bills, shows where the money actually goes, and explains why some existing users saw their old flat plan get more expensive overnight.

What does Neon cost in 2026?

As of July 2026, Neon runs a fully usage-based model with three self-serve plans. There is no flat monthly subscription anymore; you pay for the compute-hours, storage, and transfer you use. Here are the rates straight from Neon's pricing page (Neon, 2026):

We priced the three self-serve tiers side by side: Neon Free, Launch, and Scale.

Neon's own "typical spend" hints on the page: Launch around $15/mo for an intermittent 1 GB workload, Scale around $701/mo for a high-load 100 GB workload. Those are averages, not quotes, and the spread between them is the whole story.

How Neon billing actually works: the CU-hour

Everything on Launch and Scale is metered in CU-hours. A CU (Compute Unit) is roughly 1 vCPU and 4 GB of RAM, and your monthly compute cost is dead simple math from Neon's own FAQ (Neon, 2026):

> Monthly compute cost = average CU size x hours the compute runs x CU-hour price.

The lever hiding inside "hours the compute runs" is scale-to-zero. When your database is idle, Neon suspends the compute and you pay $0 for that time. On Free it is mandatory (after 5 minutes idle); on Launch you can disable it; on Scale it is configurable. That single toggle is the difference between the cheap bills and the scary ones below.

The always-on tax

A full 30-day month is 730 hours. If you keep a 1 CU database always-on so it never cold-starts:

• Launch: 730 x $0.106 = $77.38/mo in compute alone.
• Scale: 730 x $0.222 = $162.06/mo in compute alone.

If you let that same 1 CU database sleep and it is only awake ~2 hours a day (about 60 CU-hours), the Launch compute drops to roughly $6.36/mo. Same database, same data, 12x cheaper, purely because it sleeps. This is exactly the range one write-up summarized as "$3 a month, or $680 a month, for the same-sized database."

Three real 30-day Neon bills

Assumptions are stated so you can re-run them against your own usage. These are back-of-envelope calculations from Neon's published per-unit rates, not vendor quotes.

Cohort A: the hobby project that stays free

A side project on the Free plan, waking ~3 hours a day at 1 CU, burns about 90 CU-hours a month, under the 100 CU-hour free allowance, with under 0.5 GB of data.

• Compute: $0 (inside the free allowance)
• Storage: $0 (under 0.5 GB)
• Total: $0/mo, genuinely, as long as it sleeps and stays small.

The moment it needs more storage or more awake time, it graduates to Launch: ~150 CU-hours x $0.106 = $15.90 + 2 GB x $0.35 = $0.70, so about $16.60/mo, which lines up with Neon's own $15 Launch estimate.

Cohort B: the solo SaaS that cannot cold-start

You have paying users and you disable scale-to-zero because a 500 ms cold start on the first request of the morning looks broken. One 1 CU database, always-on, on Launch, 10 GB of data:

• Compute: 730 x $0.106 = $77.38
• Storage: 10 GB x $0.35 = $3.50
• Egress: under the 500 GB included = $0
• Total: ~$81/mo

This is the bill that surprises people. Nothing is misconfigured; you simply bought 730 hours of always-on compute instead of 60.

Cohort C: the growing team on Scale

Neon quotes ~$701/mo for a high-load 100 GB workload on Scale. Worked from the rates, a database averaging ~4 CU (autoscaled) always-on is 730 x 4 x $0.222 = $648/mo of compute, plus 100 GB x $0.35 = $35 storage, plus history and egress, which is how you land near $700. The reframe: on Scale, the identical compute-hour costs $0.222 vs Launch's $0.106, more than double. You are not buying speed; autoscaling to 16 CU is available on Launch too. You are buying a 30-day restore window, private networking ($0.01/GB), SOC 2, and HIPAA.

The counter-take: pay-as-you-go made some old bills bigger

Neon retired its old flat plans (the $19/mo Launch that included a compute and storage bundle) in favor of pure metering. For a hobby database that sleeps, that change is a win, you can now live on Free or pay single digits. But for a steady always-on workload, metering can cost more than the old flat fee. One user in r/PostgreSQL put it bluntly: "The $19 now costs $45 with new pricing." That is the always-on tax in miniature.

The cheapest genuine always-on production floor today is 0.25 CU (Neon's smallest compute size, 1 GB RAM): 730 x 0.25 x $0.106 = $19.34/mo. In other words, the old $19 price point still exists, but now it is a compute configuration you choose, not a plan you subscribe to.

Neon vs the flat-fee alternatives

Usage-based billing rewards spiky and sleepy workloads and punishes steady always-on ones. The opposite trade is a flat fee. Supabase charges a flat $25/mo Pro tier with an included database and compute, which is more predictable but never drops to $0 when you sleep, see our Supabase pricing teardown for that math. PlanetScale is another usage-based Postgres/MySQL option teams migrate to, with no free tier. And if your data is document-shaped rather than relational, the metering logic in our MongoDB Atlas teardown follows the same "awake vs asleep" pattern.

The honest rule: if your database is idle most of the day, Neon's scale-to-zero is the cheapest option on this list. If it is pinned always-on with steady load, a flat-fee provider is often cheaper and easier to forecast.

Five ways to lower a Neon bill

1. Leave scale-to-zero on for anything that tolerates a ~500 ms cold start (dev, internal tools, low-traffic side projects). It is the single biggest saver.
2. Right-size the autoscale maximum. Do not leave it at 16 CU if you never burst; you pay for the average CU, but a runaway query can ride the ceiling.
3. Do not upgrade to Scale for "performance." Go to Scale only for the 30-day restore window, private networking, or compliance. Autoscaling and 16 CU are already on Launch.
4. Kill idle branches. An always-on extra branch is about $1.46/mo just to exist (730 x $0.002/branch-hour) before any compute it burns; instant-restore storage runs $0.20/GB-month on top.
5. Set a spending limit. Launch and Scale both support a monthly cap so a traffic spike cannot silently 10x your bill.

Math check: the same 1 CU Postgres is $0 to ~$16 asleep, ~$81 always-on Launch, ~$162 always-on Scale. Neon does not bill your data. It bills your uptime.