Provisioned Postgres charges you by the hour whether anyone is querying it or not, which is a bad deal the moment your traffic is spiky, or you want a fresh database per pull request. That is the whole pitch for serverless Postgres, and in 2026 the numbers actually back it up. I ran the real arithmetic on Neon and Supabase's published rates in a longer piece on DevToolLab, and the short version is below.
What "Serverless" Actually Changes
Three things happen when compute and storage split apart. Compute can suspend to zero cost when idle, which is the entire economic argument. Storage keeps living on its own, which is what makes suspend-and-resume a few seconds instead of a restore-from-backup. And you can spin up a copy-on-write branch per PR, seeded with real data, without provisioning a second instance. For most teams the branching is the bigger workflow change; the bill is just the reason it got funded.
Where the Crossover Actually Sits
The interesting question isn't whether usage billing is cheaper, it's at what utilization it stops being cheaper. That's a two-line calculation from the vendors' own rate cards.
const HOURS_PER_MONTH = 730
const NEON_CU_HOUR = 0.106 // neon.com/pricing, Launch plan, Aug 2026
const FLAT_PLAN = 25 // supabase.com/pricing, Pro, Aug 2026
const monthlyCost = (utilization) => 1 * HOURS_PER_MONTH * utilization * NEON_CU_HOUR
const breakEvenUtilization = FLAT_PLAN / (HOURS_PER_MONTH * NEON_CU_HOUR)
console.log(`always-on: $${monthlyCost(1).toFixed(2)}/mo`)
console.log(`break-even vs $${FLAT_PLAN}/mo flat: ${(breakEvenUtilization * 100).toFixed(1)}%`)
always-on: $77.38/mo
break-even vs $25/mo flat: 32.3%
A database that's genuinely busy for roughly a third of the month costs the same either way. Below that line, usage billing wins by a widening margin, an ephemeral preview branch that wakes for ten minutes per PR is basically free. Above it, an always-on single compute unit runs $77.38 a month, over three times a flat plan. I walk through the full utilization table (5% through 100%) in the original breakdown, worth a look if you're sizing a specific workload rather than eyeballing the crossover.
One catch: Supabase's $25 includes 8 GB of disk, 250 GB of egress, auth and object storage, so it's a full backend product, not a database line item. The crossover tells you about compute, not about what you'd otherwise pay to assemble the rest.
Neon: Cheap Compute, a Quiet Repo
Neon dropped its monthly minimum entirely. Launch plan is pure usage billing at $0.106 per compute-hour and $0.35 per GB-month, suspending after 5 minutes idle (configurable down to 1 minute on Scale). A paid project sitting idle all month now costs nothing for compute, which makes per-branch, per-agent databases a rounding error instead of a line item somebody has to approve.
Databricks closed its roughly $1 billion acquisition of Neon in May 2025, and the stated reason explains the pricing: about 80% of databases on Neon were being spun up by AI agents, not people, a workload that only makes sense on per-second billing with a zero floor.
The part almost nobody checks is the open source repo. neondatabase/neon is Apache 2.0 with around 22,900 stars, but it landed exactly four commits in all of 2026, one of which just swapped a README link. Most recent tagged release: July 2025.
Use Neon as the excellent managed service it is. Don't build a plan around self-hosting it, or around upstream fixes landing on your timeline.
Supabase: A Platform That Happens to Include Postgres
Supabase Pro is $25 a month flat, 8 GB disk, 250 GB egress, a Micro compute instance included. No scale-to-zero on paid plans, the flat fee is a floor, not a cap, since the database stays up continuously.
Free tier projects pause after a week of inactivity, fine for a side project, annoying for a demo you show a client monthly. What you're really paying for on Pro is everything wrapped around the database: auth, row-level security, realtime, edge functions, a generated REST layer. Its GitHub repo (supabase/supabase, ~108,000 stars) had a commit the same day this was checked, a sharp contrast to Neon's.
Quick Comparison
| Neon | Supabase | |
|---|---|---|
| What it is | Unbundled Postgres | Backend platform with Postgres |
| Paid entry | No minimum, $0.106/CU-hour | $25/month flat |
| Scale to zero on paid | Yes | No |
| Repo activity (2026) | 4 commits | Daily |
How to Pick
Per-branch or per-preview databases: Neon, not close. Agent or batch workloads that spike and vanish: Neon, for the same reason Databricks bought it. Need auth, storage and realtime too: Supabase, and stop comparing raw compute rates, price the whole stack. Steady traffic above roughly a third utilization: run your own version of the arithmetic above with your real compute size before assuming usage billing wins.
A Few Things Worth Getting Right
Measure your actual utilization (a week of CPU-active time divided by hours in that week) before picking a billing model, that single number decides which shape wins. Use a pooled connection from serverless functions, not a direct one per invocation, or you'll exhaust Postgres connection slots before you exhaust budget. Our Connection String Parser is handy for confirming which endpoint and sslmode you actually pasted. And don't cron a keepalive ping to dodge cold starts, that quietly converts a usage bill back into an always-on bill, the one move that erases the whole point of scale-to-zero; if you do need scheduled jobs, size the interval with something like a Cron Expression Generator instead of guessing.
Neon is the better database, Supabase is the better platform, and comparing them on compute price alone will mislead you in whichever direction you were already leaning.
Top comments (0)