Supabase
Deploy the Supabase template on Simplifyd Cloud, open Studio, and connect your app.
The Supabase template runs managed Postgres, Auth, the REST API, Realtime, Storage, and Studio in one Simplifyd Cloud environment. supabase_gateway provides a public HTTPS URL for Studio and the APIs. The database and other runtime services are private.
Deploy from the dashboard
- Open your project and select the environment where you want to run Supabase. The template uses fixed service names, so choose an environment without a service that has one of those names.
- Click + Add on the canvas and choose Template. You can also find Template in the canvas right-click menu.
- Under From Simplifyd, select Supabase and review the services and resource sizes. If you have SQL to create your app's schema and policies, paste it into Initial SQL.
- Click Deploy to create the services. Copy
SUPABASE_PUBLIC_URLandSUPABASE_PUBLISHABLE_KEYfrom For your app, then click Done. - On the canvas, open
supabase_db, go to Deployments, and click Deploy PostgreSQL. Wait for the database to show Running. - Open Deployments for
supabase_auth,supabase_rest,supabase_realtime,supabase_storage,supabase_meta,supabase_studio, andsupabase_gateway. Click Deploy the image for each.supabase_emailis ready for domain setup as soon as it appears on the canvas.
Database and Docker services are billed when deployed. The first database startup can take about a minute.
Deploy from the CLI
Use Edge CLI v0.1.34 or later. Install or update the CLI
Sign in with edge auth login and confirm the target workspace, project, and environment with edge status. Use edge link to select them for your current directory. CLI link and status
edge template list
edge template get supabase
edge template deploy supabase --yesTo supply your schema, add --init-sql ./schema.sql to the template deploy command. The command prints the created services, the public URL, and the browser keys.
Start Postgres first and wait for edge deploy list supabase_db to show a running deployment.
edge deploy up supabase_db
edge deploy list supabase_dbThen start the Docker services.
edge deploy up supabase_auth
edge deploy up supabase_rest
edge deploy up supabase_realtime
edge deploy up supabase_storage
edge deploy up supabase_meta
edge deploy up supabase_studio
edge deploy up supabase_gatewayOpen Studio
Once the services are running, open SUPABASE_PUBLIC_URL in your browser. Sign in with DASHBOARD_USERNAME and DASHBOARD_PASSWORD. Workspace owners and developers can open supabase_gateway → Variables and use Reveal value to read those credentials.
Use Studio's SQL Editor to run queries and apply schema changes. If you supplied Initial SQL, it runs in one transaction when supabase_db first starts, after the Supabase migrations. Check the database's deployment logs for init_sql applied. If the logs say init_sql failed and was not applied, the database still starts and none of that SQL takes effect. Fix the SQL and run it in Studio.
Connect your app
Use the gateway URL and publishable key to initialise your Supabase client. Copy both values from For your app or run edge variables publishable in the same environment. Use ANON_KEY for clients configured for the legacy anon key. Supabase JavaScript client reference
import { createClient } from '@supabase/supabase-js';
const supabase = createClient('YOUR_SUPABASE_PUBLIC_URL', 'YOUR_SUPABASE_PUBLISHABLE_KEY');Enable row-level security (RLS) and define policies on tables your app accesses through the API. For privileged backend operations, reveal SUPABASE_SECRET_KEY or the legacy SERVICE_ROLE_KEY in supabase_gateway → Variables. These keys bypass RLS. Keep them on your server. Supabase API keys
Configure Auth email
- Open
supabase_email→ Setup. Add a sending domain you own, such asmail.example.com, publish the DNS records shown, and verify the domain. Sending domain setup - Open
supabase_auth→ Variables. SetGOTRUE_SMTP_ADMIN_EMAILto a sender at that domain, such asauth@mail.example.com. The SMTP credentials are already linked tosupabase_email. - Set
GOTRUE_SITE_URLto your app's URL. If your app uses additional redirect URLs, add them toGOTRUE_URI_ALLOW_LISTas a comma-separated list. - Click Deploy in the Apply Changes bar to redeploy
supabase_authwith the updated settings.
Sign-up confirmations, password resets, magic links, and invites require a verified sender. For testing password sign-in before email is configured, set GOTRUE_MAILER_AUTOCONFIRM to true and redeploy supabase_auth to skip sign-up confirmation.
Template limits
Edge Functions, Storage image transformations, the Supavisor connection pooler, and Studio log views are unavailable in this template. Use the Simplifyd deployment logs to inspect individual services.