Is it safe to point this at production?

Point it at a development database or a read replica first. Agents are good at exploratory querying, and exploration belongs somewhere it cannot cause harm. Once you trust the pattern, widen it deliberately.

Can it run migrations?

It can draft them, and explain what each one would lock and how long it might take. Running them is a decision we would leave with you — a migration is not a good place for a surprise.

Does it understand my schema without being told?

It reads the schema as part of the work, so you can ask questions in your own vocabulary rather than in column names. Well-named tables make its answers noticeably better.

Developer tools

Supabase + Burrak AI

Query your database in English, and let an agent do the follow-up work.

Connects with OAuth — revoke any time

Most questions about a production database are one query away from an answer and one hour away from someone having time to write it. Connecting Supabase lets an agent write the SQL, read the result and carry on — investigating an anomaly, drafting a migration, or checking whether a schema change is safe before you make it.

In the connector catalogue: Manage projects, inspect tables, run queries.

Things you could ask for

Written the way you would actually say them. An agent plans the steps itself.

“How many users signed up last week, and how many ran a task within a day of signing up?”
“Look at this table and tell me which columns have suspicious nulls or obvious duplicates.”
“Draft a migration that adds the columns this feature needs, and explain what it would lock.”
“Investigate why this query is slow and suggest an index, with the reasoning.”
“Every morning, check for rows that failed processing overnight and summarise the causes.”

Point this at a development or read-replica connection first. An agent is good at exploratory querying, and exploratory querying belongs somewhere it cannot hurt.

Connecting it

1Create a Burrak account — the free plan is enough to try this.
2Open Connectors and choose Supabase.
3Authorise Burrak in Supabase's own window. Your password never reaches us; we receive a token you can revoke whenever you like.
4Give an agent a task. It will use the connector when the work calls for it.

Start free How connectors work

Supabase and Burrak, in practice

Is it safe to point this at production?: Point it at a development database or a read replica first. Agents are good at exploratory querying, and exploration belongs somewhere it cannot cause harm. Once you trust the pattern, widen it deliberately.
Can it run migrations?: It can draft them, and explain what each one would lock and how long it might take. Running them is a decision we would leave with you — a migration is not a good place for a surprise.
Does it understand my schema without being told?: It reads the schema as part of the work, so you can ask questions in your own vocabulary rather than in column names. Well-named tables make its answers noticeably better.