Supabase. Database, auth, storage, and edge functions.
Connect your Supabase project to let agents monitor your database, auth, storage, and edge functions. Agents can analyze query performance, check auth flows, and help optimize your backend.
Join the waitlistWhat Polylane does with Supabase.
Projects and their pieces in the graph
Every project with its edge functions, database branches, and storage buckets, next to everything else you run.
Linked to the services that use them
Polylane matches Supabase hosts in env vars across your other clouds, so the graph already knows which service talks to which project.
Change history per sync
Functions redeploy, branches come and go, buckets appear. Each sync records what changed, so investigations start from the change.
Your rows stay yours
Polylane reads the Supabase Management API and nothing else: it never connects to your databases, never sees your rows, and never stores project API keys.
How it works.
Connect
OAuth with read scopes, or paste a personal access token. Either way it's encrypted before it's stored, and the agent never sees it.
Sync
Projects, edge functions, branches, and buckets land in the graph with their history.
Agents investigate
A failing function or an unhealthy project traces to the services around it, and the fix arrives for your review.
In the graph.
The Supabase resource types Polylane syncs, with their edges, 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 The tools agents get.
What an agent can do with Supabase mid-investigation. Every call lands in the thread transcript, cited.
supabaseApi Call any Supabase Management API endpoint that lacks a dedicated tool
supabaseGetLogs Get Supabase service logs for a project: API gateway, edge functions, Postgres, Auth, Storage, or Realtime
supabaseGetAdvisors Get Supabase security and performance advisor findings for a project
supabaseGetProjectHealth Get the live health of a Supabase project's bundled services (database, REST, Auth, Storage, Realtime)
Questions.
Is Polylane an AI SRE for Supabase?
It's what most people mean by the term: agents that keep your Supabase resources in one context graph, watch them, investigate issues and fix what they can, with a human approving anything that changes production. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.
Can Polylane change anything in Supabase?
Only if you let it. Connected read-only, agents investigate and explain, and changes only ever land as pull requests for you to review. With write access, every write pauses for your approval first, with the method, path and reason on screen. Rollbacks are off by default: you enable them per automation and can turn them off at any time.