Network Volumes
Block storage that belongs to your workspace rather than to one instance — create it once, attach it to whichever box needs it, and keep it when that box goes away.
Provider coverage
DataCrunch and Hyperstack only. A volume attaches solely to instances on the same provider in the same region it was created in, and the deploy form says so before you commit to a GPU.
Storage that outlives the instance
A network volume is provisioned independently of any deployment. You give it a name, a size in GB, a provider and a location; from then on it is yours to attach to an instance, detach, and attach somewhere else. Closing the deployment that was using it does not delete it.
Volumes can be resized upward in place and cloned into another location, and the console tracks how many you have, their total provisioned size, and which are currently attached versus idle.
Volumes vs. workspace backups
These solve different problems and it is worth being precise. A volume is live storage: a disk attached to a running box, in one provider and one region, fast because it is local to that network.
A workspace backup is portable storage: a snapshot you can restore onto a different GPU, provider or region. If your goal is to move a workload somewhere cheaper, that is the snapshot path, not the volume path — a volume cannot follow you across a provider boundary.
A detached volume still costs money
A volume keeps its data after you detach it or close the deployment that used it — which means it also keeps costing. That is the point of it, but it is the one thing worth remembering: an unattached volume you have forgotten about is a line on your bill. The console shows unattached volumes as their own count for exactly this reason.
FAQ
Which providers support network volumes on Aquanode?
DataCrunch and Hyperstack. The deploy form states this before you pick a GPU, and the volumes page only offers those providers when creating one.
Can I attach a volume to an instance on another provider?
No. A volume attaches only to instances on the same provider, in the same region where it was created. To move data across providers, use a workspace snapshot and restore it on the new instance.
Does a volume survive closing the deployment?
Yes — a volume is independent of any deployment. It keeps its data after you detach it or close the instance that used it, and it continues to be billed for as long as it exists.
Can I make a volume bigger later?
Yes. Volumes can be resized upward in place, and cloned into another location if you need a copy elsewhere on the same provider.
