How to export Lovable to GitHub and deploy the code outside Lovable in 2026
Published on 2026-10-27 by frfrand
Export Lovable to GitHub: Git sync, ZIP, Vite or TanStack Start, dependencies, variables and tests to migrate without breaking the app.
Quick answer: The first thing you need to make your application independent is not to buy a server: it's to have a copy of the code that you can build without opening Lovable. Current documentation offers Git sync and code download on certain plans. Git sync allows you to keep editing while working with external tools, but it's worth understanding which branch is the one that actually goes to production.
Open the exported repository: check package.json, scripts, lockfile, and folders. If you find Vite, you'll generally use npm ci and npm run build to produce dist/. If it uses @tanstack/react-start, deployment is not resolved by copying dist/ to Nginx; a platform capable of running the server is needed. If there is Supabase configuration, public client keys are not treated as server passwords, but real secrets must never be uploaded to Git.
What changes when you stop showing a demo
A ZIP is useful for delivering a specific state; GitHub adds history, revisions, diffs, and reproducible deployments. If you continue using the Lovable editor, respect the Git sync flow and check their docs for repository and branch limitations. ArduMaker can receive Git projects as part of a deployment flow, with specific configuration according to stack.
Practical example: how it looks in a real business
Example: you export a subscriptions page. The build command works, but when entering /panel and refreshing the browser a 404 appears. In a Vite SPA configure the route fallback in Nginx. If the error appears in a server-side endpoint of TanStack, the problem is different: you probably don't have the correct runtime. Before touching code blindly, identify the architecture.
Concrete steps to move to production
1. Enable Git sync in Lovable and verify that the repository remains under your control. 2. Clone and run installation using the lockfile; note the Node version and scripts. 3. Read the dependency tree to distinguish Vite SPA, TanStack Start, and backend functions. 4. Build in a clean environment, fix missing assets and variables. 5. Test deep routes, forms, and API calls with the target server.
Frequently asked questions
### Does GitHub contain my app's passwords? It shouldn't; secrets are managed separately. If credentials appear in the history, revoke them.
Is a ZIP the same as a migration?
No. It's just a snapshot of the code; it doesn't necessarily include data, emails, users, or hosting.
Can I keep creating with Lovable and publish elsewhere?
Yes, when the Git flow and dependencies allow keeping both environments synchronized.
Should I use npm install or npm ci?
For reproducible deployments, npm ci is usually preferable if there is a consistent package-lock.json.
What role does ArduMaker play?
ArduMaker provides infrastructure tools to host applications on VPS and prepare deployments according to each project's architecture. This does not mean that code generated by an AI is automatically correct, secure, or portable. The work consists of reviewing dependencies, validating functions, configuring services, moving data when appropriate, and checking production deployment. The specific service for migrating and deploying applications created with AI will be presented at ardumaker.com/lovable (page coming soon). While it is being prepared, you can consult ArduMaker to learn about the current platform. Do not confuse this future landing page with an already operational migration tool.
How to use this guide without making mistakes
The correct path depends on the stack and external services. Before modifying a site with real users, keep a verifiable backup and test with staging accounts and data. Commands and configurations are indicative: compare them with the current provider version, the VPS distribution, and applicable data protection obligations.
Sources and official references
- Technical documentation - Technical documentation - Technical documentation
Published in October 2026. AI platforms and their integrations change; check current requirements before contracting or migrating.
What the photograph shows
Visual review of a version flow and commits. Illustrative photograph generated to accompany this guide on migrating applications created with AI; it is not a screenshot of the platform nor does it certify a specific installation.
Continue with these practical ArduMaker guides
- From Lovable to production with ArduMaker: how to have your own stable and maintainable website - Moving a Lovable website to a VPS: Nginx, SSL and a professional domain - React + Vite created with AI: publishing a SPA with Nginx, SSL and domain
If you are evaluating your own application, compare the actual backend, database, authorization and deployment requirements before choosing the server.