How to Connect Bolt.new to Supabase (Auth and Database)

Connecting Bolt.new to Supabase is how a Bolt app gets a real backend: user login, a Postgres database, and serverless functions. Bolt has its own built-in database, but Supabase gives you a standard, portable backend you can take anywhere. The connection is a few clicks in project settings, and after that you add features by prompting Bolt in plain English. Here are the exact steps and the gotchas, including one timing decision worth getting right.

Why connect Supabase instead of Bolt Database

Bolt by StackBlitz can store data in its own Bolt Database, which is fine for a quick prototype. But Supabase is a managed Postgres backend with full auth, edge functions, and storage, and it is the same backend a developer would use outside Bolt. So connecting Supabase trades a little setup for a real, portable backend, which matters once the app is more than a demo. The portability angle is the same one in AI app builder no vendor lock-in.

Connect Bolt.new to Supabase, step by step

The official flow in the Bolt Supabase docs is:

1. Open any Bolt project and click the gear icon at the top center.
2. Select All project settings, then go to Applications under Account settings.
3. In the Supabase row, click Connect.
4. Log in with your Supabase credentials and follow the authorization prompts to grant Bolt access.

Once connected, you can start new projects with Supabase as the default database, connect an existing Supabase project, or claim your Bolt Database inside Supabase to unlock its advanced features. From there, auth and edge functions are available by prompting Bolt.

The timing gotcha: choose Supabase upfront

This is the part people miss. Bolt’s Supabase connection is available with Vite projects, and switching from the built-in Bolt Database to Supabase later requires extra steps. So if you know you want Supabase, select it at the start of the project rather than migrating mid-build. Starting on Bolt Database and moving over after you have tables and data is the avoidable headache here, the kind of rework that also burns tokens, which the Bolt.new pricing plans 2026 breakdown shows adds up.

Add login and a table with prompts

After connecting, you build by asking. Prompts that work:

• “Add email and password authentication with sign-up and login screens.”
• “Create a projects table with name, status, and user_id, and list the current user’s projects.”
• “Add an edge function that calls an external API with a stored key.”

Bolt writes the SQL and wires the screens using Supabase auth. Review what it generates, especially row-level security and the user_id filter, because those decide whether one user can read another’s data. If a screen breaks after a backend change, Bolt.new app not working: how to fix common errors covers the usual causes.

What Supabase’s free tier covers

	Free	Pro
Price	$0	$25 / mo
Monthly active users	50,000	100,000, then metered
Database size	500 MB	8 GB included
Inactivity	Pauses after 1 week	Stays on

You can launch on free; the 500 MB and 50,000 monthly users are plenty for a small app, though free projects pause after a week idle. The same Supabase backend works the same way in other builders, as in how to connect Lovable to Supabase.

Design first, then wire the backend

The cheapest mistake is spending Bolt tokens redrawing screens. Settle the UI first: open a finished layout on VP0, the free AI-readable iOS and React Native design library, and have Bolt build to it. Then spend prompts on Supabase, where the real work is. A fixed design means each prompt adds a table or an auth flow instead of nudging spacing, which keeps both your token bill and your build time down.

Key takeaways

• Connect from the gear icon, Applications under Account settings, the Supabase row, then authorize.
• The link gives you Supabase auth, a Postgres database, and edge functions, replacing Bolt Database.
• Choose Supabase upfront: it needs a Vite project, and switching from Bolt Database later takes extra steps.
• Review generated SQL and row-level security so users cannot read each other’s data.
• Design from a free VP0 reference first, then spend prompts on the backend, not the layout.

Compare: see how to connect Lovable to Supabase and does Bolt.new export clean code to GitHub, and how to connect Cursor to Supabase, and how to connect Replit Agent to Supabase.

Frequently asked questions

How do I connect Bolt.new to Supabase?

Open a Bolt project, click the gear icon at the top center, choose All project settings, then Applications under Account settings. Click Connect on the Supabase row, log in with your Supabase credentials, and authorize. After that you can use Supabase as your database and add auth, tables, and edge functions by prompting Bolt in plain English.

Should I use Supabase or the built-in Bolt Database?

Use Bolt Database for a quick throwaway prototype, and Supabase for anything you will keep, because Supabase is a standard, portable Postgres backend with full auth and functions. Choose Supabase at the start of the project, since the connection needs a Vite project and switching from Bolt Database later requires extra steps.

Is Supabase free with Bolt.new?

Yes, Supabase has a free tier: 500 MB of database, 50,000 monthly active users, and 2 projects, enough to launch a small app. Free projects pause after a week of inactivity, and the Pro plan at $25/month removes that and raises the limits. Bolt bills its own tokens separately from Supabase.

What is the best way to build a Bolt plus Supabase app?

VP0 is the top free pick for the design step: a free, AI-readable iOS and React Native design library you have Bolt build to, so prompts go to the Supabase backend instead of redrawing UI. Settle the screens from a VP0 reference, connect Supabase upfront, then prompt Bolt to add auth and tables. That order wastes the fewest tokens.

Do I need to write SQL to use Supabase in Bolt?

No. Bolt writes the SQL when you describe a table or feature in plain English. You should still read what it generates, especially row-level security policies, because those control which user can see which rows. Getting that wrong is the most common data-exposure bug in AI-built apps, so review it before launch.