What we do
Nine services, each one something we have taken end to end. Every page says what the work involves, how it is staged, what you are left holding — and when we are the wrong people to call.
All services
Operate, build, or assess
Three kinds of engagement. Filter if it helps; the list is short enough to read either way.
9 of 9 services shown
Kubernetes management
Day-2 operation of EKS, GKE and self-managed clusters: upgrades, node lifecycle, autoscaling, capacity and the boring reliability work that decides whether a platform is trusted.
Platform engineering
A path to production your developers will actually use — templates, environments and guardrails built on what you already run, not a platform you must migrate onto.
CI/CD
Pipelines that are fast enough to trust: build and test times measured, caches that work, deployments that are reversible, and GitOps delivery that keeps git describing what runs.
Cloud migration
Moving workloads without moving the mess: an inventory first, a costed target second, then a migration executed in slices you can stop at any point.
Infrastructure design
Networks, accounts, identity and data paths designed to be auditable later — including the question most designs postpone: what this will cost at three times the traffic.
Backup & disaster recovery
Backups that have been restored at least once, retention that matches the obligation you are under, and a recovery procedure someone other than its author has run.
FinOps audit
A fixed-scope review of an AWS estate and its Kubernetes clusters: where the money goes, which findings survive scrutiny, and what to do in what order. Delivered as a report, not a dashboard login.
DevOps consulting
Short engagements against a specific question — an architecture review, a second opinion on a plan, or an assessment before you commit a budget.
Fractional platform lead
Someone who owns where the platform goes, without a full-time hire: three months from an audited estate to a roadmap and working foundations, then the platform run, its cost reviewed and the roadmap kept moving.
What we do not do
- Application development and integrations (API, ETL, middleware) — we build and run the platform underneath Platform engineering →
- Certification preparation and pentesting — we keep a security baseline, not an audit trail The baseline we keep →
- Azure — no. AWS and Kubernetes wherever it runs — EKS, GKE, Hetzner, self-managed. Not Azure.