Skip to main content

​
Goal

Understand when a Compute plan can be ordered and what protects a host using thin-provisioned disks.

​
Prerequisites

  • A StackShift Compute VPS plan or an existing VPS with an extra disk.

​
Workflow

1
Check plan availability before checkout. A plan may be unavailable when the selected host lacks logical or physical disk headroom.
2
For an existing VPS, request extra storage only while the host has fresh capacity telemetry and sufficient free space.
3
If a paid order cannot be placed immediately, use its pending-capacity state rather than assuming a VM was created.

​
How capacity is checked

Compute disk sizes are logical reservations. StackShift also requires a recent measurement from the physical host: at least the requested disk size plus 100 GiB must remain available before a new VPS or extra disk is admitted. Storage is checked again before disk creation. Missing or stale host measurements block new reservations.

​
What thin provisioning means

An unused portion of a VPS disk does not occupy the same amount of host storage immediately. As customers write data, the physical files grow. The admission reserve and operator alerts reduce the risk of unnoticed pressure, but they do not preallocate every promised disk byte or guarantee that a host cannot fill. Off-server backup protection remains a separate recovery feature.

​
Operator alerts

StackShift monitors the host filesystem holding VPS disks. Operators receive warning and critical alerts below 150 GiB and 100 GiB available, plus an alert if a reporting host stops supplying fresh storage telemetry. These alerts concern the physical host, not the free space inside your VPS.

​
Expected result

You can distinguish a disk-size reservation from physical usage and understand why new storage may be temporarily unavailable.

Compute edge network

Reach a full-root VPS through opt-in HTTPS publishing or Edge SSH without assigning the guest a dedicated public IPv4.