← All guides
Cursor migration guide
Move your Cursor-built app from local to a production VPS
CursorVPSDomain
Short answer
The Cursor-built app running on your own VPS with HTTPS, a repeatable deploy path, and fewer subscriptions to keep paying for.
Why this matters
The app feels finished in Cursor or on your laptop, but the server still fails because the production environment is not the same as your local one.
Walkthrough
- 01
Document what Cursor relied on
Get the app out of local mode and list every dependency that might break when the code leaves your machine.
- Record build and start scripts plus the Node version.
- List every env var and external service the app touches.
- Identify anything that only exists on your laptop right now.
- 02
Restore the server environment
The server needs the same production inputs Cursor had locally, but configured the right way.
- Set env vars on the VPS or deploy panel.
- Update callback URLs, auth redirects, and webhook endpoints.
- Run the app under a process manager so it survives restarts.
- 03
Deploy and prove the savings
Once the app is live, the value is in ownership, reliability, and lower recurring cost.
- Smoke test the live domain end to end.
- Add backups and a rollback note before switching traffic.
- Compare your old platform bill against the new VPS cost.
Where RepoAssistant fits
RepoAssistant moves Cursor apps to a VPS you own so launch stops depending on your local machine.