Supabase (Native Integration)

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Supabase (Native Integration) working in a real project rather than a sandbox.

   Set up Supabase (Native Integration) in this project — auth, Postgres, storage, edge functions — wired in. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Full-stack SaaS MVPs with login

   The record lists this as one of the jobs Supabase (Native Integration) is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Supabase (Native Integration) for full-stack SaaS MVPs with login. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Supabase (Native Integration) is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Supabase (Native Integration) before I publish. Check auth (email, OAuth, magic link) and postgres with row-level security, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Migrate from Lovable Cloud to managed/self-hosted Supabase

   A second job the record lists for Supabase (Native Integration), useful once the first path works.

   Extend this project so Supabase (Native Integration) also covers migrate from Lovable Cloud to managed/self-hosted Supabase. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Supabase (Native Integration)?

  Supabase (Native Integration) is Lovable's Integrations feature: Auth, Postgres, storage, edge functions — wired in. Native Supabase integration backs Lovable Cloud and supports BYO Supabase projects.

• Is Supabase (Native Integration) GA or in beta?

  Supabase (Native Integration) is generally available (GA) on Lovable.

• What Lovable plan includes Supabase (Native Integration)?

  Supabase (Native Integration) is available on all Lovable plans.

• When did Supabase (Native Integration) launch?

  Supabase (Native Integration) launched on Nov 1, 2024.

• GitHub SyncSame category, also GA · Dec 2024
• Lovable APISame category, also GA · Jan 2025
• Firebase Cloud MessagingSame category, also GA · Oct 2023