Network Volumes
Create persistent network volumes that outlive individual deployments. Attach the same storage to instances within the same provider and region.
Network volumes are persistent block storage that lives independently of any single deployment. Attach a volume to an instance to keep datasets, model weights, and outputs around across deployments - and share it between deployments in the same provider and region.
Same provider and region
A volume can only be attached to instances on the same provider and in the same region where it was created. Pick the provider and location to match where you deploy.
What you can do
- Create persistent volumes of a chosen size
- Attach a volume to a running instance, and detach it later
- Resize a volume as your storage needs grow
- Clone a volume to a new location
- Track total provisioned size and which volumes are attached vs. available
Supported providers
Network volumes are available on DataCrunch and Hyperstack. Each provider exposes its own set of locations and volume types (for example, NVMe on DataCrunch and ssd on Hyperstack).
Create a volume
Create the volume
- Go to Volumes in your account
- Click Create volume
- Choose the Provider, give the volume a Name, set its Size (GB), pick a Location, and (where applicable) a Type
- Click Create Volume

Attach it to an instance
From the volume's actions, choose Attach and provide the target Instance ID and Location code (e.g. us-dallas-1). The volume becomes available to that instance.
Resize or clone
- Resize - increase a volume's size in place as you need more space
- Clone - copy a volume to a new location code (e.g.
FIN-01) to seed storage in another region
Reading the dashboard

The Volumes page summarizes:
- Volumes - total count
- Total size - provisioned capacity across all volumes
- Attached - volumes currently bound to a running instance
- Unattached - volumes available to attach
Filter the list by provider to focus on a single platform.
Volumes persist (and bill) until deleted
A volume keeps its data - and keeps costing - after you detach it or close the deployment that used it. Delete volumes you no longer need to stop charges.