OrchestrAI Live

Integration · Database

Supabase + OrchestrAI

Catalog exported 2026-09-02 · Supabase website

Inventory Supabase projects and Edge Functions from chat, and update project metadata with approval.

OrchestrAI exposes 5 Supabase operations: 4 are low-risk (read-only or low-impact), and 1 create or modify resources and run only after you confirm the plan. 1 of them also carries a step-level approval gate.

5operations
4low risk
1create or modify
0destructive
1step-level approval

What teams use it for

Platform teams with several Supabase projects use OrchestrAI to answer which projects exist in the org, which Edge Functions are deployed to the customer-portal project, and whether the stored access token is still valid, which is useful when an application's behavior suggests it is pointing at the wrong project. Renaming or otherwise updating a project's metadata is the single write operation and it is high risk with approval gating. OrchestrAI does not run SQL against a Supabase database, manage auth users or storage buckets, or deploy Edge Functions, so those tasks remain in the Supabase dashboard or CLI.

Every Supabase operation, with its risk level

Supabase operations available through OrchestrAI
Operation What it does Risk Step-level approval
List Managed Platform Deployments List deployments, machines, or runtime resources for providers that expose deployment inventory Low risk No
List Managed Platform Projects List projects, apps, sites, databases, or clusters for supported PaaS and managed database providers Low risk No
List Supabase Edge Functions List Edge Functions for a Supabase project Low risk No
Validate Managed Platform Connection Validate configured credentials for a supported PaaS or managed database provider Low risk No
Update Supabase Project Metadata Update Supabase project metadata with approval gating Modifies existing Yes

Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.

What you connect

A Supabase credential (stored as vercel, fly, railway, netlify, render, neon, supabase, planetscale, upstash, aiven, cockroachdb_cloud). Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.

Prompts that work

  • List the Edge Functions deployed to the customer-portal Supabase project
  • Which Supabase projects do we have in the organization?
  • Rename the Supabase project 'test-2' to 'billing-staging'

Before anything runs

Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.

Frequently asked questions

Can OrchestrAI run SQL on my Supabase database?
No, Supabase coverage is limited to listing projects and their resources, listing Edge Functions, validating the connection, and updating project metadata. Queries are not part of the set.
What does OrchestrAI ask before updating Supabase project metadata?
supabase_update_project_metadata is high risk and approval-gated, so it shows the project and the fields that will change and waits for confirmation before applying.
How does OrchestrAI authenticate to Supabase?
You add a Supabase credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.

Related integrations

Try it on your own account

Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.

Start for $5

Unused credits refunded in your first 14 days.