Supabase Self Hosted in 2026: What Docker Compose Actually Gets You & the Honest Limitations Table - Backups, Upgrades & Studio Gaps from Community Evidence - When to Self-Host vs Stay on the $25/mo Cloud

Quick Answer: Self-hosting Supabase via Docker Compose works and costs nothing in license fees — but you lose managed backups, point-in-time recovery, branching and multi-project Studio, and every upgrade is yours to own. The trade is full data control for full operational responsibility. The upside: your database is now plain Postgres, and you can pick better tools around it.

What Self-Hosting Supabase Actually Means

Supabase isn't one application. It's a stack of services — Postgres itself, GoTrue for auth, PostgREST for the auto-generated API, Realtime, Storage, the Kong gateway, and the Studio dashboard — wired together with Docker Compose. The official self-hosting guide brings the whole stack up with a git clone and docker compose up. We won't duplicate the setup steps here — the docs cover them well, and the exact steps shift between releases.

People self-host for three reasons: data has to stay on their infrastructure (compliance, residency, enterprise private clouds), they want out of usage-based pricing, or they simply want full control. All legitimate. But two things the tutorials gloss over:

First, self-hosted Supabase behaves as one project. No organizations, no multiple projects per instance, no branching. Running staging and production means running two full stacks.

Second, the docs are blunt about the deal. When you self-host, you are responsible for — quoting the official list — "server provisioning and maintenance," "security hardening and keeping OS and services updated," "service configuration and management," "Postgres database maintenance," "high availability and scalability," "backups and disaster recovery," and "monitoring and uptime" (official self-hosting docs, checked June 2026). That list is the entire contract.

The Honest Limitations Table

In October 2025, Supabase opened GitHub discussion #39820 — a maintainer hired specifically to improve self-hosting asked the community what's working and what isn't. The replies are the best evidence you'll find anywhere. Here's what the community reports, set against the official position:

Credit where due: #39820 was started by Supabase, not against it, and a dedicated self-hosting hire is working through the backlog. The core services — Postgres, Auth, Storage, Realtime, PostgREST — are widely reported as solid in the same thread. Plan around the gaps; don't write the product off.

Your Database Is Just Postgres Now — Pick Your GUI

Here's the part most setup guides skip: once you self-host, the database under Supabase is plain PostgreSQL on a server you control. Studio's SQL editor and table view are the thinnest part of the self-hosted stack — and nothing forces you to use them.

QueryGlow runs as a Docker database GUI right next to your Supabase stack: one more container in the compose file, and your whole team opens it at a single URL in the browser — unlimited users, $79 once. Built-in SSH tunnels mean you can reach the Postgres instance on your VPS without ever exposing port 5432. You also get the things Studio doesn't offer: schema-aware autocomplete across your tables, and a visual EXPLAIN plan that flags sequential scans and points at missing indexes — useful the day your PostgREST queries start crawling. The full QueryGlow vs Supabase Studio comparison covers the feature-by-feature breakdown.

To be explicit about scope: QueryGlow does not replace Supabase's auth, storage, or edge functions. Those stay exactly where they are. It replaces the database-facing workflow — querying, inline editing, CSV import/export, performance inspection — which is precisely where self-hosted Studio is weakest.

When to Stay on the Cloud

Honesty time. Supabase Pro is $25/month (verified May 2026), and that buys real things: managed backups with point-in-time recovery, branching, proper observability, upgrades you never think about, and someone else on call when storage misbehaves at 2 a.m.

Stay on the cloud if:

• •Nothing forces your data on-prem — no compliance or residency requirement
• •Your team is small and ops hours are your scarcest resource
• •You'd rather pay $300/year than build a backup-and-restore pipeline you also have to test
• •A weekend of downtime costs you more than a year of subscription

Self-host when the constraint is genuine: data residency, deployments inside enterprise private clouds (a recurring motivation in #39820), air-gapped environments, or predictable cost at a scale where usage-based pricing stings.

Either way, the database underneath is Postgres. The skills — and the tools you put next to it — transfer in both directions.