Deploy Supabase in one click.
The open-source Postgres backend platform. We review it, secure it and run it in production for you. Pick a region in Switzerland, France or Germany. We keep it patched, backed up and online. You just build.
★ 102k stars · Apache-2.0 · TypeScript · tested versions · shipped with a runbook
What is Supabase?
The open-source Firebase alternative, built on plain Postgres, and self-hostable end to end.
Supabase is an open-source backend platform built on Postgres. You get a full Postgres database with authentication, auto-generated REST APIs, realtime subscriptions and file storage layered on top. These are the backend pieces you’d otherwise assemble yourself, behind one dashboard. And underneath it’s plain Postgres: real SQL, extensions, direct connections.
That backend is your entire application: user accounts, sessions, production data, uploaded files. Self-hosting Supabase keeps all of it on infrastructure you control, under laws you choose, instead of a hosted backend provider’s cloud.
The catch: self-hosted Supabase is not one service but a fleet: Postgres, auth, API gateway, realtime, storage. All of it must be configured, secured and upgraded together. Plus TLS, backups of the database your whole product depends on, and patches. That job is usually yours, at the worst possible time.
Supabase, without the ops.
Everything below is what you’d otherwise build and babysit yourself.
Your users’ data stays where you put it.
Deploy to ch-zh1 (Zurich), fr-pa1 (Paris) or de-fr1 (Frankfurt). Your database, auth records and uploaded files stay in the region you choose, under Swiss or EU law and in line with GDPR.
Reviewed before it ships.
Our Supabase package is reviewed, secured and locked to versions we have tested, and it ships with a runbook. We track CVEs upstream and patch them fast.
It’s just Postgres underneath.
No proprietary database layer between you and your data. Direct SQL access, Postgres extensions, standard tooling: everything you already know how to use, and a pg_dump away from anywhere else.
TLS, upgrades, scaling: handled.
Certificates issued and renewed, rolling zero-downtime updates, instant rollback, health checks. Supabase’s services move fast and move together; we keep the whole fleet current without breaking your app.
Backups you can actually restore.
Your database is your product. Offsite backups of your data, auth records and files. We run restore drills, not just snapshots.
Leave whenever you want.
Supabase is open source and underneath it’s standard Postgres: your data leaves with you as a plain database dump, in usable form. Pilae runs it for you. It never owns it.
Self-hosting Supabase: DIY vs Pilae.
Both paths end with Supabase in production. Only one of them ends there this afternoon.
| Self-hosted DIY | On Pilae | |
|---|---|---|
| Initial setup | Docker, reverse proxy, DNS, auth. An afternoon if nothing fights back | One click, live in minutes |
| TLS certificates | Issue, wire up, remember to renew | Issued and renewed automatically |
| Upgrades | Frequent releases to track, test and apply yourself | Tested versions, rolled out with instant rollback |
| Security patching | You watch the CVE feed | Upstream tracked, CVEs prioritized |
| Backups | cron + object storage + hope | Offsite, verified with restore drills |
| Data residency | Wherever your VPS happens to be | You pick: Zurich, Paris, Frankfurt, or your own racks |
| 3 a.m. failures | Yours | Ours |
| Moving parts | Postgres, auth, gateway, realtime, storage: one compose file, tuned by hand | Shipped as one reviewed and tested package |
| Database exposure | Postgres reachable from the internet, or more gymnastics | Encrypted access on dedicated VLANs |
From catalog to production in three steps.
No servers to set up, no configuration to write. The platform work is already done.
Pick Supabase.
Find it in the catalog: reviewed, secured, locked to tested versions, runbook included.
Choose where it runs.
A Pilae region in Switzerland, France or Germany, or your own machine connected through a secure tunnel. Same console either way.
Deploy and start building.
One click to production with TLS and backups from day one. Point your app at your Supabase URL and keys, define your schema, ship.
Your app’s entire backend. Keep it close.
Every Supabase deployment is pinned to the region you choose. Encryption, dedicated VLANs, and the option to hold your own encryption keys for regulated workloads. Your users’ data stays under Swiss or EU law, not someone else’s.
Deploying Supabase: the questions we get.
If yours isn’t here, reach out and we’ll answer it, usually the same day.
Can you really self-host Supabase?
Yes. Supabase is open source and the platform is designed to be self-hostable: the same Postgres, auth, APIs, realtime and storage that power its hosted cloud. The hard part has always been running the pieces together; that’s the part Pilae takes over.
What’s the easiest way to self-host Supabase?
Deploying it through a managed platform. On Pilae you pick Supabase from the catalog, choose a region, and click deploy. TLS, backups, patching and upgrades are handled for you from the first minute. You get self-hosting’s control without its ops.
Where does my Supabase database live?
In the region you choose: Zurich, Paris or Frankfurt. Your database, auth records and uploaded files stay there, encrypted. For regulated workloads you can hold your own encryption keys. Everything sits under Swiss or EU law, in line with GDPR.
Is self-hosted Supabase just Postgres?
At its core, yes, and that’s a feature. You get direct SQL access, Postgres extensions and standard tooling, with auth, auto-generated APIs, realtime and storage layered on top. Nothing proprietary sits between you and your data.
How do Supabase updates and security patches work on Pilae?
We track upstream across the whole service fleet, prioritize CVEs, and ship updates locked to versions we have tested, rolled out with zero downtime and instant rollback. The services stay in step without you watching five release feeds.
Can I move my Supabase project off Pilae later?
Yes, and that’s by design. Underneath, it’s standard Postgres: your data exits as a plain database dump, your files and auth records with it, in usable form. No proprietary formats, no lock-in.
Runs well next to.
Build your stack from the same catalog. One console, one click each.
Workflow automation with 400+ integrations. Self-hosted, source-available.
SQL-first business intelligence. Connect Postgres, ClickHouse, BigQuery.
Turn any SQL database into a smart spreadsheet. Airtable, self-hosted.
User-friendly, extensible interface for any large language model.
Supabase, without the ops.
Deploy it in minutes, keep your data in the country you choose, and leave whenever you want. Your data goes with you.