What is Lovable Cloud?
The part of a Lovable app you do not see: where the data lives. Here is what it is, and the questions to ask before real users depend on it.
In short
Lovable Cloud is the backend built into Lovable: the database, user sign-in, file storage and server-side functions your app needs, created and managed from inside the Lovable editor. It is built on Supabase's open-source foundation and is enabled by default, so most Lovable projects never need a separate Supabase account.
What does Lovable Cloud include?
Lovable Cloud gives a Lovable app a database, authentication, file storage, realtime updates and edge functions for server-side work such as webhooks. It also has scheduled jobs, secrets, logs and a usage view. The database, sign-in and storage are provisioned together, so turning on one switches on all three.
It is on by default. When a feature needs a backend, Lovable enables it automatically or asks first, depending on a workspace permission. Backend usage is paid from the same credit balance as building and hosting.
What can be missing in a Lovable Cloud backend that looks finished?
Because Lovable Cloud sets the backend up for you, it is easy to launch without ever looking at it. But the backend is where the rules that protect your users live: which rows each person may read, which actions need a signed-in user, what the server functions trust. The interface can look finished while those rules are missing.
Since it is built on Supabase, the questions are the Supabase questions: is row-level security enabled on every table, with policies that match who should see what? Which keys are in the browser, and which stay on the server? How are schema changes made, backed up and rolled back?
Lovable Cloud or your own Supabase project?
Lovable Cloud is the managed route: nothing to set up, everything inside the editor. A Supabase project in your own account gives you direct access to its settings, logs, backups and billing, which is what an engineering team usually wants once the app is live. Lovable supports both, and the database is PostgreSQL either way.
Choose early if you can. Lovable's documentation says moving from Lovable Cloud to your own Supabase is manual: export and restore the database, move storage files and code, then set up sign-in, secrets and outside services again. Moving the other way, from Supabase into Lovable Cloud, is not supported yet. Our guide to migrating off Lovable Cloud covers the steps.
What do we check first in a Lovable Cloud project?
We start with the database rules, because in a Supabase-based backend any table in an exposed schema without row-level security can be read and written by any role that holds a grant on it. Then the server functions, then backups. Each check has a yes or no answer.
- Every table: security enabled, and a policy for each operation.
- Every server function: does it check who is calling?
- Backups and restores: tested, not assumed.
What are the common mistakes with Lovable Cloud?
Most mistakes come from trusting defaults nobody read. Lovable runs a quick security scan on every publish that flags tables without per-record access control and rules that let everyone through, but it does not review application code, and Lovable says its tools do not replace a thorough security review.
- Removing the database to start over. Lovable warns this permanently deletes the database, backups, user accounts and stored files.
- Picking a region without thinking. A project cannot move region after the backend is enabled.
- Assuming a remix carries everything across. A remix stays on Lovable Cloud and gets freshly generated keys.
If you are not sure where your project stands, the free production readiness check is a quick first pass.
Common questions
Is Lovable Cloud the same as Supabase?
It is built on Supabase's open-source foundation and managed from Lovable. If you need direct control, Lovable also connects to a Supabase project of your own. Either way the database is PostgreSQL; your own project adds direct access to settings, logs, backups and billing that Lovable Cloud manages for you.
How much does Lovable Cloud cost?
Lovable does not publish a separate backend price list in its Cloud documentation. One credit balance covers building, hosting, the backend and AI features in published apps, and backend and AI usage count toward run credits. The project usage page in Lovable shows what your app is consuming.
Can I move my app off Lovable Cloud?
Yes, but by hand. Lovable's documentation describes exporting and restoring the database, moving storage files and code, and setting up sign-in, secrets and outside services again in your own Supabase project. Moving from Supabase back into Lovable Cloud is not supported yet, so choose deliberately.
Is Lovable Cloud secure enough for real users?
The platform can be, but your app's rules decide it. Lovable scans each publish for tables without access control and over-permissive rules, yet says its tools cannot guarantee complete security. Before real users arrive, confirm row-level security and policies on every table and that server functions check the caller.
Go deeper
How to migrate off Lovable Cloud to your own SupabaseLovable Cloud vs your own Supabase, what the export includes and leaves behind, and a cutover plan that keeps production running.
Related terms
Read next
Sources
- Lovable documentation: Lovable Cloud
- Lovable documentation: Supabase integration
- Lovable documentation: Security
- Supabase documentation: Row Level Security
Sources checked October 24, 2026
More on this: Lovable mastery & prompting · All glossary terms
Built something in Lovable you want people to rely on?
We are the engineers who take it the rest of the way — secured, tested, released and supported.
