Search for self-hosted Supabase pricing and you'll get two kinds of answer. Vendors tell you it's free. Blog posts tell you it's cheaper. Neither is a number you can put in a budget.
The honest answer is that self-hosting Supabase moves your costs from a predictable monthly invoice to a mix of infrastructure spend and your own time — and whether that trade is worth it depends almost entirely on how many projects you run. This post breaks down every line item, gives you the break-even point, and is upfront about the cases where self-hosting will cost you more than it saves.
If you want the architectural comparison rather than the money, start with our self-hosted vs cloud comparison instead.
What Supabase Cloud actually costs
The sticker price is $25/month for Pro. That's the floor, not the bill.
The Pro plan includes one project's compute credit, 8 GB of database storage, 100 GB of file storage, 250 GB of egress, and 100,000 monthly active users. Past those lines you pay:
| Resource | Included on Pro | Overage |
|---|---|---|
| Database disk | 8 GB | $0.125/GB/month |
| File storage | 100 GB | $0.021/GB/month |
| Egress | 250 GB | $0.09/GB |
| Monthly active users | 100,000 | $0.00325 each |
The line that surprises people is compute. Every project runs its own Postgres instance and is billed separately. Your $25 covers a credit against the first one. A second project is roughly $10/month more at the smallest instance size, a third is another $10, and so on. Teams running a staging environment alongside production are paying for both.
For a single modest production app, expect $35–75/month once usage is included. For five projects — a production app, a staging copy, and a few side projects — you're at roughly $75/month before any overages, or about $900/year.
What self-hosting actually costs
The server
This is the only line most comparisons include, and it's the smallest one.
Supabase is a dozen containers — Postgres, PostgREST, GoTrue, Kong, Storage, Realtime, and friends. RAM is the binding constraint, not CPU. Rough 2026 pricing:
| Tier | Specs | Indicative cost | Fits |
|---|---|---|---|
| Entry | 2 vCPU / 4 GB | $5–8/month | One project, light traffic |
| Standard | 4 vCPU / 8 GB | $14–24/month | One production project, or 2–3 small ones |
| Multi-project | 8 vCPU / 16 GB | $30–50/month | 4–6 projects comfortably |
Hetzner sits at the low end of those ranges, DigitalOcean and Linode toward the top, and the hyperscalers well above. We've compared the options in detail in best VPS providers for self-hosted Supabase, and the system requirements docs cover sizing.
The key economic difference: on Supabase Cloud, project five costs the same as project two. On your own server, project five costs nothing extra until you run out of RAM. That's the entire arbitrage, and it's why running multiple projects on one host is where self-hosting starts to obviously win.
Backups
Do not skip this line. A self-hosted database with no off-server backup is not cheaper than Cloud — it's a liability with a lower monthly cost.
Object storage for backups is genuinely cheap. Cloudflare R2 runs about $0.015/GB/month with no egress fees; Backblaze B2 is roughly $6/TB/month. A 20 GB database with a month of daily retention lands well under $2/month. Budget $2–5/month and you've covered it.
What costs more than the storage is getting the backup strategy right — including file storage, which is not covered by a database dump, and actually testing that your restores work.
Your time
This is the line nobody quotes, and it's the one that decides the answer.
Initial setup is a few hours if it goes well — provisioning, Docker, TLS, DNS, environment variables, SMTP, OAuth callbacks. Budget a day if you're new to it.
Ongoing is the real question. In a steady state, expect 1–3 hours a month: applying updates, watching disk usage, checking backups actually ran. That's the honest median. It is not the number you'll hit the month Postgres fills a disk at 2am, or when a Supabase release changes a default and your auth flow breaks.
At a $75/hour opportunity cost, two hours a month is $150/month of your time — which is more than the infrastructure and more than Supabase Cloud would have charged you for a single project. If you run one small project and your time has real market value, self-hosting is a bad financial trade. It may still be the right call for data residency, compliance, or because you want control. Just don't tell yourself it's about the money. We've written honestly about reducing that operational burden, but reducing is not eliminating.
The break-even
Putting the lines together for five projects over a year:
| Supabase Cloud | Self-hosted | |
|---|---|---|
| Compute | $75/month | $15/month (one 8 GB host) |
| Backups | Included | ~$3/month |
| Management tooling | Included | $99 once |
| Year one | $900 | $315 |
| Year two onward | $900 | $216 |
The crossover is roughly two projects. At one project, Cloud is competitive once you price your time honestly. At two, self-hosting is ahead on cash. By four or five the gap is wide enough that it stops being a close call — you're comparing $900/year to a little over $200.
The full cost breakdown post works through these numbers in more depth, including the scenarios where the maths goes the other way.
Where management tooling fits
Running the Supabase Docker stack by hand is free. What costs you is everything around it: wiring up S3 backups and a restore path, binding domains and renewing certificates, configuring OAuth providers, scheduling jobs, and knowing whether any of it is currently working.
That's the gap Supascale fills. The open-source CLI deploys Supabase to your VPS at no cost. The paid license adds the web dashboard: automated S3 backups with one-click restore, custom domains with free SSL, OAuth provider configuration, scheduled tasks, resource monitoring, a full REST API, and MCP access so an AI assistant can operate your projects.
Pricing is a one-time license rather than a subscription — $99 for a solo developer, $299 for commercial use inside a company, $799 for agencies managing client infrastructure. Every tier ships the same software with every feature unlocked; they differ only in what the license permits. There's no per-project or per-server fee, and the license is perpetual: updates are included for a year, and the version you have keeps working indefinitely whether or not you renew.
Against $75/month of Cloud spend for five projects, a $99 license pays for itself in about seven weeks.
When self-hosting is the wrong answer
Some cases where you should stay on Cloud, stated plainly:
- One small project and no ops appetite. The maths doesn't work and you'll resent the pager.
- You need managed high availability today. Self-hosted HA is achievable but it is real engineering — see our high availability architecture guide for what's actually involved.
- Nobody on the team is comfortable with Postgres administration. The savings evaporate the first time you need to recover from a bad migration under pressure.
- You're pre-product-market-fit. Your time is worth more spent on the product than on infrastructure.
Self-hosting rewards people who run several projects, have some operational competence, and value control. It punishes people who wanted a cheaper invoice and nothing else.
Frequently asked questions
Is self-hosted Supabase free? The software is. The infrastructure isn't. Budget $5–50/month for a server depending on how many projects you run, plus a few dollars for backup storage, plus your own time.
How many projects can one server run? RAM decides. A 4 GB host handles one project comfortably, 8 GB handles two or three, and 16 GB handles four to six. Postgres alone wants 2–4 GB before the other containers get a share.
Do I pay per project when self-hosting? No. That's the core difference. Additional projects cost you RAM on a server you're already paying for, not another line on an invoice.
What happens to my data if I stop paying for management tooling? Nothing. Your Postgres database, your storage files, and your server are yours. Supascale licenses are perpetual — the version you own keeps running whether or not you renew for new releases.
Can I move from Supabase Cloud to self-hosted without downtime? Close to it, with planning. Our migration guide covers the process, including the auth schema and storage objects that trip most people up.