twinalps
Book a call
Case 03 / anonymized engagement

A weekly release cadence became on demand.

KubernetesArgoCDPrometheusAWS
WeeklyOn demand
Engagement
12 weeks
Team
2 platform engineers + Inpro lead
Migration
32 services
Deploy duration P95Deployment duration, P95, across the engagement / minutes
~3h1h8mW0W2W4W6W8W10W12Week 0 / weekly, by handWeek 12 / on demand

Thirty-two services migrated across the same window with zero customer-facing incidents.

In detailWorkload footprint by service
Kubernetes46%Databases20%Streaming14%Object store12%Edge / CDN8%
Kubernetes
46% of the footprint
Databases
20%
Streaming
14%
Object store
12%
Edge / CDN
8%
The brief

Build the platform and migrate services without customer impact.

The B2B software platform was releasing weekly. The work covered standing up Kubernetes and moving 32 services.

Starting pointWeekly releases
Constraint32 services in motion
ProofZero customer incidents
Delivery

Platform engineering with the operational controls included.

Two platform engineers and an Inpro lead delivered the environment with Kubernetes, ArgoCD, Prometheus and AWS.

  1. FoundationAWS
  2. OrchestrateKubernetes
  3. DeployArgoCD
  4. ObservePrometheus

Thirty-two services were migrated to the platform. The migration recorded zero customer-facing incidents.

Engagement detail

The constraint, the shape and the stack in one view.

Platform scope

Kubernetes, 32 services

The assignment covered standing up the platform and moving 32 application services.

Control plane

ArgoCD and Prometheus

Delivery included Kubernetes, ArgoCD, Prometheus and AWS as the operating environment.

Delivery shape

12 weeks, senior-led

Two platform engineers and an Inpro lead delivered the migration and platform work.

Technical + business value

How the delivery translated into operating value.

Technical delivery

A platform path from cloud foundation to observable delivery.

The twelve-week engagement combined AWS infrastructure, Kubernetes orchestration, ArgoCD deployment control and Prometheus observability. Two platform engineers and an Inpro lead delivered the platform and migrated 32 services.

Business value

Release when needed, with a measured deployment path.

The release cadence moved from weekly to on demand. Deployment P95 came in under eight minutes while the service migration completed without a customer-facing incident.

P95 <8mDeployment duration
0Customer-facing migration incidents
Outcome

On-demand deployment, P95 under eight minutes. All 32 services were migrated with zero customer-facing incidents.

WeeklyOn demand
Your platform

Bring us the delivery constraint. We will bring the operators.

Start a brief
See other cases