Client: FluxPay · Fintech & Payments · UK payments orchestration platform
Improving Deployment Success in Payments
TechSupport Team supported the Terraform and Kubernetes deployment pipeline of FluxPay’s payments platform. Over five months, the client’s GitHub Actions records show successful deployments rising from 74% to 97%.
Client and engagement facts
- Client
- FluxPay
- Industry
- Fintech & Payments
- Business context
- UK payments orchestration platform
- Delivery model
- DevOps support
- Application
- Payments orchestration with per-service deploys
- Supplied geography
- UK
Related services: DevOps support
Application stack and tools
Application stack
- Go
- EKS
- Terraform
- PostgreSQL
Tools used
- GitHub Actions
- Argo CD
- Datadog
Why Support Was Needed
The platform deployed about 20 times a week. Production state locks were hard to see in CI logs, and configuration varied between environments. The client’s engineering manager kept production approval.
Technical Work
- Migrated the whole pipeline to GitHub Actions with per-environment state.
- Introduced a deploy checklist with rollback steps for each service.
- Added a state-lock detector to the deploy logs.
Representative Incident
After the migration, the first deployment still hit a Terraform state lock from a local apply. On the next attempt, the new detector surfaced the lock and blocked deployment until it was cleared.
Results and how they were measured
| Metric | Baseline | Result | Units | Measurement window | Source and scope |
|---|---|---|---|---|---|
| Deploy success | 74% | 97% | % | 5 months | Client GitHub Actions; Scope: The five-month comparison excludes a deployment failure during a cloud-provider failover. |
| Rollbacks/week | 5.8 | 1.1 | 5 months | Client ArgoCD | |
| MTTR | 41 min | 11 min | min | 5 months | Client Datadog |
Evidence and Limitations
The five-month comparison excludes a deployment failure during a cloud-provider failover. ArgoCD and Datadog supplied rollback and recovery measures.
Production Deployment Approval
TechSupport Team prepared and tested the pipeline. FluxPay’s engineering manager approved each production deployment.
Scope a Similar Engagement
Send a recent pipeline failure and identify how your environments, state and deployment approvals are managed. Request a support plan or explore DevOps support.
Get a technical support plan
Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.
- We reply by email.
- We agree a call about the roles, your stack and the hours.
- If there is a fit, we propose engineers after an assessment.