Neon: the widest cost swing in managed Postgres

Verdict: Neon is the cheapest managed Postgres to idle and one of the most expensive to keep on — the same provider, at both ends of the price list, depending only on how many hours a day your database is actually busy. “What does Neon cost” has no single answer, and that’s the point.

One provider, both ends of the board

Across the four workloads Neon’s total ranges from free to several hundred dollars, and its rank swings from first to the bottom third. Because compute scales to zero, an idle side project fits inside the free plan, and Neon is first on price. On a bursty workload — big but only busy part of the day — scale-to-zero reclaims the quiet hours and Neon is near the top again, behind only Xata, a newer service that also bills by the active hour.

Then keep it on. For a steady, always-on small app, Neon’s metered compute runs 24/7 and it drops into the bottom third of the ranking — roughly $160 a month, about twice the cheapest options and well above flat-priced plans like PlanetScale’s (~$97, as of the snapshot). Nothing about Neon changed; the duty cycle did. This is why a single “Neon price” misleads: quote the free hobby number to a team running always-on and you’ve told them nothing.

Where the model pays you back — and where compliance takes it away

The same architecture that makes Neon cheap to idle makes its high availability free. Neon keeps no standby server: data is replicated across three zones, and if a zone fails, the database restarts elsewhere, which Neon says takes one to ten minutes. There’s nothing extra to pay for, but there is a recovery time to plan around. A regulated workload also needs a BAA, and Neon offers one only on its Scale plan, at roughly double the Launch compute rate. On the production-HA workload that puts Neon mid-table among the services that qualify, above Cloud SQL, RDS and Azure but below Aurora. It still clears HA, PITR and HIPAA outright, where several cheaper-looking options are struck out.

The ownership footnote

The “independent serverless Postgres” framing is now dated: Neon was acquired by Databricks in 2025, and Databricks’ own Lakebase is built on Neon’s engine. It’s still native Postgres and the pricing above is unaffected, but if avoiding hyperscaler lock-in is why you were looking at Neon, that reason has quietly expired.

So, when Neon

• Yes: spiky, bursty, or genuinely idle workloads; anything that benefits from scale-to-zero; HA where a restart of a few minutes after a zone failure is acceptable.
• Reconsider: a small database that’s simply on all the time, or always-on regulated production — a flat-tier provider or a hyperscaler beats Neon on those shapes, and they’re the cases the hobby-tier reputation gets wrong.