Company
Expert Services
Where you need this applied to your own systems rather than read about. Engagements are scoped narrowly enough to produce something useful, and honest about what can be achieved in the time.
Last updated 24 August 2026
What we work on
- OpenStack — architecture review, deployment with Kolla-Ansible, upgrade planning, performance investigation, and production troubleshooting
- Kubernetes — cluster operations, workload reliability, resource and scheduling problems, and platform design
- Terraform and infrastructure as code — module structure, state strategy, plan review practice, and blast-radius reduction
- Observability — instrumentation strategy, alert design that does not page for nothing, and making an incident legible while it is happening
- AI infrastructure — accelerator platform design, interconnect and storage architecture, and capacity planning
- Incident review — working through what happened, and turning it into runbooks and monitoring that catch it next time
How engagements are shaped
Architecture review
A focused review of an existing design or deployment against how it will behave under failure and growth. You get a written assessment with prioritised findings, each stating the failure scenario it prevents, and a recommended sequence.
Incident analysis
Working an incident that has already happened: reconstructing the sequence from the evidence, identifying the contributing factors, and producing the runbooks and alerting changes that would have shortened it. Blameless, and specific.
Hands-on operations work
Direct work on the system — an upgrade, a migration, a performance problem, a deployment. Scoped against a defined outcome and a validation that proves it.
Advisory
Ongoing availability for design decisions and problems as they come up, for teams that need someone to check their reasoning rather than someone to do the work.
How this works in practice
Engagements start with a conversation about what you are trying to achieve and what state the system is actually in — not a proposal. If we are not the right people for it, we will say so. If the problem is smaller than an engagement, we will tell you that too.
Work is done against a written scope with a defined deliverable. Where an engagement involves changes to production, the plan includes validation and rollback before anything is executed, the same way our runbooks do.
What we do not do
- Staff augmentation for open-ended periods
- Work we are not qualified for, taken because it is adjacent
- Recommendations that require buying something we have a commercial relationship with — there are none
Get in touch
Tell us what you are trying to achieve, what the current state is, and what the constraint is — time, budget, risk tolerance, or a date you have to hit. Contact us.