Lovable · 7 min read · Updated August 2026
Deploy a Lovable app on infrastructure you control
Short answer
Connect the Lovable project to GitHub first, treat that repository as the deployment source, then move the application, secrets, domain, database, and release process onto infrastructure your team can operate. The goal is not to replace Lovable. It is to keep building with it while production runs on a stack you control.
Choose the right path
| Keep Lovable publishing | Use it when its managed deployment and your current plan are the right fit. A custom domain and platform publishing may be sufficient for a simple public site. |
|---|---|
| Move to your infrastructure | Use this when you need control over server cost, deployment behavior, observability, databases, or the full production environment. |
| First requirement | Connect GitHub before changing hosting. The repository becomes the durable codebase and allows a repeatable deployment pipeline. |
Walkthrough
- 01
Connect the project to GitHub
Lovable documents a two-way GitHub sync for connected projects. Confirm who owns the GitHub organization and do not rename or move the linked repository without planning for the connection.
- 02
Map the live dependencies
List every environment variable, integration, database, storage bucket, auth provider, domain record, webhook, and email configuration. Code moves easily. Production dependencies are where launches commonly break.
- 03
Create the production target
Choose the smallest credible target for the workload: a managed container service for a containerized app, or a VM when full operating-system control is required. Add the database and backups deliberately, not as an afterthought.
- 04
Build a release pipeline
Deploy from the default branch through a repeatable pipeline. It should build the app, run a health check, expose the correct domain, and leave a rollback path if the release is unhealthy.
- 05
Cut over with a recovery plan
Test the new URL before DNS cutover, confirm the database and background jobs work, then update the domain. Keep the previous path available until the new production flow is verified.
Before calling it production-ready
- GitHub organization and repository owned by the customer
- Production secrets moved outside the source code
- Domain and HTTPS tested before cutover
- Database migration and restore plan
- Health check and rollback path
- Handover notes for the team
Questions founders ask
Can I still use Lovable after moving the app?
Yes. Lovable documents GitHub sync so teams can continue working with the project while maintaining a repository for collaboration and deployment.
Does self-hosting mean I lose my Lovable project?
No. It changes where production runs. Keep the project and repository organized so the code, deployment pipeline, and ownership remain clear.
What does RepoAssistant do here?
We review the code and dependencies, fix deployment blockers, set up the target infrastructure and pipeline, test the release, and hand over access and documentation.
Where RepoAssistant fits
We help startup teams turn the right path into a working setup: review the current infrastructure, use available Azure credits deliberately, deploy the app, and leave the team with ownership and handover notes.