Supabase and Postgres
Use Ahamo with Supabase
Keep your Supabase database, read your existing tables, let your Supabase users sign in, or move the whole project into Ahamo.
On this page
If you already have a Supabase project, you can build on it with Ahamo instead of starting over. Pick what fits. keep your data in Supabase, read the tables you already have, let your existing users sign in, or move everything into Ahamo.
When to use which
| You want to | Use | Plans |
|---|---|---|
| Keep the app's data in your Supabase database | Your own Postgres | Pro and up |
| Show tables you already have, without copying them | External tables | With your own Postgres |
| Let people sign in with their existing Supabase accounts | Supabase sign-in | Every plan |
| Bring rows, accounts and files into Ahamo for good | Move to Ahamo | Every plan |
| Let Ahamo's AI read your project's structure while it builds | The Supabase connector | Where your organisation has it |
How to use it
Each option is a short task in Runtime › Data, except sign-in, which the build AI sets up. For the connector, open Connectors, choose Supabase and connect with your Project ID (Project Settings › General). It reads only tables, extensions, migrations, advisors, logs and the names of Edge Functions.
I have a Supabase project with customers and orders tables. Build an admin app on top of it and keep the data in Supabase.
If you import a repository that uses Supabase
Ahamo reads which Supabase project the code uses and what for, such as its tables, sign-in, files or Edge Functions. If the code queries the project's tables, your app's data moves to Ahamo; keeping your Supabase database instead is offered during the import only when your plan includes your own Postgres, and then its existing tables become read-only in the app. A Supabase library the code never calls doesn't count.
When the import is done, the chat shows one card about the project. Before the app is published, it says Ahamo brings your data over at your first publish; once the app is published, Connect Supabase opens Move from Supabase. Not now is remembered, and the chat doesn't offer it again. If the app only uses Supabase's Edge Functions, there is nothing to bring over, and the summary says so. You can also mention your project, or paste its address, in the chat at any time, and the AI shows the card.
When you first publish an app whose data is still in Supabase, the publish review asks once whether to Publish, then bring my data publishes and then offers Connect Supabase, Publish empty starts the published app without that data. Ahamo doesn't ask again.
Plans and limits
See each task's page. Moving into Ahamo and Supabase sign-in work on every plan; keeping the app's data in your own database is included from Pro.
Troubleshooting
You're not sure which to pick. Keeping your own database suits a team that runs Supabase already and wants to keep doing so. Moving to Ahamo suits a project you want Ahamo to run, with backups and one bill.