Lovable Cloud vs Supabase vs Your Own Backend (2026)
Lovable Cloud is the backend Lovable hosts for you: a database, auth, storage and functions built on Supabase's open-source stack, billed from your Lovable credits and managed from the Lovable editor. Connecting your own Supabase project instead gives you the Supabase dashboard, direct database access and a separate Supabase bill. A third route, any backend that speaks the same APIs, gives you the same code with a different host and price. Pick Lovable Cloud for speed, your own Supabase for control inside Lovable, and your own backend when the app has outgrown the builder.
All facts about Lovable and Supabase below come from their own docs and pricing pages, as of November 2026.
#The three options in one table
| Lovable Cloud | Your own Supabase project | Your own backend (e.g. StitchDB) | |
|---|---|---|---|
| Who runs it | Lovable | Supabase, in your Supabase org | The host you choose |
| Built on | Supabase's open-source foundation | Supabase | Same APIs as the Supabase stack |
| Billing | Lovable credits (20 Cloud credits/month grant) | Supabase plan (Free, or Pro from $25/mo) | Host's plan (StitchDB Pro $15.99/mo) |
| Where you manage it | Lovable editor | Supabase dashboard | Host's dashboard and CLI |
| Direct Postgres access | Exports and the in-editor views | Yes | Yes |
| Lovable editor features | All | Most; some need the built-in backend | Lovable can edit the code; backend features in the editor do not apply |
| Moving later | Manual export and restore | Standard Postgres tools | Standard Postgres tools |
#Lovable Cloud: what you get
Lovable's docs describe Cloud as a built-in backend with a database, user authentication, file storage, edge functions, scheduled jobs, secrets, logs and usage tracking. It is the default for new projects. Lovable manages backups, instance size and pausing for you.
Pricing. Lovable uses one credit balance for building, hosting, running the backend and the AI features inside your app. As of November 2026, Free, Pro and Business each get a monthly Cloud grant of 20 credits, plus 5 daily build credits (capped at 30 a month on Free). Cloud charges depend on what your deployed app uses: database instance size and active time, database storage, network, file storage, compute and realtime. Usage draws from the Cloud grant first, then from your general credits. Lovable's pricing page says most small or new apps cost nothing to host because the grant covers them, and that apps with significant traffic or size use more. It does not publish a per-unit rate, so you learn the real cost from the project usage page as you grow.
Features that only work on Cloud. Lovable's Supabase integration page lists features that need the built-in backend: the in-editor Database, Users and Storage views, managed Google auth, SAML SSO, signed-in browser testing and sensitive data scanning. App connectors and AI features in your app also run through Lovable.
Good fit when: you are prototyping, you want one bill, and you will rarely touch the database outside the editor.
#Your own Supabase project: what changes
With the Supabase integration, a workspace owner links a Supabase organization once, and any project can then connect to a Supabase project in that organization. Lovable still designs the schema, runs migrations (you approve them first), deploys edge functions and wires up the UI. Migration files are saved in your code under supabase/migrations/. Disconnecting changes neither your code nor your Supabase project.
You manage the database in the Supabase dashboard, and Supabase bills you directly. As of November 2026:
- Free: 2 active projects, 500 MB database, 50,000 MAU, 1 GB files, 5 GB egress. Projects pause after a week of inactivity.
- Pro: from $25 a month with $10 of compute credits (one Micro instance), 8 GB disk, 100,000 MAU, 100 GB files and 250 GB egress included. Point-in-time recovery is $100 a month per 7 days of retention.
Good fit when: you want direct SQL access, the Supabase tooling, a US or Asian region, or the option to self-host later, and you are happy to give up the Cloud-only editor features.
One important limit: Lovable's docs say there is no automatic migration between the built-in backend and your own Supabase project, in either direction. Decide early if you can.
#Your own backend: same code, different host
Lovable generates a React app that talks to its backend with supabase-js, reading the URL and key from environment variables (VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY in Lovable's own migration guide). Any backend that implements the same APIs can serve that code.
StitchDB is one: it runs PostgREST-style REST, GoTrue-style Auth, the Storage API, Realtime and Deno Edge Functions with the same paths, headers, JWT roles and error formats (compatibility). You point the two variables at your StitchDB project and rebuild:
VITE_SUPABASE_URL=https://<project-ref>.p.stitchdb.com
VITE_SUPABASE_PUBLISHABLE_KEY=<anon key from Settings > API>RLS policies with auth.uid() and auth.jwt(), storage policies and edge functions with Deno.serve carry over. The Import from Supabase wizard copies a Supabase project's database, auth users with their password hashes, buckets and files, cron jobs and edge function code, with a live copy and a switch-over that takes seconds.
What you get compared with the other two:
- A lower paid entry: Pro is $15.99 a month with 10 GB of database, 100 GB of files, 100,000 MAU and 1 TB of egress (as of November 2026).
- Point-in-time recovery and daily backups included on every paid plan (7 days on Pro, 14 on Scale, 30 on Enterprise). Free has no backups, so export your own copies there.
- A spend cap that is on by default on paid plans, so the plan price is the most you pay unless you turn it off (spend cap).
- Free projects that are not paused while you use your account.
- Agent keys with a query firewall, approvals and undo, if you also use Cursor or Claude Code on the same database.
What you give up: the Lovable editor's own backend views and Cloud-only features, and Lovable no longer runs migrations for you through its Supabase integration. You keep using Lovable for the front end and apply schema changes with the StitchDB CLI or your AI tool over MCP. Regions are EU only (Germany and Finland), and StitchDB is younger than Supabase.
#Cost at three stages
Lovable does not publish per-unit Cloud rates, so an exact side-by-side bill is not possible. What you can compare is structure.
| Stage | Lovable Cloud | Own Supabase | StitchDB |
|---|---|---|---|
| Prototype, few users | Usually covered by the 20-credit Cloud grant | Free plan (pauses after 1 week idle) | Free plan (not paused while you use the account) |
| First paying users | Credits for usage above the grant | Pro from $25/mo, PITR extra | Pro $15.99/mo, PITR included |
| Steady growth | Credit spend grows with instance, storage, traffic | Pro plus compute and usage | Pro or Scale ($49/mo), spend cap on by default |
If cost predictability is your main worry, the deciding factor is whether you want a flat plan price with a cap or a credit balance that moves with usage. For a wider look at backend prices, see the BaaS pricing comparison.
#How to decide
Answer these in order:
- Do you need anything Cloud-only (managed Google auth, SAML SSO, the in-editor Database view, app connectors)? Stay on Lovable Cloud.
- Do you need direct SQL access, your own backups or a specific region outside the EU? Use your own Supabase project.
- Do you want the same code on a cheaper, capped paid plan with point-in-time recovery included, hosted in the EU? Use your own backend such as StitchDB.
- Are you planning to leave Lovable entirely later? Start on your own Supabase or own backend now. Moving off Cloud later is a manual export and restore.
When you are ready to move, the full procedure is in how to move a Lovable app to your own backend.
#FAQ
#Is Lovable Cloud the same as Supabase?
It is built on Supabase's open-source foundation and uses the same client APIs, but Lovable hosts and manages it. You do not get a Supabase dashboard or a Supabase account for a Cloud project.
#How much does Lovable Cloud cost?
As of November 2026, every Free, Pro and Business workspace gets 20 Cloud credits a month. Usage above that, based on instance size, storage, network, compute and realtime, comes out of your general Lovable credits.
#Can I switch a Lovable project from Cloud to Supabase with one click?
No. Lovable's docs say there is no automatic migration in either direction. You export the database, restore it into the new project, copy storage files and set secrets and providers again.
#Will my Lovable app work with StitchDB?
The generated supabase-js code does: change the URL and key and rebuild. Lovable-specific features that run through its built-in backend, such as app connectors and managed Google auth, need your own replacements.
Want the same code on a capped plan? Read the compatibility guide, then create a free project.