← All updates

Updated

Supabase projects and services in the context graph

Connect a Supabase organisation and every project joins the context graph with its databases, edge functions, storage and auth, watched through its service logs.

What changed

Connect a Supabase organisation with OAuth or a personal access token and Polylane adds every project to the context graph: databases and read replicas, the connection pooler, Auth, Storage, Realtime and REST services, edge functions, branches, storage buckets and custom domains, synced every 15 minutes.

Services that reach a project through a supabase.co hostname in their environment variables are linked to it, and Cloudflare Hyperdrive configs are linked to the database they point at.

Checks from service logs

Each project, database, edge function and bundled service gets its own monitor. Polylane builds series from the service logs: Postgres errors and log volume, edge function invocations, errors and execution time, Auth errors, and REST and API gateway 5xx errors. A change from the usual level that is a real problem opens an issue.

In investigations

Agents read the API gateway, edge function, Postgres, Auth, Storage and Realtime logs of a project, the live health of each service, and its security and performance advisor findings. Agents never query your database. See the Supabase integration.

Why it matters

A Supabase app spreads across Postgres, Auth, Storage and edge functions, so a failed sign-in can start in any of them. With each project's services and logs in reach, an investigation checks all of them.

How to use it

  1. Click Connect with Supabase in Polylane.
  2. Sign in to Supabase, approve the access and select the organisation to connect.
  3. Supabase sends you back to Polylane and the first sync starts.

To connect with a token instead, generate one under Account → Access Tokens in Supabase (it starts with sbp_) and paste it into Polylane.

Related