Create your account
One account, then one read-only role you create yourself in your own SQL editor. Bouncer only ever sees what that role can see.
Already have an account? Log in
What happens after this
Run one snippet in your own SQL editor
Bouncer writes the SQL and you paste it into Supabase yourself, choosing the new role's password. It builds a view over four columns of your user table and grants SELECT on that view and nothing else:
- id
- created_at
- last_sign_in_at
Paste the connection string back
Bouncer checks the credential really is read-only, turns down anything over-privileged with a specific reason, and encrypts what it stores.
Read the report
How many accounts you have, how many are flagged, which of the four reasons applies to each one, and the SQL to quarantine them when you are ready.
SELECT only. Bouncer cannot create, update or delete a row in your database, and disconnecting destroys the stored credential and every cached account row.