To host a website made with Lovable means putting the app Lovable built on a server so anyone can open it at a normal HTTPS address. Lovable's own Publish button does that at your-app.lovable.app; to host it elsewhere you build the code into a dist folder and upload it, and deed.page's Free plan holds 25 sites of up to 25 MB each with no account (pricing).
This guide covers when Lovable's built-in hosting is enough, which Lovable projects a static host can serve, and how to publish one with curl or through MCP. Every deed.page command here was run against production on November 19, 2026, and the test sites were then deleted.
How do I host a website made with Lovable?
The short answer: click Publish in Lovable, or export the code, run npm run build, and upload dist/ to a static host with a fallback to index.html.
Lovable's docs, checked November 19, 2026, say Publish puts the app on a lovable.app subdomain and that a custom domain needs a paid plan (Lovable: Publish your project). If that is all you need, stay there. Host it yourself when you want a different address, your own release process, or an agent to keep updating the page.
Check which kind of Lovable project you have
This decides whether a static host works at all. According to Lovable's external hosting guide (checked November 19, 2026):
- Older React + Vite apps build to static files in
dist/. Any static host can serve them, with a fallback toindex.htmlfor client-side routes. deed.page fits here. - TanStack Start apps (Lovable projects created from May 13, 2026) run server code: server-side rendering, server functions, and API routes. A host that only receives static files does not run those parts, so use a host that runs a server, or keep Lovable's hosting.
Open package.json in Lovable's Code tab. If @tanstack/react-start is listed, it is a TanStack Start app. The same guide says Git sync to GitHub, GitLab, or Bitbucket is available on all plans, and the Download codebase zip is on paid plans.
Build it and publish it with one curl
Clone the repository, then build. If the app uses Lovable's built-in backend, set VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY from the project's .env file before building, because VITE_ values are baked in at build time. The backend itself stays where it is; only the front end moves.
npm ci && npm run build
tar -C dist -czf site.tar.gz .
curl -T site.tar.gz "https://deed.page/v1/sites?slug=habit-tracker-lovable-r7q2&spa=1&ref=blog"
Our test tarball had index.html plus assets/index.css and assets/index.js, the shape Vite produces. The reply had "url": "https://habit-tracker-lovable-r7q2.deed.page/", "version": "v1", "files": 3, and a deed_tok_… owner token shown once. Keep that token; it is the only credential. Pick your own suffix, since that slug is only an example. A stranger sending the same request got 409 slug_taken with a suggested free slug (choosing a slug).
spa=1 is the fallback Lovable's guide asks for. With it, a deep link such as /habits/today returned the app's index.html with status 200, while /assets/index.css still served as text/css (SPA mode). Send spa=1 on every publish: when we republished without it, the same deep link returned 404.
To ship a new build, send it with the token:
curl -T site.tar.gz -H "Authorization: Bearer $DEEDPAGE_TOKEN" \
"https://deed.page/v1/sites?slug=habit-tracker-lovable-r7q2&spa=1&ref=blog"
That returned "version": "v2" at the same URL. Sending the same tarball again returned "unchanged": true and no new version. Bigger builds go up in parts (large sites).
Publish through MCP instead
If an agent such as Claude or Cursor holds the built files, it can publish through deed.page's MCP server at https://deed.page/mcp (docs). The call looks like this:
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"publish_site","arguments":{"slug":"habit-tracker-lovable-mcp-k4t9","spa":true,"files":{"index.html":"<!doctype html><title>Habit tracker</title><h1>Habit tracker, built in Lovable</h1>"}}}}
It returned ok: true, version: "v1", the subdomain URL, and a token, and a client route like /week/3 served the page. update_site with that token and spa: true gave a new version at the same address; without the token it refused with unauthorized. The MCP walkthrough covers the rest.
FAQ
Can I host a Lovable app for free outside Lovable?
Yes, if it is an older React + Vite app that builds to static files. deed.page's Free plan is $0 for 25 sites of 25 MB each. A TanStack Start app needs a host that runs a server.
Will my Lovable database still work?
The built front end keeps calling the backend whose URL and publishable key were set at build time. Lovable's guide covers moving the backend to your own Supabase project if you want it off Lovable too.
Will the site disappear if nobody visits it?
No. deed.page sites do not expire unless you send X-Ttl for a throwaway page (TTLs). Free sites show a small "Published with deed.page" link; Hobby at $3 a month removes it.