OxyPages

A Lovable Hosting Alternative: Which Parts Can Move

A Lovable Hosting Alternative: Which Parts Can Move

Looking for a Lovable hosting alternative? Check if your app is static or server-rendered, see what stays on Lovable Cloud, and compare hosts. Nov 2026.

The OxyPages Team · · 8 min read

You built an app in Lovable without writing a line of code, and it's live on a lovable.app address. People are using it. Now you want your own domain, or the badge gone, or you just don't like your whole business living inside the tool that made it.

So you go looking for a Lovable hosting alternative, and every guide starts talking about builds, adapters and environment variables as if you already know which of those apply to you.

Here's the part they skip. A Lovable app isn't one thing. It's a set of screens, plus a backend with your data, logins and files. The screens can often move. The backend usually stays exactly where it is, and that's fine.

There's one more fork, and it's dated. Apps Lovable created before 13 May 2026 build to plain files any static host can serve. Apps created since then use a framework that runs code on a server, so they need a host that can run it.

Every vendor fact below was checked on the vendor's own pages, and prices are as of November 2026. I run a static host, so I'll be plain about which apps it can't take. Every static host compared side by side covers the wider field.

TL;DR: Publishing to a lovable.app address is free on every Lovable plan, but Free has no custom domain and keeps the "Edit with Lovable" badge. Pro is $25 a month, or $21 a month billed yearly, and adds both. Before moving, check when the app was created. Before 13 May 2026, Lovable apps are React and Vite, and the built files run on any static host. From 13 May 2026, new apps use TanStack Start, which renders pages on a server, so they need Netlify, Vercel, Cloudflare Workers or a server host like Render. Either way, the database, logins and uploaded files stay on Lovable Cloud or Supabase. Moving the front end doesn't move them.

Why Do People Move Their App Off Lovable Hosting?

People move off Lovable hosting for a custom domain, for the badge, or to stop one credit balance from covering everything. The hosting itself isn't the problem.

On the Free plan, publishing is free but limited. There's no custom domain, the "Edit with Lovable" badge stays on, and you can't download the code, though you can sync it to GitHub. Lovable's docs also say Free apps "can be unpublished after about a year of inactivity."

A custom domain and badge removal start on Pro at $25 a month, or $250 a year. That's a fair price if you're still building in Lovable every week. It's a lot for a domain on an app you've finished.

The third reason is credits. Since 1 June 2026, building, backend activity and in-app AI all draw on one balance, and Lovable notes that credits "are not necessarily equal in value across different plans." Some founders want hosting on a bill they can predict separately.

Who Should Stay On Lovable Hosting

Plenty of people should stay. If you're still building with Lovable's AI, staying means every change goes live with one click. Lovable says "A live site does not consume credits on its own," and paid plans don't cap visitors or bandwidth.

Stay too if your app was created after 13 May 2026 and you don't have a developer. Moving a server-rendered app is a bigger job than moving files, and Lovable already runs the server for you.

Which Parts Of A Lovable App Need A Server?

Which Parts Of A Lovable App Need A Server? - OxyPages

Only the parts that run code when someone visits need a server; everything else is files. Go through your app and sort it like this:

  1. The screens. On an older app, these are built into a folder of HTML, JavaScript and CSS that runs in the visitor's browser. On a newer app, the server builds them per request.
  2. Logins. Handled by Lovable Cloud or Supabase. Your screens talk to it from the browser, so it stays where it is.
  3. The database. Your customers, bookings or orders. It lives on Lovable Cloud or Supabase and stays there.
  4. Uploaded files. Photos and documents users add live in the backend's storage, not in the code.
  5. Server functions and API routes. Newer apps can run code on the server for things like payments. These need a host that runs server code.
  6. AI features. These run on Lovable's backend and spend Lovable credits. Moving the screens doesn't move them.

Read that list again and notice how little is in the "moves" column. Lovable's own guide says exports don't include the database or uploaded files, and the supported backend destinations are managed or self-hosted Supabase. So moving hosting mostly means moving item one.

web.dev's guide to rendering on the web explains the difference between pages built in the browser and pages built on a server, if you want the background.

How To Tell Which Kind Of Lovable App You Have

Check the date first: an app created before 13 May 2026 is React and Vite, and one created after is TanStack Start.

If you're not sure of the date, sync the project to GitHub (every Lovable plan can), open package.json and search for @tanstack/react-start. If it's there, the app needs a server. If the build command is vite build and nothing launches a server, it's a static app, and the built folder is called dist.

That one check decides which list below you're shopping from.

Where Can A Lovable App Go Instead?

A static Lovable app can go to almost any host; a TanStack Start app needs one that runs server code. All prices below are monthly unless marked, as of November 2026.

Netlify

Netlify suits both kinds of app. It serves static builds and has a setup guide for TanStack Start. The Free plan allows commercial projects and custom domains, but runs on 300 credits a month, where a production deploy costs 15 and each GB of bandwidth costs 20. Sites pause when credits run out. Personal is $9 a month, and Pro is $20 a month with unlimited members.

Vercel

Vercel suits newer TanStack Start apps and anyone planning to hire a developer, since most know it well. The free Hobby plan is for "personal or non-commercial use" only. Pro is a $20 monthly platform fee with one deploying seat and $20 of usage credit, and extra deploying seats are $20 a month each.

Cloudflare

Cloudflare suits founders who want the most generous free tier for a static app. Static asset requests are free and unlimited, with custom domains included. Cloudflare Workers also has a TanStack Start guide, and Workers Paid starts at $5 a month per account. The catch is two overlapping products: Cloudflare's own Pages docs now tell new projects to start on Workers instead, which confuses newcomers.

Render

Render suits newer apps when you'd rather have a plain always-on server. A TanStack Start app runs as a web service, from $7 a month always-on. Static sites are free, but the free Hobby workspace includes only 5 GB of bandwidth, then $0.15 per GB.

OxyPages, For Older Static Apps Only

OxyPages is the host I run, and it fits only apps created before 13 May 2026. It builds the React and Vite project from GitHub on every push, has an SPA mode so links don't break on refresh, and keeps version history for rollback. The free plan is for personal, non-commercial use with no custom domain. Lite, at $5 a month or $48 a year, adds custom domains and commercial use.

It can't take a TanStack Start app. There's no server rendering, no server functions and no database on any plan.

Choosing A Lovable Hosting Alternative, Side By Side

HostOlder static appNewer TanStack Start appFree tierCustom domain fromThe catch
LovableYesYeslovable.app address, badge$25 Pro ($21 yearly)One credit balance for everything
NetlifyYesYes300 credits, commercial OKFreeSites pause when credits run out
VercelYesYesHobby, non-commercial onlyFree on Hobby, $20 Pro for businessPer deploying seat on Pro
CloudflareYesYes, on WorkersUnlimited static requestsFreePages and Workers overlap
RenderYesYes, as a web serviceStatic sites, 5 GB bandwidthFree (2 included)$7 for an always-on server
OxyPagesYesNo1 non-commercial site$5 Lite ($48 yearly)No server rendering or functions

Notice that every row keeps the same backend. Whichever host you pick, logins, data and uploads still come from Lovable Cloud or Supabase.

A Walkthrough: Moving A Booking App Built In March

A Walkthrough: Moving A Booking App Built In March - OxyPages

Say you run a cleaning business and built a booking app in Lovable in March 2026. Customers sign in, pick a slot, and you see the bookings. It uses Lovable Cloud for the data and logins. You want it on book.yourcompany.com.

March is before 13 May, so it's a static React and Vite app. Here's the move:

  1. Connect GitHub from Lovable. Every plan can sync code to GitHub. Keep editing in Lovable afterwards if you like, because each change lands in the repository.
  2. Import the repository on your new host. The build command is npm run build and the output folder is dist. Turn on SPA mode, or add the redirect rule your host documents.
  3. Check the environment values. The address and public key the app uses to reach its backend must be present at build time. How Vite handles environment variables explains where they live.
  4. Add the new address to the backend's sign-in settings. Login systems keep a list of allowed redirect addresses. If the new domain isn't on it, sign-in fails.
  5. Test the real journeys. Sign in, make a booking, cancel it, upload a file if the app allows it.
  6. Point the domain last. Keep the lovable.app version live until the new one has worked for a few days.

If links work from the home page but break on refresh, that's a missing SPA rule, and the fix for a 404 on refresh covers every host.

What To Do Next

Check the creation date before anything else. That one fact tells you whether you're choosing a static host or a server host.

If the app is older and static, a static host gives you a custom domain for free or a few dollars a month, while Lovable Cloud keeps running the backend. If it's newer, Netlify, Vercel or Cloudflare Workers can run it, and staying on Lovable Pro is a reasonable call too. Picking a Lovable hosting alternative only changes where your screens live.

Got an older app and want to see it running on a free subdomain first? Put your Lovable build online and test it before you touch the domain.

FAQ

Can I Host A Lovable App Somewhere Else?

Yes. Lovable syncs code to GitHub on every plan, so another host can build and serve it. Apps created before 13 May 2026 run on any static host, while newer TanStack Start apps need a host that runs server code. The database and logins stay on Lovable Cloud or Supabase either way.

Is Lovable Hosting Free?

Publishing to a lovable.app address is free on all plans. The Free plan has no custom domain and shows the Lovable badge, and Lovable says Free apps can be unpublished after about a year of inactivity. A custom domain starts on Pro at $25 a month.

Will My Database Move With My Lovable App?

No. Lovable's exports don't include the database or uploaded files. Moving the front end to another host leaves the data on Lovable Cloud, and the only supported backend destinations are managed or self-hosted Supabase.

Can I Keep Editing In Lovable After Moving The Hosting?

Yes, if your Lovable hosting alternative builds from the GitHub repository Lovable syncs to. Each change you make in Lovable lands in GitHub, and the host rebuilds the site from it. Check the live site after big changes, since Lovable won't warn you if a build fails on another host.

Try It Now

Still Here? Drop It In.

The whole pitch fits in one sentence: your HTML, on a link, in seconds.

Drag and drop your HTML files, a folder, a ZIP, your app's build folder, a PDF or an image

or ·

No account needed. Your unclaimed website stays live for 30 minutes on a free subdomain. Claim it to your account to keep it permanently.

  • No Account Needed
  • Free SSL
  • 30-Minute Unclaimed Link, Claim To Keep It