Many of you asked how we moved our Lovable app to our own VP

A lot of people asked me how we moved our Lovable application away from the hosted setup and onto infrastructure we control.

The process involved more than copying the frontend. We had to migrate:

• The code through GitHub
• Database and user accounts
• Storage files
• Backend functions
• API keys and secrets
• Payments and webhooks
• System emails
• Cron jobs
• HTTPS, DNS and rollback procedures

The final workflow is:

Lovable → GitHub → local development → VPS + database/backend

After the migration:

Local changes → GitHub → automated deployment → VPS + database/backend

We also created a private web-based workflow with YepAnywhere, allowing us to work on the application from anywhere using Codex or Claude subscriptions without adding a separate API key for every task.

I documented the complete process here, including the practical migration steps, VPS comparison, security considerations, testing checklist and the mistakes we encountered:

How to Save Up to 99% on Lovable Costs by Moving to Your Own VPS

And here is the follow-up about the remote web CLI workflow:

How We Built a Web CLI for Codex and Claude with YepAnywhere

The “up to 99%” figure depends heavily on your current plan, traffic, storage, backups and maintenance requirements. It is not a guaranteed saving, but for some projects the difference can be substantial. We went from 300 to 400 per month for credits down to 29 € for the VPS and 10€ for supabase.