Templates
Self-host Supabase with Unbind
Deploy Supabase on your own servers with Unbind. Postgres, auth, storage, edge functions and the Studio dashboard from one template.
Supabase is an open-source Firebase alternative built on Postgres. This template gives you the database, auth, the REST API, storage, edge functions and the Studio dashboard.
Deploy it from the template list. It takes a minute or two.
What gets deployed
| Service | Runs |
|---|---|
| PostgreSQL | postgres |
| Studio | supabase/studio:2026.08.24-sha-8ec45b2 |
| Storage | supabase/storage-api:v1.71.0 |
| MinIO | minio/minio:RELEASE.2025-09-07T16-13-09Z |
| PostgREST | postgrest/postgrest:v14.17 |
| Auth | supabase/gotrue:v2.196.0 |
| Postgres Meta | supabase/postgres-meta:v0.98.0 |
| Functions | supabase/edge-runtime:v1.74.3 |
| Kong | kong:3.9.3 |
Plan for at least 2 CPU cores and 4 GB of memory.
Your data lives in the PostgreSQL service. Files uploaded through Supabase Storage go to the MinIO service, on a volume mounted at /data.
What you fill in
| Input | Description | Default |
|---|---|---|
| Domain | The domain for the Supabase instance. | |
| Database Size | Size of the storage for the PostgreSQL database. | 1 GB |
| Storage Size | Size of the storage for the Supabase storage service. | 1 GB |
After it deploys
Everything you need is on the Kong service. Open it and look at its variables:
| Variable | What it is for |
|---|---|
DASHBOARD_USERNAME | Studio sign in. It is admin. |
DASHBOARD_PASSWORD | Studio sign in. |
SUPABASE_ANON_KEY | The public key your frontend uses. |
SUPABASE_SERVICE_KEY | The service role key. It bypasses row level security, so keep it on your backend. |
JWT_SECRET | Signs the two keys above. |
Open your domain and sign in to Studio. In your app, use https://your-domain as the Supabase URL with the anon key.
Good to know
- One domain: Kong sits in front of every other service, so Studio, the APIs and storage all share the domain you picked.
- What is left out: Realtime, image transformations and the analytics stack are not part of this template.
- Do not rename the dashboard user:
DASHBOARD_USERNAMEis protected because the Kong configuration depends on it. - Email: auth emails need a mail server. Add the
GOTRUE_SMTP_*variables to the Auth service and redeploy. - It is a big template: nine services. Give it the recommended resources or more.