# Ray and Supabase

> Project health, migrations, and schema, answered in the thread.

Source: https://heyray.io/integrations/supabase

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 leave it for you. 17 reads run without asking. Writing to Supabase is not switched on yet.

## What Ray reads in Supabase

Reading changes nothing, so Ray never stops to ask whether it may look something up.

- Projects, branches, and their service health
- Migration history, tables, and function definitions
- Backups and project logs

## What Ray writes

Ray reads Supabase and answers from it in the thread. Writing to Supabase is not switched on yet, so there is nothing to approve.

## 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.

- Run SQL against your database
- Create or delete a project, branch, or function
- Touch API keys, secrets, or auth integrations

## Ask it like this

- "@Ray is the staging project healthy, and what migration ran last?"
- "@Ray what does the orders table look like now?"
- "@Ray show me the errors in the project logs from the last hour."
- "@Ray which edge functions are deployed, and when did they last change?"

## Connecting Supabase

Every person on the team connects their own Supabase account on Supabase's own login screen, so Ray can only reach what that person can already reach, and the history in Supabase shows who actually asked. Passwords never pass through Ray. Disconnecting Supabase or uninstalling Ray revokes the connection.

## More

- This page for people: https://heyray.io/integrations/supabase
- Every integration: https://heyray.io/integrations.md
- Install Ray: https://heyray.io/install.md
- Pricing: https://heyray.io/pricing.md