- Auto-scaling - Volumes automatically scale up with regional pod deployments and detach when scaling down
- Encrypted by default - All persistent data is AES encrypted
- Flexible storage - Each volume can expand up to 100GB (standard accounts) or 30GB (trial accounts), but can only be extended, never reduced
- Dedicated volumes - Each pod generates its own unique blank volume with no data duplication
- Shared access - Containers within the same pod can share the same volume
- Automatic reattachment - Detached volumes reattach automatically if your app scales up regionally
- Unique mount paths - Mount paths are unique to the application
Regional behavior
Volumes are tied to specific regions. This means:- If your app runs in multiple regions (e.g., EU, US, APAC), each region gets its own independent volumes
- A pod in one region cannot access volumes from another region
- When scaling to a new region, new volumes are automatically provisioned in that region
- Each pod within the same region gets its own dedicated blank volume (no data duplication between pods)
Node unavailability
Persistent volumes are bound to specific nodes within a region. If a node becomes temporarily unavailable (for example, due to maintenance or infrastructure changes), the platform preserves your volume and pod association so data remains intact when the node returns:- Volume retention - The persistent volume stays safely on its node, preserving all data during the outage
- Pod association - The pod remains associated with its volume, ensuring it resumes exactly where it left off once the node recovers
- Automatic resumption - When the node returns to service, your pod restarts automatically with the existing volume and all data intact
Recovery options
If you need your pod running sooner, you have two paths forward:Wait for node recovery
The recommended option when your data matters. Once the node is back, your pod resumes automatically with the existing volume and all data intact — no action required.
Redeploy with a fresh volume
If the data is not needed, delete the detached volume from the Volumes tab. The pod will be scheduled to a healthy node in the same region and start fresh with a new empty volume.
Hardware failure
In the rare event that a node requires a disk replacement, the affected volume is recreated as a new empty volume once the node is restored.Persistent volumes do not currently support automatic backups or replication. For critical data, implement a backup strategy within your application (for example, periodic exports to object storage) so you can restore quickly if needed.
Quickstart
Add volume details
During container setup, add your volume details including the mount path and
initial size.
Limits
| Feature | Standard account | Trial account |
|---|---|---|
| Volumes per application | 2 | 1 |
| Maximum volume size | 100GB | 30GB |
FAQ
Will I still be charged while my volume is detached from the container?
Will I still be charged while my volume is detached from the container?
Yes, you will still be charged while the volume exists, even if it’s
detached from a container. The volume still reserves storage capacity.
How do volumes scale down?
How do volumes scale down?
The default behavior means the volume will detach when scaling down.
Can I reduce the size of my volume?
Can I reduce the size of my volume?
No, you cannot reduce the size of your volume. You can only extend it to
make it larger.
Why is my pod not running when a node is unavailable?
Why is my pod not running when a node is unavailable?
Are persistent volumes backed up?
Are persistent volumes backed up?
No, persistent volumes do not currently support automatic backups or
replication. If the underlying hardware fails and the disk is replaced,
all data on that volume will be lost. For critical data, you should
implement your own backup strategy within your application.