Supabase

SpinBuild natively supports Postgres. Anyone can import the project's data into Supabase and start using Supabase as the database if they want.

The data that already exists — public tables, functions, and rows — is copied over. After the import, this project uses that Supabase database. You can import back to native Postgres later.

This is the database for the app you are building. It is not login for the people who use that app. For that, see Sign-in for your app.

Stripe, OpenAI, and the other tiles on Connect are still coming soon.

Import into Supabase and use it as the database

You must be the project owner.

1. Open the project.
2. Go to Settings → Database.
3. Choose Supabase.
4. Click Continue with Supabase.
5. Sign in on Supabase's page with the account that should own the database.
6. Allow SpinBuild when it asks.

You never paste a connection string.

SpinBuild then:

• Uses the organization you picked on the authorize page (or a SpinBuild organization if you already have one).
• Creates a new database project in that organization.
• Copies this project's public tables, functions, and rows into it.
• Makes that database the active one for this SpinBuild project.

The first create can take a minute while Supabase starts the project. Stay on the settings page until it finishes.

What you pay

Supabase usage is billed to your Supabase account: their free tier, or a paid plan if you add one there. SpinBuild does not put this database on our bill.

After it is connected

• Settings → Database shows the tables and functions in that Supabase database only.
• Chat still talks to Postgres through DATABASE_URL. New tables from prompts are created in the active database.
• Preview and the live app at your-app.apps.spinbuild.ai share that same database.
• You can open the same project in the Supabase dashboard under the organization you authorized.

Switching back to PostgreSQL copies the public tables, functions, and rows onto SpinBuild Postgres again. Only one database is active. Switching never starts empty.

What this does not do

• It does not add Supabase Auth, Storage, or Edge Functions to the app.
• It does not change how visitors sign in to your app. Ask in chat for email/password or Google, GitHub, and LinkedIn — see Sign-in for your app.
• It does not give the app a custom domain.
• It does not two-way sync GitHub.

If something goes wrong

You cancelled the sign-in page. Click Continue with Supabase again and finish the prompt.

The page said it expired. The sign-in link lasts a short time. Start again from Database settings.

Supabase did not allow an organization. Pick an organization you own on the authorize page, then try again.

It is still on SpinBuild Postgres. The switch is not done until settings shows Supabase as the active database. Wait for the import to finish, then refresh the page.

The rest of how tables, SQL, and browsing work is in Database.