Supabase
Supabase is on the roadmap. Agents will run read-only SQL against your Postgres, inspect table schemas, list storage objects and answer questions about your data — while writes, migrations and any DDL stay destructive-tier and need explicit human approval.
What your agents can do with Supabase
- Run read-only SQL against Postgres
- Inspect table schemas and relationships
- Insert or update rows (with approval)
- List and read storage objects
How to connect Supabase to Velaris
- 1
Get early access
Join the waitlist — we open access in waves.
- 2
Request Supabase
Vote for the Supabase connector in the community.
- 3
Get notified
We'll ping you the moment Supabase goes live.
Popular ways to use it
Supabase + Velaris — common questions
Can an agent write to my Supabase database?
Reads run automatically. Any insert, update, delete or migration is staged as a destructive-tier action, shown to you as the exact SQL, and runs only once you approve it.
Does Velaris respect my row level security policies?
Yes — connect with a key scoped to the role you want agents to have, and RLS applies to agent queries exactly as it would to any other client.
Should I connect with the service role key?
Only if you truly need it. A restricted role keeps agents inside RLS and is the safer default; the service role bypasses those policies for everything the agent touches.