What do I need to set up Lovable on a VPS?

You need a VPS (starting at $4-6/month), SSH access, and the app code in a GitHub repo. For Lovable and Bolt.new, you also need environment variables, a domain, and SSL configured before going live.

How long does it take to move to a VPS?

A straightforward Lovable deployment takes 2-4 hours for someone familiar with servers. RepoAssistant does it in 24h with a ship-or-refund guarantee.

How much does it cost to host Lovable on a VPS?

A VPS for Lovable or Bolt.new starts at $4-6/month for a 1-2 GB instance from providers like Hetzner, DigitalOcean, or Hostinger. RepoAssistant's deploy service is a fixed $39-149 one-time fee.

What if something breaks after deployment?

Every deployment includes a smoke test (login, forms, database writes, API calls) and a handover doc with restart, rollback, and deploy commands. If the app is blocked pre-launch, we fix and ship within 24h or refund.

Launch checklist

Production-ready checklist for AI-built apps

Lovable, Bolt, Base44, v0, Replit, or Cursor can generate the app, but production is the boring layer around it: domain, SSL, secrets, database durability, backups, monitoring, recovery, and ownership.

Base44 Bolt.new Cursor Lovable Replit v0 VPS

What is probably broken

The app looks done, but nobody can answer where secrets live, how backups restore, who owns the server, or what happens when deploy breaks.

What production should look like

A launch checklist you can use before paying for hosting, sharing the app publicly, or handing it to users.

STEP 01

Lock down ownership

Before deployment, make sure the important accounts belong to the product owner, not a random builder account or the AI tool workspace.

Domain registrar, DNS, GitHub repo, hosting account, database, email, and payment provider must be owned by you.
If the app started in Lovable, Bolt, Base44, v0, Replit, or Cursor, export it into a repo and host you control.
Use a shared password manager or access handover doc, not screenshots in chat.
Remove unused collaborators after launch.

STEP 02

Move secrets out of the app

AI-built apps often work because secrets were pasted somewhere convenient. That is not production, especially after moving between builders and hosts.

Keep API keys, database URLs, JWT secrets, and webhook secrets out of git.
Use production, preview, and local env vars separately.
Rotate secrets if they were ever pasted into chat, logs, public repos, or screenshots.

STEP 03

Prove the app can recover

A production app is not production-ready until you know how to recover it.

Create database backups and test at least one restore.
Write restart, rollback, and deploy commands in plain English.
Smoke test signup, login, database writes, file uploads, email, payments, and admin actions.

Quick check

Is your app production-ready?

If you cannot tick all five, we can fix it. Send us the repo and we handle the rest.

?Custom domain with HTTPS
?Environment variables configured
?Database wired and backed up
?Auto-deploy on push
?Smoke tested and live

Free checklist

Deploying this yourself?

Get the exact 5-step checklist we run before every deploy. No fluff, just the things that actually break.

Done-for-you deploy

RepoAssistant turns AI-built apps into production setups with ownership, backups, secrets, and handover covered.

Fixed price per repo. 24h delivery or full refund. No hourly billing.

Deploy my app

Related guides