Plug in your database size, compute usage, egress, MAU, and PITR requirements. The calculator computes both providers’ monthly bills using verified May 2026 list pricing and highlights the cheaper option in real time.
Supabase and Neon do not price along the same axes, which is why founders consistently underestimate the cost of one of them after switching. Supabase charges a flat $25/month for Pro plus per-unit overages on storage, egress, and MAU above generous included quotas. Neon charges nothing flat — you pay $0.106 per CU-hour of compute, $0.35 per GB-month of storage, and $0.10 per GB of egress over 100 GB included, with scale-to-zero stopping the compute meter when nobody’s querying. At low compute and high egress, Supabase wins. At high compute and low egress, Neon wins. This calculator does the math at your inputs.
Methodology. Pricing verified against supabase.com/pricing and neon.com/pricing as of May 2026. Both vendors change pricing models frequently; treat this calculator as a snapshot. Calculations use list pricing; volume discounts available at higher tiers are not modeled.
Direct rate-versus-rate comparison is impossible because the two providers expose different units. Supabase bundles things into a plan; Neon unbundles into metered components. Here are the verified line items the calculator runs against.
| Component | Included | Overage rate |
|---|---|---|
| Base fee | $25/mo (includes $10 compute credit) | n/a |
| Database storage | 8 GB | $0.125 / GB-month |
| Egress / bandwidth | 250 GB | $0.09 / GB |
| Monthly active users (auth) | 100,000 | $0.00325 / MAU above 100K |
| File storage | 100 GB | $0.021 / GB |
| Edge function invocations | 2,000,000 | $2 per 1M |
| Compute — Micro | Covered by $10 credit | $0/mo net |
| Compute — Small | $15/mo gross | $5/mo net after credit |
| Compute — Medium | $60/mo gross | $50/mo net after credit |
| Compute — Large | $110/mo gross | $100/mo net after credit |
| PITR add-on | not included | $100/mo (7-day retention) |
| Free tier limits | 500 MB DB / 5 GB egress / 50K MAU; project pauses after 7 days idle | n/a |
| Team plan | $599/mo | SOC 2, ISO 27001, priority support |
| Component | Included | Rate |
|---|---|---|
| Base fee | $0/mo (no minimum) | pay-as-you-go |
| Compute | nothing pre-bundled | $0.106 / CU-hour (1 CU = 1 vCPU + 4 GB RAM) |
| Storage | nothing pre-bundled | $0.35 / GB-month |
| Data transfer (egress) | 100 GB / month | $0.10 / GB above 100 GB |
| Branches | 10 included | $1.50 / branch-month above 10 |
| Snapshots | 10 manual per project | $0.09 / GB-month archive |
| Scale-to-zero | default ON, suspends after 5 min idle | $0 compute while suspended |
| Free tier limits | 0.5 GB storage / 100 CU-hours / 5 GB egress / 10 branches / 6-hour restore window | n/a |
| Scale plan | pay-as-you-go; $0.222 / CU-hour | PITR (30-day restore), 99.95% SLA, HIPAA, SOC 2, 25 branches included |
| Business plan | custom | dedicated infra, premium support |
Plugging the same workload into both providers yields wildly different numbers because the cost models attack different parts of the bill. Here are the five differences that explain almost every variance.
Supabase Pro charges you for compute every hour of every day, whether your app has traffic or not. The Pro plan’s $10 compute credit covers a Micro instance (1 vCPU, 1 GB RAM) for the full 730-hour month. If you need more — say a Small at $15/mo or a Medium at $60/mo — you pay the difference net of the credit. There is no scale-to-zero option on Supabase. The container runs.
Neon’s pricing for the same compute is unrecognizable. Compute is billed in CU-hours where one CU is 1 vCPU plus 4 GB RAM, the meter starts when a connection arrives, and the meter stops 5 minutes after the last query (configurable). A Neon database that gets 200 active hours of traffic per month at 0.5 CU costs 100 × $0.106 = $10.60. The same workload on Supabase Pro requires the Small (2 GB RAM) compute tier — $25 base + $5 net Small surcharge = $30/mo. At 730 active hours per month at 1 CU (no idle time at all), Neon’s compute alone hits $77.38 — well past Supabase Pro’s $25 + $50 net Medium upgrade of $75 for equivalent 4 GB RAM. The crossover point on the database line item alone is roughly 235 billable CU-hours; below that, Neon wins compute. Above it, Supabase does.
Supabase Pro hands you 8 GB of Postgres storage at no extra cost. At a $0.125/GB-month overage rate, that 8 GB is worth $1/month of value baked into the $25 plan fee. Most solo SaaS never exceed 8 GB — a B2B app with 1,000 customers and modest tabular data sits at 1–3 GB.
Neon charges $0.35/GB-month for every gigabyte of stored data, starting at byte one. A 5 GB Neon database costs $1.75/month in storage alone. At 20 GB the storage bill is $7. The Neon storage line is also higher per-GB than Supabase’s overage rate ($0.35 vs $0.125), which means once you cross Supabase’s 8 GB included quota, Supabase actually has cheaper marginal storage. This catches people who assume serverless = always cheaper.
This is where Supabase quietly wins for content-heavy products. Supabase Pro includes 250 GB of egress per month before charging $0.09/GB. Neon Launch includes 100 GB before charging $0.10/GB. A consumer SaaS pushing 500 GB/month of data to clients pays $22.50 in Supabase egress overage versus $40 in Neon egress overage — a $17.50/month gap that grows linearly with traffic. For an indie product streaming media or shipping JSON to mobile clients, this gap can swamp every other savings.
Supabase Pro’s $25 is not just for a Postgres database. It includes authentication for 100,000 MAU, S3-compatible file storage with 100 GB included, edge function execution with 2M invocations, and a realtime layer that streams Postgres changes to clients. If you used Neon and bolted on equivalent services, you’d be looking at Clerk Pro at $25/mo for auth, Cloudflare R2 or AWS S3 for files, Cloudflare Workers or Vercel functions for edge compute, and Pusher or Ably for realtime. The marginal cost of replicating Supabase’s bundle around a Neon database is typically $40–$80/month, sometimes more. We walked through that stack in best Supabase alternatives and Supabase vs Firebase.
Neon Launch includes 10 instant database branches at no extra cost; Scale includes 25. These are real isolated copies of your production database that spin up in seconds and only bill for the compute used while they’re queried. Solo founders use them as per-pull-request preview databases and as staging environments that don’t need a second always-on instance. Supabase has a preview branching feature but it requires a second Supabase project per environment, which means a second $25/month plan if you want non-trivial staging. Branching isn’t a line item on either bill, but it’s a real workflow cost that lands differently.
Run these inputs through the calculator to confirm; the math is shown for transparency.
Cost is the most measurable axis but rarely the most decisive. Three honest concessions.
Supabase’s bundling is the feature. Authentication that ties into row-level security policies you write in SQL is genuinely valuable. File uploads that respect those same policies. Realtime subscriptions that fire when a Postgres row changes. A polished dashboard where you can edit data like a spreadsheet. If you’d be hand-rolling these on top of Neon, the time cost is more than the dollar gap. We covered the deeper case in is Supabase’s free tier enough for SaaS and Supabase pricing explained.
Neon’s branching is the feature. Per-pull-request preview environments with isolated databases is a workflow nobody using Supabase replicates without significant effort. If your team ships schema migrations weekly, the safety net is worth real money. The Vercel integration that auto-provisions a Neon branch per preview deployment is something Supabase cannot match technically. For Postgres-native teams using Prisma or Drizzle, Neon feels like the database was built for you.
The cost answer changes annually. Both companies have re-architected pricing multiple times in the last 24 months. Neon moved from fixed Launch ($19/mo) and Scale ($69/mo) plans to pure usage-based pricing with no minimums. Supabase has tightened its Pro plan compute credit model. Re-run this calculator before any migration decision — what was true six months ago may not be true today.
| Profile | Pick | Why |
|---|---|---|
| Pre-revenue side project, low traffic, hates downtime | Neon free | Stays available 24/7 (scale-to-zero, no inactivity pause). Supabase free tier pauses after 7 days idle. |
| Solo B2B SaaS, Postgres-only needs, Prisma or Drizzle ORM | Neon Launch | Pay-as-you-go compute beats Supabase’s always-on container for typical business-hours traffic. Branching is real value. |
| Solo founder needing auth + storage + DB in one bundle | Supabase Pro | $25 includes auth (100K MAU), file storage (100 GB), edge functions (2M invocations), realtime. Replicating around Neon costs more. |
| High-egress consumer SaaS (>200 GB/month bandwidth) | Supabase Pro | 250 GB egress included beats Neon’s 100 GB; per-GB overage is also cheaper ($0.09 vs $0.10). Egress kills Neon at scale. |
| Compliance-required workload (HIPAA, SOC 2, PITR mandatory) | Tie / depends | Neon Scale ($0.222/CU-hour) includes HIPAA + SOC 2 + 30-day PITR baked in. Supabase needs Team plan ($599/mo) for SOC 2, or Pro + $100/mo PITR add-on. Run the calculator. |
Re-read the inputs you fed the calculator. The two values founders consistently get wrong are active compute hours and egress. Compute hours: a typical solo SaaS with traffic in US business hours hits 50–200 active CU-hours per month after Neon’s scale-to-zero kicks in — not 730. If your app has a cron job that pings the database every minute, scale-to-zero never engages and you’re effectively at 730 hours; turn off the toggle in the calculator and re-check.
Egress is the other one. Your egress number is mostly driven by what you ship to clients, not by Postgres internals. A SaaS that serves JSON to a SPA might do 5 GB/month. One that ships images, videos, or large file downloads through Supabase Storage can easily do 100–500 GB/month. Look at your actual Vercel or Cloudflare bandwidth bill from the last three months and use the highest number, not the average. Calculator users systematically underestimate egress.
Finally, the cost difference at the 0–$1K MRR stage is rarely worth optimizing. The full delta between Supabase Pro and an equivalent Neon configuration at $1K MRR is typically $5–$15/month. That’s less than two coffee runs. Pick the platform whose dashboard you find easier to navigate, ship the product, and re-evaluate when you cross $5K MRR — we built a broader cost framework for that stage in SaaS cost at $1K MRR and the true cost of running an AI SaaS. The right answer at $5K MRR is rarely the same as the right answer at $50K, and migrating between Postgres providers takes one weekend.
For more on how Supabase compares head-to-head with Neon on features rather than just price, read Supabase vs Neon. For the broader question of payment infrastructure, our payment processor fee calculator applies the same line-item teardown to Stripe vs Lemon Squeezy.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.