Release history & rollbacks
Return to an available retained release when an application change goes wrong. Openship creates a rollback deployment using its recorded image and configuration.
Open the guideHow it works
Inspect a previous release and review its restore plan before rolling back. Retained images avoid rebuilding old source against new dependencies. Artifact availability follows your configured retention.
Replacement images are prepared before activation. Service cutover remains sequential, and rollback does not reverse database writes or restore persistent volumes; use a backup for data recovery.
What you can do
Retained artifacts
Restore an available image without a new source build.
Restore plan
Review the target release and required changes first.
Separate data recovery
Use backups when data state must also be restored.
Explore more
Ship it your way.
Self-hosted and free, or managed on Openship Cloud — the same workflow either way.