Guide · 5 minute read · 21 October 2026

How to put a Lovable app online on your own address

Publishing in Lovable is one click and a free lovable.app link. Your own name on it is where the choices start: pay for a plan and connect the domain there, or take the code out and host it where you like. Both work. They differ in what stays on Lovable, and, since May 2026, in what kind of project you are moving.

yourapp.lovable.appyourname.com

Route one: connect a domain on Lovable

Open the project, then Settings, then Domains, and under Connect existing domain click Connect domain. Lovable asks you to add two records where you bought the domain: an A record pointing at Lovable's address, 185.158.133.1, and a TXT record at the host _lovable whose value starts with lovable_verify= (Lovable shows the full value during setup). The www redirect is on by default, so www.yourname.com sends people to yourname.com. Lovable's docs say changes “may take up to 72 hours to propagate, though most updates are live within a few hours”, and the certificate is issued for you; if it hasn't appeared after 72 hours, support is the next step. A domain can be connected to one project at a time. Domains bought through Lovable skip the records: Lovable creates them and connects both names.

This route costs the plan every month, for as long as the name should keep working.

Route two: take the code out

Git sync is free on every plan: Project settings, then Git, then GitHub, then Connect. Lovable creates a new private repository and keeps it in step with your project, one branch at a time. From GitHub you can download the folder (Code, then Download ZIP) at no charge. Download codebase, the direct button in Project settings under Git, needs a paid plan. How to get your code out of Lovable, Bolt, Replit or v0 has the detail for all four builders.

Know which project you have

Since 13 May 2026 every new Lovable project is built on TanStack Start and renders its pages on a server. Lovable's own words: these apps “run server code, so they need a host that runs the server as well”. Projects from before that date are React and Vite and build to plain files that any static host serves. Drop a new project onto a files-only host and you get a 404, which is what this year's “exported Lovable app shows 404 on Vercel” threads are about. If you don't know which you have, ask Lovable “What stack is this project on?”.

What stays on Lovable

The built-in backend. If your app uses Lovable Cloud for its database, sign-in or stored files, those stay on Lovable when the code leaves. The code keeps calling them, which works, and keeps using your credits for it. Lovable's docs say moving to your own Supabase project is not one step: you export the database and rebuild its shape in a new Supabase-connected project, and moving the database alone “does not move authentication, storage, realtime, or Edge Functions”. The Settings tool can pause or remove the backend, and removal is permanent, database and backups included.

The editor and the AI. There is nothing to move; you keep paying Lovable for building, not for hosting.

Sign-in redirects. Lovable's self-hosting page tells you to configure, on the new host, “environment variables, server secrets, and sign-in redirect URLs”. The last one is the one people miss: a password reset that lands back on the old lovable.app link means the sign-in provider still points there.

Settings and keys

The project's settings live in Lovable, not in the files. The Supabase address and its publishable key are meant to be public and can go in a .env file on the new host; a secret key never goes near a browser. Is it safe to put API keys in my app? sorts the two kinds.

Putting it on saturn

Drop the folder as it came from GitHub or from the download. saturn reads it, says what it thinks it is, and works out whether it builds to files or needs a server: files are built in a sandbox and served, an app that needs a server is built and run. It gets a free address at once. Settings go in separately and are kept encrypted, never inside what is served. You pick the smallest plan it fits in and pay at go-live, and your own domain is part of the first release.