Export your Lovable.dev code to Git. Deploy with Ship.
You built it in Lovable. You exported to GitHub. Now comes the hard part: picking a host that won't surprise you with a $400 bill. This guide walks through Ship's workflow in 15 minutes—no credit-based billing, no per-app fees, no vendor lock-in.
What You Get When You Export Lovable.dev to Git
When you export Lovable.dev code to Git, you get a full-stack app: React frontend, TypeScript, Tailwind CSS, Supabase backend, and Edge Functions. Everything your app needs to run independently.
Except three critical things.
Your .env secrets stay in Lovable's vault. GitHub clone gets a .env.example with blank values. You rebuild the secrets file locally before deployment.
Live database data doesn't export. You get the schema and migrations, but your Lovable project's data—user accounts, uploaded files, everything—stays locked in Lovable's Supabase instance. You decide: start fresh, or manually migrate your data to your own PostgreSQL.
Lovable stops updating your code. Two-way sync ends at export. Stay in Lovable and lose code ownership. Export and move to your IDE (Ship, Vercel, or elsewhere) and Lovable becomes a code generator you used once.
Understanding these three points prevents the surprise tech debt 30 days after export.
Search results for 'lovable.dev export to git'
Real demand. Thousands of developers export Lovable apps every month. Hosting them is your next decision—and it matters.
Hosting Your Exported Lovable App: Side-by-Side
All platforms run the same React + Supabase code. The differences are cost, ops burden, and surprise bills.
Pricing as of August 2026. Lovable exports use Supabase regardless of host; Ship focuses on your app container cost.
Vercel vs Netlify vs Cloudflare: The Tradeoff
Vercel ($20/user/mo): Best for marketing sites. Cold starts can hit 60ms. Per-function billing surprises happen.
Netlify ($20/mo credit-based): Recent shift to hard credit caps (Sept 2025). Sites pause when credits run out mid-month. EU performance is slow (340x variance noted).
Cloudflare Pages ($5/mo flat): Fastest globally. No per-function fees. Limited Workers KV. Best for frontends; backend complexity gets expensive.
Railway, Render, xCloud: The Contenders
Railway ($5/mo): Usage credit model (similar Netlify risk). Restored free tier in 2025 but limited.
Render ($7/mo starter): $40/mo once you add database. Free tier sleeps aggressively. Works well for non-critical apps.
xCloud ($5/mo/server): Flat-rate. Unlimited apps on one server. GTmetrix 97-99%. Small team favorite. No credit surprises.
Why Ship Wins for Lovable Exports
You exported to own your code. Ship lets you own your hosting too.
Flat-rate pricing, no surprises
Your Lovable app costs the same whether it serves 10 users or 10,000. No per-invocation overages. No credit counters ticking down. Hardware size determines price. Predictable bills let you focus on product, not vendor accounting.
EU data. Actual GDPR compliance.
Lovable Cloud stores data in US data centers (implied). Ship runs on German infrastructure, 100% EU. If you have customers in Europe or work with EU data, you move from 'technically non-compliant' to 'fully GDPR-ready' in one deployment.
Zero DevOps. We manage the servers.
Export to GitHub, Ship deploys via git push. No Docker knowledge needed. No SSH into servers. Opsily handles backups, monitoring, SSL, scaling, recovery. You ship code. We ship infrastructure.
Built for teams who need reliability
From Export to Live in 15 Minutes
Your lovable.dev code is already in GitHub. Ship handles the rest.
Choose Your App
Select an app to get started.
Connect your GitHub repo
Authorize Ship to access your exported lovable repo. Ship reads your Dockerfile and environment variables.
Set environment variables
Paste in your .env secrets: Supabase keys, API keys, database credentials. Ship encrypts and stores them securely.
Deploy and scale
Ship builds your container, runs migrations, and serves your Lovable app live. Choose your server size (RAM/CPU) based on expected traffic.
Git push to update
Every GitHub commit auto-deploys. No CI/CD config. No manual build steps. Your dev workflow doesn't change.
Predictable hosting for your Lovable app
All Ship plans include 99.9% uptime, automated daily backups, GDPR-compliant German hosting, and 24/7 monitoring. Choose the server size that fits your app.
Loading pricing...
Enterprise security, zero enterprise pricing
Your exported Lovable code deserves the same trust guarantees you'd get from running production infrastructure elsewhere.
GDPR Compliant
100% German data centers. EU standard-compliant. Full data portability on request.
Automated Daily Backups
Every app backed up to encrypted storage. Point-in-time recovery available. No manual intervention needed.
99.9% Uptime SLA
Monitored 24/7 with automatic failover. Downtime credits apply if we miss the target.
SSL & Security Certificates
Automatic HTTPS provisioning via Let's Encrypt. Renewed silently. No expired cert surprises.
Encrypted Storage & Transit
Data encrypted at rest and in transit. Secrets never logged. Environment variables stored in a vault.
Monitoring & Alerting
Real-time monitoring of CPU, RAM, disk, and uptime. Alerts sent if anything is wrong. Automatic recovery scripts run.
Questions about exporting and deploying
Most Lovable users ask these when moving from Lovable Cloud to Ship.
Lovable generates a complete repo with your React frontend (Vite + TanStack), TypeScript code, Tailwind CSS styling, and Supabase backend setup (migrations and Edge Functions). You get a Dockerfile ready for deployment and a .env.example file. What you don't get: your .env secrets (they stay in Lovable) or your live database data (schema only, no rows). You're responsible for copying secrets locally and deciding whether to migrate existing data.
Ready to deploy your Lovable app?
Ship handles EU compliance, backups, and scaling. You focus on building.