Supabase

Supabase bundles Postgres, real-time listeners, storage, and auth with edge functions. Use this component when you want Diploi to manage Supabase deployments alongside the rest of your stack so you can ship a unified backend without wiring infrastructure by hand.

Add to your project

Paste this entry into the components list in diploi.yaml to add Supabase to your project.

components:
  - name: Supabase
    identifier: supabase
    package: https://github.com/diploi/component-supabase#v2026.02-patch.1

If the folder of the component in your repository is not named supabase, add a folder parameter with the name of the folder.
Import the environment variables of add-ons, such as a database, into the component with env.include in diploi.yaml:

components:
  - name: Supabase
    identifier: supabase
    package: https://github.com/diploi/component-supabase#v2026.02-patch.1
    env:
      include:
        - postgres.*

Supabase reference

What Supabase defines in a deployment.

Environment variables

Supabase sets these values in every deployment. Other components can import them with env.include as supabase.*. Defaults marked generated are unique to each deployment.

Parameters are set on the deployment’s Setup tab.

Dashboard

Supabase dashboard configuration.

Variable	Type	Default	Description
`DASHBOARD_USERNAME`	string	`supabase`	Username
`DASHBOARD_PASSWORD`	secret	generated	Password
`STUDIO_DEFAULT_ORGANIZATION`	string	`Default Organization`	Default Organization
`STUDIO_DEFAULT_PROJECT`	string	`Default Project`	Default Project

Custom SMTP Settings

Configure custom SMTP settings to send emails. Optional, off by default.

Variable	Type	Default	Description
`SMTP_ADMIN_EMAIL`	string	`admin@example.com`
`SMTP_HOST`	string	`core.diploi`	An SMTP server (core.diploi) is available within your deployment, see https://docs.diploi.com/reference/built-in-email
`SMTP_PORT`	integer	`2525`
`SMTP_USER`	string
`SMTP_PASS`	string
`SMTP_SENDER_NAME`	string
`ENABLE_EMAIL_SIGNUP`	boolean	`true`
`ENABLE_EMAIL_AUTOCONFIRM`	boolean	`false`	Enable Email Automatic Confirmation

API Keys & Values

Secure keys & values for accessing and running your Supabase services.

Variable	Type	Default	Description
`JWT_SECRET`	secret	generated
`ANON_KEY`	string	generated
`SERVICE_ROLE_KEY`	secret	generated	To generate new JWT values, see https://supabase.com/docs/guides/self-hosting/docker#generate-api-keys
`VAULT_ENC_KEY`	secret	generated	Vault Encryption Key
`POOLER_TENANT_ID`	secret	generated
`LOGFLARE_PUBLIC_ACCESS_TOKEN`	string	generated
`LOGFLARE_PRIVATE_ACCESS_TOKEN`	secret	generated
`SECRET_KEY_BASE`	secret	generated	Phoenix Secret

PostgreSQL

Superuser & connection configuration.

Variable	Type	Default	Description
`POSTGRES_HOST`	string	generated	Host
`POSTGRES_PORT`	integer	`5432`	Port
`POSTGRES_USER`	string	`postgres`	User
`POSTGRES_PASSWORD`	secret	generated	Password
`POSTGRES_DB`	string	`postgres`	Database
`POSTGRES_URL`	string	generated	Connection URL

OpenAI

Add your OpenAI API key to enable SQL Editor Assistant. Optional, off by default.

Variable	Type	Default	Description
`OPENAI_API_KEY`	secret

Google Cloud Project

Support Sign in with Google by connecting to a Google Cloud Platform project. Optional, off by default.

Variable	Type	Default	Description
`GOOGLE_PROJECT_ID`	string		Google Cloud Project ID
`GOOGLE_PROJECT_NUMBER`	string		Google Cloud Project Number

Internal Addresses

Internal endpoints for different Supabase services.

Variable	Type	Default	Description
`AUTH_INTERNAL_URL`	string	generated	Auth
`REST_INTERNAL_URL`	string	generated	REST
`REALTIME_INTERNAL_URL`	string	generated	Realtime
`STORAGE_INTERNAL_URL`	string	generated	Storage
`FUNCTIONS_INTERNAL_URL`	string	generated	Functions
`ANALYTICS_INTERNAL_URL`	string	generated	Analytics
`META_INTERNAL_URL`	string	generated	Meta
`STUDIO_INTERNAL_URL`	string	generated	Studio
`KONG_INTERNAL_URL`	string	generated	Kong

Other variables

Set by the package. Override them on the deployment’s Environment tab or in diploi.yaml.

Variable	Default
`SITE_URL`
`DISABLE_SIGNUP`	`false`
`ENABLE_ANONYMOUS_USERS`	`false`
`ENABLE_PHONE_SIGNUP`	`true`
`ENABLE_PHONE_AUTOCONFIRM`	`true`
`FUNCTIONS_VERIFY_JWT`	`false`
`JWT_EXPIRY`	`3600`
`PGRST_DB_SCHEMAS`	`public,graphql_public`
`REALTIME_TENANT_NAME`	`realtime`
`ADDITIONAL_REDIRECT_URLS`

Readme

Run Supabase on Diploi.

Based on the official supabase/docker docker-compose.yml file.

Operation

A full Supabase self-hosted implementation.

Limitations

We know of a few limitations that currently exist with Supabase on Diploi. We are actively working on fixes.

Connection URI’s displayed on Supabase Studio are wrong, please use the ones on Diploi Console

Authentication

Self-hosted Supabase comes with a simple basic auth implementation by default. Diploi implements custom authentication for the admin panel, making it easier to use. You can authenticate with a single-click from Diploi Console, or use username & password to login.

You can find the admin credentials from a deployments “Options” tab in the Diploi Console.

Development

Functions

You can develop custom functions with Deno. Diploi automatically creates a /functions directory for you with a preconfigured main function and an example hello function.

Migrations

Database migrations and seeding are supported.

Diploi automatically creates a /migrations directory and a seed.sql file for you. They work with the Supabase CLI to manage schema changes and database seeding in a repeatable way.

If the component folder is not named supabase, Diploi creates a supabase symlink inside it so the Supabase CLI works as expected.

For guidance and best practices, see the official Supabase docs on database migrations.