# What Is Lovable Cloud? Backend, Pricing & Limits

- Tool: Lovable
- Difficulty: Beginner
- Fix time: ~10 min
- Compatibility: All plans, including Free (20 Cloud credits/month + 4 AI credits/month grant; usage beyond that draws from paid-plan credits).
- Last updated: September 2026

## TL;DR

Lovable Cloud is the built-in backend that comes with every Lovable project: a managed database, authentication, storage, edge functions, and an AI gateway, all provisioned automatically. It is managed Supabase and is not visible in your own Supabase dashboard. Since August 2026, its usage is billed from the same unified credit balance as building and AI features, not a separate dollar amount, with a monthly grant of 20 Cloud credits on every plan.

## Why Lovable Cloud exists and how it changed in 2026

Before Lovable Cloud, adding a real backend to a Lovable project meant manually creating and connecting a separate Supabase project. Lovable Cloud removed that step: every project can get a database, authentication, storage, and edge functions provisioned automatically the moment a prompt needs them, without the builder ever leaving the Lovable editor or creating an external account. The trade-off for that convenience is that Lovable Cloud is managed Supabase and is not visible in your own Supabase dashboard — you give up direct dashboard-level access in exchange for zero setup.

The bigger 2026 change is billing. Lovable Cloud used to be billed as its own dollar-denominated usage, separate from build credits and AI usage. As of August 2026, all three were unified into a single credit balance, so 'how much does Lovable Cloud cost' no longer has a standalone dollar answer — it depends on your plan's credit rate and how much of your usage is Cloud versus build versus AI in a given month. This is convenient for simplicity but means a busy backend can quietly eat into the credits you expected to spend on building new features.

- Lovable Cloud is a Lovable-managed Supabase instance, provisioned automatically and not visible in your own Supabase account
- Since August 2026, Cloud usage is billed from the same unified credit balance as build and AI usage, not a separate dollar amount
- Every plan gets a monthly Cloud credit grant (20 on Free) that resets each cycle and does not roll over
- Because Cloud and build share one pool, high production traffic can deplete credits and pause backend functions unexpectedly

## Before you start

- A Lovable project (Lovable Cloud is available on every plan, including Free)
- Basic familiarity with what a database, auth, and storage backend does, even without prior Supabase experience
- A rough sense of expected traffic if you are evaluating Lovable Cloud for a production launch

## How to fix it

### 1. Understand what Lovable Cloud is, and what it is not

*Confusing it with a personal Supabase account is the most common source of wasted troubleshooting time*

Lovable Cloud is the backend automatically wired into every Lovable project the moment it needs a database, auth, storage, or server-side logic. It runs on Supabase's open-source technology under the hood, but Lovable Cloud is managed Supabase and is not visible in your own Supabase dashboard — there is no separate login, and it will not appear in your existing Supabase account's project list. Everything about it is configured and viewed inside Lovable's own Cloud tab.

**Expected result:** You stop looking for the Lovable Cloud project inside Supabase's own dashboard, since it does not live there.

### 2. Tour the sections inside the Cloud tab

*Knowing where each piece lives saves time once you start building features that need backend support*

Open the Cloud tab in your project. Database shows your tables and lets you browse rows. Users & Auth manages sign-in methods (email/password, OAuth providers) and the user list. Storage handles file uploads, similar to an S3-style bucket. Edge Functions run backend code (Deno-based) for anything that should not happen in the browser, like calling a third-party API with a secret key. AI is a built-in model gateway for chat, image, video, embedding, and transcription features without configuring your own AI provider key. Secrets stores encrypted API keys and environment variables. Logs and Usage let you see what is actually consuming credits.

**Expected result:** You know exactly which Cloud tab section to open for a given task instead of guessing.

### 3. Understand how Lovable Cloud is billed

*The billing model changed materially in August 2026, and older guides describing a separate Cloud dollar balance are now outdated*

Since August 2026, Lovable unified its billing: one credit balance covers building the app, Cloud usage (database, network, storage, compute, realtime), and AI gateway usage, replacing the previous system of separate dollar-denominated balances for Cloud and AI. Every plan, including Free, still gets a monthly grant specifically for Cloud (20 credits) and AI (4 credits) before regular workspace credits are drawn down. On paid plans, once those grants are exhausted, Cloud usage simply consumes from the same pool as your build credits — there is no separate Cloud invoice to track.

**Expected result:** You can read your Usage page in the Cloud tab and understand that Cloud, build, and AI usage all share one number.

### 4. Know the real limits before you rely on Lovable Cloud in production

*The shared credit pool creates a specific production risk that a dedicated database bill would not*

Because Cloud usage draws from the same balance as everything else, a published app under real traffic can deplete a workspace's credits faster than expected, especially during a launch spike. Once credits run out, backend functions — database queries, auth, storage — can pause until more credits are purchased or the next billing cycle grants arrive. This is a meaningfully different risk profile than a traditional dedicated Supabase project, where you would see a usage bill trending up but the database itself would not simply stop responding. Check the Usage page regularly once real users are on the app, and choose a credit tier with real headroom, not just enough for development.

**Expected result:** You have a monitoring habit in place before Lovable Cloud usage becomes a production incident rather than a line item.

### 5. Know your exit path if you outgrow Lovable Cloud

*Because it runs on standard Supabase/PostgreSQL underneath, migrating away is possible without a rewrite*

If a project outgrows Lovable Cloud, dashboard access needs, larger scale, or a desire to decouple the database bill from the build credit bill are the usual triggers, you can connect your own external Supabase project and point new features there, or export the schema and data to a Supabase project you control directly and manage from its own dashboard going forward. There is no proprietary lock-in format to fight through. For teams planning this kind of migration on a live app with real user data, RapidDev's engineers handle Lovable Cloud audits and migrations to dedicated infrastructure as part of standard $13K-$25K engagements, minimizing downtime along the way.

**Expected result:** You know Lovable Cloud is a convenience layer, not a trap — there is a clear, standard-technology path out if you need it.

## Complete code example

File: `cloud-tab-sections.txt`

```text
Cloud tab (inside the Lovable editor)
├── Database        → tables, rows, migrations, RLS policies
├── Users & Auth     → sign-in methods, OAuth providers, user list
├── Storage          → file uploads, buckets, signed URLs
├── Edge Functions   → Deno-based backend logic, Secrets injected at runtime
├── AI               → built-in model gateway (chat, image, video, embeddings, TTS/STT)
├── Secrets          → encrypted API keys and environment variables
├── Logs             → runtime and error logs
└── Usage            → credit consumption across all of the above
```

## Best practices

- Remember Lovable Cloud is managed Supabase and is not visible in your own Supabase dashboard — manage it entirely from the Cloud tab
- Check the Usage page regularly once an app has real users, since Cloud usage shares a credit pool with everything else
- Verify Row Level Security on every table inside Lovable Cloud's Database section — it is not guaranteed automatically for every table
- Choose a credit tier with real headroom before a launch, not just enough to cover development-stage usage
- Connect your own external Supabase project instead of Lovable Cloud if you need direct dashboard access or already have production data elsewhere
- Store every third-party API key in Secrets, never hardcoded, since Lovable Cloud's Edge Functions are the only safe place to use them server-side

## Frequently asked questions

### What is Lovable Cloud?

Lovable Cloud is the built-in backend that ships with every Lovable project: a database, authentication, file storage, edge functions, and an AI gateway, all managed automatically without setting up a separate Supabase account. It runs on Supabase's open-source foundation, but it is a Lovable-managed instance — Lovable Cloud is managed Supabase and is not visible in your own Supabase dashboard.

### Is Lovable Cloud the same as connecting my own Supabase project?

No. Lovable Cloud is provisioned and managed by Lovable automatically; you never see a supabase.com login for it. Connecting your own separate Supabase project is a different, optional path for teams that need direct dashboard access, existing data, or control outside Lovable's Cloud tab.

### How much does Lovable Cloud cost?

As of the August 2026 unified billing change, Lovable Cloud is no longer billed in separate dollars. Its usage (database, storage, network, compute, realtime) draws from the same credit balance as everything else in your workspace. Every plan, including Free, gets a monthly grant of 20 Cloud credits before regular workspace credits are used.

### How much is Lovable Cloud on the Free plan specifically?

Free workspaces get 20 Cloud credits per month plus 4 AI credits per month, alongside the 5 daily build credits (capped at 30/month). These Cloud and AI grants refresh each billing cycle and do not roll over, so unused Cloud credits reset to zero at the start of the next month.

### What's included in Lovable Cloud besides the database?

The Cloud tab is organized into Database, Users & Auth, Storage, Edge Functions, AI, Secrets, Logs, and Usage. Auth covers email/password and OAuth sign-in, Storage handles file uploads, Edge Functions run backend logic (Deno-based), the AI section is a built-in model gateway, Secrets stores your API keys encrypted, and Logs/Usage let you monitor what is consuming credits.

### Can production traffic run out of Lovable Cloud credits?

Yes. Because Cloud usage draws from the same pool as build and AI usage, a published app under real traffic can deplete the workspace's credits, and once depleted, backend functions like the database or auth can pause until more credits are available. Monitoring usage in the Cloud tab and choosing a plan tier with headroom matters more once an app has real users.

### Can I migrate away from Lovable Cloud later?

Yes, since it runs on standard Supabase/PostgreSQL underneath. You can connect your own external Supabase project and prompt Lovable to point new features there, or export the project's code and migrate the schema and data to a Supabase project you control directly. There is no lock-in to a proprietary Lovable-only data format.

### What if I can't fix this myself?

Understanding exactly what is consuming Cloud credits, or migrating a production app off Lovable Cloud without downtime, is a common project for teams scaling past the prototype stage. RapidDev's engineers handle Lovable Cloud audits and migrations as part of standard $13K-$25K engagements.

---

Source: https://www.rapidevelopers.com/lovable-issues/what-is-lovable-cloud
© RapidDev — https://www.rapidevelopers.com/lovable-issues/what-is-lovable-cloud