Supabase Pricing: Managed vs Self-Hosted
The cheapest managed Supabase starts at about $25/month. Self-hosted, this stack measures 8 GiB across 8 services, which fits a $49/month flat plan with room left over.
#the numbers
Managed prices as of June 2026, each linked to its source. The self-hosted row is not an estimate: the RAM figure is what this stack allocates in its compose file, and the plan is the smallest one that holds it.
| Option | Plan | Monthly | What you get |
|---|---|---|---|
| Self-hosted on Miget ★ | 8 GiB, 4 vCPU | $49 | the whole stack, flat - no per-user or per-request metering, and the plan holds your other apps too |
| Supabase Cloud | Pro | ~$25 | per org + metered compute/egress/storage/MAUs past included quotas |
Hosted Pro is excellent value at small scale - self-hosting wins on data ownership and once the meters (egress, MAU, compute) start running.
#what it costs on other platforms
Same stack, published rates elsewhere - estimates from each platform's own pricing page, not quotes. Per-service platforms are the expensive case here, because every container in this stack is its own paid service.
| Platform | Estimated monthly | Why |
|---|---|---|
| Miget ★ | $49 | flat plan, 8 GiB - databases included, no meters |
| Heroku | ~$400 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| Render | ~$105 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| DO App Platform | ~$101 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Railway | ~$83 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$50 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
#sizing, if you outgrow the small plan
The $49 plan is the smallest that fits. For production traffic you generally want the next tier up, and dedicated vCPU if the workload is CPU-bound rather than idle-waiting.
| Use case | Plan | Monthly |
|---|---|---|
| Fits the stack | 8 GiB, 4 vCPU shared | $49 |
| Comfortable, room for your own apps | 16 GiB, 8 vCPU shared | $97 |
| Dedicated vCPU (production) | 8 GiB, 4 vCPU dedicated | $85 |
Core stack (no optional profiles) totals ~6.5 GiB. Enabling supavisor + functions + imgproxy adds ~2.5 GiB - size for 16 GiB if you want everything on.
Run Supabase yourself
The compose file is open source and runs locally with docker compose up. One step to deploy it to
Miget on the $49/month plan, databases included.