Done for you
Move an existing application into your own cloud
We create and verify a new deployment alongside your current one, from Heroku, Render, Railway, Vercel, Replit or another host. Traffic moves only after you approve the cutover.
Your original environment
We do not modify or delete the original application resources. It remains available as a fallback while you validate the new deployment. Any DNS or traffic-routing change required for cutover is made only after your approval.
Database rollback has limits. Once writes begin on the new database, the old database no longer holds current data, so it is not automatically a complete rollback. The cutover plan states the data rollback limitations for your application before traffic moves.
What a migration plan covers
- Running the source platform in parallel while the new deployment is validated.
- Domain and DNS cutover, and when it happens.
- Database copy method. If you give us a connection string, the copy reads from your current database on your new server; we never write to the original database.
- Whether a write freeze is needed during cutover.
- Rollback limitations, including the database.
- Secrets and environment variables.
- Background workers and scheduled jobs.
- File storage, queues and webhooks.
- Email providers, and external IP allowlists that must be updated.
- Provider-specific features that may not have an exact equivalent.
Repository exposure check
Included: a check for common committed credentials and deployment-related security issues. It is not a penetration test or a complete application security audit.
If we can't complete it
If we cannot verify the new deployment or complete the cutover you approve, you get a full refund. See the Refund Policy. Move includes three months of Pro while that remains part of the offer. Your cloud provider bills you directly for the new infrastructure.