⚡ TL;DR Link a Supabase organization, then connect one Supabase project per Lovable project. Lovable manages schemas, migrations and functions; Supabase bills usage.
Already on Supabase? Keep it, and let Lovable build on it.
🔌 What It Does
Makes your own Supabase project the backend: Lovable designs schemas, runs reviewed migrations, deploys edge functions and wires up database, auth, storage, realtime and secrets.
⚙️ Setting It Up
An owner or admin links a Supabase organization under Connectors. Then go to Settings, General, External Supabase, Connect, pick a project and confirm under More, Supabase.
💡 What You Can Build
A few ideas:
- ✅ Teams already on Supabase
- ✅ Apps needing direct Supabase dashboard control
- ✅ One database shared by several apps
- ✅ Custom Supabase plans
⚠️ Limits
One Supabase project per Lovable project, no automatic data migration, and some features (managed backups, managed Google auth, signed-in browser testing) need the built-in backend.
💡 Pro tip Stick with the built-in backend unless you specifically need Supabase dashboard control.
Need a Supabase backend set up? Lord of the Wix can help. ✨
❓ Lovable Supabase integration FAQ
Do I need Supabase?
No, the built-in backend is the default.
Who bills Supabase usage?
Supabase.
Does disconnecting delete data?
No.
How many Supabase projects per app?
One.
Can Lovable migrate data automatically?
No.
🙏 Credit: Based on public information from the Lovable documentation. Lovable is a product of Lovable. Source: docs.lovable.dev. Lord of the Wix is an independent agency and is not affiliated with Lovable.