Production Ready
From Lovable, Bolt or Replit to production
Your app proved the idea. Here's how to make it hold up, on the platform or off it.
By Joe Minock · Last reviewed
You can take an app built on Lovable, Bolt, Replit or Base44 to production two ways: stay on the platform and harden it, or move the code, data and hosting to accounts you own. Either way, the work is the same last stretch: lock down data, move keys to the server, fix logins and payments, add backups and monitoring, and set up a safe way to keep building.
Stay or move?
- Stay when You're early, the app is simple, and the platform's hosting and database cover what you need. Fix the security and keep going.
- Move when You need your own backend, a mobile app, integrations the builder can't do, an enterprise customer's security review, or control over where data lives. Owning your code and hosting also lowers platform risk: in April 2026, a Lovable flaw left some projects' code, chats and database keys readable for 48 days (The Register).
How a move works
- Code Connect the project to GitHub, so the code lives in a repo you own.
- Data Export the database. On Lovable Cloud, plan the move to your own Supabase project; Lovable's own docs say there's no one-click migration.
- Secrets Keys don't travel with the code. Re-create them in your new hosting, and rotate any key that was ever in browser code.
- Hosting and domain Move hosting to accounts you own, for example Vercel, Render or AWS, and point your domain at it.
- Harden it Row-level security, server-side login checks, Stripe webhooks, backups, monitoring and spending caps.
Keep building with AI
Moving off a builder doesn't mean giving up AI. Many founders move to Claude Code or Cursor. We set up the guardrails: your own repo, a test copy of your data, review before changes go live, and spending limits on every key. It's how we build Deliberate ourselves.
Notes for Bolt, Replit and Base44
- Bolt If code changes on GitHub and in Bolt at the same time, one can overwrite the other. Pick one place to edit.
- Replit Keep development and production databases separate, and keep the agent away from live data. Replit split them after its agent deleted a live database in July 2025 (Fortune).
- Base44 Confirm that private apps are really private. In July 2025, Wiz found a flaw that let anyone register on private Base44 apps.
Want help?
Start with our Production Ready review: a senior read of your app, delivered within a week, with a plan to stay or move and what to fix first.
Common Questions
Frequently asked questions
Will I lose my data if I leave Lovable?
Not if you plan it. Export the database first, and move it to a Supabase project you own before you switch hosting. Lovable's own docs say there is no one-click migration from Lovable Cloud.
Can I move from Lovable to Claude Code or Cursor?
Yes, and many founders do. Connect the project to GitHub, open the repo in Claude Code or Cursor, and keep building, with guardrails: a test copy of your data, review before changes go live, and spending limits.
Can my app scale to thousands of users?
Yes, if the data model, queries, hosting and limits are right. What usually breaks first is slow database queries, missing indexes, and calls to AI or other services with no limits.
Can you help me get my app into the App Store?
Often, but it takes a native wrapper or a rebuild, and Apple looks closely at apps that run downloaded code. In 2026 Apple blocked updates to some apps that let people vibe code on the iPhone. We'll tell you which path fits after the review.
Proof
How we built Deliberate with Claude Code
Deliberate is our own Mac app, built by a three-person team with Claude Code. We built the app, its registration and billing site, and integrations with Gmail, Outlook, Slack, Asana, Zoom and Granola. It runs on your Mac, never saves the full text of your email, and sends nothing without your yes.
Meet DeliberatePlanning a move?
Tell us where your app runs today and where it needs to go. We'll map the move.