Every release rolls through canary to production with one click back
Conveyor is the delivery console a payments platform team watches on every push. Each run moves through build, unit and integration tests, a security scan and a 10% canary before full rollout, with a deploy history per environment and a rollback to the last healthy version that takes one confirmation instead of a war room.
- 10x
- Deploy frequency
- 4 min
- Mean time to recovery
- 0
- Critical findings shipped
What they came with
A release was one person following a checklist by hand, usually out of hours, and the way back from a bad deploy was another manual sequence carried out under time pressure. Because each release cost someone an evening, changes were batched, and every release carried more of them than the last. There was no quick way to state which build was running in which environment.
What the engagement covered
- Six-stage pipeline with test counts, scan results and canary progress on every run
- Deploy history per environment with commit, author, duration and outcome
- One-click rollback to the last healthy production version
Technical detail
One artefact promoted by digest
The image is built once per commit and promoted through environments by digest, with environments differing only by config. What passed staging is the same bytes that reach production.
Canary held on health signals
The rollout shifts a slice of traffic and pauses while error rate and latency are compared against the running baseline. A failed gate aborts the step rather than continuing to the next weight.
Rollback is a git revert
Desired state lives in the repository and Argo CD reconciles the cluster to it, so rolling back is a re-sync of the previous revision. The image is already in the registry, which makes it a pull rather than a rebuild.
Environments come from Terraform
Clusters, namespaces and roles are Terraform modules, so a new environment is an invocation rather than a console session. Drift shows up in a plan before it surprises a release.
The stack
Delivery
Infrastructure
Build
Observability
- Practice
- CI/CD Automation
- Sector
- Fintech Payments
- Shape
- Client engagement
- Stack
- GitHub Actions, Kubernetes, ArgoCD
Something like this to build?
Tell us what runs today and where it hurts. An engineer reads it and replies.