Supabase, without opening Supabase.
Read-only project health, migrations and schema.
In your channel
Ask Ray for something in Supabase and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in Supabase
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Supabase
- List all organizations
- Get organization
- List all projects
- Get project
- Gets project s service health status
- Get project readonly mode status
- Get project upgrade status
- List branches
- Get branch
- List migration history
- Get migration
- List functions
- Get function
- List backups
- List tables
- Get table schemas
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What Ray answers with
Ray reads Supabase and answers from it in the thread. Writing to Supabase is not switched on yet, so there is nothing here to approve.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete all branches
- Disable preview branching
- Run read only query
- Create bulk secrets
- Delete custom hostname config
How Ray works with Supabase
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Supabase
One click, right where you asked. Ray posts a connect card, you authorise Supabase with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Ray answers where you asked
Ray only reads Supabase, so there is nothing here to approve. It looks up what it needs and replies in the thread.
Priya
@Ray the checkout bug is back. Take a look in Supabase, and tell Dana it is being looked at.
Ray
Checked Supabase. The spec was last edited on Tuesday and the open question about refunds is still unanswered.
What does connecting Supabase to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Supabase and it can do the Supabase part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Supabase account, so Ray can only reach what that person can already reach, and the history in Supabase shows who actually asked.
Security and permissions
- You authorise Supabase on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Supabase in a message, or uninstall Ray and every connection it held is revoked.
More dev & deploys integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Supabase.
Free to start, no credit card, and it asks before it acts.