For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

Deploy self-hosted Supabase on Ubuntu 24.04 with Docker Compose and Nginx. Supabase provides Postgres-backed Auth, REST/Realtime APIs, Storage, and Studio. By default the stack uses its local db container; with Add a Database, Supabase is configured to use Managed PostgreSQL instead.

Included System Components

• Ubuntu 24.04 LTS
• Docker Engine and Docker Compose plugin
• Supabase (pinned release from the image build, currently v1.26.05) — Studio, Kong, Auth, PostgREST, Realtime, Storage, and related services
• PostgreSQL via the Supabase db container (supabase/postgres), or DigitalOcean Managed PostgreSQL when Add a Database is selected
• Nginx reverse proxy (ports 80/443 → Kong on localhost:8000)
• Certbot (Snap) for optional custom-domain TLS
• UFW — SSH, HTTP, and HTTPS
• postgresql-client — used on first boot when a Managed Database is attached

System Requirements

Software Included

Creating an App using the Control Panel

Click the Deploy to DigitalOcean button to create a Droplet based on this 1-Click App. If you aren’t logged in, this link will prompt you to log in with your DigitalOcean account.

Creating an App using the API

In addition to creating a Droplet from the Supabase 1-Click App using the control panel, you can also use the DigitalOcean API. As an example, to create a 4GB Supabase Droplet in the SFO2 region, you can use the following curl command. You need to either save your API access token to an environment variable or substitute it in the command below.

curl -X POST -H 'Content-Type: application/json' \
         -H 'Authorization: Bearer '$TOKEN'' -d \
        '{"name":"choose_a_name","region":"sfo2","size":"s-2vcpu-4gb","image":"supabase"}' \
        "https://api.digitalocean.com/v2/droplets"

Getting Started After Deploying Supabase

1. Deploy the Droplet

1. Select the Supabase 1-Click from the DigitalOcean Marketplace
2. Choose a Droplet size (2 GB RAM minimum recommended)
3. Optionally select Add a Database to provision Managed PostgreSQL (see below)
4. Add your SSH key and create the Droplet

2. Access Supabase

1. Open http://your-droplet-ip in a browser (Nginx → Kong / Studio)
2. SSH in for credentials:

ssh root@your-droplet-ip

Dashboard username and password are shown in the MOTD and stored in /root/.digitalocean_passwords.

3. Optional domain / HTTPS

Domain and TLS setup is manual (not prompted on every login). When ready, run:

/var/supabase/supabase-setup.sh

Managing Supabase

Supabase runs as Docker Compose services under /srv/supabase/supabase/docker.

Nginx: systemctl {start|stop|restart|status} nginx

Configuration paths

• Supabase stack: /srv/supabase/supabase/docker
• Env / secrets: /srv/supabase/supabase/docker/.env
• Passwords: /root/.digitalocean_passwords
• Managed DB credentials (when attached): /root/.digitalocean_dbaas_credentials
• Domain / TLS helper: /var/supabase/supabase-setup.sh
• Setup log: /var/log/one_click_setup.log

Using a DigitalOcean Managed Database (Optional)

When creating the Droplet, select Add a Database to provision Managed PostgreSQL for Supabase.

On first boot the Droplet:

1. Waits for the managed cluster (up to a few minutes) and aborts if unreachable (e.g. Trusted Sources)
2. Points Supabase at Managed Postgres and removes only the local db service (keeps vector)
3. Fail-fast bootstraps required roles/schemas (auth, storage, _supabase, etc.) and TLS for analytics/auth/storage
4. Saves connection details to /root/.digitalocean_passwords and DATABASE_URL in /etc/environment

Add the Droplet IP under the database cluster’s Trusted Sources in the control panel. If the DB is unreachable on first boot, DBaaS setup aborts instead of starting a broken stack — see /var/log/one_click_setup.log, then re-run /var/lib/digitalocean/setup-dbaas.sh and docker compose … up -d.

Prefer a 2GB+ Managed Database. Small plans (~25 connections/GB) can be exhausted by the Supabase stack; this 1-Click lowers pool sizes on DBaaS first boot. If you see remaining connection slots are reserved…, resize the DB or reduce POOLER_DEFAULT_POOL_SIZE in /srv/supabase/supabase/docker/.env and restart Compose.

Storage talks to Managed Postgres over TLS via DATABASE_URL?sslmode=require (and PGSSLMODE=require); this image does not set NODE_TLS_REJECT_UNAUTHORIZED=0.

Marketplace release note (Vendor Portal)

Image code alone does not show Add a Database to customers. Before publishing or updating this 1-Click in the Marketplace:

1. Open the Vendor Portal
2. Edit the Supabase Droplet 1-Click
3. Enable PostgreSQL under managed database / predeploy options
4. Save so create-droplet offers Add a Database

Without that checkbox, /root/.digitalocean_dbaas_credentials is never injected and DBaaS predeploy will not run.

Security notes

• Change the Studio dashboard password after first login if needed (value in /root/.digitalocean_passwords)
• Prefer restricting SSH (and optionally HTTP/HTTPS) with a Cloud Firewall
• For production, configure a custom domain and TLS via /var/supabase/supabase-setup.sh
• Rotate default JWT / API secrets in /srv/supabase/supabase/docker/.env for production use

Additional Resources

• Marketplace: https://marketplace.digitalocean.com/apps/supabase
• Supabase self-hosting: https://supabase.com/docs/guides/self-hosting/docker
• Managed Databases: https://docs.digitalocean.com/products/databases/