Best VPS for Supabase in 2026
Updated Aug 2026 · 8 plans benchmarked
Self-hosted Supabase is not one app — it is a Postgres database plus roughly a dozen containers (auth, REST, realtime, storage, functions, a Kong gateway, Studio) started together by one compose file. That stack has a real floor: 4 GB before your own data is in it, and disk that can keep up with Postgres write patterns rather than just being large.
- 4 GB is the floor, not the target. Postgres wants the biggest share, and the surrounding services each take a few hundred megabytes — 8 GB is where a self-hosted Supabase stops feeling tight once you have real traffic.
- Disk IOPS matter as much as capacity. Postgres under concurrent writes is latency-sensitive, so insist on NVMe rather than network storage or spinning disks, and remember the storage service keeps user uploads on the same volume unless you point it elsewhere.
- Budget CPU for the containers you forget about: realtime holds websocket connections, the storage service does image transformations, and edge functions execute your code — all on the same box. Two vCPUs is a minimum, four is more comfortable.
- Treat backups and secrets as part of sizing. The compose file ships example credentials that must be replaced, Studio and the database must never be exposed directly to the internet, and a Postgres backup routine is the difference between a hobby stack and a usable one.
The picks
Cheapest route to genuine headroom — a dozen containers plus Postgres get real breathing room here without the bill that much memory usually carries elsewhere.
The cheapest honest fit: the CX32 (4 vCPU / 8 GB NVMe) clears the stack's floor with room for your own data, rather than the 4 GB box that technically boots and then struggles. The best price/performance ratio here by a wide margin.
The stack's needs are lopsided — lots of RAM for Postgres, moderate CPU — and custom sizing lets you buy exactly that. Hourly billing is also the cheapest way to actually run the full compose stack for a day and see what it needs.
The pragmatic pick if you'd rather not operate Postgres yourself: run the Supabase services on a Droplet and point them at a managed Postgres with its own backups and failover. Predictable pricing, at a premium over the value options.
The picks, side by side
Prices verified Aug 2026 · How we benchmark →
Common questions
How much RAM does self-hosted Supabase need?
Plan for 4 GB as an absolute floor and 8 GB for anything real. The compose stack runs Postgres alongside auth, REST, realtime, storage, functions, a gateway and Studio — Postgres takes the largest share, and the rest add up to more than people expect.
Can I run Supabase on a $5 VPS?
Not the full self-hosted stack. A dozen containers plus Postgres will not fit comfortably in the 1–2 GB those plans typically give you. The cheapest realistic route is an 8 GB box from a value provider, which still costs a fraction of a managed backend.
Should I self-host Supabase or use the hosted version?
Self-host when you need data residency, want to avoid per-project pricing, or already operate Postgres. Use the hosted version when you'd rather not own upgrades, backups, and the security of a directly internet-facing database — the self-hosted stack gives you the same APIs but hands you all of that.