Northwind Financial
18,400 database instances
Cut quarterly patch execution from 11 weeks to 6 days
North AmericaCustomers
Estates where the change window is the constraint
Infrapilot runs in organisations where infrastructure change is measured in tens of thousands of assets, reviewed by regulators, and visible to millions of people when it goes wrong.
92%Patch automation coverage reachedFortune 100 bank, from a 34% baseline, across 18,400 instances
41m → 3.2mMean time to restoreHospital network, 340 clinical applications across 62 sites
400Database migrations in eleven weeksTier-1 telecom datacentre exit, delivered four months early
$4.2MAnnual operating cost avoidedSingle customer, measured against their own prior baseline
Selected customers
NORTHWINDCASTELLANMERIDIANTRELLISAURICVOLTAHALDENSENTINELLUMENCOBALTPINNACLECORVID
By the estate
Who runs Infrapilot, and at what scale
Castellan Insurance Group
9,700 servers across 14 countries
Continuous evidence for Solvency II and DORA
EuropeMeridian Health System
340 clinical applications
Zero downtime across 62 hospital migrations
North AmericaTrellis Telecom
41,000 nodes
MTTR down 71% on the core signalling estate
APACAuric Manufacturing
112 plants, 6,800 edge servers
Plant-floor patching without production stoppage
EuropeVolta Energy
7,200 OT and IT systems
NERC CIP evidence generated continuously
North AmericaHalden Retail Group
2,100 stores, 14,000 endpoints
Peak-season change freeze cut from 9 weeks to 2
GlobalSentinel Federal
Accredited federal environment
Automation operating inside the authorisation boundary
North AmericaLumen Biosciences
GxP-validated estate
Validated change with automated 21 CFR Part 11 records
EuropeCobalt Logistics
5,400 instances, 38 regions
Datacentre exit completed four months early
GlobalPinnacle Airways
3,900 systems
Change failure rate reduced to 0.4%
North AmericaCorvid Bank
12,600 instances
Core banking upgrade delivered in a single weekend
APACCase studies
Three programmes in detail
Written with the customer, reviewed by their engineering leadership, and published with the measurement methodology intact.
In their words
What changed for the team
We were spending eleven weeks a quarter on database patching and still finishing late. The first automated cycle took six days, and the second took four. The difference was not speed of execution — it was that nobody had to negotiate a sequence any more.
11 weeks → 6 daysQuarterly patch cycle
The dependency graph paid for the platform on its own. We had four services nobody could account for sitting in the path of our signalling stack. Two of them were single points of failure.
71%Reduction in MTTR
Our regulator asked for evidence of control over privileged database access. Previously that was a six-week exercise across four teams. We exported it in an afternoon, and the auditors accepted it without a follow-up request.
6 weeks → 1 dayAudit evidence preparation
Clinical systems do not get maintenance windows. Being able to rehearse a cutover against production data, then roll it back cleanly, is what let us move sixty-two hospitals without a single patient-facing outage.
0Patient-facing outages across 62 sites
Plant floors run three shifts. The wave planner understood which lines could take a restart and which could not, because it read our own dependency data rather than a spreadsheet somebody maintained in 2019.
112 plantsPatched without production stoppage
We committed to a datacentre exit with a fixed lease end. The migration factory turned a bespoke project into a repeatable production line — we finished four months ahead of the deadline.
4 months earlyDatacentre exit completed
Reference calls
Talk to someone who has already done this
We will introduce you to a customer in your sector, at a comparable scale, who deployed within the last eighteen months — with no account team on the call.