Skip to content
SHC Docs

Supabase

These answers used to sit on this app’s store listing. They moved here on 2026-08-17: a shopper deciding whether to install is not reading six hundred words of Q&A, and the listing page is the pitch. The knowledge is no less true for being off the storefront: it is the part you want before you commit, which is what a guide is for.

Is this the same thing as Supabase’s hosted service?

Section titled “Is this the same thing as Supabase’s hosted service?”

It is the open-source Supabase stack, self-hosted: the same gateway, auth server, REST layer, realtime server, storage API, edge runtime and studio. It is not the hosted control plane, and this page does not describe features that only exist there.

Yes. Storage keeps object bytes in one S3 bucket, and the install is refused without an s3 integration or vars.s3.endpoint. SHC ships no S3 server of its own: make the bucket at a hosted provider (Backblaze B2, Hetzner Object Storage, Cloudflare R2 or any S3-compatible service) and bind the s3 plug to an s3 connection, directly or through an external-s3 front. See Object storage for apps.

How do I open Studio, and what do I have to bind?

Section titled “How do I open Studio, and what do I have to bind?”

One hostname, and you are done:

Terminal window
shc install supabase -t <tenant> --stack supabase --expose backend.corp.example.com

Kong is the front door for the whole host. It routes the API prefixes (/auth/v1/, /rest/v1/, /graphql/v1, /realtime/v1/, /storage/v1/, /functions/v1/, /pg/) to their services and hands / to Studio, so opening the bare hostname in a browser lands on the dashboard. There is no second hostname to bind and no path prefix to remember.

SHC’s SSO gate, and nothing else. The host ships access: gated, so Keycloak authenticates you before Kong sees the request. Upstream’s self-hosted Supabase puts a shared DASHBOARD_USERNAME / DASHBOARD_PASSWORD on the dashboard instead; this package leaves those unset and drops the basic-auth prompt, because a second static password shared by everyone, behind an SSO gate that already knows who you are, buys nothing.

The API prefixes above are exempt from that gate on purpose. They carry their own credential (the anon and service_role API keys Kong checks), and the gate answers a non-browser caller with a bare 401 rather than a redirect, so gating them would break supabase-js, the edge runtime and every CI job in one move.

If you want the API surface reachable but the dashboard closed off entirely, that is --open plus your own edge policy, not a setting in this package.

Yes. It is PostgreSQL, and everything above it talks to it the same way you can. Your migrations, your extensions, your backup tooling: all of it works because none of it was ever abstracted away.

What happens when I restore a backup somewhere else?

Section titled “What happens when I restore a backup somewhere else?”

Service passwords are re-asserted by a post-restore job, so the restored deployment stops holding the source deployment’s credentials. That is one fewer way for a staging copy to become a production incident.