Meridian Health · Healthcare · 2024
A deploy pipeline that stopped being a quarterly event
Took a regulated healthcare platform from ten-week release trains to daily deploys without loosening a single control.
- Release cycle
- 10 wks → 1dRelease cycle
- Change failure rate
- -63%Change failure rate
- Audit controls retained
- 100%Audit controls retained
Services
- Platform & cloud
Stack
- Terraform
- GitHub Actions
- Kubernetes
- OpenTelemetry
Duration
9 weeks
The problem
Every release required a manual evidence pack assembled by hand. Deploys were rare, enormous, and consequently terrifying.
What we did
- 01Automated evidence collection as a pipeline artefact rather than a document.
- 02Split the release train into independently deployable services with contract tests.
- 03Introduced progressive rollout with automated rollback on error-budget burn.
- 04Ran a game day with the on-call rota before switching anything on.
Where it landed
Meridian now deploys on demand. The compliance team reports that evidence quality improved, because a pipeline does not forget steps at 11pm on a Friday.
Next step
Tell us what you’re building.
A 30-minute call with an engineer, not a salesperson. You will leave with a straight answer about scope, cost and whether we are the right people for it.
Or email hello@nexa.com · Austin, Texas · United States