Taking a Lovable app to production

Lovable syncs the project with GitHub in both directions, and the codebase can also be downloaded (GitHub integration). Lovable states that the code can be hosted elsewhere (external hosting).

Check which kind of project you have: older projects build to a static React and Vite site, while projects created from May 2026 are TanStack Start apps that need a host able to run server code (external hosting).

There are two setups. Lovable Cloud is a backend managed by Lovable on Supabase’s open-source base, with no Supabase project in your own account (Lovable Cloud). Your own Supabase project lives in your Supabase account, under your billing (Supabase integration).

With your own Supabase project, the backend is already yours. With Lovable Cloud, the documentation describes an export of the database — schema, data, user accounts and password hashes — with size limits, and states that storage files, edge function code, secrets, sign-in provider settings and API keys are not in that export (database, self-hosting).

Lovable uses one credit balance for building, hosting, the built-in backend and AI features in deployed apps. With no credits left, published pages stay live, AI features stop and a Cloud backend can pause (plans and credits).

1. Connect GitHub— so the code has a home outside the builder.
2. Decide where the backend lives— your own Supabase project, or an export from Lovable Cloud recreated from migrations and then filled with the data.
3. Move what the export leaves out— storage files, secrets, sign-in providers and their redirect addresses.
4. Pick a host that can run your build— static files, or a server runtime for newer projects.
5. Rehearse before switching— on a disposable copy, with real sign-in. If the authentication signing secret changes, users sign in again.