What happens when you publish
Publishing takes a snapshot of your project and puts it live. You publish with the Publish button in the top right of the editor, or by asking Lovable in the project chat. Either way:- Your app gets a public URL on
lovable.app, with a web address you can customize (or your custom domain, a branded workspace URL, or your workspace’s publishing domain). - HTTPS is included automatically: visitors always connect securely (the padlock in the browser). Lovable sets up the SSL certificate, the file that makes that secure connection possible, for every published URL, including custom domains.
- The published site is a snapshot. Changes you make after publishing don’t affect the live site until you open the Publish dialog again and click Publish changes, so you can keep building without breaking what your visitors see.
lovable.app URL is free and available on all plans. Custom domains require a paid plan, and branded workspace URLs are available on Business and Enterprise plans. On the Enterprise plan, a workspace can connect one publishing domain that every app in it publishes under. For the full path from publishing to a live site on your own domain, follow Launch your site on a custom domain.
A live site does not consume credits on its own. Usage-based Run credits cover the work your app does while it runs, such as backend activity and AI features.
Who can visit your published app
By default, anyone with the link can visit your published app, on every plan. You can instead restrict the published app to invited people. On Business and Enterprise plans, you can also restrict it to workspace members or groups. In both cases, visitors log in to open the site. See website access control for the options. Who can visit the live site is separate from who can open the project in the editor: publishing never exposes your source code, chat history, or unpublished work. You can also take your site down at any time: click Publish, open the ⋮ menu in the top-right corner of the dialog, and select Unpublish, or go to Project settings → Unpublish project. You can publish again later.Your site is delivered globally
Published apps are served from locations around the world, close to your visitors, so your site loads fast regardless of where your users are. You do not set any of this up. It is simply how every published app is served. This is separate from the region setting, which controls where your app’s backend data is stored. Choosing a hosting region for a project affects the built-in backend, such as its database and storage. It does not restrict where your site itself is delivered: the frontend is always served globally.How search engines and AI see your site
Crawlers only index what they can read, and many tools struggle with JavaScript-heavy apps. Lovable hosting solves this for you: search engines, social platforms, and AI crawlers all receive readable, fully rendered pages.- Apps created from May 13, 2026 use server-side rendering: every visitor and crawler receives fully rendered pages.
- Older apps serve rendered pages to verified search engines, social preview bots, and AI crawlers, so your content is indexed and link previews work. You can upgrade an older project to TanStack Start to get server-side rendering for every visitor.
Traffic and scale
Your published app scales with traffic automatically. Your plan does not cap visitors or bandwidth. The one exception is workspaces without a paid plan. There, newer apps (created from May 13, 2026, which use TanStack Start) have a limit of 1,000 server requests per project per 10 seconds. A server request is a page load or a server-function call. Files Lovable serves ready-made do not count: static files such as images and scripts, and pages your app built in advance rather than per visit. Requests above the limit are refused, not queued. A visitor who loads a page above the limit sees an App temporarily unavailable page and can try again after a minute. A background call from your app gets an error instead, with the same wait, and so does a page displayed inside another website. This limit applies to page traffic. Your app’s backend has its own capacity, set by its database instance size. Automated abuse protection runs on every published app. It targets attack patterns, not real audiences, but unusually aggressive traffic from a single source can be challenged or slowed down.Hosting and the built-in backend
Hosting serves your app’s pages to visitors. The built-in backend is what those pages talk to: the database, authentication, storage, and functions behind your app. They work together, but they are separate:- Every published app is hosted, whether or not it uses a backend.
- Backend activity, such as database work and AI calls, is what consumes Run credits as your app is used.
- Pausing the backend affects your app’s data and logic, not the hosting of its pages.
- Newer apps run their server code inside the hosted app, and older apps run it on the backend as edge functions. See Where your app’s server code runs.
Preview vs published
The preview is your live working view inside the editor: it updates as you build, and it can differ from what visitors see on the published site. Share preview links let you show that work in progress to someone before publishing, but they are view-only and, by default, expire after 7 days. Neither is hosting: only publishing puts your app on a public URL.Hosting somewhere else
You own your code and data, and you can host parts or all of your app outside Lovable. See Deployment, hosting, and ownership options for the trade-offs and Deploying and hosting outside Lovable for the walkthroughs.FAQ
Do I need my own hosting provider or server?
Do I need my own hosting provider or server?
Do I need to keep Lovable open for my site to stay up?
Do I need to keep Lovable open for my site to stay up?
My published site is down. What should I check?
My published site is down. What should I check?
- Open the Publish dialog and check that your project is still published.
- If the project is unpublished and your workspace is on the Free plan, Lovable may have unpublished it for inactivity. Check your email for a notice from Lovable. To bring the site back, see Does my published site expire?.
- If you use a custom domain, go to Project → Settings → Domains and check that its status is Active. For other states, see Domain statuses.
- Ask Lovable in the project chat about your domain. It reports the domain’s current state and whether the project is published.
The Lovable hosting IP is on a spam blocklist. Does that affect my site?
The Lovable hosting IP is on a spam blocklist. Does that affect my site?
185.158.133.1 is the standard value of a custom domain’s A record, the DNS record that connects the domain to Lovable.Many Lovable sites share this address, and some spam blocklists, such as RATS, list it. Lovable does not assign a dedicated IP address to individual projects.The listing does not affect your app’s emails either. Lovable sends them from separate email servers, and inbox providers check the domain the emails are sent from. If your app’s emails go to spam, see Why are my emails going to spam?.My site doesn't load from some networks in one country. What can I do?
My site doesn't load from some networks in one country. What can I do?
Where is my app hosted?
Where is my app hosted?
How do I update my live site?
How do I update my live site?
How many visitors can my site handle?
How many visitors can my site handle?
Can I take my site down?
Can I take my site down?
Is HTTPS included?
Is HTTPS included?
Does my app's own server code have the same limits as an edge function?
Does my app's own server code have the same limits as an edge function?
Can my runtime limits be raised?
Can my runtime limits be raised?
Can visitors seek through a video my app serves?
Can visitors seek through a video my app serves?
Can my app cache data between requests?
Can my app cache data between requests?
Which TanStack Start build modes can I publish?
Which TanStack Start build modes can I publish?
index.html, which Lovable serves for page routes so client-side routing works.Not every TanStack Start single-page configuration is supported, so keep your project’s build configuration unless support confirms another mode.Are requests queued when traffic spikes?
Are requests queued when traffic spikes?