Supabase

What it watches

Supabase feeds Backend — Database and auth health, config drift, security advisors — as Backend health and auth config.

What Keelnest reads

Management API token · health, advisors (experimental), logs, auth URL configuration.

Security advisor is experimental; treated as advisory. No destructive writes.

Read-only, like every connection: Keelnest never refunds, charges, changes a price, edits a setting or an environment variable, merges on its own or runs a migration. The credential is checked with one read call before it is stored, encrypted at rest, and can be revoked at the provider at any time. Security says the whole of it.

How to connect

1. Create the personal access token. Supabase > Account > Access Tokens > Generate new token. Read access to projects is enough. Open Supabase.
2. Paste it into Keelnest. In your workspace, open Integrations, find Supabase and press Connect. Keelnest makes one read call to confirm the credential works, stores it encrypted, and starts reading on the next five-minute tick.
3. Link the apps. Under Manage, pick which applications this account watches. An app linked to a host is checked the moment that host reports a deploy; an app linked to a payment or AI account starts building its baseline from that hour.

Or sign in instead of pasting a key

Where this Keelnest has Supabase sign-in enabled, the Connect drawer also offers a button. Your client signs in to Supabase and picks the organization. Keelnest asks for four read scopes and no write scope of any kind: the project list and health, whether the database has stopped accepting writes, the auth URL configuration, and failed sign-ins counted per hour. A personal access token carries whatever its owner can do; this cannot change anything.

Start watching

Create a workspace and connect Supabase from Integrations, or run the free check on any public URL first. All docs.