Lovable Cloud Explained: Costs, Supabase, and What You Actually Own

Lovable Cloud: The Quick Answer

Lovable Cloud is the backend and hosting that Lovable provisions for your project automatically, so you never set up infrastructure. It is genuinely convenient. It also involves a few decisions that are permanent, and an ownership distinction that its documentation makes precisely but most users never notice.

Quick answer: Lovable Cloud is a managed backend built on Supabase's open-source foundation, giving you a database, authentication, storage, edge functions and AI with no setup. It is billed through your credit balance, which covers building, hosting and AI together, with a separate usage-based layer as traffic grows. The important nuance: Cloud is built with Supabase technology, but it is Lovable's managed instance, not a Supabase account you own. If you want a backend you hold directly, connect your own Supabase project instead. Three things cannot be undone later: the hosting region, removing Cloud, and the fact that Lovable does not support migrating an existing Supabase project into Cloud.

What Lovable Cloud Actually Is

When you ask Lovable for something that needs a backend, logins, saved data, file uploads, it enables Cloud and provisions the infrastructure for you. Per Lovable's documentation, Cloud "utilizes Supabase's open-source foundation, which means you get a production-ready environment from day one, without needing to set up Supabase separately."

Inside a project's Cloud tab you get a database with table editing and SQL, user management and sign-in methods, file storage buckets, edge functions for serverless backend code, scheduled jobs, a secrets store for API keys, built-in AI, branded custom emails, logs, and a usage view. Advanced settings let you resize the instance, export data, and pause or remove Cloud.

For a first product this is a real advantage. Most people building their first app do not want to think about Postgres or auth providers, and Cloud means they do not have to.

Is Lovable Cloud Just Supabase?

Yes on the technology, no on the ownership, and the difference matters more than any feature comparison.

Lovable's own documentation draws the line clearly. It calls Cloud "the built-in backend (Cloud)" as distinct from "an external backend you connect yourself, such as Supabase." Cloud is built on Supabase's open-source foundation and runs as Lovable's managed instance. There is no Supabase account in your name, no Supabase dashboard you log into, no Supabase billing relationship.

Connect your own Supabase project instead and the picture inverts. You create the project, the account is yours, the billing is yours, you get the full Supabase dashboard, and any client can talk to it: your Lovable web app, a server, a native iOS app. Lovable states that existing Supabase projects continue to work and that it will keep supporting them.

So when you read "Lovable Cloud is Supabase," treat it as a statement about the engine, not about the keys.

What Lovable Cloud Costs

Lovable uses one credit balance for three different things: building your app, hosting and running it, and AI features inside your deployed app. That single-pool design is what makes cost hard to reason about, because generating a feature and serving your users compete for the same budget.

Two mechanics decide your real bill. First, expiry. Monthly plan credits expire two months after they are issued, annual plan credits expire one month after the annual period ends, top-up credits last twelve months from purchase, and the free daily build credits expire at the end of each day with no rollover. Credits are perishable, so buying ahead does not bank value.

Second, the usage layer. On paid plans, hosting is billed as usage and is not covered by your subscription. Lovable's position is that small and new apps typically cost nothing because the included grants absorb them, and that apps reaching significant traffic start incurring costs. Read that carefully: the cost arrives exactly when your app succeeds.

Neither is unusual for managed infrastructure. Both are worth modelling before you have users rather than after.

Three Decisions That Are Permanent

These are documented, easy to miss, and hard to reverse.

The region is locked forever. You choose a hosting region when Cloud is enabled, and Lovable's docs are explicit: "After Cloud is enabled, you cannot change the selected region, and you cannot move existing projects between regions." If you pick the region nearest you while your users end up in another continent, the fix is a new project, not a setting.

Removing Cloud destroys it. The remove option "permanently deletes your Cloud instance and cannot be undone," and the docs instruct you to export your database and download your storage files first. There is no undo, no grace period, no snapshot waiting for you.

You cannot migrate an existing Supabase project into Cloud. Per the docs, "At the moment, migration from Supabase to Cloud is not supported." Note the asymmetry this creates: the backend choice you make when a project starts is effectively the one you keep.

None of this makes Cloud a bad product. It makes the enable-Cloud moment a decision worth thinking about for sixty seconds rather than clicking through.

Lovable Cloud vs Your Own Supabase

For a new project, you choose one. Here is the honest split.

Cloud suits you if you want zero setup, a single bill, and no infrastructure to think about, and your project is a prototype, an internal tool, or an early product finding its footing. The convenience is real and the time saved is real.

Your own Supabase suits you if you expect the project to matter. You hold the account and the billing, you get the full Supabase dashboard and its tooling, you control the region, you can back up and migrate on your own terms, and, most importantly for what follows, any client can connect to it, not just your Lovable web app.

The tiebreaker question is simple: if this product works, will you want more than a web app? If the answer is maybe, the portable option costs you an afternoon of setup now and saves you a migration later.

Your Backend Already Fits a Native Mobile App

This is the part almost nobody realises, and it applies whichever backend you chose.

The assumption that stops people from putting their Lovable product on the App Store is that a mobile app means rebuilding everything. It does not. A backend is a backend. Your tables, your users, your auth, your storage, your Stripe integration are all sitting in Postgres, and a native iOS app connects to them the same way your web app does. What actually needs building is the frontend.

That is the lane our product occupies, with a disclosure: Superapp generates native Swift and SwiftUI for iPhone, iPad, Apple Watch and Mac from a plain-English description, runs in the browser so no Mac is needed, and hands you the Xcode project to own. It works with Supabase both ways, a self-hosted Supabase instance or Supabase Cloud, so your backend can live wherever you want it, including a project you hold outright.

You do not have to move your Lovable project to do this. You can add a native mobile app alongside it, pointed at the same backend, so the web app and the iOS app share one source of truth and one set of users. Or you can convert the project and make native the primary experience. Both are normal.

Being straight about the work involved: this is not a one-click import. Superapp uses your existing project as a reference and you rebuild the screens that matter as native ones, usually the three or four that carry the product. What you skip is the backend, which is the larger half of most migrations. Superapp starts free with 5 credits a day, Pro is $25 a month, and Apple charges $99 a year to publish.

For the fuller version of this topic, see can Lovable make mobile apps and our comparison of the best no-code app builders.

Which Setup Should You Choose

If you are prototyping and want to move fast, take Cloud, pick your region deliberately, and get on with building.

If you are building something you expect to still be running in a year, connect your own Supabase project. You will own the data layer, you will keep your options open, and when someone asks for an iPhone app you will already be most of the way there.

If you are already on Cloud and worried you chose wrong, the practical answer is to export your database and storage before you change anything, and to remember that a native mobile app does not require moving your backend at all.

Frequently Asked Questions

What is Lovable Cloud?
Lovable Cloud is Lovable's built-in backend and hosting: database, authentication, storage, edge functions, scheduled jobs, secrets and AI, provisioned automatically when your project needs them, with no infrastructure setup.

Is Lovable Cloud the same as Supabase?
It is built on Supabase's open-source foundation, but it is Lovable's managed instance rather than a Supabase account you own. Lovable's docs distinguish the built-in backend (Cloud) from an external backend you connect yourself, such as Supabase. With Cloud there is no Supabase dashboard or billing relationship in your name.

How much does Lovable Cloud cost?
It draws on the same credit balance as building and AI, and on paid plans hosting is an additional usage-based layer not covered by your subscription. Small apps are usually absorbed by the included grants; costs appear as traffic grows. Credits also expire, monthly credits two months after issue and daily free credits at the end of each day.

Can I use my own Supabase project with Lovable?
Yes. New projects can choose either Lovable Cloud or an external Supabase project, and existing Supabase integrations continue to work. Bringing your own gives you the account, the billing, the dashboard and full portability.

Can I migrate from Supabase to Lovable Cloud?
No. Lovable's documentation states that migration from Supabase to Cloud is not currently supported, and recommends continuing with Supabase if your project is already connected to it.

What happens if I remove Lovable Cloud?
It permanently deletes your Cloud instance and cannot be undone. Export your database and download any storage files first, because there is no recovery afterwards.

Can I change my Lovable Cloud region later?
No. The region is set when Cloud is enabled and cannot be changed, and existing projects cannot be moved between regions. Choose based on where your users are, not where you are.

Can I turn my Lovable project into a mobile app?
Lovable itself builds web apps only, but your backend already works for mobile. A native iOS app can connect to the same Supabase database your web app uses, so only the frontend needs building. Superapp does this in native Swift and supports both self-hosted Supabase and Supabase Cloud, and you can add a native app alongside your existing project rather than replacing it.

---

References

• Lovable Cloud documentation
• Lovable credits and usage and usage and costs
• Lovable Supabase integration docs
• Lovable pricing
• Supabase pricing
• Can Lovable Make Mobile Apps?
• Lovable documentation quoted as published, July 2026