Deployment health & preparation
Make release failures visible before and during activation. Prepare replacement images before activating containers and inspect health outcomes.
Open the guideHow it works
Registry-backed images are resolved before activation, while local builds and rollback artifacts retain their recorded provenance. A failed preparation prevents the replacement image cohort from starting cutover.
Readiness depends on health settings and runtime support. Multi-service activation remains sequential; image preparation does not turn container cutover, database changes, and volume operations into one transaction.
What you can do
Image preparation
Resolve replacement images before activation.
Artifact provenance
Distinguish registry updates from local and retained artifacts.
Health feedback
Inspect readiness and deployment failure details.
Explore more
Ship it your way.
Self-hosted and free, or managed on Openship Cloud — the same workflow either way.