Lovable Cloud or Supabase: which one does your app use?

A Lovable app with logins or saved data has a Supabase backend. Either it is your own Supabase project, or it is Lovable Cloud, which Lovable runs for you on Supabase. The move is different for each, so check first.

vsFind out where your backend runs

Why it matters

Your own Supabase projectLovable Cloud
Who runs itYou, at supabase.comLovable
In your Supabase dashboardYesNo
When you leave LovableIt stays where it isIt moves to a Supabase project you own
Login settingsIn the Supabase dashboardIn Lovable, More, Cloud, Users

Check in Lovable

In your Lovable project open More, Cloud. If it shows screens to manage your database tables and users inside Lovable, it is Lovable Cloud. If it shows the Supabase icon and your Supabase project name, it is your own project.

The Lovable Cloud overview with the database tables, users, storage and secrets

Check in Supabase

Log in at supabase.com and look at your project list. If the project is there, it is yours. Lovable Cloud projects do not show up there.

Check in the code

Open the .env file in the repo. A supabase.co address that you can open in your own Supabase dashboard means it is your own project. Or ask Claude Code, Codex or Cursor:

Look at the .env file and the supabase folder. Tell me if this app uses its own Supabase project or Lovable Cloud, and how you know. Do not print any key.

Can Lovable Cloud stay?

Yes. Cloud can stay where it is while you build in Claude Code, Codex or Cursor, and even while you host the app somewhere else. It only has to move if you leave Lovable or want the backend in your own account.

Sources

  1. Supabase docs: Identifying Lovable backend, Lovable Cloud or Supabase
  2. Lovable docs: Lovable Cloud

Read next

Pick your route.

Choose where you are and where you want to go. The guide takes it from there.