The full open source Supabase stack, Postgres, Auth, Storage, Realtime, Edge Functions and Studio, in one click on a dedicated server we provision, secure and run. Your frontend can live on the same server.
Why self host Supabase the hard way, when Selfhost.dev can run it for you?
Supabase is the open source Firebase alternative: Postgres with Auth, Storage, Realtime and auto-generated APIs. Here the whole stack deploys in one click onto a dedicated server, a VPS we provision and run.
Teams who want Supabase on a server they control, without assembling and maintaining the Docker Compose stack themselves.
When your data has to stay on infrastructure you control, when you want one predictable server bill or when you want your frontend and backend on one machine.
The full open source Supabase stack on one project server, wired together and served through a single gateway.
Some managed Supabase templates ship a trimmed stack. This one does not. Edge Functions, Analytics and log shipping are all part of the deploy. pg_cron and pgvector sit in the Postgres image, ready to enable with a CREATE EXTENSION.
Studio and every Supabase API are served through the gateway on one address. Add your own domain and both move with it, so your app needs a single URL.
Dashed = your own frontend from GitHub, optional.
Your app and your browser
TLS, then the Kong gateway
Supabase Studio
PostgreSQL
Auth
PostgREST
Realtime
Storage + MinIO
Edge Functions
Analytics and Vector
Your frontend from GitHub, on the same server
| 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. The sixteen containers ship as one upstream release, so their versions move together when the stack build is updated. A running deployment never changes on its own: it stays on its release until you upgrade it.
Supabase self hosted means running the whole stack behind a gateway with TLS. The template ships all of it on one server, so you only pick the size.
Specifications current as of September 2026.
Four GB is the platform minimum. Supabase counts as a heavy workload: many containers, large images and a memory reserve, so the platform checks free space more strictly before it deploys. Eight GB is our recommendation, not a hard Supabase minimum.
Supabase's own platform does not host frontends, so most teams add Vercel or Netlify and a second bill. Here your Next.js, React or Node app deploys from GitHub into the same project as Supabase, on the same server.
A project holds five workloads in total. Supabase counts as heavy; apps deployed from GitHub count as light.
Deploy a Next.js app โ ยท Deploy a React app โ ยท Deploy a Node.js app โ
No Docker Compose, no reverse proxy, no certificate to renew. The template deploys in about seven minutes.
Name the project and pick a location. Then Add service, Template, Supabase: we provision the server and deploy the stack.
Choose a Studio username and a password of at least 8 characters. The database password, JWT secret and API keys are generated and wired in for you.
In your app, use the Supabase URL and keys or the Postgres connection string. Add your own domain when you like; HTTPS provisions and renews itself.
Supabase needs a handful of secrets and URLs. We generate sensible defaults you can override; you can also paste a .env to import in bulk.
| Item | Cost |
|---|---|
| European 8 GB project server | $0.03/hr, $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.
We manage the infrastructure. You own what happens inside Supabase. This is managed hosting, not a managed backend.
The stack itself is complete. Three things work differently from Supabase Cloud.
DISABLE_SIGNUP=true if your app should not accept public registrations.Whether self hosting Supabase is worth it for your project (and when Supabase Cloud is the better call) is in our full breakdown.
None of these a dealbreaker? The template deploys in about seven minutes.
Launch SupabaseIt is standard PostgreSQL at both ends, so moving is a dump and a restore:
Take a pg_dump of your existing project.
Deploy the template here.
Restore into the project Postgres over SSH with your own key.
Schema, data, row level security policies and functions all come across. Nothing is in a proprietary format.
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.
Yes. Supabase deploys in one click onto a dedicated server we run: all sixteen containers wired through one gateway, HTTPS on your own domain, a default deny firewall, health checks every 60 seconds and optional daily backups. Your schema, keys and Auth settings stay yours. How Projects work.
You pay for the project server and nothing for the template. A European 8 GB server, the size we recommend, is $0.03/hr, about $23 a month left running. Nothing is charged per request, per user or per gigabyte. Signing up adds a $5 welcome credit, no card needed. See pricing.
Yes. Deploy your Next.js, React or Node app from GitHub into the same project and it runs on the same server as Supabase. An 8 GB server holds Supabase plus up to four apps from GitHub; a 4 GB server holds Supabase plus one. Supabase's own platform does not host frontends.
The full stack. The template deploys Postgres, Auth, Storage, Realtime, the auto-generated APIs, Edge Functions, Analytics and Studio: the same open source Supabase you would run yourself with Docker, without assembling it. Postgres ships with pg_cron and pgvector available to enable with one command.
Use the Supabase API URL and the anon or service role key from your project, exactly as you would with Supabase Cloud, so your client libraries work unchanged. The Postgres connection string is there too if you want direct database access from your backend or a migration tool.
Yes. The stack answers on a generated HTTPS address the moment the deploy finishes. You can move it to your own domain: set the DNS records and verify with a TXT record, then SSL is provisioned and renewed automatically. Studio and the APIs share that hostname.
Use the Supabase template if you want the whole backend: Auth, Storage, Realtime and APIs. Use managed PostgreSQL if you only need a dedicated, production grade database with PITR, pooling and Multi-AZ. Managed PostgreSQL runs on AWS, separately from project servers. You can run both on one account. Managed PostgreSQL.
Yes. Creating the project, deploying the template, setting env vars and managing domains are all covered by 216 MCP tools, so you can launch and run Supabase from Claude, Cursor or any MCP client. Nothing in the flow requires opening the console. Explore the MCP server.
For a full head-to-head, see our Selfhost.dev vs Supabase comparison.
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, ClickHouse, OpenSearch and Kafka.