Skip to content

Migrate to exe.dev

Moving house is mostly packing. These recipes do the packing: they copy what you run elsewhere onto an exe.dev VM, check the copy against the original while the original keeps serving, and leave the moment of the move to you. Until then, the original serves as before, and your copy is private behind exe.dev's proxy.

All 2 Migration recipes

Droplets from DigitalOcean Migration Same server, new home. Rehearsed while the droplet keeps serving. Migrate a DigitalOcean Droplet to exe.dev Durable Objects from Cloudflare Migration Same Worker, same objects, new home. Every key and row checked. Migrate a Durable Object from Cloudflare

Frequently asked questions

Is my app down while it moves?

Only for the final copy. The rehearsal copies everything while the original keeps serving; the move stops it, copies what changed since, and then your domain points at the VM.

Can I go back?

Until your domain moves, yes: the original keeps its data and carries on as before. After that, new data lives only on the VM.

Who can reach the copy?

Only you, until you share the VM or make it public with ssh exe.dev share set-public <vm> as part of the move.

Don't see what you need?

Anything that runs on Linux runs on exe.dev. Describe it, and Shelley sets it up on a new VM.

Describe a VM →