Connect your Supabase project

Cockpitify connects to your app through a small, isolated ops layer that it installs in your own Supabase project. Your users’ data stays there; Cockpitify reads it through that layer.

Before you start

• You need to be able to approve OAuth access for the Supabase organization that owns the project.
• One Supabase project backs one app in Cockpitify.
• A paused project can’t be set up. If Supabase paused it for inactivity, restore it in the Supabase dashboard first.

Step 1: choose the backend

1. Tap + at the top (or Connect an app on an empty screen).
2. On Connect your app, keep Supabase selected and tap Connect with Supabase.
3. Your browser opens Supabase’s consent screen. Approve it and you’re sent back to the app.

Using your own Postgres, Firebase or AWS? Those are listed under Soon. Tap Notify me on the one you use and we’ll email you when it’s ready; the most requested comes first.

Step 2: pick the project and review

1. Pick your project from the list. Projects already connected show Connected or Another account.
2. Check the App name (it defaults to the project name, up to 60 characters).
3. Read To be added to your project:
   • the ops schema and its tables
   • two Edge Functions: ops-api and ops-revenuecat
   • a few scheduled jobs (heartbeat, readings, retention and similar)
   • the pgcrypto, pg_net and pg_cron extensions, skipped if already enabled
   • one entry point that your app sends usage events to; it writes only to ops tables
4. Under Left untouched you see your existing tables and the auth schema. They are only read.
5. Want to see every line? Tap See all the SQL and function code, which also shows the SQL that removal runs.
6. Tap Confirm and install.

Step 3: install

The install screen shows seven steps, from Enabling extensions to Testing the connection, with a progress bar. It takes about 30–60 seconds. You can leave the screen: you’ll get a notification when it’s done.

When it finishes you see that your app is connected and how many users were found. From here, allow notifications and work through the Finish setup checklist (see Get started).

If setup doesn’t finish

You see Setup couldn’t finish with the step that failed. Tap Repair to run it again; repair reinstalls missing parts without deleting anything. Common causes:

• The Supabase authorization expired. Connect again; the consent is only valid for a short time.
• This project is already connected. Repair or update it from Settings → Apps instead.
• Your plan allows 1 app. The Free plan has one app. See Plans, trials and billing.

More fixes are in Troubleshooting.

What Cockpitify stores

Your users’ records stay in your project. Our backend keeps your account, how to reach each app’s ops layer, and notification metadata such as when and how many pushes went out. API keys you add later go into your project’s Supabase Vault, not to us.