Deploy Supabase
Your own Supabase: Postgres, Auth, APIs, Realtime, Storage and Edge Functions
Deploy the full self-hosted Supabase stack in one click: the Kong API gateway, Studio, Auth, the REST API, Realtime, Storage with image transforms and Edge Functions, on its own PostgreSQL, its own S3 server for files, and email. Every key and password is generated for this deploy, Studio has its own sign-in, and Edge Functions run inside a Kata micro VM.
What you get with Supabase
- Table Editor and SQL EditorCreate tables and edit rows in a spreadsheet-like grid, or write SQL with saved queries. Every table is served right away over the REST API, with Row Level Security deciding who reads and writes which rows.
- Auth that sends its own mailEmail and password sign up, magic links and password resets. Confirmation mails go out through the email add-on, so new users verify their address before they sign in.
- Realtime and StorageSubscribe to inserts and updates over websockets, and store files on the stack’s own S3 server, which keeps each file’s type, with access rules, signed URLs and on the fly image resizing.
- Edge Functions in a micro VMWrite a function in Studio and deploy it in one click. Functions run your code inside a Kata micro VM with its own kernel, and never see the database, storage or mail credentials of the stack.
- An AI assistant in StudioAsk in plain English and the assistant writes the SQL: a table with its policies, a query, a fix. Nothing runs until you approve it. It runs on StackBlaze AI and is billed to your workspace like the rest of StackBlaze AI.
- Backups and restore in StudioDatabase, Backups lists the backups StackBlaze takes of this database. Take one now, or restore one in place: Studio replaces the live database once you type its name to confirm.
After you deploy Supabase
- 1Sign in to StudioOpen the public URL and sign in as supabase with the password in DASHBOARD_PASSWORD, from the gateway card’s Variables in the dashboard.
- 2Create your schemaAdd tables in the Table Editor or the SQL Editor and turn on Row Level Security with a policy for each table your app reads.
- 3Connect your appCopy the public URL and the publishable key from Project Settings, API Keys into supabase-js or any client library. Keep the secret key on your server.
How Supabase is wired
Supabase ships as one group of eleven services, including its own S3 server for Storage’s files, with its own PostgreSQL and email. The Kong gateway is the only public URL: it serves Studio and every API under it.
- One URL for everything
- The gateway routes /rest/v1, /auth/v1, /realtime/v1, /storage/v1 and /functions/v1 to their services, and everything else to Studio behind its sign-in. Database, bucket and services stay private.
- Reads on the replicas
- Data API reads go to a second REST API on the Postgres replicas, writes to the primary. Set KONG_REST_READ_REPLICAS to off on the gateway to keep every read on the primary.
- Edge Functions in Kata
- The functions service runs inside a Kata micro VM. Your functions get the Supabase URL, keys and database URL, but not the stack’s internal credentials.
- Keep the JWT secret
- JWT_SECRET signs every session and both legacy keys. It is generated at deploy and shared by every service; changing it signs everyone out and replaces the anon and service_role keys.
Why run Supabase on StackBlaze
- Scale your appChange CPU, RAM, and replicas without a rebuild, or let autoscaling add replicas when CPU climbs.
- Git-based CI/CDPush to GitHub and it builds and ships. Pull requests get their own preview URL on Pro and Business.
- One-click rollbackA deploy went wrong? Go back to any previous successful deploy.
- Environments built inProduction, staging, and dev as separate environments in one project, each with its own URL.
- Built-in observabilityCPU, memory, and response time per app, live logs with search, and alerts to Slack, Discord, or a webhook.
- Developer-first toolsA CLI and Stack MCP: deploy, read logs, and wire services from your terminal or your AI assistant.
- Built for teamsInvite teammates with roles. An audit log records who changed what.
- Managed Postgres with HAPostgres is run for you. Turn on high availability for a three-node cluster when the app needs it.
Common questions about Supabase
How do I sign in to Studio?
Open the public URL and sign in as supabase with the password generated in DASHBOARD_PASSWORD, under the gateway card’s Variables in the dashboard. Studio has its own sign-in page, so nothing is reachable before you sign in.
Where are my API keys?
In Studio under Project Settings, API Keys. The publishable key is safe in a browser when Row Level Security is on. The secret key and the legacy service_role key bypass Row Level Security, so keep them on your server.
Does sign up send emails?
Yes. Auth sends confirmation, magic link and password reset mails through the email add-on, and new users confirm their address before they can sign in. Set GOTRUE_MAILER_AUTOCONFIRM to true on the Auth card to skip confirmation.
Are Edge Functions safe to run?
Functions run your code on the server, so the functions service runs inside a Kata micro VM with its own kernel. Functions see the Supabase URL, keys and database URL, and secrets you add in Studio, never the storage or mail credentials.
How are backups handled?
StackBlaze backs up the PostgreSQL database, and Studio shows those backups under Database, Backups. Take one now, or restore one in place: you type the database name to confirm, the project is unavailable while the restore runs, and it comes back by itself. Storage’s files live on a volume of the stack’s RustFS service: turn on snapshots for it in the dashboard to back them up too. Backups
Is the AI assistant included?
Yes. Studio’s AI assistant writes and explains SQL, creates tables with their policies and helps debug errors, and every query it wants to run waits for your approval. Project Settings, AI decides what it may see: the schema by default, and query results only when a project admin allows them. It runs on StackBlaze AI and is billed to your workspace like the rest of StackBlaze AI. Pricing
Can I use my own domain?
Yes. Attach a custom domain to the gateway from the dashboard, then set API_EXTERNAL_URL and GOTRUE_SITE_URL on the Auth card and SUPABASE_PUBLIC_URL on the Studio card to it. Custom domains
What does it cost?
You pay for the compute, storage and bandwidth the services, PostgreSQL and the files volume use, not per user or per request. Pricing
More Development templates
nocodbBuild databases as spreadsheets: tables with typed fields, grid, kanban, gallery, form and calendar views, and a REST API for every table. An open source Airtable alternative on your own Postgres.
infisicalOpen-source secrets manager: store, version and sync app secrets across projects and environments, with machine identities for CI and servers, an internal PKI and audit logs.
keycloakOpen source identity and access management. Single sign-on for your apps over OpenID Connect and SAML, user federation with LDAP and Active Directory, social login, multi-factor authentication and an admin console for realms, clients and users.
strapiOpen-source headless CMS. Edit content in a clean admin panel and serve it to any frontend over REST and GraphQL, with a media library and role-based access.