Layer 3 · self-hosting reality check
What it actually takes to self-host Supabase
The docs say 4 GB. In practice you want 8 GB. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Firebase alternatives, where Supabase is one of the picks.
| RAM — documented minimum | 4 GB |
|---|---|
| RAM — what it really needs | 8 GB |
| CPU | 4 vCPU |
| Disk | Database size × 2 for WAL and backups |
| Monthly cost | $30–60/mo self-hosted, against $25+/mo on their cloud — the saving is real but smaller than most self-hosting moves |
| Setup time | Half a day |
| How you install it | docker compose — it is roughly eight services (Postgres, GoTrue, PostgREST, Realtime, Storage, Kong, Studio, and the meta service) |
| Ongoing maintenance | High for a self-hosted stack. You own Postgres upgrades, JWT secret rotation and the coordination of eight components that release independently. |
| Where it stops scaling | Fine for internal tools and modest apps. At real traffic you are operating a Postgres cluster, and that is the actual job. |
The thing that catches people out
Self-hosted Supabase is not the hosted product minus the bill. Automated backups, point-in-time recovery, connection pooling at scale, and the dashboard's more advanced features are either absent or yours to build. Read their self-hosting docs honestly before committing — a good number of teams migrate back.
When not to self-host Supabase
You chose Supabase to avoid running infrastructure. Self-hosting it reinstates exactly the work you were paying to skip, and their hosted pricing is reasonable.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 3 self-hosting guides
Common questions
- How much RAM does Supabase actually need?
- 8 GB in practice. The documented minimum is 4 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 4 vCPU alongside it.
- What does self-hosting Supabase cost per month?
- $30–60/mo self-hosted, against $25+/mo on their cloud — the saving is real but smaller than most self-hosting moves This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for high for a self-hosted stack. You own Postgres upgrades, JWT secret rotation and the coordination of eight components that release independently.
- How long does it take to set up Supabase?
- Half a day, via docker compose — it is roughly eight services (Postgres, GoTrue, PostgREST, Realtime, Storage, Kong, Studio, and the meta service).
- When should I NOT self-host Supabase?
- You chose Supabase to avoid running infrastructure. Self-hosting it reinstates exactly the work you were paying to skip, and their hosted pricing is reasonable.
- What is the most common mistake when self-hosting Supabase?
- Self-hosted Supabase is not the hosted product minus the bill. Automated backups, point-in-time recovery, connection pooling at scale, and the dashboard's more advanced features are either absent or yours to build. Read their self-hosting docs honestly before committing — a good number of teams migrate back.