NewOut Plane raises funding, backed by Maza VenturesRead the announcement
DevTools

Supabase

Overview

Deploy Supabase on Out Plane — the open-source Firebase alternative built on PostgreSQL. Supabase provides a complete backend-as-a-service with a managed database, authentication, instant REST and GraphQL APIs, real-time subscriptions, and file storage with CDN — all through a unified Studio dashboard.

Supabase authentication supports email/password, magic links, OAuth providers (GitHub, Google, Apple, and more), and row-level security policies that tie directly into your PostgreSQL database. The real-time engine streams database changes over WebSocket to connected clients. Self-hosting on Out Plane gives you full data ownership without the limitations of Supabase Cloud.

Ideal for web and mobile app development, SaaS products, real-time collaboration tools, and any project that needs a modern backend with authentication, storage, and database access without building custom APIs.


Supabase Self Hosted (2026): Docker Setup and Costs

Updated

Supabase is an open source backend built on PostgreSQL, with Auth, an instant REST API, Realtime, Storage and the Studio dashboard. To run Supabase self hosted on Out Plane, deploy the core services in Supabase's official Docker Compose file as separate apps: eight apps, one Postgres volume and private networking between them, on the Pro plan.

Out Plane does not run Docker Compose itself, so this guide maps Supabase's self-hosting guide, release self-hosted/v0.8.4, to apps. Browse more templates, or compare Supabase alternatives.

What You Need

  • The Pro plan. The stack is eight apps, and Starter allows three.
  • A GitHub repository with two folders, db and gateway, each built from its own root directory.
  • One volume for Postgres. Volumes are 10 to 50 GB and cannot be resized. An app with a volume runs one instance.
  • A real SMTP server for sign-up and password emails.

From Supabase Docker Compose to Out Plane

App names use letters and numbers only, 5 to 45 characters, so db, auth, rest and meta get longer names. Apps reach each other at {app}:{port}.

Compose serviceImageOut Plane app, port, size
dbsupabase/postgres:17.6.1.136supadb, 5432 TCP, op-46
api-gwenvoyproxy/envoy:v1.39.6supagateway, 8000 public HTTP, op-22
authsupabase/gotrue:v2.197.0supaauth, 9999, op-22
restpostgrest/postgrest:v14.18suparest, 3000, op-22
realtimesupabase/realtime:v2.148.3suparealtime, 4000, op-34
storagesupabase/storage-api:v1.89.12supastorage, 5000, op-22
metasupabase/postgres-meta:v0.100.0supameta, 8080, op-22
studiosupabase/studio:2026.11.02-sha-a05e7ecsupastudio, 3000, op-34

Ports are HTTP except 5432, and only the gateway's is public. Left out: imgproxy, Edge Functions, the supavisor pooler (apps can reach supadb:5432 directly), and Logs and Analytics, whose Vector service needs the Docker socket.

Deploy Supabase on Out Plane

  1. Generate the configuration locally:
bash
git clone --depth 1 --branch self-hosted/v0.8.4 https://github.com/supabase/supabase
cd supabase/docker && cp .env.example .env
sh utils/generate-keys.sh --update-env
sh utils/add-new-auth-keys.sh --update-env

In .env, set POSTGRES_HOST=supadb, SUPABASE_PUBLIC_URL=https://supagateway-8000-TEAM.outplane.app with your team slug, and API_EXTERNAL_URL to that URL plus /auth/v1. Set SITE_URL to your frontend and fill in SMTP_*, since the example host supabase-mail does not exist here.

  1. In your repository, create db/ with the seven SQL files from docker/volumes/db/ and this Dockerfile, which puts them where compose mounts them:
dockerfile
FROM supabase/postgres:17.6.1.136
COPY _supabase.sql /docker-entrypoint-initdb.d/migrations/97-_supabase.sql
COPY realtime.sql /docker-entrypoint-initdb.d/migrations/99-realtime.sql
COPY logs.sql /docker-entrypoint-initdb.d/migrations/99-logs.sql
COPY pooler.sql /docker-entrypoint-initdb.d/migrations/99-pooler.sql
COPY webhooks.sql /docker-entrypoint-initdb.d/init-scripts/98-webhooks.sql
COPY roles.sql /docker-entrypoint-initdb.d/init-scripts/99-roles.sql
COPY jwt.sql /docker-entrypoint-initdb.d/init-scripts/99-jwt.sql
RUN sed -i 's|/etc/postgresql-custom/pgsodium_root.key|/var/lib/postgresql/data/pgsodium_root.key|' /usr/lib/postgresql/bin/pgsodium_getkey.sh
CMD ["postgres", "-c", "config_file=/etc/postgresql/postgresql.conf", "-c", "log_min_messages=fatal"]

The sed line keeps the pgsodium and Vault root key on the volume. Compose mounts /etc/postgresql-custom for it, but that folder also holds the image's config files, which an empty disk would hide.

  1. Create gateway/ with the four files from docker/volumes/api/envoy/ and this Dockerfile:
dockerfile
FROM envoyproxy/envoy:v1.39.6
COPY envoy.yaml cds.yaml lds.template.yaml /etc/envoy/
COPY docker-entrypoint.sh /docker-entrypoint.sh
ENTRYPOINT ["/bin/sh", "/docker-entrypoint.sh"]

In cds.yaml, change each upstream address: to your app name, such as auth to supaauth and realtime-dev.supabase-realtime to suparealtime. The gateway still sends Realtime the Host header it expects. Delete the functions cluster and the /functions/v1/ route in lds.template.yaml, then push.

  1. Open Create → Application, choose GitHub, pick the repository, and set Root directory to db with the Dockerfile build method. Name it supadb, pick op-46, and add port 5432 as TCP with Public off. Under Volumes, select Create volume, 20 GB, mounted at /var/lib/postgresql. That is one level above the data folder, because Postgres refuses to initialise a non-empty directory and a new disk can contain lost+found. Paste these variables and select Deploy app:
bash
POSTGRES_HOST=/var/run/postgresql
POSTGRES_PORT=5432
PGPORT=5432
POSTGRES_DB=postgres
PGDATABASE=postgres
POSTGRES_PASSWORD=YOUR_POSTGRES_PASSWORD
PGPASSWORD=YOUR_POSTGRES_PASSWORD
JWT_EXP=3600
  1. When supadb is Running, create the six image apps with Create → Application → Image, each with the image, size and private port from the table. Copy each service's environment: block from docker-compose.yml, fill each ${VAR} from .env, and rename hosts: rest to suparest, meta to supameta, api-gw to supagateway. On Studio, leave out HOSTNAME, which Out Plane reserves. On Storage, set ENABLE_IMAGE_TRANSFORMATION=false and use a bucket, as shown below.

  2. Create supagateway like supadb, with root directory gateway, op-22, port 8000 as public HTTP and no volume. Its variables are the api-gw block.

  3. Open https://supagateway-8000-TEAM.outplane.app and sign in to Studio with the dashboard login. The APIs live under /rest/v1/, /auth/v1/, /storage/v1/ and /realtime/v1/. Pass that URL and SUPABASE_PUBLISHABLE_KEY to createClient.

Supabase Docker Environment Variables

VariableWhat it does
POSTGRES_PASSWORDPassword for postgres and the service roles. Use letters and numbers only.
SUPABASE_PUBLISHABLE_KEY, SUPABASE_SECRET_KEYAPI keys: publishable for clients, secret for servers only. ANON_KEY and SERVICE_ROLE_KEY are the legacy pair.
API_EXTERNAL_URLAuth's public URL for OAuth callbacks, email links and the token issuer.
DASHBOARD_PASSWORDStudio login. Letters and numbers, with at least one letter.

roles.sql sets the role passwords only on the first boot of an empty volume. To change POSTGRES_PASSWORD later, run ALTER USER for each role in utils/db-passwd.sh from the Shell tab of supadb. Variable changes apply on the next deployment, so use Save & deploy.

Store Files in an Out Plane Bucket

Create a bucket and a read and write key under Buckets, then give supastorage these values. Buckets accept only virtual-hosted requests, so path style stays off:

bash
STORAGE_BACKEND=s3
GLOBAL_S3_BUCKET=YOUR_BUCKET_NAME_WITH_SUFFIX
GLOBAL_S3_ENDPOINT=https://obj.outplane.dev
GLOBAL_S3_PROTOCOL=https
GLOBAL_S3_FORCE_PATH_STYLE=false
REGION=auto
AWS_ACCESS_KEY_ID=YOUR_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY=YOUR_SECRET_ACCESS_KEY

Supabase covers these in its S3 storage guide. With a bucket, supastorage needs no volume.

Custom Domain and HTTPS

Once supagateway has deployed, open Domains → Add domain, enter a host such as api.example.com, and pick supagateway on port 8000. In the DNS dialog, a subdomain gets a CNAME to domains-management.outplane.app, and an apex domain gets an A record at @ with the value shown. DNS takes 5 to 30 minutes, then HTTPS is issued automatically.

Then update SUPABASE_PUBLIC_URL on supagateway and supastudio, STORAGE_PUBLIC_URL on supastorage, and API_EXTERNAL_URL and GOTRUE_JWT_ISSUER on supaauth. Do this before real users sign in, since tokens and OAuth callbacks use these URLs.

Updates and Backups

Supabase publishes tested snapshots about once a month. Take every tag from one release's docker-compose.yml, and diff its SQL and Envoy files against yours. Image apps never update on their own: use Deployments → Deploy with the full new reference, or:

bash
outplane deploy create supaauth --image supabase/gotrue:NEW_TAG --wait

For supadb and supagateway, change the FROM line and push. Keep supabase/postgres on the same major version: a major upgrade is a data migration, which Supabase handles with utils/upgrade-pg17.sh.

Volumes have no snapshots, so keep your own dumps. Make port 5432 public TCP, link an IP access profile that allows only your network, redeploy, run the dump, then turn Public off and redeploy:

bash
pg_dump "postgresql://postgres:YOUR_POSTGRES_PASSWORD@HOST:PORT/postgres" -Fc -f supabase-$(date +%F).dump

If you use Vault, also copy pgsodium_root.key from /var/lib/postgresql/data, because a dump alone cannot decrypt its secrets.

Supabase Hosting Costs on Out Plane

Compute is billed per instance-minute. For a 30-day month, supadb on op-46 ($0.0008333 a minute) is $36.00, Studio and Realtime on op-34 ($0.0004167) are $18.00 each, and five apps on op-22 ($0.0001389) are $6.00 each. A 20 GB volume at $0.30 per GB adds $6.00, so usage is $108.00. Pro costs $29 a month and includes $15 of usage, so the stack comes to about $122 a month. Starter and Pro both start with a 14 day free trial, and this stack needs Pro. See the pricing page.

Self-Hosted Supabase vs Supabase Cloud

Supabase pricing, checked on 2026-11-11: Free includes a 500 MB database and pauses projects after a week of inactivity. Pro starts at $25 a month with $10 of compute credits, enough for one Micro instance with 1 GB of RAM, plus 8 GB of disk, 100,000 monthly active users, 250 GB of egress and daily backups kept for 7 days.

For one small project, Supabase Cloud is the cheaper start. Self-hosting on Out Plane fits when you want your database on servers in Germany, no charges per active user or per GB of egress, and Supabase next to your apps.

FAQ

Is self-hosted Supabase free?

The software is free and open source, so you pay only for hosting: about $122 a month for this stack on Out Plane Pro, after a 14 day free trial.

What is the self-hosted Supabase login?

Studio sits behind basic auth on the gateway. The user is DASHBOARD_USERNAME, supabase by default, and the password is DASHBOARD_PASSWORD.

Can I use managed PostgreSQL instead of supabase/postgres?

Not in this setup. The services log in as roles such as supabase_auth_admin and authenticator, which the supabase/postgres image and its init scripts create, so this guide keeps that image.

What are the minimum requirements for self-hosted Supabase?

Supabase lists 4 GB of RAM, 2 CPU cores and 40 GB of SSD as the minimum, and 8 GB, 4 cores and 80 GB as recommended.



Start deploying in minutes

Connect your GitHub repository and deploy your first application today. Start with a 14-day free trial.

Start 14-day free trial