These are named references, not anonymised examples. Each one is published verbatim on the customer references page, so you can read the words as the client wrote them.
CTO - software development company
Four years on QA, UAT and live environments. GMX Tec handled everything from planning to executing the migration from the previous provider, in a nearly seamless fashion. Deployment, high availability, stability and self-healing came with it.
Finance Controller - multi-region UK NFP
A medium-size charity with a dispersed team of employees and volunteers. An RDP cluster with two-factor authentication and a web portal for remote users. The migration was planned and executed in just over a month, and it was a total success. Three years in.
Entrepreneur - chairman
Ian W. was the business partner in the previous venture, Premier IT Networks - built, run, and acquired by Node4 in 2015. Average hosting reductions across that customer base were 20-35%. The acquisition is a public record (DCD, 31 July 2015).
Each figure below is either stated from the record or written into a contract — and each is paired with the mechanism that produces it. A number without a mechanism is a slogan; a technical buyer should be able to check the reasoning before qualifying us on the number.
Twenty years in Linux and open source infrastructure, across more than 350 complex infrastructure migrations. The count compounds because the playbook is the same on every engagement: audit the estate, design the target state, rehearse the cutover, keep a rollback path. GMX Tec Ltd was founded in 2017 — the twenty years are the practice that predates the company — and the team of around 20, inside a wider group of 120+, is the bench that runs the playbook.
Multi-tenant SaaS infrastructure at NHS scale, with ISO 27001 in place — a control regime you can audit, not a promise of security. The 30-40% range is what the mechanism produces: one platform replaces per-estate duplication, and consolidation removes orphaned capacity. It is stated as a range because it is a range.
The uptime figure is what we contract for and monitor against — a commitment you can hold us to, not an average we claim. It is backed by the architecture the SLA is written against: replication by policy, a failover path documented before it is needed, and records that show what the platform actually did. No achieved average is published here, because an achieved average depends on the window, the scope and the definition.
Bring the numbers to your own estate: an audit is the lowest-commitment way to find out whether the mechanism applies to you.