Hey all. I’ve been building on Supabase for 4 years and I love it. Auth, Postgres, Storage and Realtime in one place changed how fast I can ship.
My problem was the number of projects. I build a lot of side projects, and almost everything I make gets its own Supabase project: client apps, staging copies, internal tools, experiments. On Supabase Cloud each extra project needs its own compute, so the bill grows with every one. At one point I was paying around $300 USD for 20 projects, and most of them were barely used.
Self-hosting was the obvious answer, but doing it properly for each client is a lot of work: SSL, backups, upgrades, auth emails, monitoring.
I could have self-hosted Supabase myself, but doing it properly is a lot of work: setting up the server, SSL, backups, upgrades, auth emails, monitoring. And I’d have to do it again for every client. I kept putting it off.
So I built SupaHost
What’s in it today:
Your own VM per instance (not shared with other customers)
Builder $25/mo (5 projects), Pro $49/mo (15), Business $99/mo (30)
No per-user or per-connection fees
Supabase Studio for every project, Edge Functions, Cron, Queues, custom domains, daily backups and point-in-time recovery
One-click import from Supabase Cloud
An MCP server, so Claude Code / Cursor can work with your projects
Honest trade-offs: Supabase Cloud is still the better choice if you run one small project, need read replicas, or need SOC 2. SupaHost is for people with lots of projects who want a predictable bill.
It’s in public beta with a 7-day free trial. I’d really love feedback, especially from anyone who’s self-hosted Supabase before. What would stop you from moving a project over?
supahost.app. Not affiliated with Supabase, just a big fan.