Resize sandboxes lets you adjust CPU, memory, and disk on an existing sandbox without having to delete and recreate it.
You can scale compute on a running sandbox when a workload needs more resources, or update the full resource specification on a stopped sandbox before restarting. This keeps the same environment and avoids rebuild overhead.
Resource scaling
Resource requirements change as workloads move across CI, testing, and production stages. Initial sandbox allocations are not always sufficient once workload intensity increases. Without in-place resizing, the workflow is stop, recreate, and reconstruct environment state.
Resize Sandboxes removes that overhead. You can increase CPU or memory on a running sandbox without interruption or state loss. For disk changes or full resource reconfiguration, stop the sandbox, apply the new specification, and start it again with updated resources.
Resize behavior
CPU and memory can be increased while a sandbox is running. The sandbox keeps operating during the resize, which covers the common case where compute demand grows after startup.
To decrease CPU or memory, or to increase disk capacity, the sandbox must be stopped first. Disk size can only be increased and cannot be decreased. Once resized, the sandbox can be started again with the updated resource allocation.
Get Started
Resize sandboxes is available to all Daytona organizations. Read the sandboxes documentation to get started.
