Does Bolt integrate with Supabase?
Partially — built-in, but Vite-only and paid-plan-gated
Partially. Bolt has a built-in Supabase connector, but it is an optional alternative to the default Bolt Database, not native out of the box. It is available only on paid Bolt plans and only for Vite projects, not Next.js. You connect via OAuth and Bolt then generates tables, auth and edge functions in your Supabase project.
| Integration method | Native (built-in connector) — Bolt has a built-in Supabase connector, but Supabase is an optional alternative to the default Bolt Database, not the out-of-the-box backend. You connect your Supabase account via OAuth from the project settings — no middleware (Zapier, Make, MCP) required. |
|---|---|
| Sync direction | Bolt writes tables, auth and edge functions into your Supabase project. Migration is one-way: you can claim a Bolt Database into Supabase, but there is no supported flow for migrating a Supabase database back into a Bolt Database. |
| Plan required | Supabase connections require a paid Bolt plan (the default Bolt Database is free and unlimited). A free-tier Supabase project works on the Supabase side. |
| Setup time | ~10 minutes unverified estimate |
How to connect Bolt to Supabase
- Open your Bolt project and click the gear icon, then "All project settings".
- Go to "Applications" under Account settings and click "Connect" in the Supabase row.
- Sign in to Supabase in the OAuth window and authorize Bolt to access your organization.
- Ask Bolt to add a backend feature (e.g. "add user login"); it provisions the database, auth and edge functions in your connected Supabase project.
- Check the Supabase dashboard if logins fail, since generated row-level security (RLS) policies sometimes need a follow-up prompt or manual SQL fix.
Known friction points
- Auth and RLS policies generated by prompts can throw row-level security errors, so generated logins sometimes fail until the policy is corrected with a follow-up prompt or manual SQL. [source]
- Bolt's docs warn that connecting Supabase to an existing Bolt project may cause data loss, and Supabase connections are limited to Vite projects (Next.js is not supported). [source]
FAQ
- Does Bolt integrate with Supabase?
- Partially. Bolt has a built-in Supabase connector, but Supabase is an optional alternative to the default Bolt Database. It is available only on paid Bolt plans and only for Vite projects. Once connected via OAuth, Bolt can create tables, auth and edge functions in your Supabase project.
- Do I need a paid plan to connect Bolt to Supabase?
- Yes. Bolt's Supabase connection is available on paid Bolt plans only. The default Bolt Database is free and unlimited, but switching to Supabase requires a paid Bolt subscription. A free-tier Supabase project is enough on the Supabase side.
- Do I need Zapier or an MCP server to connect Bolt and Supabase?
- No. The Supabase connector is built into Bolt and uses OAuth — no Zapier, Make or MCP middleware is involved.
✓ Last verified: 2026-06-10 · Every claim on this page links to a primary source. If the integration changed, the page is out of date — check the sources below.
Sources
- Bolt support — Supabase integration (accessed 2026-06-10)
- Supabase GitHub Discussion #33785 (RLS errors) (accessed 2026-06-10)