· Product · 5 min read
Every deploy is a Git commit: designing one-step rollbacks
By Ethan Cole, Co-Founder & CTO
Rebuilding a container to roll back production wastes critical minutes when latency spikes. Promoting and reverting immutable commit SHAs makes recovery predictable.
When a production release misbehaves, the worst possible rollback workflow is waiting six minutes for CI to rebuild an earlier branch while error rates climb.
In Nimbus, every deploy points to an immutable commit SHA and the exact OCI image digest built for that revision. Staging can roll forward automatically on every push to your branch, while production stays an explicit click or promotion command.
Promoting staging to production deploys the exact verified artifact you already tested — not a fresh build with different dependency resolution or base-layer drift.
Rolling back works the same way in reverse. Selecting an earlier commit re-applies its image and service specification immediately, without touching a cluster console or editing manifests by hand.
When deployments map one-to-one with Git history, answering what changed in production takes five seconds instead of twenty minutes.