Twenty years of infrastructure, in environments that had to stay up.

Government, finance, education and airline environments in Australia and overseas — usually alongside an internal team who kept running the platform long after we handed it over.

Where we have worked

The industries, and what infrastructure means in each of them.

Different sectors, the same underlying requirements: availability, recovery, cost control and a defensible answer when someone asks who has access to what.

01 Government Efficiency and cost-effectiveness in environments where change control, records and access review are not optional extras. Consolidation, platform modernisation and continuity planning under procurement rules that reward being able to justify the design. Public sector

02 Finance Availability, recovery objectives and auditability. Systems where downtime is measured in money and the recovery plan has to be demonstrable, not aspirational. Financial services

03 Education Large user populations, constrained budgets and seasonal peaks. Centralised desktop and application delivery, capacity that flexes, and licensing that survives scrutiny. Education

04 Airline & transport Systems with no acceptable window for failure, spread across geography, where remote and branch operations and recovery design carry the most weight. Transport

05 Growing businesses Organisations of twenty to a few hundred staff who need the discipline of the environments above without a team to run it themselves. This is where most of our managed service work sits. SMB & mid-market

06 Service providers Organisations hosting on behalf of their own customers, where tenancy separation, density and the unit economics underneath the platform are the whole design. Hosting & MSP

References

We publish what we are allowed to publish.

You will not find a wall of client logos on this page. Publishing a customer’s name is their decision, not ours, and a logo wall is a poor substitute for the conversation you actually want to have — which is with someone who runs infrastructure like yours.

So we do it the direct way. If our experience in your sector matters to your decision, ask, and we will arrange a reference who can speak to the work: what the estate looked like before, what was done, what it cost to run, and what they would do differently.

Case studies are published here as clients approve them, in their words where possible.

Asking for a reference

What we can put in front of you

A named contact in a comparable environment, with their consent, before you commit.
Anonymised design documents and migration plans from similar engagements.
A walkthrough of a recovery plan and its test results.
The current evidence behind any certification or partner claim we make.

Request a reference

What engagements look like

Four patterns, over and over.

Most of our work falls into one of these shapes, regardless of industry.

The inherited estate

The platform works, nobody is quite sure why, and documentation is thin.
Typical fix: assess, document, remove the single points of failure, then stabilise and hand back with a monitoring baseline.

The ageing platform

Out of support, out of capacity or out of licensing headroom, with a deadline attached.
Typical fix: targeted design and migration, rehearsed cutover, often to a different platform than the incumbent.

The recovery gap

Backups exist. Recovery has never been demonstrated, and ransomware is now the scenario.
Typical fix: backup redesign with immutable copies, documented recovery objectives, and restore tests that get run on a schedule.

The new capability

A requirement the current team cannot absorb: private AI, a migration, a platform build with a date on it.
Typical fix: project delivery or contracted senior engineers inside your own team and process.

Which one is yours?

Most people know within the first two minutes of describing their environment. We will tell you what we would do about it.

Book a technical call Services