Opsphere
← All news

Supabase integration adds read-only backend diagnostics

Opsphere now queries Supabase during an operational investigation. Read-only tools cover project status, logs, database capacity, connections, advisors, migrations, backups and service health. Supabase remains the source of those results.

Access goes through the Supabase Management API with a read-only personal access token. Opsphere does not use a project URL, a service role key, a database password or free-form SQL.

What changes

A Supabase project can now be checked during an investigation, next to deployments, errors and incidents from other connected systems. The result is backend evidence from the Management API.

How it works

A tenant adds a read-only personal access token. An organization slug and a project ref are optional. Opsphere calls the Management API at api.supabase.com and returns the result to the investigation.

  • 12 core tools cover projects, project status, logs, errors, metrics, database capacity, connections, usage, database inspection, advisors, migrations and backups.
  • 10 service tools cover Edge Functions, auth, storage, realtime, branches, configuration summary and secrets metadata.
  • Logs do not use the retired logs.all endpoint. Metrics come from the Management API Prometheus endpoint with a closed list of series.

Limits and requirements

Opsphere is read-only by default. Supabase remains authoritative for the underlying data.

  • The module starts disabled. Community has no Supabase tools, Developer includes the 12 core tools, and Team, Enterprise and Custom include all 22.
  • No write access, restore, arbitrary SQL, secret values, Edge Function source code, invoices or probes to the project host.
  • The secrets tool returns metadata only.