Self-hosted Supabase, managed from your phone.
Add the stack you run yourself next to your Supabase Cloud projects. Supanator checks which services it exposes before you save it, and copes with reverse proxies, self-signed certificates and Basic Auth.
Self-hosted access is part of Pro.
Works with the way you deploy
Four kinds of self-hosted setup are supported. Self-hosted Supabase is a set of services that can be missing, replaced or routed differently, so the connection check decides what you get, not the deployment label.
- Official Docker setup
- The self-hosted Docker Compose stack from the Supabase repository, including platforms built on it such as Coolify and Easypanel.
- Kubernetes
- Clusters running the Supabase services, wherever they are reachable from your phone.
- Supabase CLI
- The local development stack started by the Supabase CLI on your computer.
- Custom Postgres
- Your own Postgres with your own mix of Supabase services.
Know what works before you connect
Add a self-hosted project the same way you add a Cloud project: paste the URL and keys, adjust the advanced settings if your stack needs them, and run the connection check.
Supanator shows a compatibility chart for tables, SQL, Auth users, Storage, Edge Functions, Realtime and advanced monitoring before you confirm. After you connect, screens for services your stack does not run stay hidden instead of leading to empty pages.
Advanced connection settings
- Reverse proxies and custom service paths
- Self-signed certificates with per-host trust
- HTTP Basic Auth in front of the stack
- Custom auth header names
- Extra static headers on outbound requests
- Legacy JWT keys and the newer sb_publishable and sb_secret keys
What changes on a self-hosted stack
Self-hosted Supabase has no Cloud platform behind it, so Cloud features such as managed backups, point-in-time recovery, advisors, SSL enforcement, custom domains and branches do not apply. Direct Postgres access unlocks a different set of tools instead.
- Active connections
- See every connection and terminate one that is stuck.
- Query performance
- Slow and frequent queries from pg_stat_statements.
- Table health
- Bloat, vacuum and analyze status per table.
- Lock monitor
- Current locks with deadlock detection.
- Migration assistance
- Help with database migrations on your stack.
The Apple Watch app supports self-hosted accounts too, reading database size, connection count, table count and active queries from your stack. If your deployment behaves differently from the setups above, write to support@supanator.com. The launch post covers what changed: Supanator now connects to self-hosted Supabase.
Self-hosted questions
Which self-hosted setups does Supanator support?
The official Docker setup, Kubernetes deployments, the local Supabase CLI stack and custom Postgres databases. Because stacks vary, the connection check is the final word on which features are available.
Is self-hosted support free?
Self-hosted access is part of Pro. The Free plan works with Supabase Cloud projects.
What happens if my stack does not run Realtime or Storage?
Supanator checks which services your stack exposes before you save it, and keeps navigation for services you do not run out of the way instead of leading to empty screens.
Why are backups and advisors missing for my self-hosted project?
They come from the Supabase Cloud platform and its Management API, which self-hosted stacks do not have. Self-hosted projects get Postgres tools such as active connections, query performance, table health and a lock monitor instead.
Does the Apple Watch app work with self-hosted projects?
Yes. Database size, connection count, table count and active queries are read from your stack. Tiles that depend on Cloud analytics stay hidden.
Bring your own Supabase.
Free to download on the App Store and Google Play. Upgrade to Pro in the app to add self-hosted projects.
Requires an existing Supabase project or a self-hosted environment.