Skip to main content
Lovable hosts your app and includes a built-in backend (Cloud) with a database, storage, authentication, realtime, and functions. Describe what you want directly in Lovable, and Lovable generates both the frontend and backend, ready to run. Lovable manages the hosting and backend infrastructure for you. App hosting scales with traffic automatically, and you adjust your database’s instance size and storage in Advanced settings as your app grows. The built-in backend utilizes Supabase’s open-source foundation, which means you get a production-ready environment from day one, without needing to set up Supabase separately: a database, real-time updates, user authentication, and storage, with none of the manual setup steps. Across the docs, this is called the built-in backend (Cloud), as opposed to an external backend you connect yourself, such as Supabase.

​
Why use the built-in backend

Three things make it the default choice for most projects:
  • Scales as you grow: App hosting handles traffic changes automatically, and you can increase your database’s instance size and storage when your app needs more.
  • Secure by default: Enterprise-grade authentication, fine-grained access controls, and compliance best practices protect your app and data.
  • Cost-effective: Manage multiple projects in one workspace with credit-based usage. Lovable includes monthly Cloud grants on Free, Pro, and Business plans. For details, see Credits and usage.

​
What’s included

You’ll find the Cloud tools inside any Lovable project by opening the More tab in the project toolbar and selecting Cloud. Each area has its own page with full details, in the order they appear in the Cloud view: Your app’s AI features have their own AI section in the More menu, outside Cloud.

​
Enabling the built-in backend (Cloud)

By default, the built-in backend (Cloud) is enabled for your workspace. When a feature you ask for requires backend functionality (for example, authentication or file storage), Lovable enables Cloud automatically or asks for your approval in the project chat first, depending on the Enable Cloud permission described below. Lovable can’t turn Cloud on from inside a draft. Ask in the main version of your project instead, then continue in the draft once Cloud is on.
On some Enterprise workspaces, the built-in backend (Cloud) is disabled at the workspace level, and projects show “Lovable Cloud has been disabled by your workspace admin”. This setting is not self-serve; contact your Lovable account team to change it.

​
Cloud permissions

Each Cloud tool has three permission options:
  • Always allow: Lovable automatically performs the action, without asking for review or approval. This is the default for most Cloud tools.
  • Ask each time: Lovable asks for your approval whenever the action is needed.
  • Never allow: Lovable blocks the action, informs you that Cloud access is required, and instructs you to enable Cloud.

​
Tool settings and defaults

You can change your Cloud tool preferences anytime: open Connectors, select Cloud, and adjust the settings under Manage my agent’s permissions. You can also change them from Account settings → Preferences → Agent permissions, which lists every connector’s permissions in one place. For how Lovable records changes to your database structure and which changes Execute backward incompatible database migrations controls, see How Lovable changes your database structure.

​
Region selection

Projects can be hosted in three regions:
  • Americas
  • Europe
  • Asia Pacific
You can set a preferred default region for new Cloud projects under Where project data is stored in the same permissions view. If no preferred region is set, Lovable automatically preselects the region closest to your current location, and you can change it before confirming. Choosing a region closer to your users results in:
  • Lower latency
  • Faster database responses
  • Region-based data hosting
  • Better overall backend performance
After Cloud is enabled, you cannot change the selected region, and you cannot move existing projects between regions.
To see which region an existing project is hosted in, go to More → Cloud → Overview → Advanced settings and check the Database location row.

​
Workspace-level default hosting region

On Business and Enterprise workspaces, admins can set a required default region for every new project from Privacy & security (Workspace settings → Security → Privacy & security → Default hosting region). When a default hosting region is set, workspace members cannot choose a different region when creating a project. The setting applies only to new projects. Existing projects keep the region they were created in. Country-specific regions (for example, Germany, Japan, or United States East) can be enabled for Enterprise workspaces on request, subject to available capacity in that region. Contact your Lovable account team to discuss your requirements. See Default hosting region for more information. The default hosting region covers where project data is stored, not where AI model requests are processed. To keep the workspace’s AI model requests in the European Union, Enterprise admins enable EU inference.

​
Tutorial: build a CRM by prompting

This walkthrough builds a real app, a customer relationship manager (CRM), entirely by prompting. Each step introduces one backend capability and shows the kind of prompt that activates it.

​
Step 1: Organize the data (Database)

Tell Lovable what kind of information the tool should keep track of for you. Lovable will automatically create the tables for you, so you don’t need to touch databases yourself.

​
Step 2: Make it secure (Users & Auth)

Add login so data is private and users can sign in easily.

​
Step 3: Handle files (Storage)

You can let users upload and see files right inside the app. Lovable takes care of the storage and linking, so you just describe what files should go where.

​
Step 4: Automate workflows (Edge Functions and Jobs)

Set up automatic actions that save you time. Prompt one automation at a time so each one is set up and tested properly:
Sending emails from your app requires an email domain you own. See Custom emails for setup.

​
Step 5: Connect to other tools (Secrets)

Services like Stripe or Resend give you private API keys. Lovable prompts you to add them securely whenever they’re needed, and only your app can use them. Tools that sign in with an account instead of a key, such as Google services, connect through Connectors.

​
Step 6: Add AI superpowers (AI)

Make the tool act like your assistant.

​
Cloud and AI gateway usage costs

Lovable uses one credit balance for building your app, hosting it and running its built-in backend (Cloud), and AI features in deployed apps. Cloud and AI gateway usage is measured as part of Run credits. See Project usage for the per-project usage breakdown and monthly grants, and Credits and usage for how credits work across your workspace.

​
FAQ

Don’t worry, nothing changes for your existing projects. Your Supabase integration will continue to work exactly as it does today, and we will continue to support it.
  • For existing projects: continue using Supabase with no changes.
  • For new projects: choose either the built-in backend (Cloud) or Supabase.
Yes. If you no longer want a project to use the built-in backend (Cloud), go to More → Cloud → Overview → Advanced settings and use Remove Lovable Cloud.This permanently deletes your Cloud instance and cannot be undone. Export your database and download any storage files you need before continuing.
Yes, Cloud projects can be remixed to Cloud projects only. This creates a copy of your project that you can edit separately in your currently selected workspace. The structure of backend-related data, such as tables and Edge Functions, is copied over without any information. For any automatically generated keys in the original project, Lovable generates fresh keys in the remixed project. Manually added keys are not copied over.Lovable chooses the region for the copy’s backend: the workspace’s default region when one is set, otherwise the region you used last or the one closest to you. The region can’t be changed afterward.Keep in mind that in a remixed Cloud project you can’t revert to versions from before the remix. Versions created after the remix revert normally.
At the moment, migration from Supabase to Cloud is not supported. If your project is already connected to Supabase, we recommend continuing to use it, as we will keep supporting Supabase moving forward.
There is no one-click migration from the built-in backend (Cloud) to your own Supabase project. If you want to move, you export your Cloud data, connect a Supabase project to a new Lovable project, and rebuild the schema there. Remixing a Cloud project produces another Cloud project, so it does not switch the backend for you. See Export Lovable Cloud data and Connect your own Supabase project for the steps.
Yes. You can set a preferred default region for new Cloud projects: open Connectors, select Cloud, and choose a region under Where project data is stored.On Business and Enterprise workspaces, admins can also set a required default region for every new project from Privacy & security (Workspace settings → Security → Privacy & security → Default hosting region). When this workspace-level default is set, members cannot choose a different region when creating a project. See Default hosting region for more information.
If your workspace has a required default hosting region (available on Business and Enterprise), Lovable uses that region automatically and members cannot change it when creating a project.If your workspace does not have a required default hosting region, Lovable automatically preselects the region closest to your current location, but you can change it before confirming.
No. Once Cloud is enabled for a project, the selected region is locked and cannot be changed. Existing projects cannot be moved across regions.
Cloud supports a fixed set of extensions, such as pg_cron for scheduled jobs, pg_net for HTTP requests from the database, vector for embeddings, and postgis for geographic data. Lovable refuses CREATE EXTENSION for any other extension in the project chat, the SQL editor, and the API. Extensions already installed in your database keep working. See Supported PostgreSQL extensions for the full list.