Yes, you can take an app you built in Lovable and run it somewhere else. Lovable's own documentation is clear on this: the editor and AI agent cannot be self-hosted, but the applications you build with it can be hosted anywhere. The smoothest setup is to sync the project to GitHub and let your host deploy from the repository. You keep editing in Lovable, the changes land in GitHub, and the live site updates on its own.
This guide walks through that setup on RoamerHost's Vibe Coding Hosting, and covers what to check before you move.
Why people move Lovable apps out
The usual reasons are wanting their own domain, wanting to control their own data, or needing local billing and support. Cost is the other one: Lovable's official blog explains that building and running apps now draw from one credit balance, so hosting and your app's AI features keep using credits after launch. Once a site is built and mostly stable, some people prefer to handle the hosting part separately.
First, check which kind of project you have
Lovable's self-hosting guide describes two kinds of projects. Older projects are React plus Vite. They build into static files in a dist folder, and the Supabase URL and publishable key are passed in at build time through VITE_SUPABASE_ environment variables. Newer projects use TanStack Start, which builds into a Node server that keeps running. Lovable's instructions build it in node-server mode and run .output/server/index.mjs, with the Supabase settings and any secrets your server functions read set as environment variables on the server.
Vibe Coding Hosting runs static sites and Node.js 22 or 24 apps. We have deployed the Lovable-style React, Vite and Supabase structure successfully. We have not tested TanStack Start projects yet, and your app needs to listen on the PORT environment variable the platform provides. Try a first deploy before you switch your domain over: if a deploy fails, the previous version stays live.
Two more things to know
If your project uses Lovable's built-in backend (Lovable Cloud), the docs say the supported destinations for moving it are managed Supabase or self-hosted Supabase. Secrets stored in Lovable stay out of the repository, and the credentials behind connectors and Lovable AI cannot be copied out. If your app relies on those, set up replacements on the Supabase side first.
Also, Lovable's Git sync always creates a new repository rather than linking an existing one, and it syncs one branch at a time. Repositories created by Lovable are private by default.
Auto-deploy from GitHub to Vibe Coding Hosting
- Turn on GitHub sync in your Lovable project and let it create the repository.
- On your Vibe Coding Hosting project page, open GitHub auto-deploy and enter the repository and branch. For a private repository, add the deploy key shown on the project page to the repo's Deploy keys. Write access is not needed.
- Follow the steps on the project page to add the webhook in GitHub, then click "Update from GitHub and deploy" once yourself.
- From then on, when you edit in Lovable and it pushes to GitHub, the site redeploys automatically.
The platform builds the new version and checks that it responds before switching traffic to it. If the build fails, the old version keeps running. Every deploy keeps a snapshot, and the last three can be rolled back to. Public variables in your .env that start with VITE_ (such as the Supabase URL) are passed into the build automatically, and the deploy log lists which variable names were used. The .env file itself is never deployed.
One thing to keep in mind: once GitHub is connected, GitHub is the source of truth. Files edited directly on the host will be overwritten by the next sync, so make changes in Lovable or in the repository.
Settings to update in Supabase
Your app now lives at a new address, so add it to the Site URL and Redirect URLs in Supabase Auth. Otherwise users may be sent back to the old address after signing in, or see an error. Never put the service_role key in a VITE_ variable: those values are bundled into the front end where anyone can read them. Make sure Row Level Security is enabled on your tables.
Pricing and limits
Vibe Coding Hosting is billed yearly. The Basic plan is NT$3,588 a year (about NT$299 a month on annual billing) and you deploy and manage it with your own AI tools over MCP. The Advanced plan is NT$11,988 a year (about NT$999 a month on annual billing) and includes Roamer AI, which helps with migrated apps on a best-effort basis. See the Vibe Coding Hosting annual plans for the differences.
The limits, up front: one site per plan, with up to one custom domain. Auto-deploy works with GitHub only, does not fetch Git LFS files or submodules, and the compressed code must be under 95 MB and 100,000 files. Dockerfiles are not supported.
If you have finished an app in Lovable and want it on your own domain with billing in New Taiwan dollars, local invoices and Traditional Chinese support, sync it to GitHub and connect it to RoamerHost Vibe Coding Hosting. RoamerHost is run by a team in Taiwan.
FAQ
Can I keep editing in Lovable after moving the app out?
Yes. Lovable syncs with GitHub in both directions, and its recommended setup keeps development and previews in Lovable while your host deploys from the repository. Changes you make in Lovable reach GitHub and the site updates automatically.
Does this work for projects built with Bolt?
Bolt-style React and Supabase projects are structured much like Lovable ones, so once the code is on GitHub the steps are the same. If you would rather not use GitHub, you can upload a ZIP from the project page or let your own AI tool deploy over MCP.