Migrate Replit Agent to your VPS: processes, secrets, GitHub, and custom domain
Published on 2026-10-27 by frfrand
From Replit Agent to a VPS with GitHub, systemd processes, Nginx proxy, environment variables, databases, and HTTPS.
Your Replit project shouldn't depend on a tab
Replit makes it easy to develop an app in the cloud with its agent. It also offers managed deployment options: you don't have to leave Replit for something to be production. But if you want to control the runtime or combine services on another infrastructure, GitHub is a good bridge to export the code and rebuild the execution environment.
Don't forget what isn't in the repository
Note versions, system packages, start command, variables, credentials, storage, tasks, and database locations. A FastAPI app starts differently than a Node + Express or static React app. Databases hosted by providers require separate export and restoration. Secrets must be reconfigured securely on the new server.
Example: inventory that crashes when you close SSH
A merchant receives their inventory panel, clones it from Git, and opens it with npm run dev. When closing the terminal, the site stops responding. It's an operational error, not necessarily a code error. You prepare a production build and a systemd service that starts after every reboot. Nginx publishes HTTPS and the internal port remains protected. Then you create and modify a product with a test user, reboot the VPS, and confirm that the data survives.
How to do the migration
1. Keep in Git a stable commit and the origin state. 2. Note down runtime version, scripts, ports, and dependencies. 3. Make an inventory of database, files, secrets, and scheduled tasks. 4. Bring up build and persistent process in staging. 5. Configure Nginx, HTTPS, domain, logs, and backups. 6. Run smoke tests and a restart before the final cutover.
Decide without fanaticism
Replit reduces initial configuration; the VPS offers another level of control and responsibility. For a personal prototype it may not be worth moving it; for a complex integration with several APIs and processes it can be useful.
Frequently asked questions
### Does GitHub copy the database? No. Treat it as a separate migration. ### Do I have to keep the browser open? No, not in a service properly deployed. ### Is Docker essential? No, but it helps package dependencies and reproduce deployments. ### When do I connect the domain? After passing staging tests and HTTPS.
Sources
Replit: Git and GitHub integration · Docker Compose in production.
ArduMaker and the future migration service
Once the code has been audited, ArduMaker can serve as deployment infrastructure according to the stack: VPS, services, domain, certificates, and operation tools. This does not guarantee that the AI-generated application is already secure, nor that moving data is automatic. The page ardumaker.com/lovable is being prepared to present a migration and deployment service from AI builders to production environments; it is not yet published. For now, you can learn about the platform at ardumaker.com. The decision to migrate should be based on concrete requirements, not on a supposed obligation to abandon the current provider.
Updated: October 2026. The features, plans, and exports of these platforms may change. Check the current documentation and back up real data before intervening.
What the photograph shows
Developer reviewing the application from the console. 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 Bolt.new to production: GitHub, server, and stable deployment with ArduMaker - Node.js Express generated with AI: publishing a stable API without downtime - Checklist: 30 verifications before publishing an app made with Lovable or AI
If you are evaluating your own application, compare the real backend, database, authorization, and deployment requirements before choosing the server.