Storage
Pods are disposable; volumes are not. A persistent volume keeps your data across pod stops, restarts, and re-creations. Meshive has two kinds:
| Local volume | Network volume | |
|---|---|---|
| Lives on | The pod’s own host machine (fast, direct disk) | A dedicated storage node (NFS) |
| Created | Together with a pod, in the create flow | Standalone, from Resources › Storage |
| Tied to | That one machine — the pod must stay there | Any pod in the workspace can mount it |
| Pod types | Demand pods only | Demand and spot |
| Encryption | Opt-in at creation (details) | Opt-in at creation (details) |
Sizes start at 10 GB per volume, up to what the host has free. Rates are per GB·month — see Pricing & Instances.
Connect — access without a pod
Section titled “Connect — access without a pod”A network volume doesn’t need a running pod to be reachable. Connect on the volume card opens a temporary access channel (SSH/SFTP credentials shown in the modal) so you can upload or pull data directly. Preparing the channel usually takes about a minute.
For encrypted volumes, Connect is also what unlocks the volume — and an idle countdown locks it again automatically.
Choosing between the two
Section titled “Choosing between the two”- Local — training scratch space, model weights next to the GPU, anything latency-sensitive. Remember it pins the pod to that machine: to move GPUs, copy the data out first (why).
- Network — datasets shared across pods, data that must outlive any single machine, spot workloads (local volumes aren’t offered on spot — they’d be lost on reclaim).