Apps
Self-host Supabase
Open-source Firebase alternative (starter stack) — Postgres, GoTrue auth, PostgREST and Studio. Expose rest/auth with extra domains for public API access.
Deploy Supabase with Nixploy
Install Nixploy on any Docker host — a €5 VPS is enough for most of these:
curl -fsSL https://raw.githubusercontent.com/bablilayoub/nixploy/main/install.sh | sudo bash- 1
Open Templates in the panel
Search for Supabase and open it. The compose file, the variables and the suggested domain are already filled in.
- 2
Give it a domain
Point a DNS record at your server and enter it. Traefik requests the certificate on the first request — there is no separate certbot step and nothing to renew by hand.
- 3
Deploy
Nixploy renders the compose file, validates it against the platform's safety rules, and brings the stack up on a private per-environment network. Live logs stream while it happens.
- 4
Schedule a backup
Supabase keeps its state in a named volume (supabase-db-data). Add a schedule and Nixploy streams the dump to S3 or to disk, encrypted, and can verify a restore.
What this deploys
- Images
- supabase/studio:2026.08.03-sha-022b374
- supabase/postgres:15.8.1.085
- supabase/gotrue:v2.189.0
- postgrest/postgrest:v14.12
- supabase/postgres-meta:v0.96.6
- Routed to
- studio:3000
- Persistent volumes
- supabase-db-data
- Variables it asks for
- JWT_SECRETHS256 secret used to sign JWTs — must match ANON_KEY and SERVICE_ROLE_KEY (rotate all three together)
- ANON_KEYAnon JWT (must be signed with JWT_SECRET)
- SERVICE_ROLE_KEYService-role JWT (must be signed with JWT_SECRET)
- SITE_URLPublic URL of your frontend (used in auth emails/redirects)
- API_EXTERNAL_URLPublic URL of the API (add a domain for the
restservice and set its URL here)
- Secrets Nixploy generates
- POSTGRES_PASSWORD, PG_META_CRYPTO_KEYCreated at deploy time and stored encrypted — you never invent or paste them.
What you get with it
Automatic HTTPS through Traefik and Let's Encrypt, renewed for you.
Live logs, a web terminal into the container, and CPU/memory/network history.
Encrypted backups to S3 or disk, on a schedule, with verified restores.
Roll back to the previous version when an update goes wrong.
An MCP endpoint, so an AI agent can deploy, read the logs and diagnose it for you — see the MCP guide.
Why self-host Supabase?
Running it yourself means the data lives on a disk you control, there is no per-seat price as the team grows, and nothing is retired or repriced by somebody else. The cost is the part Nixploy takes over: a reverse proxy, certificates that renew, a volume that survives a redeploy, backups you can actually restore, and a way to see the logs when it misbehaves.
Supabase upstream
Nixploy packages the project; it is not affiliated with it. Website · Docs · Source
All 146 templates