← All field notes

Lovable Cloud vs. Supabase: Should You Move the Backend?

Compare Lovable Cloud with a Supabase project you control. See what changes for data, logins, files, billing and the work of moving a live app.

Nov 22, 2026 · 5 min read


Field Notes from Thunkle, a studio that takes AI-built apps from prototype to secure, production-ready software.

Keep Lovable Cloud if it meets your needs and you want one place to build and run the app. Choose a Supabase project your business controls when you need direct control over the backend and someone on your team can take responsibility for it. If customers already use the app, the decision is also about what it will take to move their accounts, records and files.

Lovable Cloud is Lovable's built-in backend. It includes a database, authentication, storage and server-side functions. It uses Supabase's open-source foundation, but a Lovable-managed backend is not the same thing as a hosted Supabase project in your own organisation. The important difference is who administers the project and which controls you can use, not which name appears in the code. Lovable's built-in backend documentation describes the managed setup.

Compare the choice you actually have

Stick with Lovable Cloud if you're testing a new workflow, the controls are enough for your team, and keeping backend operation alongside the builder saves time. Moving because someone says a “real” app needs separate infrastructure is a bad reason. It gives you a transition to manage and might fix nothing.

Use managed Supabase in your own organisation if you want to grant backend access directly, keep its billing and project lifecycle under your business account, or need a particular Supabase feature or recovery arrangement available on your plan. Your team takes on configuration, releases, billing oversight and the job of checking that recovery works. Supabase still operates the managed infrastructure. Check the plan, region and project features you need before deciding; a different dashboard is not a guarantee of a lower bill or a safer app.

Self-host Supabase only for a requirement managed hosting cannot meet. It gives you more control over where and how the stack runs and makes you responsible for updates, monitoring and backups. Budget for those jobs and check which managed-platform features aren't included. There is a real difference between owning a cloud account and having a team that can keep the service healthy. Supabase's self-hosting guide sets out those responsibilities.

You may not need to move the backend at all

  • You want developers to work in GitHub or another editor: change the development workflow. You may not need to change the running app.
  • You need a different frontend host or deployment pipeline: move the frontend and keep the backend, if the project supports that combination. Verify the new host's sign-in redirects, configuration and frontend-to-backend calls on a preview.
  • You already use a Supabase project your company controls: check its owner and what is connected. Leaving Lovable's editor or frontend hosting does not automatically mean moving Supabase.
  • You need direct backend administration: scope the backend move. You can keep the interface and may be able to keep Lovable in your workflow. Verify the supported setup for your actual project before promising that nothing else changes.

Lovable documents separate choices for code, frontend hosting and backend. Check the app rather than reasoning from its builder: two Lovable projects that look identical can have different backends.

What a backend quote should cover beyond the database

Start with an inventory. A quote that says “migrate Supabase” without listing what's included doesn't tell you whether customers will be able to use the app the next morning.

  1. Customer sign-in. Identify which sign-in methods exist, what can be carried over, and whether existing sessions or credentials will need special handling. Check which customer ID owns each workspace or order. An imported profile isn't proof that the same customer can sign in and see their own data.
  2. Records and files. Look at the relationships that matter to the product. Confirm which records and objects you can export and map the file references. Supabase's database backup documentation explains that a database backup does not include the files managed by its Storage API. Plan how those objects move and test private file access at the destination.
  3. Functions and jobs. List what runs when nobody has the app open: subscription updates, scheduled notifications, imports and outbound webhooks. Assign exactly one environment to live work during cutover. Record which external services must be reconnected, without putting any credentials in the brief.
  4. Access rules and recovery. Agree which roles can access which records. Rehearse an allowed and a denied case in a test environment with synthetic accounts. Also agree who can pause the switch, what happens to new writes if you need to go back, and what a restore actually brings back.

The best acceptance check is a complete customer journey. In a rehearsal, take a test customer from sign-in to an existing workspace, open a migrated file and exercise one important backend action. Run the same journey again on the agreed target before you switch traffic. A green deployment and matching table counts are useful, but neither proves the customer journey works.

Make the decision in one sentence

Write down: “We need to change this part because the current setup can't meet this requirement, and we'll know it's done when this check passes.” If the requirement is only faster frontend releases, don't move customer data. If the requirement is backend control and a tested recovery process, scope the backend work before choosing a host.

If you have live users and aren't sure what the move involves, see Thunkle's Lovable migration service. We can review the repository and the running setup, tell you what can stay, and quote the work around explicit acceptance checks. If the issue is app security rather than ownership, start with a Supabase security review instead of assuming a change of host will fix it.

Find out what actually needs to move.

Share where your app runs and what the current setup can't do. Thunkle can review the dependencies and scope a backend-only move or a full migration.