Supabase Pricing 2026: What You'll Actually Pay
Supabase pricing is base-plus-usage: $25 Pro plus metered MAUs, egress and compute. Real monthly costs for four app profiles, the hidden charges, and a flat alternative.
That is the short answer. The longer answer — and the reason Supabase bills climb past $25 — is that Pro is a base plus usage model: a flat plan fee, a dedicated Postgres compute instance, and metered charges for extra monthly active users, disk, bandwidth and storage. Supabase is genuinely predictable while you stay inside the quotas, but the moment you switch off the spend cap the meter starts running. Below we break down every charge, compute the real monthly cost for four app profiles from Supabase's published rates, walk through two worked examples, and cover the flat-price alternative if a single all-in number matters more to you than a managed Postgres platform.
How does Supabase pricing work in 2026?
The layers, from Supabase's own pricing page (supabase.com/pricing):
- Plan fee (per organization) — Free $0, Pro $25/month, Team $599/month, Enterprise custom. Pro includes 100K MAUs, 8 GB disk, 250 GB egress and 7-day backups.
- Compute — every project gets a dedicated Postgres instance, billed hourly. Paid plans include $10/month of compute credits, enough to cover one Micro instance; larger instances cost more.
- Metered usage (over quota) — $0.00325 per MAU, disk at $0.125/GB, egress at $0.09/GB, cached egress at $0.03/GB, and storage at $0.021/GB.
- Add-ons — custom domains at a flat $10/month, point-in-time recovery, and log drains at $60 per drain, per project.
The key difference from a truly flat host: the $25 is a floor, not a ceiling. It stays $25 only while you are inside every quota — MAUs, disk, egress and compute all have their own meters underneath.
What will you actually pay? Cost by app profile
We estimated these from Supabase's published rates (Pro $25 with $10 compute credit, MAU $0.00325, egress $0.09/GB, disk $0.125/GB) for always-on projects.
| App profile | What it runs | Est. Supabase / month | shiply.now (flat) |
|---|---|---|---|
| Hobby / prototype | Free plan, 1 project, Micro compute | $0 | $0 |
| Small production app | Pro, within quotas, Micro compute | ~$25 | $8 |
| Growing SaaS | Pro + Small compute + extra egress | ~$60 | $24 |
| Busy app over quota | Pro + Medium compute + MAU + egress overage | ~$120+ | $24 |
Worked example: a small production SaaS
Take the third row — a growing SaaS on Pro that has moved past the free Micro instance and serves real traffic:
- Pro plan = $25 (includes $10 compute credit)
- Small compute instance — upgrade from Micro, roughly $15 after the credit is applied
- Egress — 450 GB used, 250 included, 200 over at $0.09 = $18
- MAUs — 90,000, inside the 100K quota = $0
- Custom domain add-on = $10
That is roughly $68 a month for one growing app — and it climbs the moment MAUs cross 100K or compute needs bump up again. The same app on shiply.now is a flat $24, with no MAU meter and no egress meter.
Worked example: a busy app that outgrew the quotas
Scale that up — a popular app on Pro with a bigger compute instance, more users and heavier traffic, spend cap off:
- Pro plan = $25
- Medium compute instance — roughly $50 after the credit
- MAUs — 160,000, 60,000 over at $0.00325 = $195
- Egress — 700 GB, 450 over at $0.09 = $40.50
- Disk — 30 GB, 22 over at $0.125 = $2.75
That is about $313 a month — the kind of bill that grows with every active user and every gigabyte. On a flat plan, neither moves it.
The hidden costs that inflate a Supabase bill
In order of how often they catch people out:
- Compute upgrades — the $25 includes only $10 of credit, enough for a Micro instance. A busier app needs a Small, Medium or larger instance, billed hourly on top.
- MAU overages — at $0.00325 each, users past the 100K quota add up fast; 60,000 extra is nearly $200 a month.
- Egress and cached egress — $0.09/GB over 250 GB, plus $0.03/GB cached; an image-heavy app or public API adds real cost.
- Spend cap off — Pro ships with a spend cap on. Turn it off to scale past quota and there is no ceiling on the bill.
- Add-ons — custom domains ($10/month), point-in-time recovery, and log drains ($60 per drain, per project) all stack on.
None are hidden in Supabase's docs. They are just easy to leave out when you quote yourself the $25 sticker price.
Supabase vs Railway vs Render: which pricing model fits?
The practical read: Supabase suits Postgres-first apps that want auth, storage and APIs bundled and predictable pricing while small; Railway suits spiky, variable workloads where idle time should be near-free; Render suits steady always-on services that want a flat instance price. What none of them offer is one flat number covering database, compute, bandwidth and users — which is the gap shiply.now fills. We go deeper in the Railway pricing breakdown and the Render pricing breakdown.
How to estimate your Supabase bill before you deploy
A quick sanity-check: assume a real production app needs a Small compute instance and moderate traffic, so ~$40–$60 before it gets popular. If that number, or the prospect of a user spike moving it, makes you wince, a flat plan is worth a look before you build the bill in.
When Supabase's pricing is the right call
None of this makes Supabase a bad product — it is the strongest open-source Postgres platform going, and the free tier is genuinely generous. It makes it a base-plus-usage one, where a competitive plan fee is bundled with metered compute, users and bandwidth. Knowing how big your app will get is the whole decision.
Three ways to cut a Supabase bill
- Right-size compute. The $10 credit covers a Micro instance; only move to Small or Medium when the database actually needs it, and scale back down in quiet periods.
- Watch egress. Serving images and API responses straight from Supabase bills $0.09/GB over 250 GB. A CDN in front, caching and compression take a real bite out of it.
- Keep the spend cap on. It caps you at the plan quota so a traffic or user spike cannot silently balloon the bill — turn it off only deliberately.
These help, but they are all ongoing maintenance — you are managing meters and a compute dial. The alternative is to have neither.
Is Supabase worth it? A quick verdict
Put simply: Supabase gives you a superb Postgres platform at a low entry price, then bills compute, users and bandwidth on top. That is the right trade for many teams and the wrong one for others. If you find yourself right-sizing compute, watching egress and guarding the spend cap to keep costs down, that effort is the real price — and it is the effort a flat plan removes.
The flat-price alternative: shiply.now
It is also built for agents: your AI tool publishes in one HTTP call, with no account needed to start and no build step to wait on. If you are weighing metered and base-plus-usage hosts more broadly, the same logic runs through the flat vs metered pricing guide and our flat pricing.
How to move from Supabase to shiply in four steps
- Export your app from Supabase — the built output, plus your Postgres schema and seed data.
- Create a free account on shiply.now and pick a flat tier.
- Publish in one call from your agent or the CLI — you get a live URL, a SQL database, and a custom domain.
- Point your domain at the new site and retire the Supabase project. The bill is now flat.