Supabase integration. Trace failures across your Supabase database, auth, storage and functions.
Praxen Inc. reads your Supabase logs, health and advisor findings, traces a failure to the layer that broke, and writes the fix. It never touches your rows.
Get started for freeHow to set up Supabase
The connection guide says resource discovery can take a few minutes. Total consent and setup duration is not measured.
- Choose Supabase and authorize Praxen Inc. using the console’s OAuth flow.
- Select the organization on the authorization/organization-selection flow. Each connected account covers a single organization.
- For the API alternative, generate a personal access token under Supabase Account → Access Tokens. Supply the sbp_ token and an organization slug when the account can reach multiple organizations.
Permissions and access
OAuth requests are built without a scope parameter: the app’s provider-side configuration determines the exact consent grants, which cannot be confirmed from this code. Personal access tokens act with the creator’s Supabase account permissions. The console has no separate read-only/full-access selector. Review the consent screen; do not substitute a database password or project anon key for management API authorization.
Discovery, refresh and the connected view
A scheduled inventory refresh runs every 15 minutes. Projects, edge functions, branches and storage buckets are discovered with project status, region and compute size. Inactive projects remain listed, but their child functions, branches and buckets are only synced while active. Open project health, logs and advisor tools from an investigation alongside the graph.
Disconnect and revoke access
Disconnect the organization in Praxen Inc. Revoke the personal access token if used, or remove the OAuth application authorization in Supabase to revoke access at the provider.
Provider credentials and Praxen Inc.’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every Supabase resource Praxen Inc. picks up sits in the graph with its connections, config and history.
Project Postgres Database Connection Pooler Edge Function Database Branch Storage Bucket Auth Service Storage Service Realtime Service REST API Custom Domain Secret Network Restrictions Supabase tools.
The calls Praxen Inc. can make to Supabase when it looks into an issue.
Supabase -
supabaseApiCall any Supabase Management API endpoint that lacks a dedicated tool -
supabaseGetLogsGet Supabase service logs for a project: API gateway, edge functions, Postgres, Auth, Storage, or Realtime -
supabaseGetAdvisorsGet Supabase security and performance advisor findings for a project -
supabaseGetProjectHealthGet the live health of a Supabase project's bundled services (database, REST, Auth, Storage, Realtime)
Supabase setup and troubleshooting
Common questions.
How does Praxen Inc. connect to my Supabase organization?
Choose Supabase and authorize Praxen Inc. using the console’s OAuth flow. Select the organization on the authorization/organization-selection flow. Each connected account covers a single organization. For the API alternative, generate a personal access token under Supabase Account → Access Tokens. Supply the sbp_ token and an organization slug when the account can reach multiple organizations.
What Supabase resources does Praxen Inc. sync?
A scheduled inventory refresh runs every 15 minutes. Projects, edge functions, branches and storage buckets are discovered with project status, region and compute size. Inactive projects remain listed, but their child functions, branches and buckets are only synced while active. Open project health, logs and advisor tools from an investigation alongside the graph.