Check your connections and update the project
See everything that feeds an app on one page, whether each part works, when data last arrived, and when your project has an update.
The Connections page lists everything that brings data into one app: the Supabase project, RevenueCat, AI cost, usage tracking, Sentry, each service you track and more. Each row says what it gives you, whether it works, and when data last arrived. It is also where you update the Cockpitify layer in your project.
Open it
- Phone: tap the app’s name at the top, then Connections under App.
- Web: in the sidebar, open App → Connections.
At the top, a count tells you how many connections are working, how many need you and how many aren’t set up.
What each row is
| Group | Connection | Gives you |
|---|---|---|
| Project | Supabase project | Users, events, everything |
| Project | People source | Who your users are |
| Project | Profile data (optional) | Plan, premium, platform, language |
| Money | RevenueCat | Revenue per user |
| Money | AI cost | AI cost per user |
| Money | Ads | Ad revenue per user |
| Product | Usage tracking | Screens, features, funnels |
| Product | Sentry | Crashes, release health |
| Product | Expo | Builds, update usage |
| Service balances | One row per service | Balance, days left, spending |
| Tools | Ask: your own AI key (optional) | Ask without a monthly limit |
Under Service balances, each service you track has its own row, and + Add service opens the catalog. See Add a service.
A row marked Pro needs a paid plan. Rows marked optional, and rows your plan doesn’t include, aren’t counted as not set up.
What the states mean
| State | What it means |
|---|---|
| Working | Data arrives. The line says when it last did |
| Waiting for data | Set up, but nothing has arrived yet, for example “Waiting for the first purchase” |
| Not set up | Not connected yet |
| Stale | Data was expected and didn’t come |
| Running low | A service is under your warning line, past its monthly budget, or runs out within days |
| Broken part | Something stopped working: a scheduled step failed, data stopped arriving, or parts of the project are missing |
| Needs update | Works once the project is updated |
A source that is just quiet stays Working. For example, “No new app events in 2 days. They arrive when people use the app.” RevenueCat only turns Stale when renewals were due and no events came; Sentry when it hasn’t been read for longer than its hourly reading.
Open a connection
Tap a row.
- Web: a panel opens beside the list with numbered steps to set it up and a check that it works. Once it works, the panel shows a summary and its options.
- Phone: the screen where that connection is set up opens. A few are set up only on the web, such as the people source; the row then says “Set this up in the web console at console.cockpitify.app.”
A row that needs you names what it opens: Check webhook, Check Sentry, Check project, Check the reading or See what’s wrong.
When something needs fixing, Home shows a Needs attention card with the same rows, and a link to the rest on Connections.
Update the project
Each app runs a small Cockpitify layer (ops) in its Supabase project. When a newer version is out, a mark appears beside the row’s title. Hover it on the web, or tap it on the phone, to read what it brings.
| Mark | What it means |
|---|---|
| Update available | Fixes only. Nothing breaks without it; update when it suits you |
| Update requested | It brings something new or a security fix. The row says Needs update |
| Update required | This install is too old to use safely: update it now |
A row that needs the update to work, for example a newer feature, says Comes with the project update.
To update:
- Open the Supabase project row (on the phone, tap Update in the mark’s note).
- Tap Update (web: Update to and the version).
- Choose how to apply it:
- Automatic: Cockpitify applies it after you approve Cockpitify in Supabase. About a minute. The access key is deleted when the job ends, so every update asks again.
- Do it myself: you run it with your own Supabase login, and Cockpitify gets no access to your project. Review what changes, run the SQL in the SQL Editor, deploy the functions with the Supabase CLI, then tap I’ve run it — check.
Updates don’t touch your data. The function files for Do it myself download from the web console on a computer.
Who can change connections
Everyone on the app can see the states. Owners and admins set connections up and change them; on a team, people with edit access to an area can change its connection, such as Services.
Older projects
Some states show only once the project runs ops 0.64.0 or newer. Until then a row says “Its state shows once this project runs Cockpitify 0.64.0 or newer.” Update the project to see them.