close
Skip to main content
Lovable Cloud is a full-stack cloud platform that takes care of every part of your application — from the frontend your users see, to the backend that powers it behind the scenes. All you do is describe what you want directly in Lovable, and Lovable automatically generates both the frontend and backend, ready to run in the Cloud. Instead of managing hardware or complex infrastructure, you get on-demand access to hosting, compute, and storage that scale automatically as your app grows. Lovable 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. You have the power of a production-ready database, real-time updates, user auth, and storage — with none of the manual setup steps.

​
Why choose Lovable Cloud

  • Scales as you grow: From your first prototype to millions of users, Lovable scales seamlessly with your needs.
  • 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.

​
Enabling Lovable Cloud

By default, Lovable Cloud is enabled for your workspace. You can manage Lovable Cloud behavior for your projects in Connectors → App connectors → Lovable Cloud → Manage permissions

​
Region selection

Lovable Cloud projects can be hosted in three different regions:
  • Americas
  • Europe
  • Asia Pacific
You can set a preferred default region for hosting new Cloud projects in Connectors → App connectors → Lovable Cloud → Manage permissions If no preferred region is set, Lovable automatically selects the region closest to your current location. See Configuring Lovable Cloud tools for more information. 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.

​
Permission preferences

The default setting for Cloud integration is Always allow, meaning Lovable automatically performs the action, without asking for review or approval. You can change your preference anytime from Connectors → App connectors → Lovable Cloud → Manage permissions Lovable prompts you when a feature requires backend functionality (for example, authentication or file storage). You have three options:
  • Allow: enable the integration for the current project.
  • Deny: decline the integration for this request (you may be asked again later).
  • Adjust preferences: change the default behavior for future projects (does not affect the current project).

​
Configuring Lovable Cloud tools

Cloud tools have three permission options:
  • Always allow: Lovable automatically performs the action, without asking for review or approval.
  • 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.
You can change your Cloud tool preferences anytime from Connectors → App connectors → Lovable Cloud → Manage permissions

​
Tool settings and defaults

SettingDescriptionDefault behavior
Enable CloudCreate and connect a Cloud project to add backend features (database, auth, storage). Required to use Cloud tools.Always allow
Cloud regionSelect the default region (Closest to me, Americas, Europe, or Asia Pacific) for new Cloud projects. If Cloud is auto-enabled using Always allow, this region will be used automatically.Region closest to your location
Read databaseAllow Lovable to read your database.Always allow
Read analyticsQuery logs to investigate issues and behavior.Always allow
Run security checksRun automated security checks on your database. Not a full audit.Always allow
Modify databaseMake schema and policy changes via SQL migrations. Updates generated types.Always allow
Add dataAdd data to your database tables.Always allow
Read project infoRead project configuration and environment details.Always allow
Configure authAllow Lovable to configure authentication settings (for example, signup policies).Always allow
Read backend logsRead logs from backend services.Always allow

​
Lovable Cloud features

You’ll find the Cloud tab inside any Lovable project by clicking the + button next to Preview mode. Lovable Cloud icon The following features and settings live inside the Cloud tab:

​
Database

  • Generate schemas automatically: describe the data you need in plain language, and Lovable creates the tables and schema for you.
  • Manage without SQL: view, edit, and organize records directly in the UI. Update values, inspect tables, and keep your app’s data in sync without writing queries.
Backup and restore Lovable Cloud takes a daily backup of your project’s database. You can browse and restore them from Cloud tab → Database → Backups. Up to roughly 14 days of backups are retained. Each entry shows the snapshot timestamp in UTC (for example, 18 May 2026, 04:27:12 UTC). Click Restore to this backup on any backup row and confirm in the dialog. Lovable rolls the database back to that point, schema and data, and the project’s database is unavailable for a few minutes while the restore runs.
Restoring is permanent. Any data created or changed after the chosen backup is lost. Because the schema is also reverted, your app may no longer match the database if it changed after the backup.When the restore finishes, ask Lovable in chat to test your app and patch any schema mismatches.
Restoring is available to anyone with edit access to the project. On Enterprise plans, every restore is recorded in your workspace audit log.

​
Users & Auth

  • User management: view user accounts, track activity, and manage access control.
  • Built-in authentication: Lovable can generate signup/login pages for your app. Supports email, phone, and Google sign-in.
    • Google authentication: Lovable Cloud supports Sign in with Google using OAuth 2.0. Google authentication can be enabled in Managed mode (Lovable-managed OAuth) or using your own Google Cloud credentials (BYOK). See Add Google authentication to Lovable Cloud apps for detailed information.
  • Secure by default: authentication is backed by Lovable Cloud, keeping user credentials safe.

​
Storage

  • File handling without code: upload, manage, and serve files such as profile photos, documents, videos, or static assets.
  • Storage buckets: files are stored securely in a project bucket, with URLs or references you can use in your app. Storage buckets are private by default, but can be made public if needed.
Public storage buckets are blocked by default on all plansThis prevents users from creating publicly accessible storage buckets in Lovable Cloud. Workspace owners and admins on all plans can disable this in Settings → Privacy & security → Block public storage buckets.
  • Limits: Supports files up to 2 GB.

​
Edge Functions

  • Serverless logic: run custom code for APIs, workflows, or advanced features, without provisioning servers. Functions scale automatically with traffic.
Common use cases:
  • AI-powered features, such as AI summaries or AI chatbots. Use built-in Lovable AI.
  • Sending emails or push notifications
  • Payment processing, for example with Stripe
  • Scheduled tasks
  • Heavy computations or external API calls
Other highlights:
  • Easy to create: just describe the function you need in Lovable chat.
  • Debugging built-in: each function includes logs of executions, output, and errors. If something fails, Lovable surfaces the error for quick troubleshooting.

​
AI

  • Built in AI functionality: Lovable Cloud comes with built in AI so you can quickly create features that make your app smarter and more engaging. For more information, see Lovable AI.
  • Some examples of AI powered features include:
    • AI summaries – automatically condense long text into clear takeaways
    • AI chatbot or agent – build conversational helpers into your app
    • Sentiment detection – understand user feedback at scale
  • You can monitor Lovable AI usage and performance for your project from the AI overview.

​
Secrets

  • Secure environment variables: store sensitive data such as API keys, tokens, or credentials without exposing them in code.
  • Automatic detection: when a feature needs a secret, Lovable prompts you to input it through a secure UI.
  • Encrypted and safe: secrets are stored securely and automatically injected into Edge Functions or other integrations.
Example: Store your Stripe Secret Key once, and Lovable ensures it’s included in payment-processing functions without you hard-coding it.
Some secrets, such as the Supabase keys and Lovable API key, are added automatically and are required for the functioning of the Lovable platform. These keys cannot be deleted.

​
Secrets vs. VITE_ environment variables

Lovable’s Secrets manager is for backend values only: values used by Edge Functions and server-side integrations. Anything prefixed with VITE_ is a build-time, browser-exposed value and must live in your project’s .env file instead, not in Secrets.
  • Backend secrets (use Secrets): STRIPE_SECRET_KEY, RESEND_API_KEY, OPENAI_API_KEY, third-party service credentials, and anything that must never reach the browser.
  • Frontend variables (use .env): anything prefixed with VITE_, such as VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY. These are embedded into the client bundle at build time and are safe to be public. You can find and edit them in the .env file in Lovable’s code editor or in your synced GitHub repository.
Do not add .env to .gitignore in a Lovable project. Lovable needs .env committed to the repository so build-time VITE_* values are available when generating previews and published builds. Gitignoring it will break the preview.
If you try to add a VITE_-prefixed name in Secrets, Lovable rejects it with a message like “VITE_ prefixed variables are build-time browser values and should be defined in .env files, not in secrets.”

​
Reserved secret name prefixes

The following name prefixes are managed automatically by Lovable Cloud and cannot be created or overwritten in the Secrets UI:
  • SUPABASE_: for example SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, SUPABASE_DB_URL. These are populated by Lovable when Cloud (or a connected Supabase project) is enabled.
  • LOVABLE_: reserved for Lovable-managed values such as the Lovable API key used by built-in AI. You can rotate LOVABLE_API_KEY from the Secrets UI if you suspect it has been exposed; Lovable issues a new key and updates the value in your Edge Function environment automatically.
If you see an error like “Secret name uses the reserved prefix SUPABASE_ and cannot be created”, you don’t need to add it manually. It already exists in your Edge Function environment and you can reference it directly from your function code (for example, Deno.env.get("SUPABASE_SERVICE_ROLE_KEY")). If you’re using an external Supabase project rather than Lovable Cloud, manage the connection from Project settings → Integrations → Supabase instead of the Secrets section; Lovable updates the reserved SUPABASE_* values for you when you connect.

​
Logs

  • Real-time monitoring: watch app activity as it happens.
  • Debug and trace issues: identify errors, track events, and ensure your backend is healthy.

​
Usage

The Usage tab gives you a visual breakdown of how your app is consuming Lovable Cloud resources over a selected time period. The time period defaults to Last 7 days. You can switch to Last day from the dropdown to adjust the period shown. Cloud usage updates daily at 10 AM CET. Usage is broken down across resource categories, displayed as a segmented bar and listed individually with a percentage:
  • Database server: used when your app queries or updates data. Adjust your instance size to match your app’s traffic. Larger instances provide more capacity but increase Cloud costs.
  • Database storage: the disk space used by your database to store your app’s data (like users, orders, and settings).
  • Compute: used when your app’s code runs.
  • Storage: used to store files like images, videos, and uploads.
  • Live updates: used to send real-time updates to users (for example, notifications or chat).
  • Network: used when your app sends or receives data over the internet.
Categories are sorted from highest to lowest. The percentage next to each category shows its share of your total Cloud costs for the selected period. For example, if Compute shows 29%, then 29% of your Cloud spend during that time came from compute usage.

​
Database health check

Get an on-demand snapshot of your Cloud database, including connections, memory, disk usage, uptime, and more, directly from Lovable chat. Prompt Lovable in chat with something like: 
Run a health check on my Cloud database.
Lovable returns a summary of your database’s current status so you can quickly spot issues such as high connection counts, low disk space, or memory pressure before they impact your app.

​
Find and fix database performance problems

Lovable can pinpoint the slowest queries in your database and use that data to optimize performance, so you can fix real bottlenecks before considering a larger instance. Prompt Lovable in chat with something like: 
My app feels slow. Find the slowest database queries and optimize the worst ones.
Lovable reads your database’s query statistics and ranks the heaviest queries by total execution time, with call counts and timing data for each. It then investigates the worst offenders, inspects their query plans, and applies targeted optimizations, such as adding an index, where they help. A few things to know:
  • Query statistics build up as your app handles real traffic. A brand new or recently restarted database may have nothing to report yet.
  • Finding slow queries is read-only. Lovable only changes your database when it applies a fix, and it tells you what it changed.

​
Advanced settings - Upgrade instance

Use the advanced settings to view and manage your current instance size. A larger instance allows your app to handle more users and traffic. Keep in mind that a larger instance can increase Cloud usage and use more credits as your app usage grows.
  • Free plan users: upgrade from Tiny to a larger instance by upgrading your plan at anytime
  • Paid plan users: choose a new instance size from the options below:
    • Tiny: great for trying things out
    • Mini: reliable for early projects
    • Small: room to grow with your app
    • Medium: steady choice for regular use
    • Large: confident option for higher demand
Lovable alerts you when approaching your Lovable Cloud resource limits. This lets you upgrade your instance in a timely manner to ensure fast and reliable performance. The alert is triggered when any of the following happens:
  • There is less than 10% of disk space left
  • IO budget is less than 50%
  • CPU load is above 80%
The upgrade alert also includes a detailed breakdown of usage (disk space, disk IO, CPU). Alert notification showing Cloud instance resource limits with disk space, IO budget, and CPU usage breakdown, prompting user to upgrade instance size

​
Example flow - Prompting Lovable to build a CRM tool

Build me a CRM tool to manage clients, track deals, handle invoices, and keep notes organized. Keep the design simple, modern, and business-friendly with a sidebar for navigation.

​
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. I want a place to keep track of my clients with their name, email, phone number, and notes. I also need a way to track deals, including which client it’s for, the value, the stage it’s in, and when I expect it to close. And I need a section for invoices with the client it belongs to, the amount, the status, and the due date.

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

Add login so data is private and users can sign in easily. Add login to the app. Require login before accessing the CRM dashboard. Also, add a ‘Sign in with Google’ button so users can log in with their Google accounts.

​
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. Add a contract upload field to each deal. Let clients have profile pictures and display them on the client detail page. Upload invoice PDFs and show a download link on the invoices table.

​
Step 4: Automate workflows (Edge Functions)

Set up automatic actions that save you time. When a new lead is added to the Clients table, send me an email notification. Analyze client meeting notes with Lovable AI and save a sentiment score in the Clients table. Sync new contacts automatically. Schedule a daily job at 7 AM that emails me a summary of today’s follow-ups. When a payment is marked ‘paid’ in Stripe, automatically update the related invoice’s status to ‘Paid’.

​
Step 5: Connect to other tools (Secrets)

When you use services like Stripe or Google Calendar, they’ll give you private “keys.”
Lovable will prompt you to add them securely whenever they’re needed, and only your app can use them.

​
Step 6: Add AI superpowers (AI)

Make the tool act like your assistant. Summarize each client’s meeting notes and save them to their profile. Suggest next steps for every open deal. Generate personalized email drafts for following up with leads. Classify client messages into categories: sales, support, or billing.

​
Cloud and AI gateway usage costs

Lovable now uses one credit balance for building your app, hosting and running it with Lovable Cloud, and AI features in deployed apps. Cloud and AI gateway usage is measured as part of Run credits. Cloud usage is based on the Lovable Cloud infrastructure resources your deployed app consumes, and AI gateway usage is based on the model calls made by AI features inside your deployed app.
Temporary offering, subject to change: Free, Pro, and Business workspaces receive a 20-credit monthly Cloud grant for Lovable Cloud usage. Free workspaces also receive a 4-credit monthly AI grant for AI gateway usage in deployed apps.On Free plans, monthly Cloud and AI grants reset on the 1st of each calendar month at 00:00 UTC and do not roll over. On Pro and Business plans, the monthly Cloud grant refreshes with the subscription billing cycle and does not roll over.
For details about Cloud and AI gateway usage costs, monthly Cloud and AI grants, top-ups, auto top-up, alerts, and usage tracking, see Credits and usage.

​
FAQ

Yes. Lovable now uses one credit balance for building your app, hosting and running it with Lovable Cloud, and AI features in deployed apps.Cloud and AI gateway usage are shown as Run credits in Settings → Plans & credit usage → Usage details.
  • Cloud usage covers Lovable Cloud infrastructure resources used by deployed apps, such as database, network, storage, Edge Functions, and Realtime.
  • AI gateway usage covers AI features inside deployed apps, such as model calls made by your app.
For more information, see Credits and usage.
Yes. Lovable gives you several ways to control credit usage and top-up charges.
  • Add credits manually: On Pro and Business plans, workspace owners and admins can buy one-time top-ups when more credits are needed.
  • Use auto top-up: On Pro and Business plans, workspace owners and admins can enable auto top-up so Lovable automatically adds credits when the workspace balance reaches or falls below a threshold you set. You can also set a monthly spend limit to control how many credits auto top-up can add in a calendar month.
To manage credits, top-ups, and auto top-up, go to Settings → Plans & credit usage. For more information, see Credits and usage.
AI gateway usage rates are based on the underlying provider model costs. AI gateway usage is charged in credits based on the model used and the number of tokens processed.  To estimate relative model costs, refer to the official provider pricing sources linked from the supported model list.
Go to Settings → Plans & credit usage → Usage details.You can filter by project across All credits, Build credits, and Run credits. Use Run credits to review Cloud and AI gateway usage by project.For more information, see Tracking credit usage.
This can happen if you have too much data running on a smaller Cloud project instance.To fix it, go to Cloud tab → Overview → Advanced settings, then choose a larger instance size. After you switch to a larger instance, give it a few minutes to update. Your data should then load, and your Cloud project should work again.A larger instance size can increase Cloud usage and use more credits. To review Cloud usage, go to Settings → Plans & credit usage → Usage details and select Run credits.
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 Lovable Cloud or Supabase.
No, when you connect your project to Cloud, you can’t revert that change or disconnect your project from the Cloud.
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.When remixing, you can select which region to host the new project’s backend (Americas, Europe, or Asia Pacific). Lovable preselects the region closest to you based on your location. Once selected, the region cannot be changed for that project.Keep in mind that you can’t revert to a previous version of your app in the remixed project if the project is using Lovable backend. For frontend-only projects hosted in the Cloud, reverts are possible.
This is technically possible since you own the code in GitHub, but not straightforward. We are looking into making this easier. For more information, see Self-hosting: Run your Lovable Cloud project anywhere.
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.
No. Once Cloud is enabled for a project, the selected region is locked and cannot be changed. Existing projects cannot be moved across regions.
Lovable automatically preselects the region closest to your current location, but you can change it before confirming.
Yes. You can set a preferred default region for new Cloud projects in Connectors → App connectors → Lovable Cloud → Manage permissions.