Skip to main content
Updated May 8, 2026 A Raff volume is a single block device that you attach to a VM. Every volume on the platform today shares the same characteristics — Raff offers one volume class at the moment, so the choice you actually make at create time is size and billing term, not a performance tier. This page describes the model so you know what behaviour to expect, where volumes sit relative to your other storage options, and which properties are fixed vs which the platform may expand later.

​
What every Raff volume is

There are no performance tiers, IOPS classes, or “general purpose vs optimized” variants today. Future tiers may be added; this page will list them when they exist.

​
Persistence model

A volume is independent of the VM it attaches to. Conceptually, a volume sits next to the VM, not inside it. This is the practical reason to put data you can’t lose on a volume, not on the VM’s base disk. The base disk is destroyed with the VM; volumes outlive it. See Storage model for the full survival matrix across all storage objects.

​
Single-attach scope

A volume can be attached to one VM at a time. This is a hard constraint — Raff doesn’t support multi-attach (where two VMs see the same volume simultaneously). If you find yourself wanting two VMs to see the same volume contents, you almost certainly want Object Storage or an application-level approach.

​
Region and project binding

A volume’s region and project come from the VM it’s attached to. Three rules follow:
  1. A volume can only be reattached within its original region. You can’t take a us-east volume and attach it to a VM in another region.
  2. Volumes follow their VM’s project. Attach to a VM in project prod and the volume sits in prod.
  3. Standalone (unattached) volumes sit in the dashboard’s currently-selected region until you attach them. Pick the region carefully when creating an unattached volume — same one-way constraint applies.
To “move” a volume across regions: snapshot it, restore the snapshot in the new region, then delete the original. (Cross-region snapshot restore depends on platform support — see Create a snapshot.)

​
Volume vs other storage

Five storage products on the platform serve different jobs. Volumes are the right answer for persistent block storage attached to one VM.

​
What’s billed

See Pricing for how volume billing fits into the wider subscription / balance / credit model.

​
What’s coming, what’s not

  • Performance tiers — not available today; if added, they’ll appear in the create dialog and be documented here.
  • Multi-attach — not on the roadmap; for shared access, use Object Storage.
  • Encryption-at-rest configuration — volumes are encrypted by default at the platform level; per-volume key management is not exposed today.
  • Cross-region replication — not at the volume layer; do it at the application layer or via snapshot/image.

Create a volume

Pick size, billing term, format, and target VM.

Storage model

How volumes fit alongside snapshots, backups, and images.

Object Storage

The right answer when you need shared, multi-reader storage.
Last modified on May 8, 2026