Supabase and Postgres
Let your Supabase users sign in to your app
Trust your Supabase project's accounts, so people who already have one sign in to your Ahamo app without a new password.
Your app can trust your Supabase project's sign-in, so a person signs in with Supabase as before, and the app accepts that sign-in and gives them an account of their own. Nobody needs a new password, and your users stay in Supabase.
When to use it
- You keep Supabase for sign-in and add an Ahamo app next to an existing one.
- You want to move gradually, before or instead of moving accounts into Ahamo.
How to use it
Ask the build AI.
Let people sign in with our Supabase project at https://abcd1234.supabase.co (opens in a new tab).
It adds Supabase sign-in to the app and sets the variable SUPABASE_URL to your project's address in
Secrets & variables. A project that signs its tokens with a shared secret also needs that secret,
which the build AI asks for in a secure input.
Users then says people sign in with your Supabase project, and a person who signs in with Supabase appears there.
Plans and limits
The same on every plan.
| Rule | Value |
|---|---|
| Projects | One per app; a different project gives separate accounts |
| Custom Supabase domain | Must be listed for the app |
| A Supabase token | Used once; tokens valid for more than 24 hours are refused |
Troubleshooting
Sign-in is refused. Check that SUPABASE_URL is your project's address and that the person signed in to that
project. For a custom domain, ask the build AI to add it.
The same person has two accounts. They signed in through two different Supabase projects or addresses. Use one project per app.