Move your app off Lovable or Replit: where to host it
Short answer: Moving off Lovable or Replit is two jobs: the front end (the pages people see) and the backend (database, logins, server code). A Lovable app becomes a folder of plain files after npm run build, and any static host can serve it: DropTheHassle (no account, free link, your own domain with one A record), Netlify, Vercel or Cloudflare Pages. The backend can stay on Lovable Cloud, which still uses Lovable credits, or move to your own Supabase project; there is no one-click migration. A Replit Static Deployment has no backend server and moves like a plain site.
Your AI can publish. It can never spend your money.
Built it with ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf or by hand? Same steps.
Last updated: 30 September 2026. Claims about Lovable and Replit come from their own documentation on that date; links are at the bottom of this page.
You're not the only one asking
"How to move out of lovable??"
"I don't want to spend any cash on hobby project but want to keep it running."
"Do you think I should also move the Lovable website to another server or hosting provider, just to reduce the risk?"
These are from r/lovable in August and September 2026. Moving is very doable, but you need to know which parts can move where.
First: do you need to move at all?
- Lovable: if the only reason is money, you may not have to. Lovable's docs say a published app stays live after a downgrade to Free and a connected domain keeps working. What changes is explained in Downgrading Lovable: does your custom domain keep working?
- Replit: on the free Starter plan, Replit's docs say you get one free published app and that its link goes down after 30 days. Downgrading doesn't delete anything ("Your projects and data stay intact"), but to keep a site up for free, a move is the practical option.
Step 1. What kind of app do you have?
This decides everything else.
| Your app | What it is | Can it go on a static host (like us)? |
|---|---|---|
| Lovable app (React + Vite) | Pages as plain files after a build; the backend lives separately | Yes. The front end can. |
| Replit Static Deployment | "There is no backend server" (Replit's words) | Yes. |
| Replit Autoscale or Reserved VM deployment | A running server | No. It needs a server host. |
How to tell: in Replit, check which deployment type you chose when you published: Static, Autoscale or Reserved VM.
Step 2. Get your code out
- Lovable: connect the project to GitHub. That works on every plan. Then download it from GitHub (green Code button → Download ZIP). On a paid plan you can also use Download codebase in Project settings → Git. Do that before you downgrade.
- Replit: in the file tree, open the three-dot menu at the top and choose Download as zip.
Step 3. Host the front end
For a static app, build it once: put the .env file in the project folder (it holds your backend's address, and it's baked in when you build), then run npm install and npm run build. You get a dist folder. Step-by-step help for beginners is in Put your Lovable app on your own domain.
Then choose a host. All of these can serve a dist folder over HTTPS:
| Host | Good for | Keep in mind |
|---|---|---|
| DropTheHassle | Dropping a finished folder with no account, then adding a domain | Static files only. The claim link works for 7 days. After that you cannot claim the site, and an unclaimed site can be removed. Once claimed, the free link stays. Before claim, an upload can be 25 MB and 1,000 files. After claiming, uploads can be 100 MB and 5,000 files. Noindex until claimed |
| Netlify | Building automatically from GitHub on every change; also runs server functions | You set up the build, and an account is needed |
| Vercel | Building from GitHub; runs server code too | You set up the build, and an account is needed |
| Cloudflare Pages | Building from GitHub on Cloudflare's network; also supports server code | You set up the build, and an account is needed |
For prices and renewals, see Netlify vs Vercel vs Cloudflare Pages. We don't list their prices here because they change.
On DropTheHassle: go to dropthehassle.com, click Upload (free), then Drop your folder and choose dist (a .zip works too). A few seconds later it's live on yourname.dropthehassle.app with HTTPS. Click Claim this site, enter your email and the 6-digit code, and it's yours. The free link stays free. Prefer your AI tool? npx -y dropthehassle deploy does the same, but paying is never something it can do.
"My site is blank on my own domain"
"when I type my custom domain, my site is fully blank"
When a moved app shows a white page, it's usually one of these:
- The
.envfile was missing when you built. The app can't find its backend. Add it and build again. - You uploaded the project instead of the build. Upload the
distfolder, not the folder withsrcin it. - Sub-pages give a 404 after a refresh. The host has to send unknown paths to
index.html. On DropTheHassle that's automatic. Lovable's docs explain how to set it up for Netlify, Cloudflare and others.
If the domain is still connected inside Lovable and that's what's broken, see Lovable custom domain not working.
Step 4. Decide where the backend lives
We don't host backends, so this part is between you and Lovable, Supabase or Replit. Your options:
A. Leave it on Lovable Cloud (the easiest) Your new front end keeps talking to it. It still uses Lovable credits for logins, the database and AI calls. Lovable pauses idle Cloud projects automatically, and while a backend is paused, your app can't read or write data. If people sign in, add your new address under More → Cloud → Users → Auth settings → Advanced.
B. Move it to your own Supabase project Lovable Cloud is built on Supabase, so this is the closest match, but it isn't one click. From Lovable's docs:
- The database schema and storage buckets come across through SQL migrations.
- Data: export tables as CSV, or request a full database export in More → Cloud → Overview → Advanced settings. That export is limited to databases up to 15 GB, a 5 GB file, and one export per 24 hours.
- The export does not include storage files, Edge Function code or secrets. Move those yourself.
- User accounts come with their password hashes, so users keep their passwords. Sign-in providers have to be set up again, and people who are signed in have to sign in again.
- Then update the
VITE_SUPABASE_*values in.envand build again.
C. Run the backend yourself (self-hosted Supabase or another platform) Possible, but Lovable points out you then own backups, security, monitoring and auth settings yourself. That's a lot for a hobby project.
Replit database: Replit's docs show how to export data from the Database tool (My Data) or with pg_dump. Your new backend host has to run the server part of your app.
Step 5. Move the domain last
Only switch the domain once the new site works on its free link.
- Domain bought elsewhere: change its A record to the one shown in your DropTheHassle dashboard, then disconnect it on the old platform. One A record is all we need, and connecting is free.
- Domain bought through Lovable: the workspace owner can transfer it out in Workspace settings → Workspace domains (Transfer out: turn off the transfer lock, then reveal the authorization code). New domains are locked for 60 days.
- Domain bought through Replit: transfers go through Replit Support, also with a 60-day wait after purchase. Leave time for it. One person who moved off Replit wrote: "Replit needs to release my custom domain from its managed Clerk integration."
- No domain yet? Buy one with your site on DropTheHassle and there's nothing to set up. A .com costs EUR 19 a year including VAT in the EU, or USD 19 elsewhere, the same every year (.org and .net the same; .nl and .eu 12; .app 25).
What we don't do
- No backends: no databases, logins, server functions or API routes.
- No apps that need a running server (Node, Python, PHP).
- No automatic builds from GitHub. You upload a finished folder (or your AI does).
If your app is mostly backend, Netlify, Vercel or Cloudflare are the better fit. If it's pages that talk to a backend somewhere else, we're the shortest route to your own domain.
Questions
How do I move my app out of Lovable?
Connect the project to GitHub (every plan can) to get the code. For a React + Vite app, put the .env file in the folder, run npm install and npm run build, and upload the dist folder to a static host. The backend stays on Lovable Cloud unless you move it to your own Supabase project yourself.
Do I have to leave Lovable to stop paying?
Not necessarily. Lovable's docs say a published app stays live after a downgrade, and a connected domain keeps working. Apps using Lovable Cloud or AI features still need credits.
Can DropTheHassle host my Lovable backend?
No. We host static files only: HTML, CSS, JavaScript, images. Your database, logins and server functions stay on Lovable Cloud or Supabase, and the published pages keep talking to them.
Why is my site blank on my own domain?
Common causes: the .env file wasn't in the folder when you built, you uploaded the project folder instead of the built dist folder, or the host doesn't send unknown paths to index.html. On DropTheHassle unknown paths already serve index.html.
How do I move a Replit app?
If it's a Static Deployment (no backend server), download the project as a zip from the three-dot menu at the top of the file tree, build it if needed and upload the output. Apps with a server or database need a server host; export the database first.
What about a domain I bought through Lovable or Replit?
Lovable lets the workspace owner transfer it out in Workspace settings → Workspace domains. Replit transfers go through Replit Support. Both have a 60-day lock after purchase. Or keep it there and only change its DNS.
Related
- Downgrading Lovable: does your custom domain keep working?
- Put your Lovable app on your own domain, step by step
- Lovable custom domain not working
- Put your Bolt.new site on your own domain
- Netlify vs Vercel vs Cloudflare Pages, with renewal prices
- AI app builders with your own domain, compared
- Deploy with your AI (MCP)