Deploy
Self-host Supabase, without managing servers.
Run the full open-source Supabase stack, Postgres, Auth, Storage, Realtime, and auto-generated APIs, as a one-click template on a server we provision and maintain for you. The control of self-hosting Supabase, with none of the server upkeep.
Why self-host Supabase the hard way, when Selfhost.dev can run it for you?
What you get
The whole Supabase stack.
On infrastructure you control.
Supabase is the open-source Firebase alternative: a Postgres database with authentication, file storage, realtime subscriptions, and instant APIs. With Selfhost.dev you deploy it as a one-click template onto your project server, so you self-host Supabase without standing up Docker, wiring a reverse proxy, or maintaining the host. We run the server; you own the stack.
Deploy in 5 steps
From zero to live.
No server to set up.
Self-hosting Supabase usually means a Docker Compose file, a reverse proxy, TLS certificates, and a server you keep patched. On Selfhost.dev it is five steps and no server maintenance.
Create a Project
Give it a name and Selfhost.dev provisions a dedicated server for you. There is no cloud or region wrangling, the server is ready in a couple of minutes.
Add the Supabase template
From the project's add-service screen, choose the Supabase template. It deploys the full open-source stack, Postgres, Auth, Storage, Realtime, and the API gateway, in one click.
Set your environment variables
Accept the generated secrets or set your own. Paste a .env to import in bulk, the database password, JWT secret, and API keys are wired into the stack for you.
Point your domain
Use the default wildcard subdomain on selfhost.dev, or add your own domain: drop in the DNS records, verify with a TXT record, and HTTPS goes live automatically.
Connect your app
Use the project Postgres connection string and the Supabase API URL and keys from your app. Watch CPU, memory, and connections live from the project metrics.
Environment variables
Configure it
in minutes.
Supabase self-hosting relies on a handful of secrets and URLs. Selfhost.dev generates sensible defaults you can override:
Paste a .env to import in bulk, or set keys one by one. Values are wired into every build and deploy.
Key variables
Why Selfhost.dev
Supabase, the easy way.
On a server you control.
The full open-source stack
Postgres, Auth, Storage, Realtime, and auto-generated REST APIs, the same Supabase you know, self-hosted on your server.
A server you control
Your Supabase runs on a dedicated project server with live metrics and full logs, not a shared black box. Your data stays on infrastructure you control.
Nothing to maintain
No Docker Compose to babysit, no reverse proxy to debug, no OS to patch. Selfhost.dev provisions and runs the server; you use Supabase.
Custom domain + SSL
Add your domain, verify DNS, and HTTPS is provisioned and renewed automatically. A wildcard subdomain works out of the box.
Pay only for what you run
Billed by the hour against prepaid credits. A project server starts around $0.02/hr, about $0.50 a day, and pauses at a zero balance.
Drive it with AI
Manage the project, its domains, env vars, and databases from Claude, Cursor, or any MCP client with 150+ MCP tools.
Self-host vs cloud
Self-hosted Supabase
vs Supabase Cloud
The choice usually comes down to control versus convenience. Self-hosting Supabase gives you full ownership, your data, your server, your config, but you run the Docker stack, reverse proxy, TLS, and upkeep yourself. Supabase Cloud removes all of that, but your data lives on their infrastructure with usage-based pricing. Selfhost.dev is the middle path: the self-hosted open-source stack on a server you control, with the operations handled for you and predictable hourly pricing.
Self-host it yourself
Full control and data ownership, but you own the ops, Docker, reverse proxy, TLS, patching, uptime.
Supabase Cloud
Zero ops, but your data sits on Supabase's infrastructure with usage-based billing.
Selfhost.dev
The self-hosted open-source stack with your control, and we run the server. Predictable pay-as-you-go by the hour.
For a full head-to-head, see our Selfhost.dev vs Supabase comparison.
Self-hosted Supabase vs managed PostgreSQL
If you want the whole Supabase backend, Auth, Storage, Realtime, and APIs, deploy the Supabase template. If you only need a production-grade Postgres database with PITR, connection pooling, and Multi-AZ, a dedicated managed PostgreSQL instance is the better fit. Many teams run both on one account.