dropthehassle

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 host for built files can serve it, for example DropTheHassle (no account, free link, your own domain with one A record). 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 server of your own runs on AWS, Google Cloud, DigitalOcean or your own server, connected in the Backend card. 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?

Step 1. What kind of app do you have?

This decides everything else.

Your appWhat it isCan it go on DropTheHassle?
Lovable app (React + Vite)Pages as plain files after a build; the backend lives separatelyYes. The front end can.
Replit Static Deployment"There is no backend server" (Replit's words)Yes.
Replit Autoscale or Reserved VM deploymentA running serverYes, with the Backend card: run the server on AWS, Google Cloud, DigitalOcean or your own server and connect it.

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

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:

HostGood forKeep in mind
DropTheHassleDropping a finished folder with no account, then adding a domainBuilt files; your server connects in the Backend card. The claim link works until the site is removed. An unclaimed site is kept for at least 7 days. 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
A server of your own (AWS, Google Cloud, DigitalOcean or your own machine)The backend: database, logins, server codeConnected in the Backend card, so it runs behind your own domain here

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@latest 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:

  1. The .env file was missing when you built. The app can't find its backend. Add it and build again.
  2. You uploaded the project instead of the build. Upload the dist folder, not the folder with src in it.
  3. 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:

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.

What we don't do

If your app is mostly backend, host it on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card: it then runs on your own domain here, with HTTPS and email. 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 any host for built files. 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?

Not on our machines: we don't run servers. Your database, logins and server functions stay on Lovable Cloud or Supabase, or run on AWS, Google Cloud, DigitalOcean or your own server, connected in the Backend card. The published pages keep working with 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: run it on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card; 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