Deploy
Supabase self hosted. One click. We run the server.
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, secure and run. Supabase self hosted, with none of the server upkeep.
Why self host Supabase the hard way, when Selfhost.dev can run it for you?
One click. The whole stack, wired up.
no signup
+$5.00 added at signup · deployment choice preserved · no card
What is Supabase self hosted?
The whole Supabase stack.
On infrastructure you control.
What it is. Supabase is the open source Firebase alternative: Postgres with authentication, file storage, realtime subscriptions and auto-generated APIs. Here the whole stack deploys as a one-click template onto a dedicated server we run.
Who it is for. Teams who want the Supabase developer experience with their data on a server they control, and who would rather not assemble the Docker Compose stack themselves.
When to use it. When your data cannot sit on someone else's infrastructure, or when you want one predictable server bill instead of usage-based backend pricing.
Supabase self host requirements
What the stack needs, and what we already provide.
Supabase self hosted means running the whole stack behind a gateway with TLS: the database, Auth, Storage, Realtime, APIs, Edge Functions and Studio. The template ships all of it on one server, so you only pick the size.
| Studio | Included, reachable at your service URL |
|---|---|
| Edge Functions | Included |
| Storage | S3-compatible, backed by bundled MinIO on the server volume |
| Analytics and log shipping | Included |
| Available Postgres extensions | pg_cron 1.6.4, pgvector 0.8.0 |
| Minimum server | 4 GB RAM |
| Recommended server | 8 GB RAM |
| APIs | REST, Realtime and GraphQL, auto-generated |
| HTTPS | Automatic, wildcard subdomain or your own domain |
| Email / SMTP | Not configured by default, you supply it |
| Regions | Falkenstein, Nuremberg, Helsinki, Ashburn, Hillsboro, Singapore. Which locations are open depends on the machine you pick |
| Backups | Optional. Daily, whole-VM, last 7 kept, +20% of the server price. One image is every container, database and volume together |
| MCP tools | 189 |
Specifications current as of September 2026.
Why 8 GB and not 4
Four GB is the platform minimum. Supabase is treated as a heavy workload: it runs many containers, pulls large images and holds a memory reserve, so the platform applies stricter free-space checks before it will deploy. Eight GB is the size we recommend, not a hard Supabase minimum.
What's in the Supabase deployment
The whole stack. One click.
The full open source Supabase stack on one project server, wired together and served through a single gateway. Edge Functions and Analytics are included, not stripped out.
| Component | What it does |
|---|---|
| Kong gateway | Single public entry point. Serves Studio and every Supabase API on one URL |
| Supabase Studio | The dashboard, reachable at your service URL. Credentials are pre-seeded, so there is no open first-run window |
| PostgreSQL | Your database. pg_cron 1.6.4 and pgvector 0.8.0 are available as extensions |
| Auth | Sign-up, sign-in, sessions and JWTs |
| PostgREST | The auto-generated REST API over your schema |
| Realtime | Live subscriptions to database changes |
| Storage + MinIO | S3-compatible object storage, backed by MinIO on the server volume |
| Edge Functions | Included, running on the same server |
| Analytics and Vector | Log collection and shipping across the stack |
| TLS and routing | Managed by Selfhost.dev. Public HTTPS URL, auto-renewed certificates |
Version note. Supabase is a sixteen-container stack, and we deploy it as one upstream release rather than pinning each component separately, so the component versions move together when the stack build is updated. That never changes a deployment you are already running: existing deployments stay on the release they were deployed with until you upgrade them.
Everything is included, including Edge Functions
Some managed Supabase templates ship a trimmed stack. This one does not. Edge Functions, Analytics and log shipping are all part of the deploy, and pg_cron and pgvector sit in the Postgres image ready to enable with a CREATE EXTENSION.
One URL for Studio and your APIs
Studio and the Supabase APIs are both served through the gateway on the same address. Add your own domain and it lands on the same place, so your dashboard and your app's API share one hostname.
How to self host Supabase in 5 steps
From zero to live.
No server to set up.
Five steps. No Docker Compose, no reverse proxy, no certificate to renew.
1. Create a project
Name it, pick where it runs, and we provision a dedicated server. There is no cloud account to connect.
2. Add the Supabase template
Add service → Template → Supabase. The full open source stack deploys in one click. When it finishes we email you the URL and credentials.
3. Set your environment variables
Choose your Supabase Studio login, at least 8 characters, then accept the generated secrets or set your own. The database password, JWT secret and API keys are wired in for you.
4. Point your domain
Keep the wildcard subdomain on selfhost.dev or add your own: set the DNS records, verify with a TXT record, and HTTPS provisions and renews automatically.
5. Connect your app
Use the project Postgres connection string and the Supabase API URL and keys in your app. Watch CPU, memory and connections live from project metrics.
Supabase environment variables
Configure it
in minutes.
Supabase needs a handful of secrets and URLs. We generate sensible defaults you can override, or paste a .env to import in bulk.
Key variables
What we run, and what you run
The honest split.
We manage the infrastructure. You own what happens inside Supabase. This is managed hosting, not a managed backend.
| We run | You run |
|---|---|
| Server provisioning, capacity and the network | Your schema, data and Row Level Security |
| The container stack and its wiring | Your API keys and JWT secret |
| Reverse proxy, TLS, renewals | Your Auth configuration and SMTP |
| Firewall and network rules | Your Supabase version, and when to move to a newer one |
| Optional daily backups | |
| Metrics, logs, and a health check every 60 seconds |
Why host Supabase on Selfhost.dev
Supabase, the easy way.
On a server you control.
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.
Custom domain + SSL
Add your domain, verify DNS and HTTPS is provisioned and renewed automatically. A wildcard subdomain works out of the box.
Drive it from your editor
189 MCP tools across 31 modules. Create the project, deploy the template, set env vars and manage domains from Claude or Cursor.
Supabase self host cost: what you actually pay
One server rate. Nothing per request.
You pay for the server and nothing else. An 8 GB server is $0.03/hr, about $23 a month in our EU locations if you leave it running, billed hourly against prepaid credits. The template, its sixteen containers and every byte of traffic are included.
| What you pay for | Cost |
|---|---|
| 8 GB project server | $0.03/hr in our EU locations, $23.36/mo at 730 hours |
| The Supabase template and its containers | $0 |
| HTTPS and custom domain | $0 |
| Bandwidth | $0. Traffic is included |
| Daily server backups | Optional, +20% of server price |
Monthly figures assume 730 hours. Rates are for our EU locations; US and Singapore machines are different types at different rates, priced live in the calculator.
For how this compares with Supabase Cloud's own pricing, see our breakdown of Supabase pricing.
Sizing Supabase before you deploy?
Tell us what you are building and we will send back the server size, the monthly cost and what to watch as it grows. One email, no newsletter.
Supabase template or managed PostgreSQL?
Two different things you can run here.
Deploy the Supabase template if you want the whole backend: Auth, Storage, Realtime and APIs. Choose managed PostgreSQL if you only need a production-grade database with PITR, pooling and Multi-AZ. Many teams run both on one account.
Supabase self host limitations
What this does not do.
The stack itself is complete. These are the operational differences worth knowing before you deploy.
- SMTP is not configured. Auth emails, invitations, confirmations and password recovery need your own SMTP details before they will send.
- Storage runs on bundled MinIO on the server volume, not external S3. It speaks the S3 protocol, but the objects live on your server.
- Supabase upgrades are not automatic. Existing deployments stay on the release they were deployed with until they are explicitly upgraded and redeployed.
- Backups are VM snapshots, not Postgres PITR. Daily server backups capture the whole disk including the database and storage volumes, so a restore brings back the whole machine, not a single database at a point in time.
- Edge Functions are included, but there is no first-class deployment workflow for them yet.
-
pg_cronandpgvectorare available, not pre-enabled. RunCREATE EXTENSIONwhen you want them. - Supabase Auth sign-ups are open by default. Set
DISABLE_SIGNUP=trueif your app should not accept public registrations. - 4 GB minimum, 8 GB recommended for this stack.
- One project server holds up to five things total, counting apps, databases and one-click apps together.
Moving an existing Supabase project here
A dump and a restore. Nothing proprietary in the way.
It is standard PostgreSQL at both ends, so this is a dump and a restore rather than an export negotiation. Take a pg_dump of your existing project, deploy the template here, then restore into the project Postgres over SSH with your own key. Your schema, your data, your row level security policies and your functions all come across, because none of it is in a proprietary format.
Two things to redo by hand
Your API keys are derived from the JWT secret, so a new deployment issues new ones and your app needs the new values. And Auth provider configuration and SMTP are set inside Supabase rather than in the database, so those are re-entered once in Studio.
Frequently asked questions
Can I self host Supabase on Selfhost.dev?
How much does it cost to self host Supabase?
Is it the full Supabase stack or just Postgres?
Do I have to manage the server?
How do I connect my app to self hosted Supabase?
Can I move my data off later?
What server size does Supabase need?
What is not included compared to self hosting Supabase myself?
Do I have to claim the dashboard before someone else does?
Can I use my own domain with self hosted Supabase?
Should I use the Supabase template or managed PostgreSQL?
What happens if my credit balance reaches zero?
Can I deploy Supabase with AI?
About Selfhost.dev
Selfhost.dev is a managed self hosting platform for developers and small teams. Open source apps and databases on dedicated servers you control, billed by the hour with no subscription tiers.
Best for: Supabase, n8n, Twenty CRM and managed PostgreSQL, MySQL, Redis and ClickHouse.