If you run Supabase on your own infrastructure, the Supanator mobile app can connect to it alongside your Supabase Cloud projects.
Add a self-hosted instance the same way you add a Cloud project. Paste your URL and keys, adjust the advanced settings if your stack needs them, and Supanator runs a connection probe to identify which services the stack exposes. You see the result before you finish setup.
What it works with
Four kinds of self-hosted setup are supported:
- The official self-hosted Docker setup
- Kubernetes deployments
- The Supabase CLI running on your computer
- Custom Postgres databases with their own service mix
Because self-hosted stacks vary, the connection probe—not the deployment label—is the final check of which features are available.
A compatibility chart, not a guessing game
Self-hosted Supabase is a collection of services that may be missing, replaced, or routed differently depending on the deployment. Some setups expose Realtime. Some do not. Some have Storage, while others use a stripped-down Auth setup or sit behind a reverse proxy.
Before you connect, Supanator shows a compatibility chart for tables, SQL, Auth users, Storage, Edge Functions, Realtime, and advanced monitoring. After you connect, navigation for unavailable services stays hidden instead of leading to empty screens.
Auth, certificates, and unusual networks
The Advanced section of the connection flow supports:
- 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 applied to outbound requests
Both legacy JWT keys and the newer sb_publishable_* and sb_secret_* key formats are supported.
Where the limits are
Self-hosted Supabase does not provide the Cloud platform Management API, so Cloud-specific functionality does not apply:
- No managed backups or point-in-time recovery
- No Cloud advisors or SSL enforcement
- No custom-domain configuration through the app
- No Cloud project branches
Direct Postgres access enables several self-hosted administration tools instead:
- Active Connections with terminate controls
- Query Performance through
pg_stat_statements - Table Health for bloat, vacuum, and analyze status
- Lock Monitor with deadlock detection
- Database migration assistance
Apple Watch
The Apple Watch app supports self-hosted accounts too. Database size, connection count, table count, and active queries are read from the stack through pg-meta. Tiles that depend on Cloud-only analytics remain hidden when they do not apply.
How to try it
Self-hosted access is a Pro feature. Add a new account, choose Self-Hosted, paste the connection details, and review the compatibility result before confirming. If your deployment behaves differently from the setups above, contact [email protected].