Volumes
Your /workspace: code, checkpoints, and datasets. Automatic history, one point per Stop, and it attaches to a pod on any provider we support, not just a select few.
Storage that outlives the box, on every provider
A Volume is provisioned independently of any one pod. It has a name and a size; from then on it is yours to attach to a pod, and its data survives that pod closing. Unlike a provider's own native block storage, an Aquanode Volume is not tied to one provider or region: it restores onto whatever box a pod starts on next, on any provider we support.
There is no manual save button. Every Stop of the pod a volume is attached to writes a new point in its history, and while the pod runs, the volume saves itself in the background too, so a sudden loss costs at most an interval, not everything since the last Stop.
Volumes vs. workspace backups
These are two views of the same underlying mechanism now, not two different problems. A workspace backup is what a Volume's Stop-time and background captures give you automatically. Duplicating a volume is the deliberate fork: an independent copy, seeded from the source's current data, that you attach to a second pod without either one's writes reaching the other.
A volume attaches to one pod at a time. Attaching the same starting data to two pods at once is Duplicate, not Attach: an honest fork, where writes never merge back.
History, not just a live disk
Every Stop of the pod a volume is attached to is a point in that volume's history, labelled by why it happened (a manual Stop, or an auto-stop). Restore any earlier point while the volume is not attached to a running pod, without losing the later ones: restoring only moves what the next Start reads, it never deletes history.
A detached volume still costs money
A volume keeps its data after you detach it or delete the pod that used it (unless you choose to delete the volume too), 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.
FAQ
Does every provider support Volumes on Aquanode?
Yes. Unlike the old provider-native network volumes, an Aquanode Volume is restic-backed on Aquanode's own storage, so it attaches to a pod on any provider we support, not a select few.
Can I attach a volume to a pod on a different provider than where I created it?
Yes. A volume is not tied to a provider or region. Starting a pod restores its attached volume onto whatever box that pod lands on, on any provider we support.
Does a volume survive deleting the pod?
By default, yes: deleting a pod asks first, with the volume kept unless you choose to delete it too. A kept volume lists as unattached and keeps billing for as long as it exists.
Can I get a second copy of a volume's data?
Yes. Duplicate makes an independent copy: a new volume, its own history, seeded from the source's current data. Writes on the copy never flow back to the source.
