> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# How Lovable hosts your app

> Lovable hosts your published app for you: no servers to set up, HTTPS included, and delivery from locations around the world. Learn how hosting works.

Lovable hosts your app. When you [publish](https://docs.lovable.dev/features/publish.md), your app goes live on its own URL, and Lovable takes care of everything behind it: there are no servers to set up, no hosting provider to choose, and nothing to configure. Hosting is part of Lovable, not a separate product or add-on.

This page explains what that means in practice: what happens when you publish, how your live site is delivered to visitors, and how hosting relates to [your app's built-in backend](https://docs.lovable.dev/features/cloud).

## 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](https://docs.lovable.dev/features/custom-domain), a [branded workspace URL](https://docs.lovable.dev/features/branded-workspace-urls.md), or your workspace's [publishing domain](https://docs.lovable.dev/features/publishing-domain.md)).
* 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.

Publishing to a `lovable.app` URL is free and available on all plans. [Custom domains](https://docs.lovable.dev/features/custom-domain) require a paid plan, and [branded workspace URLs](https://docs.lovable.dev/features/branded-workspace-urls.md) are available on Business and Enterprise plans. On the Enterprise plan, a workspace can connect one [publishing domain](https://docs.lovable.dev/features/publishing-domain.md) 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](https://docs.lovable.dev/tips-tricks/launch-on-a-custom-domain.md).

A live site does not consume credits on its own. Usage-based [Run credits](https://docs.lovable.dev/introduction/credits-and-usage.md) 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](https://docs.lovable.dev/features/website-access.md#who-can-see-your-published-app) 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](https://docs.lovable.dev/features/publish.md#unpublish-your-project) 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](https://docs.lovable.dev/features/cloud#choose-where-your-project-data-is-stored), 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](https://docs.lovable.dev/features/upgrade-to-tanstack-start.md) to get server-side rendering for every visitor.

Readable pages are the baseline. How well they rank depends on their content, metadata, and structure. Use the built-in [SEO review](https://docs.lovable.dev/features/seo-aeo.md) to check how your live site looks to search engines and what to improve.

> [!NOTE]
>
> For older apps, rendered pages are served only to verified crawlers. Third-party SEO scanner tools are not verified crawlers, so they may report your pages as empty even though Google, social platforms, and AI search engines see the full content.

## 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](https://docs.lovable.dev/features/database-performance.md#database-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.

> [!TIP]
>
> Expecting a major traffic spike, such as a product launch or a TV appearance? [Contact support](https://lovable.dev/support) beforehand so your domain is prepared for it.

## Hosting and the built-in backend

Hosting serves your app's pages to visitors. The [built-in backend](https://docs.lovable.dev/features/cloud) 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](https://docs.lovable.dev/introduction/credits-and-usage.md) as your app is used.
* [Pausing the backend](https://docs.lovable.dev/features/database-pause-remove.md#pause-a-database-youre-not-using) 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](https://docs.lovable.dev/features/edge-functions.md#where-your-apps-server-code-runs).

Running out of credits does not remove your published site. Building stops, and apps that rely on the backend or AI features can pause until credits are available again. Your site and its URL remain in place. Building and AI features resume once credits are added. A paused backend may not restart by itself: if it is still paused, open **More → Database** in the project and click **Wake up** on the paused card. See [What happens when you run out of credits](https://docs.lovable.dev/introduction/out-of-credits.md#what-happens-when-you-run-out-of-credits) for the full breakdown, the alerts you receive along the way, and the options for adding credits.

## Preview vs published

The [preview](https://docs.lovable.dev/features/projects/preview.md) 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](https://docs.lovable.dev/features/share-project.md) 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](https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership) for the trade-offs and [Deploying and hosting outside Lovable](https://docs.lovable.dev/tips-tricks/external-deployment-hosting.md) for the walkthroughs.

## FAQ

> [accordion] Do I need my own hosting provider or server?
>
> No. Publishing your project is all it takes: Lovable builds your app, puts it on a public URL with HTTPS, and serves it to your visitors. You don't need to install, rent, or configure anything.

> [accordion] Do I need to keep Lovable open for my site to stay up?
>
> No. Your published app runs on Lovable's infrastructure, not on your machine. You can close the editor, and your site keeps serving visitors.

> [accordion] My published site is down. What should I check?
>
> Check [status.lovable.dev](https://status.lovable.dev/) first. Lovable posts platform-wide incidents and updates there. If no incident is reported, work through these checks:
>
> * 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?](https://docs.lovable.dev/features/publish.md#does-my-published-site-expire).
> * If you use a [custom domain](https://docs.lovable.dev/features/custom-domain), go to **Project → Settings → Domains** and check that its status is **Active**. For other states, see [Domain statuses](https://docs.lovable.dev/features/custom-domain#domain-statuses).
> * Ask Lovable in the project chat about your domain. It reports the domain's current state and whether the project is published.
>
> If the site loads for some visitors but not others, see [My site doesn't load from some networks in one country. What can I do?](#my-site-doesnt-load-from-some-networks-in-one-country-what-can-i-do). If a blocklist checker lists your site's IP address as spam, see [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).
>
> If everything looks right and the site still does not load, [contact support](https://lovable.dev/support) with your project URL and what you see.

> [accordion] The Lovable hosting IP is on a spam blocklist. Does that affect my site?
>
> No. A spam blocklist listing does not take your published site down. The IP address `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?](https://docs.lovable.dev/features/custom-emails.md#why-are-my-emails-going-to-spam).

> [accordion] My site doesn't load from some networks in one country. What can I do?
>
> The visitor's internet provider is blocking the site. Your site itself is working.
>
> Some providers block IP addresses for all their customers, for example to comply with a court order. Many sites share one IP address, so a block aimed at another site can also stop yours from loading. On those networks, your site times out or shows a security warning, but it loads on other networks.
>
> To confirm, open the site on a different network, such as mobile data from another carrier, or through a VPN. Lovable can't lift a block that an internet provider applies.

> [accordion] Where is my app hosted?
>
> Your site is delivered from locations around the world, close to each visitor. If your project uses the built-in backend, its data lives in the [region](https://docs.lovable.dev/features/cloud#choose-where-your-project-data-is-stored) chosen when the backend was enabled.

> [accordion] How do I update my live site?
>
> Publish again. The live site is a snapshot from your last publish, so edits in the editor don't affect it until you republish. See [Publish](https://docs.lovable.dev/features/publish.md).

> [accordion] How many visitors can my site handle?
>
> Your plan does not cap visitors or bandwidth, and published apps scale with traffic automatically. The one exception is workspaces without a paid plan, which have a per-project limit on server requests. See [Traffic and scale](#traffic-and-scale) for the figure and what counts toward it.
>
> Planning something unusually large? [Contact support](https://lovable.dev/support) in advance.

> [accordion] Can I take my site down?
>
> Yes. Click **Publish**, open the **⋮** menu in the top-right corner of the dialog, and select **Unpublish**, or go to **Project settings → Unpublish project**. The site stops serving, and you can publish again whenever you're ready.

> [accordion] Is HTTPS included?
>
> Yes. Every published URL is served over HTTPS, and Lovable sets up the SSL certificate automatically, including for custom domains. See [Custom domain](https://docs.lovable.dev/features/custom-domain).

> [accordion] Does my app's own server code have the same limits as an edge function?
>
> No. The two run on separate services and do not share limits, so do not apply [edge function limits](https://docs.lovable.dev/features/edge-functions.md#what-are-the-limits-for-an-edge-function) to it. See [Where your app's server code runs](https://docs.lovable.dev/features/edge-functions.md#where-your-apps-server-code-runs).

> [accordion] Can my runtime limits be raised?
>
> Not with a setting in Lovable. [Contact support](https://docs.lovable.dev/introduction/support-policy.md#contact-support) about the specific limit and the runtime it applies to.
>
> A larger database instance does not raise them on its own. See [Decide between a larger instance and more storage](https://docs.lovable.dev/features/database-performance.md#decide-between-a-larger-instance-and-more-storage).

> [accordion] Can visitors seek through a video my app serves?
>
> Yes. Hosted static files support range requests, which is what lets a player jump to a point in a video without downloading the whole file first.

> [accordion] Can my app cache data between requests?
>
> Yes. Hosted apps have a simple project cache that stores text values by key, with its own size caps. The project cache is not the standard Workers Cache API, so code written against that API does not work.

> [accordion] Which TanStack Start build modes can I publish?
>
> Lovable hosting serves server-rendered output and static output. Static output has to include a root `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.

> [accordion] Are requests queued when traffic spikes?
>
> No. Requests above the limit are refused, not queued, and the limit applies to workspaces without a paid plan.
>
> A visitor who opens a page above it sees an **App temporarily unavailable** page and can try again after a minute. See [Traffic and scale](#traffic-and-scale) for the figure, what counts toward it, and what a call made in the background gets instead.
