Skip to content

Work we can describe

Five of these are real engagements, anonymised under NDA, so the figures are generalised and the client is not named. Two are marked illustrative: the method is real and checkable, the figures are not yet backed by an engagement record. In every case the method is the part stated precisely, because it is the part that transfers to your estate.

Case studies

Seven case studies

Each one says what was measured before anything changed, because that is the step most often skipped.

Gambling · 500+ applications across several data centres · under NDA

Published Jun 2026 · 5 min read

Moving more than 500 applications to AWS, one at a time

An on-premise estate spread across several data centres, grown past what it could carry. More than 500 applications moved to AWS one at a time, least critical first, with the strategy chosen per application — and about one in seven retired instead of moved.

  • 500+ applications
  • ~15% retired instead of moved
  • plan beaten by 22%

B2B SaaS · two EKS clusters on AWS · under NDA

Published Aug 2026 · 3 min read

Making a savings number smaller

Detectors summed to a headline figure. Reconciling the overlaps between them removed roughly three quarters of it — and that is what made the remainder usable.

  • −73% on the claim
  • 2 clusters
  • every figure traced to a bill line

E-commerce · production EKS on AWS · under NDA

Published Sept 2026 · 4 min read

A storage bill grew 20× on a filesystem holding 8 GB

Daily spend started climbing in the same week a dozen database instances were shut down — so the bill should have been falling. The billing line said EFS. The cause was in node provisioning, two layers away.

  • $6 → $138/day
  • 8.57 GiB filesystem
  • 2,314 GB/day read

E-commerce · 18 RDS PostgreSQL instances on AWS · under NDA

Published Sept 2026 · 4 min read

Consolidating 18 production databases into 5

A legacy account with one RDS instance per service, most idling at 2–10% CPU. The business would grant two maintenance windows of fifteen to twenty minutes, on separate days, for a payment-adjacent platform. Everything else had to happen under live traffic.

  • 25 min total downtime
  • two maintenance windows
  • ≈$24k/year

Gambling · several production databases on one server · under NDA

Published Aug 2026 · 3 min read

Splitting one database server into three

Several production PostgreSQL databases shared a single server, so one busy neighbour was everybody's problem. Split onto three dedicated RDS instances, grouped by what actually contended rather than by size.

  • 1 shared server → 3 instances
  • resources isolated per database
  • maintenance no longer shared

Illustrative · managed Kubernetes on AWS

3 min read · Illustrative

Three EKS versions upgraded without a maintenance window

A cluster two versions past its support window, moved forward across three minor releases with no scheduled downtime — rehearsed first, with the disruption budgets fixed before anything moved.

  • 3 versions
  • 0 maintenance windows
  • rehearsed first

Illustrative · CI on a hosted runner fleet

3 min read · Illustrative

A CI pipeline from 38 minutes to 9

Build and test times measured per step before anything was touched, then caches that actually hit, parallelism where the dependency graph allowed it, and the work that had been running on every commit for no reason.

  • 38 min → 9 min
  • measured per step
  • no new CI vendor