Can you host a Lovable app outside Lovable?
Yes. Lovable's own docs say the app's source is yours and runs on any compatible host, so moving it is a deployment change, not a rewrite. The code moves through the GitHub repository Lovable keeps in sync; the database, sign-in users and uploaded files move with the Hostwares migration tool into a dedicated Supabase project. You keep editing in Lovable afterwards, pay a flat monthly pack instead of Lovable hosting, and own the environment variables and the domain.
Step by step
- 1
Connect the Lovable project to GitHub
In Lovable, open the project and connect GitHub. Lovable creates the repository and pushes every later edit to it. That repository is what you deploy; nothing else is needed from Lovable for the code.
- 2
Deploy the repository on a pack
Go to Dashboard → Deployments → New, pick the repository and a pack. A pack is fixed CPU, RAM and disk at a flat monthly price. Lovable apps are Vite builds, so the framework is detected and the commands are filled in. The order creates an invoice and the build starts once it is paid.
Projects created after Lovable's switch to server-rendered TanStack Start output need a host that runs code rather than one that only serves files; a pack runs the start command, so both kinds deploy the same way.
From Claude Code or Cursor over MCP
deploy → returns a price and an approval link; the build starts once the invoice is paid - 3
Move the data with the migration tool
If the app has a database, users or files, order a dedicated Supabase pack at Dashboard → Supabase → New and create a project. Then run the backup tool on your own computer. It signs in to Lovable in your browser, keeps the token on your machine, and saves your tables, rows, functions, access rules, users and files. Upload the result in the project's Restore tab.
The Restore tab takes uploads up to 200 MB; a larger backup is restored for you through a support ticket. Users keep their passwords. Secrets you typed into Lovable (payment or email keys) are not exported, so add them again in step 4.
macOS / Linux
curl -fsSL https://migrate-lovable.hostwares.com/install.sh | bashWindows (PowerShell)
irm https://migrate-lovable.hostwares.com/install.ps1 | iex - 4
Set the environment variables
Open the site's Environment tab and add every VITE_ variable the app reads. Your Supabase project's Overview has a "Connect to your frontend site" block with the exact names (VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY, VITE_SUPABASE_PUBLISHABLE_KEY) and values. Over MCP this is the set_env tool.
Variables are read at build time, so the site rebuilds after you change them; the current version keeps serving until the new build is ready.
- 5
Fix the sign-in redirect, add the domain, verify
Add the new address to Site URL and Redirect URLs in the Supabase project's Auth settings. Attach your domain on the Domains tab (or add_domain from an agent). Then sign in with an existing account and open a page that shows uploaded files; diagnose_site over MCP checks reachability, container state and recent logs in one call if anything looks off.
What breaks, and the fix
- Every VITE_ variable is empty on the new host
- They are not exported with the code. Add each one on the Environment tab; the Supabase block on your project's Overview gives the Supabase ones.
- Sign-in emails link to the old address
- Update Site URL and Redirect URLs in Supabase Auth settings.
- Payment or email features fail
- Secrets typed into Lovable are not exported. Add them again on the Environment tab.
- Edge functions and Lovable-only AI features
- These may need a small amount of rewiring in the code; the migration tool moves database functions, rules, data, users and files, not Lovable's hosted functions.
What it costs
- A Frontend pack from $1/mo for the app (1 vCPU / 1 GB / 10 GB); the pack most production apps pick is $5/mo.
- A dedicated Supabase pack from $5/mo if the app has data, users or files; several projects fit on one.
- Nothing is metered and there is no per-seat fee. Payment comes before the build starts.
App
$1/mo
Starter Frontend pack, 1 vCPU / 1 GB RAM / 10 GB
Database, users and files
$5/mo
Smallest dedicated Supabase pack; several projects fit on one
For comparison
- Lovable Pro (custom domain, credit top-ups): $25/mo (checked 2026-11-06, lovable.dev)
Questions
Do I have to stop using Lovable?+
No. Keep building in Lovable. The GitHub repository it maintains is what Hostwares deploys from, so every edit still reaches the live site through a push.
Can I keep the domain on Lovable instead?+
Yes, on a paid plan: Project → Settings → Domains, with an A record to 185.158.133.1 and a TXT verification record, or a CNAME for a subdomain. New domains cannot be connected on the free plan, which is the usual reason to host the export elsewhere.
Does the migration need my Lovable password or API keys?+
No. The backup tool runs on your computer and signs in to Lovable in your own browser. Nothing from Lovable passes through our servers.
What exactly moves?+
Database structure, every row, database functions, access rules, triggers and views, sign-in users with their passwords, and uploaded files from public and private storage. Code moves through GitHub.
What does not move?+
Secrets you typed into Lovable, Lovable's hosted edge functions and Lovable-only AI features. Add secrets on the Environment tab; functions may need a small rewrite.
Can the AI do the whole move?+
Yes. Tell HW "migrate my Lovable app" in the dashboard. It creates the project and site, gives you the one backup command to run, waits for your upload, connects the site and deploys it, then reports what was restored.
What does it cost?+
A Frontend pack from $1/mo and, if the app has data, a dedicated Supabase pack from $5/mo. Both are flat for the term.
Related
Next guides
Sources: Lovable docs: Deployment, hosting and ownership (2026-11-06) · Lovable FAQ: Code export (2026-11-06) · Lovable pricing (2026-11-06)