PaaS & DevOpsSave ~$816/yr vs Supabase Pro + Compute Add-on
Self-Hosting Supabase on a VPS (2026): Real RAM, Docker Stack & Cost
Self-hosted Supabase runs 12+ services (Postgres, Kong, GoTrue, PostgREST, Realtime, Storage, Meta, Studio, Analytics). Baseline idle RAM is ~2.4–3.0 GB. Deploy on KVM 2 (8 GB, ~$7.03/mo) for single projects or KVM 4 (16 GB, ~$10.39/mo with XF3PLUTARXVF) for high-traffic production.

RATE SHEET
November 22, 2026Hardware Spec & Verified Rate Sheet: Supabase
| Provider / Tier | Hardware & Architecture | List | Net Benefit | Code | Link |
|---|---|---|---|---|---|
Hostinger KVM 2 Recommended for Supabase | 2 vCPU AMD EPYC · 8 GB DDR5 · 100 GB NVMe · 8 TB | $8.79/mo | ~$7.03/mo (-20%) | Claim -20% | |
Proton (VPN & Privacy) WireGuard + VPS Privacy | Gluetun WireGuard + NAT-PMP · Swiss No-Logs · Mail/Drive/Pass | Subscription | $20 USD credit | Claim $20 |
01 Open the link to bind XF3PLUTARXVF (-20%) or 5AA9X0DA ($20 USD).02 Pick 12/24-mo KVM VPS or Proton Plus/Unlimited.03 Deploy Ubuntu 24.04 + Docker + WireGuard tunnel.
01 / HARDWARE TELEMETRY
Measured RAM, vCPU & NVMe Profile for Supabase
Min → Rec RAM
4 GB → 16 GB
Idle 2650 MB · Peak 7800 MB
Min → Rec vCPU
2 → 4 vCPU
AMD EPYC / High-Clock
Min → Rec NVMe
50 → 200 GB
PCIe Gen4 NVMe SSD
Primary Bottleneck
PostgreSQL shared_buffers + Logflare Analytics + Realtime Elixir cluster RAM
Projected Memory Footprint on Hostinger KVM 2 (8 GB RAM)Idle 32% · Peak 95% · Headroom 5%
02 / DOCKER COMPOSE & SHELL
Docker Stack SizerProduction Deployment Stack (Supabase)
docker-compose.ymlyaml
# Production memory override for official supabase/docker compose:
# Place alongside supabase/docker/docker-compose.yml as docker-compose.override.yml
services:
db:
deploy:
resources:
limits:
memory: 3G
kong:
ports:
- "127.0.0.1:8000:8000"
deploy:
resources:
limits:
memory: 512M
realtime:
deploy:
resources:
limits:
memory: 768M
analytics:
deploy:
resources:
limits:
memory: 768Mdeploy-and-verify.shbash
git clone --depth 1 https://github.com/supabase/supabase /opt/supabase
cd /opt/supabase/docker && cp .env.example .env
# Generate strong JWT_SECRET, POSTGRES_PASSWORD, ANON_KEY & SERVICE_ROLE_KEY before booting!
docker compose pull && docker compose up -d03 / PRODUCTION FIELD NOTES
Critical Operational Insights
Disabling the `analytics` (Logflare) container saves ~650 MB RAM immediately on 4–8 GB nodes.
NVMe random 4K IOPS directly govern PostgreSQL transaction throughput — avoid legacy SATA/HDD VPS tiers.
04 / SECURITY & PRIVACY
UFW Firewall, TLS & WireGuard / ProtonVPN Hardening
Never leave default .env JWT/Postgres passwords or Studio basic auth credentials. Place Studio behind a VPN (WireGuard/Headscale) or Cloudflare Zero Trust Access rather than public basic auth.
Isolate container egress with ProtonVPN WireGuard + Proton Suite (US$20 in credits · code
5AA9X0DA).Claim US$20 on Proton05 / VERIFIED DEPLOYMENT STACK
Deploy on Verified Infrastructure
KVM COMPUTE · EXTRA −20%
Hostinger KVM 2
~$7.03/mo
$8.79/mo
vCPU
2 EPYC
RAM
8 GB
NVMe
100 GB
24m Save
~$42
Renew: $12.99/mo · Free backups
SWISS PRIVACY · ACCOUNT CREDIT
Proton VPN & Unlimited
US$20
in credits
Tunnel
WireGuard
Docker
Gluetun + NAT
Suite
VPN·Mail·Drive
pr.tn/ref/5AA9X0DA
Frequently Asked Questions
Does self-hosted Supabase support multiple projects per VPS?
Officially one Supabase stack equals one project; you can isolate multiple apps via separate Postgres schemas or run multiple stacks on a KVM 4 (16 GB) / KVM 8 (32 GB) host.


