Can’t Access Supabase Project When Using Lovable Cloud

Last edited: 11/4/2025

Problem

Your Lovable project has Lovable Cloud enabled, and you’re trying to connect directly to your Supabase project.

However, you don’t see the project listed on your Supabase Dashboard, or you’re unable to access it through your Supabase account.

Why this occurs

When you create a project connected to Lovable Cloud, the underlying Supabase instance is provisioned and managed entirely by Lovable.

These projects are not owned by your Supabase account, so they don't appear on your Supabase Dashboard or be accessible using your Supabase credentials.

How to diagnose

You might be affected by this if:

  • You recently created a project on Lovable and enabled the backend from the chat interface. By default, the Lovable platform uses Lovable Cloud for backend hosting.
  • You see Supabase references in your project’s configuration but can’t access the project from your Supabase Dashboard.
  • The project ID or credentials used in your Lovable setup don’t match any project under your Supabase account.

How to fix

There is no automated way to transfer a Supabase project from Lovable Cloud to your own Supabase account.

However, you can manually clone your project backend and migrate your data following Lovable’s official guide: Self-Hosting Guide (Lovable Docs)

This process allows you to create a new Supabase project under your own account and connect it independently.

How to prevent

If you want direct access to your Supabase project from the start, make sure to:

  • Avoid enabling Lovable Cloud if you plan to manage your Supabase project independently.
  • Create your project directly from the Supabase Dashboard and then manually connect your Lovable project to your Supabase project, or start your Lovable project already connected to your own Supabase project from the beginning.

Additional resources

For more information, read the Lovable Cloud FAQ

Frequently asked questions