Updated May 8, 2026 Volumes are NVMe SSD block storage you attach to a Raff VM as additional disk capacity. Use them when a VM needs more storage than its plan includes, or — more importantly — when you want data to outlive the VM itself. Volumes survive VM destroy, attach to a different VM, and bill independently.Documentation Index
Fetch the complete documentation index at: https://docs.rafftechnologies.com/llms.txt
Use this file to discover all available pages before exploring further.
At a glance
| Property | Value |
|---|---|
| Storage class | Single tier — NVMe SSD (no tiers to choose) |
| Size range | 10 — 1000 GiB at create time |
| Resize | One-way grow — capacity increases only |
| Attach | One VM at a time; reattach to a different VM in the same region |
| Survives VM destroy | Yes — detached, kept in the account, ready to reattach |
| Filesystems | Linux: ext4 / xfs (auto-format option). Windows: NTFS (manual via Disk Management) |
| Device naming | /dev/vdb, /dev/vdc, … (virtio-blk; never sd* or nvme*) |
| Billing | Subscription default $0.05/GiB/month (PAYG on request, same rate) |
| Bandwidth between VM and volume | Free, never metered |
When to use a volume
| Goal | Use a volume? | Use what instead |
|---|---|---|
| Add disk to one VM beyond the plan’s base NVMe SSD | Yes | — |
| Keep data when destroying a VM (databases, customer uploads, app state) | Yes | — |
| Move data between VMs serially (detach → attach to another) | Yes | — |
| Two VMs reading the same files at once | No — single-attach | Object Storage |
| Files served to the public (static assets, downloads) | No | Object Storage |
| One-off snapshot before risky changes | No (snapshots are a separate object) | Snapshots |
| Reusable disk image for many new VMs | No | Custom images |
How volumes fit in the storage stack
A Raff VM has up to five storage objects in its orbit. Volumes are one of them:| Storage object | Lives | Survives VM destroy | Best for |
|---|---|---|---|
| Base disk (in the plan) | Inside the VM | No — destroyed with VM | OS, transient working files |
| Volumes | Attached to one VM | Yes — kept | Data you can’t afford to lose with the VM |
| Snapshots | Independent of the VM | VM-disk snapshots: deleted with VM. Volume snapshots: survive | Restore points before risky changes |
| Backups | Independent | Yes (per retention) | Routine scheduled VM protection |
| Custom images | Account-wide | Yes | Golden images for new VMs |
Most viewed
Create a volume
Pick size, billing term, target VM, and how it should be formatted.
Attach to a VM
Dashboard attach + format and mount inside the VM.
Resize a volume
Grow capacity, then expand the filesystem inside the guest.
Detach from a VM
Free a volume cleanly so you can reattach it elsewhere.
Browse
Quickstart & guides
Create, attach, resize, detach, delete.
Concepts
Persistence model and single-attach scope.
Details
Features, limits, pricing.
Troubleshooting
Common volume issues — attach, mount, resize, detach.
API Reference
Volume endpoints.
Changelog
All API updates and changes.