Host what you built in Lovable, on an address you own

Lovable ships your app to a lovable.app subdomain. Export the build and put it somewhere that doesn't depend on your plan staying active.

You can host:

Free to use, live at your-name.99helpers.site in about ten seconds.

Why you might not want to leave it there

Lovable already publishes for you, which makes this page a different argument from the ones about chat assistants. The question isn't where to put it — it's whether you're happy with where it is. A lovable.app subdomain is fine for showing work in progress. It's less fine as the address you print on a business card, hand to a client, or expect to still work in a year.

What Lovable gives you

  • A React project you can push to GitHub and build yourself
  • A preview deployment on a lovable.app subdomain
  • The full source, once you've connected a repository

The address isn't yours

A long subdomain on somebody else's domain says more about the tool you used than about the thing you made.

It's tied to your plan

Hosting that comes bundled with a builder tends to stop when the subscription does. A static file you host yourself has no such clause.

You can't share it selectively

Builder previews are usually all-or-nothing: public to anyone with the link, or invisible. A password is often exactly what you want in between.

Putting Lovable output online

  1. 1

    Export and build

    Connect Lovable to GitHub, clone the repository, and run the project's build command — usually npm run build. You'll get a dist or build folder.

  2. 2

    Drop the built folder in

    Drag that folder — not the source — into the box above. It contains an index.html and its assets, which is exactly what a static host needs.

  3. 3

    Pick your address

    Choose a name and publish. Every route and asset resolves the way it did locally, and the link is yours to hand out.

Worth knowing

  • Publish the build output, not the project folder — src and node_modules aren't needed and will push you over the size limit.
  • A Lovable app that talks to Supabase keeps working, because those calls happen in the visitor's browser, not on the host.
  • If your app uses client-side routing, add a 404.html that loads the same page so deep links resolve.
  • Set the base path to / in your Vite config before building, or assets will look for themselves in the wrong place.
  • Publish new builds to the same address as you iterate — old versions are kept and you can roll back.

Questions

Why host a Lovable app somewhere else?
Control. Your own short address, no dependency on a subscription, optional password protection, and a copy that keeps working regardless of what happens to the account you built it in.
Will my Supabase backend still work?
Yes. Those requests go from the visitor's browser straight to Supabase and never touch the host, so nothing changes.
What about server-side rendering?
This is static hosting, so anything needing a Node server at request time won't run. A standard Vite React build is entirely static and works fine.
Do I need to keep Lovable to keep the site up?
No. Once the built files are published they're independent of Lovable entirely.
How big can the build be?
Up to 100 MB across the whole site, which comfortably fits a typical React build.

Try it with what Lovable just made you

Drop it in at the top of this page and see the link for yourself. You only make an account once it's ready to go live.

Back to the topEvery AI tool we cover

Hosting artifacts from other tools

Hosting guides by file type

Everything gets its own address on 99helpers.site — see AI artifact hosting for every tool or free file hosting for any file type.