Platform Migration
Virtualisation and cloud migrations with the least possible operational disruption. From inventory audit through target architecture to cutover and support through to handover.
When this fits: When an existing platform is hitting its limits — licensing costs, scalability, vendor lock-in, consolidation pressure. Or when a cloud exit is on the horizon. Or when historically grown structures need to become a hyperconverged platform.
What you get: A robust migration strategy that names risks instead of hiding them. A target architecture that works in practice, not only on paper. Hands-on support during the hot phase, when real data is flowing.
Infrastructure Architecture
Platforms built to last for the years ahead. Compute, storage, network, identity — designed to work together rather than grown side by side.
When this fits: For greenfield projects, larger redesigns, or when an architecture review reveals that what exists no longer carries the load. Equally when the question “cloud, on-prem or hybrid?” needs a clean answer that doesn’t lean on vendor marketing.
What you get: An architecture that fits your requirements — not those of a particular vendor. With an eye on digital sovereignty, scaling paths and operability by your own team.
Automation & Operations
Infrastructure-as-Code, GitOps pipelines, monitoring stacks. So platforms aren’t just built once but stay reproducible when requirements change.
When this fits: When manual interventions have become the rule rather than the exception. When standing up a cluster takes “three weeks and nobody knows quite how”. When the operations team spends more time fighting fires than improving things.
What you get: Pipelines that describe your environment as code. Monitoring that surfaces problems before they escalate. Documentation that lives in the repository, not in a stale wiki.
Software Development
Tools, interfaces, small applications — wherever off-the-shelf software doesn’t fit or a gap needs closing. Focus: Python, Go, Bash, REST APIs.
When this fits: When a workflow between two systems gets stuck and a connector is missing. When a recurring report would be better off as a reproducible CLI tool than in a spreadsheet. When a small internal utility would make a complex platform easier to operate.
What you get: Cleanly written, documented code that fits your language ecosystem. With tests, in a repository, with a hand-overable operating concept.
Advisory & Second Opinion
Architecture reviews, migration assessments, tool selection. For teams that need an experienced outside perspective before an investment decision is made.
When this fits: Before a major purchase. Before a vendor lock-in that’s hard to reverse. When internal opinions clash and a neutral assessment is missing. Also as a recurring second opinion over several months.
What you get: An honest assessment. In writing, with reasoning, with alternatives. Not advisory that ends in an implementation contract — but one that helps you decide for yourself.