Documentation
Volumes
Attach persistent volumes to services for stateful workloads, migrations, and backups.
When to use volumes
Volumes are ideal for file storage, cached assets, and data that should survive restarts. You can attach volumes to apps, workers, or databases to keep data persistent.
Volume lifecycle
- Create a volume from the project settings or service detail panel.
- Attach it to a service and choose a mount path.
- Resize or migrate volumes as your storage needs grow.
Snapshots and backups
Use snapshots to capture file based workloads or to stage a recovered volume before you swap it onto a service. PostgreSQL point in time recovery uses pgBackRest, not filesystem snapshots.
Best practices
- Mount volumes to clear, dedicated paths like /data or /var/lib/app.
- Keep backups of critical volumes before major releases.
- Practice the restore workflow before swapping a recovered volume into production.