Neon vs Supabase: the price flips with your duty cycle

Verdict: Neon is cheaper right up until you run the database full-time — then Supabase wins, until you need real HA, where Supabase drops out. The two never trade blows on the same axis, so a flat “which is cheaper” has no answer. The duty cycle decides it.

The flip nobody quotes

Neon bills serverless — compute-time plus storage — and scales to zero when idle. Supabase is a flat plan with a compute add-on: a fixed floor whether you serve one request or a million. That single structural difference is the whole comparison.

Idle or spiky, Neon’s floor is essentially the storage bill and Supabase is paying for a server that’s mostly asleep — so on the hobby workload Neon is cents against Supabase’s flat plan. Push the same small database to always-on (steady 24/7, modest size) and it inverts: Neon’s metered compute now runs around the clock and overshoots Supabase’s fixed plan by roughly 2×. The crossover is duty cycle, not size — Supabase wins the moment you stop scaling to zero.

Bump the workload up but keep it bursty — bigger, but only busy part of the day — and it flips back to Neon: scale-to-zero reclaims the idle hours Supabase still charges for.

The catch at the HA line

At the production-HA workload the two totals land within a few dollars of each other — which reads like a coin toss and isn’t. Supabase offers point-in-time recovery only as a paid add-on, so for a workload that requires PITR it doesn’t clear the bar and is marked disqualified in the dataset. Neon includes it, and because its storage is decoupled from compute, adding a high-availability standby duplicates no storage and the standby itself scales to zero — so HA costs Neon almost nothing. The near-tie on price is really Neon qualifying and Supabase not.

So, which one

• Prototyping, side projects, anything that idles: Neon, decisively — you pay for storage and little else.
• A small app that’s genuinely on 24/7: Supabase — the flat plan beats Neon’s metered clock at low size.
• Bursty production (spiky but real): Neon — scale-to-zero pays for the quiet hours.
• Regulated or HA-required production: Neon — Supabase’s PITR-as-add-on disqualifies it here regardless of the sticker price.

One more thing the price can’t show: Supabase ships auth, realtime, and storage in that plan; Neon is Postgres and nothing else. If you’d otherwise buy those separately, Supabase’s “expensive” steady-state number is buying more than a database.