Executive Summary
Vercel has launched automatic persistence for its Sandboxes feature, now available in beta. This update automatically saves a sandbox's filesystem state when it is stopped and restores it upon resumption, creating durable, long-running development environments without manual snapshotting. The new model separates storage from compute, meaning users are only billed for active compute sessions, not for the stored state, making it more efficient for developers to manage persistent remote workspaces.
Key Takeaways
* Automatic State Persistence: Filesystem state is automatically saved when a sandbox session is stopped and restored when it resumes, eliminating the need for manual snapshots.
* Separation of Compute & Storage: A sandbox's identity and filesystem state are now distinct from its active compute session, allowing for stateful, on-demand environments.
* Usage-Based Costing: Users are only charged when a sandbox session is actively running, not for the stored filesystem state.
* Named Sandboxes: Sandboxes are now identified by a persistent name, allowing developers to easily retrieve and resume specific work environments.
* New Management Tools: The beta SDK and CLI have been updated with new methods for managing the entire sandbox lifecycle, including creating, resuming, updating resources, inspecting sessions, and deleting sandboxes.
* Availability: The feature is available in beta on all Vercel plans and requires an upgrade to the beta versions of the SDK (`@vercel/sandbox@beta`) and CLI (`sandbox@beta`).
Strategic Importance
This update makes Vercel Sandboxes a more powerful and persistent cloud development environment, improving the developer experience for long-term projects and aligning its capabilities more closely with competitors like GitHub Codespaces.