Deploy Lovable to Netlify: Your Migration Guide
Move your Lovable app to production with confidence. Learn the exact steps to deploy to Netlify, Northflank, or Ship. Handle SPA routing, environment variables, and backend separation.
Why Migrate from Lovable Cloud?
Lovable Cloud is great for getting started. But you might want to move for reasons: lower costs, vendor independence, custom backends, or running on your own infrastructure.
The process is straightforward. Your Lovable app is standard React - it's portable.
Step 1: Export Your Code to GitHub
Lovable's Git sync feature keeps a GitHub repository in sync with your project. If you haven't already, connect your Lovable project to a GitHub repo.
Once connected, every change you make in Lovable is committed to GitHub. This is your export step.
Step 2: Set Up on Your Target Platform
Netlify, Vercel, Cloudflare, Northflank, and Ship all support Git-based deployments.
The basic flow: create an account, connect your GitHub repo, select the branch to deploy, and allow the platform to detect your build settings. Each platform has documentation for this step. Netlify publishes an official deployment guide. Northflank published a Lovable-specific guide in May 2026.
Step 3: Configure Environment Variables
Lovable apps often use Supabase for auth and storage. These integrations need API keys.
Here's what matters: Vite embeds environment variables at build time. Variables prefixed with VITE_ are compiled into your app bundle. This means you must set environment variables before your platform builds your code, not after deployment.
Missing or wrong env vars at build time will cause your app to fail. Set them in your platform's settings, then redeploy.
Step 4: Enable SPA Routing
Lovable uses client-side routing. When a user visits a direct URL (e.g., /dashboard), the web server needs to return your app's main index.html file, not a 404.
This is standard for single-page apps. Without this configuration, direct links and page refreshes break.
Your platform needs to know: if a route doesn't match a static file, serve index.html.
Most platforms support this. Netlify uses a _redirects file. Northflank has a rewrite rule setting. Ship has a checkbox in application settings.
Step 5: Deploy and Verify
Trigger a new deployment. Your platform builds the code, installs dependencies, and publishes to production.
Test everything: click links, refresh pages directly, use your browser's back button. All routes should work without 404 errors.
Backend Migration: Three Paths
Lovable Cloud includes a Supabase stack for auth and storage. When you move the frontend, you have three options for the backend:
Option 1: Keep Lovable Cloud for the backend. Your frontend runs on Netlify (or elsewhere). Your backend stays on Lovable Cloud. This is simplest - no data migration needed. Downside: your stack is split across two vendors.
Option 2: Migrate to managed Supabase. Point your deployed app to your own Supabase project. Lower risk than self-hosting. Still a third-party dependency, but you own the data.
Option 3: Self-host your database. Some platforms like Ship and Northflank include built-in databases. Migrate your Lovable data and manage the database yourself. Most control, most operational work.
Most teams start with Option 1, then evaluate data residency and cost as they grow.
Platform Comparison
Side-by-side look at how Netlify, Northflank, and Ship stack up for Lovable deployments.
Pricing as of August 2026. Netlify pricing uses credit system; actual costs vary by usage.
Monthly savings with built-in mail.
Ship includes an SMTP mail server. Netlify deployments typically add a third-party service like Mailgun, Sendgrid, or Resend. Ship eliminates that cost category.
Why Ship for Lovable Deployments?
Ship is built for teams that want portability and cost control. It launched July 17, 2026.
Zero-downtime deploys
Deploy new versions without dropping traffic. No 503 errors, no downtime windows. Roll back instantly if needed. This matters once your Lovable app has real users.
Complete platform included
Databases, email, object storage, and secrets management all built in. No hunting for SaaS add-ons. One platform, one bill, no fragmented costs.
Open-source, zero lock-in
Ship is Apache 2.0 licensed. Deploy on your own VPS, Hetzner, or any cloud. Export your data and configuration anytime. True vendor independence.
Built for teams who need reliability
Built for Production
Ship is designed for teams that need reliability, transparency, and control.
Open-source (Apache 2.0)
Full source code transparency. No proprietary restrictions. Fork it, modify it, run it anywhere.
Self-hostable anywhere
Deploy on Hetzner, DigitalOcean, AWS, or your own datacenter. You choose your infrastructure.
Zero-downtime deploys
Update your app without interrupting service. Users never see downtime or errors.
Production-ready
Battle-tested on real production workloads. Millions of deployments daily.
Migration Questions
Common questions about migrating Lovable to Netlify, Northflank, or Ship.
No. Your code lives in GitHub via Lovable's Git sync. That's yours to keep. You can deploy it anywhere. Lovable Cloud can continue hosting your app alongside your new platform - there's no rip and replace. You're in control.
Ready to deploy Lovable?
Choose your platform and take control of your app's infrastructure.