Disks that do not punish growth
A block volume sounds simple until the day someone detaches a mounted disk, or a restore turns out to depend on whatever state happened to be current when somebody remembered. ProjectX block storage enforces the orderings you would otherwise maintain by hand — detach-first is a rule, not a runbook.
What you get
- Volumes that attach to your servers, billed by the gigabyte and drawn from the same balance.
- Snapshots as recorded point-in-time copies: a restore always names a defined source, never “whatever was current”.
- Resize as a verb on the volume itself when the data outgrows the disk — no migration window, no rewired mounts.
- The dangerous orderings refused at the API, so a mounted disk cannot be detached out from under a workload.
Why it matters
Storage incidents are ordering bugs. Moving the ordering from a runbook into the platform means the safe path is the only path, and the audit chain records who did what to which volume.