Documentation
Persistent disks for sandboxes
Coming soon. Host-local persistent disks are in development and are not available yet.
Use case: keep development data
A persistent disk will keep a development database or downloaded dependencies separately from a sandbox’s temporary system disk. It will belong to one workspace and one physical host. Only one sandbox will write to it at a time.
Host-bound storage
The sandbox must run on the host holding the disk. If that host is unavailable, the disk is unavailable. There is no automatic failover. Today, /workspace files survive a stop and start only until the sandbox expires. That is not a persistent disk.
Snapshots are not off-host backups
The design takes local snapshots only while the disk is detached. Losing the host’s storage could lose both the disk and its local snapshots. Customer create, attach, restore and delete actions are not yet available.
Capacity and billing
Runzivo will measure allocated capacity until deletion, including while a sandbox is stopped. No new disk charge is active and no disk price is published.