People search “Supabase self-hosting cost” expecting a number. The honest answer is that the money is the small part: self-hosting Supabase means operating their entire platform — Postgres, auth server, storage service, realtime server, edge runtime and the glue between them — yourself. This post breaks down what that actually costs, and when a different shape of ownership is saner.
Key takeaways
- Self-hosted Supabase is free to license, but you’re running ~10 coordinated services.
- The real costs are a beefier server and the operational attention of a small platform team.
- If what you want is ownership, running one compiled binary is a fundamentally lighter way to get it.
- Staying on Supabase’s cloud is a legitimate choice — it’s their platform run by the people who built it.
What “self-hosting Supabase” actually means
Supabase open-sources its platform, which is genuinely commendable. But the platform is a composition: Postgres plus separate services for auth, storage, realtime, APIs and functions, typically orchestrated with Docker Compose. Self-hosting it means you become the operator of all of them — upgrades, migrations between versions, inter-service config, and the debugging when one of the ten moving parts disagrees with another.
The cost breakdown
- License: $0. Genuinely free and open source.
- Hardware: the full stack wants real resources — plan for a mid-tier VPS or small dedicated server, not the $5 droplet.
- Attention: this is the dominant term. A platform of coordinated services needs the kind of care a DevOps-comfortable person gives it. If that’s you and you enjoy it, it’s a fine hobby-to-prod path.
- What you save: the managed-cloud subscription and its usage-based growth — the compounding math that probably brought you to this search.
The question behind the question
Most people searching this don’t specifically want Supabase-on-their-server — they want their backend on their server: their users’ data in their database, no usage meter, no platform dependency. If that’s the actual goal, there’s a lighter shape: a single compiled backend with auth, data, files and payments built in, written by your AI as code you own. One binary to run instead of ten services to operate — the full comparison with Supabase is candid about both directions.
When each path wins
| You want | Sane choice |
|---|---|
| Managed Postgres + ecosystem, no ops | Supabase cloud |
| The exact Supabase stack, on your hardware, and you like ops | Self-hosted Supabase |
| Your product’s backend as your own lightweight code | An owned backend (jerrycan) |
Frequently asked questions
Is self-hosted Supabase production-ready? The components are; the burden is the orchestration. Teams do run it — budget the operational attention honestly.
Does jerrycan use Supabase under the hood? No — it’s a self-hostable Rust backend framework; your AI generates your backend as code, with a standard database you control.
What’s the cheapest ownership path? One compiled binary on a small VPS. That’s the shape jerrycan optimizes for — tens of dollars monthly, flat.
Own the thing you actually need. If that’s the full Supabase platform, self-host it with eyes open; if it’s your backend, one sentence gets you one.