Financial servicesGCCDevOps
Cutting deploy lead time from days to minutes for a regional fintech
Replaced a fragile Jenkins-on-VMs pipeline with GitOps on EKS, hardened with policy-as-code and progressive delivery.
Client: A Riyadh-based digital bank
Challenge
What we walked into
Two-week change cycles, frequent rollback emergencies, and weekend-only deployment windows that capped product velocity. Compliance evidence was assembled by hand for every release.
Approach
How we engaged
- ●Migrated 40+ microservices to a GitOps platform on EKS with Argo CD and Argo Rollouts
- ●Replaced ad-hoc Jenkins jobs with reusable shared libraries and ephemeral build agents
- ●Wired SAST/SCA/IaC scanning into PR checks with automated remediation suggestions
- ●Introduced canary deploys and SLO-based progressive rollback
- ●Automated SOC 2 evidence collection straight from the pipeline
Results
What changed
Deploy lead time
from 9 days to 12 minutes
Change-failure rate
11% → 2.4%
MTTR
4h → 22m
Audit prep effort
−85%
“We went from dreading release Fridays to shipping on demand. Their team operates as part of ours.”
Head of Platform · Digital banking
Looking for similar outcomes?
Tell us about your situation. We respond within one business day.
This case study is an illustrative, anonymized representation of recent client work.