exe.dev buying guide: A draft surviving a reboot is not proof you can rebuild elsewhere
Use a fictional exhibition label to distinguish resuming work on one machine from reconstructing it on another. A persistent disk addresses the first; an independent handoff package addresses the second.
exe.dev explains in its note on persistent design that its virtual machines do not suspend for lack of incoming traffic and that a reboot does not wipe the disk. A workspace that keeps its drafts can be convenient when you repeatedly revise one prototype. But being able to resume in the original environment does not mean you have the material you need to leave it. Check those two requirements separately.
One draft, two handoffs
Imagine changing a fictional exhibition label from “four objects in the blue group” to “three,” and changing the display order from B then A to A then B. Put the revised version in an envelope marked “working disk.” In a separate handoff package, update the count but omit the updated order card.
First give the next reviewer a card saying “after reboot, use the original envelope,” and ask for the count and order. Then use the card saying “no original envelope, only the handoff package.” Three objects are confirmed, but there is no basis to say that A comes first. Mark count and order separately and do not count a perfect first round as two passes. This illustrates the acceptance check; it does not simulate a service failure or predict vendor recovery.
Do you need to resume or to work without the original environment?
Compare persistent VMs when a long-running project relies on intermediate drafts, provided the team can specify what to store separately and who updates it. If every batch already starts from an independently delivered final version, keeping the last working disk can instead create cleanup work. Budget for tidying, handoff, and an independent rehearsal where needed. The vendor's reboot behavior cannot replace verification of the handoff package. No environment is connected, configured, run, or rebuilt here.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:exe.dev