If you run Supabase on your own infrastructure, Supanator now talks to it. Same app, same UI, same security model. Just point it at your own stack instead of Supabase Cloud.

Add a self-hosted instance the same way you'd add a Cloud project. Paste your URL and keys, tweak a couple of advanced bits if your stack needs them, and the app runs a connection probe to figure out which services your stack exposes. You see the result before you finish setup.

What it works with

Four flavors of self-hosted Supabase are supported out of the box:

• The official self-hosted Docker setup
• Kubernetes deployments
• The Supabase CLI running on your laptop
• Custom Postgres databases with your own service mix

That covers the ways I've actually seen people run Supabase outside of Cloud. If you have a stack I'm missing, write in.

A compatibility chart, not a guessing game

Self-hosted Supabase is not one product. It's a collection of services that can be missing, swapped, or routed strangely depending on how you put your stack together. Some setups expose Realtime. Some don't. Some have Storage. Some have a stripped-down auth setup. Some sit behind a reverse proxy that mangles headers.

So before you connect, the connect sheet shows you a compatibility chart. Each row is a feature you might use (tables, SQL, auth users, storage browser, edge functions, realtime, advanced monitoring). Each column is your stack type. You see exactly what will work, what won't, and why, before you commit.

After you connect, if the probe finds something missing, that nav row just goes away. No empty screens, no confusing errors.

Auth, certificates, and the weird-network stuff

The hard part of self-hosted isn't the SQL. It's getting the request to the right place with the right headers. Real-world stacks do strange things.

So the Advanced section in the connect sheet handles:

• Reverse proxies and custom service paths
• Self-signed certificates with per-host trust (the trust override never leaks to other hosts the app talks to)
• HTTP Basic Auth in front of the stack
• Custom auth header names (some setups want X-API-Key instead of apikey)
• Extra static headers applied to every outbound request

Both API key formats work too: legacy JWT keys and the new sb_publishable_* / sb_secret_* format.

Where the limits are

Self-hosted Supabase doesn't have a platform management API, so the things that depended on it don't apply:

• No managed backups or point-in-time recovery (you run your own)
• No Cloud advisors or SSL enforcement (your infrastructure, your call)
• No custom domain configuration through the app (your DNS, your reverse proxy)
• No project branches (a Cloud-only feature)

What you get in trade is a few tools Cloud users don't have, since direct Postgres access lets us do them properly:

• Active Connections with terminate
• Query Performance via pg_stat_statements
• Table Health (bloat, vacuum, analyze status)
• Lock Monitor with deadlock detection
• DB Migration assistant

These admin tools are Pro features, alongside Logs which has always been Pro. They read enough about your database that gating them felt right.

Apple Watch

The Watch app supports self-hosted too. The same account list shows on your wrist. Database size, connection count, table count, and active queries are read directly from your stack via pg-meta. Tiles that don't apply on self-hosted (request counts that depend on Cloud-only analytics) are hidden, so you get a clean dashboard instead of a row of zeros.

How to try it

If you have a Pro subscription on iOS, you have self-hosted access already. Add a new account, pick Self-Hosted, and paste your details. The compatibility chart shows you what to expect before you confirm.

If you run into a stack the app doesn't handle well, email me at [email protected]. As always, it's one person reading the inbox.

Supanator is on Google Play.

Download Supanator for Android

A quick note before you go install it. The Android version isn't at full feature parity with iOS yet, and I'd rather you hear that from me than discover it in a one star review.

What works today is the core of the app. The SQL editor, the table editor, storage, edge functions, auth, and multi project support. Same security model as iOS. Your credentials stay on your device, every API call goes direct to Supabase, and there are no servers in the middle.

What's missing is mostly the polish layer. Some of the more advanced filters, push notifications, the AI assistant, and a few of the smaller niceties that the iOS app picked up over months of small tweaks. The Android version will get all of it. It just doesn't have it yet.

I'm closing the gap fast. Builds ship often. The roadmap is already a checklist of "match iOS, then keep going."

The reason iOS shipped first, and the reason parity is taking a minute to land, is the same reason every email gets a real reply. Supanator is built by one person. So when you email [email protected] about a bug on your Pixel, it goes straight to the developer. That's a feature, not a disclaimer.

If you've been waiting since launch, the wait is over. Install it, push it hard, and tell me what you really need for your workflow. Google Play, [email protected], @getsupanator.

Every week since Supanator launched, I've gotten the same question: "When is the Android version coming?"

Today I can finally say: we're building it. For real.

Why it took this long

Supanator started as a native iOS app. Not a cross-platform wrapper, not a React Native project, pure Swift, built specifically for iPhone. That decision is what makes it fast, smooth, and feel like it belongs on your phone.

But it also means I couldn't just flip a switch and ship an Android version. I had to make a choice: build a native Android app from scratch with Kotlin, or find a cross-platform approach that doesn't sacrifice what makes Supanator good.

I chose to go native. Kotlin Multiplatform lets me share the core logic — networking, data models, API layer — while building truly native UIs for each platform. No compromise on performance. No compromise on feel. It's more work, but it's the right call.

What to expect

The Android version will have full feature parity with iOS:

• SQL Editor — run queries with syntax highlighting and instant results
• Table Editor — browse, filter, edit, and delete rows
• Storage — upload files, preview images, manage buckets
• Edge Functions — invoke, monitor, and read logs
• Auth management — view users, sessions, and providers

Same security model too. Your credentials stay on your device. Every API call goes directly to Supabase. No middleman. No servers. No exceptions.

The timeline

I'm not going to give you a fake date. Here's what I can tell you:

• Core networking and API layer is already shared and working
• The Kotlin/Compose UI is in active development
• Closed beta will come first — small group, raw builds, fast feedback
• Public beta on Google Play will follow

I'd rather ship something solid than rush something broken. But this is my top priority right now.

Get early access

If you want to be one of the first to try Supanator on Android, sign up for the beta on the homepage. I'll send you one email when the beta is ready. No spam, no newsletter, no "updates" — just one notification when you can download it.

To the Android devs who've been waiting

I hear you. I know it's been frustrating watching the iOS version get all the love. The wait is almost over.

Your Supabase projects deserve a native experience too. We're building it.

Hope you're having a wonderful holiday season, wherever you are in the world.

Here in Sweden, we celebrate Christmas on the 24th, so yesterday was the big day. My daughter was absolutely spoiled with presents, and yes, Santa made an appearance. Seeing her excitement is honestly the best part of the holidays.

I wanted to take a moment to say thank you to everyone who's downloaded and tried Supanator since launch. Building an app as an indie developer can feel like shouting into the void sometimes, so every download, every piece of feedback, and every kind word means a lot.

I've got some exciting updates planned for the new year, and I can't wait to share them with you. For now though, I'm going to enjoy the rest of the holidays with family.

Merry Christmas and happy holidays!

As a developer, I've often found myself needing to quickly check on a database, look up a user, or monitor an Edge Function, but not always at my desk. That's why I built Supanator.

What is Supanator?

Supanator is a native iOS app designed specifically for Supabase developers. It's not a web wrapper or a responsive website. It's built from the ground up for iOS, delivering the smooth, fast experience you expect from a native app.

Key features

• Table editor: browse, search, create, edit, and delete rows directly from your phone
• SQL editor: run queries with syntax highlighting and view results in a clean interface
• Storage browser: navigate buckets, preview images, upload files
• Edge Functions: view, invoke, and monitor your serverless functions
• Auth management: browse users, view details, manage authentication
• Logs and monitoring: check API logs and usage stats on the go

Security first

I take security seriously. Your credentials never leave your device, stored securely in iOS Keychain. Every API call goes directly to Supabase's servers. There's no backend, no servers, no way for anyone to access your data. You can verify this yourself with any network proxy tool.

Getting started

Getting started is simple. Download Supanator from the App Store, sign in with your Supabase account using OAuth 2.0 or an access token, and you're ready to go. The free tier includes all core features for one project, perfect for personal projects or trying out the app.

What's next

This is just the beginning. I have a roadmap full of exciting features based on community feedback. Have an idea? I'd love to hear from you at [email protected] or on X (Twitter).

Download Supanator today and take your Supabase projects with you, wherever you go.