Volumes & persistent files
Attach persistent storage to services that need files across releases. Review mounts separately from application images and include them in recovery planning.
Open the guideHow it works
Declare supported volumes and mount paths in project or Compose configuration. Data in persistent mounts follows its storage lifecycle instead of the replacement container lifecycle.
Prepared clusters can use project-owned shared volumes with supported attachment health, expansion, and external backups. Node-local mounts need a deliberate data transfer when moving servers.
What you can do
Persistent mounts
Retain database and application files across releases.
Storage visibility
Review paths and ownership before changing a stack.
Shared cluster files
Use supported volumes on prepared clusters.
Explore more
Ship it your way.
Self-hosted and free, or managed on Openship Cloud — the same workflow either way.