Engagements are scoped in weeks, billed monthly, and cancellable with 30 days' notice. We would rather leave early than be needed forever.
Pick one, or let the assessment tell you which two matter most.
Cluster topology, ingress, secrets management and GitOps delivery. Terraform or Pulumi, your choice — we write it the way your team already writes it.
Data-centre to cloud, cloud to cloud, or VM to container. Each workload moves behind a documented rollback, and we keep the old path warm until you say otherwise.
Prometheus, OpenTelemetry and structured logging, with SLOs agreed by the people who carry the pager rather than the people who buy the tooling.
Load and failure testing, capacity planning, backup restore drills, and blameless incident reviews that produce actual backlog items.
Network segmentation, least-privilege IAM, supply-chain controls and secret rotation. We report findings in writing, ranked by exploitability.
Usage attribution per team and per service, commitment and spot strategy, plus a monthly review so savings do not quietly evaporate.
Three shapes cover nearly everything we are asked for.
| Model | Commitment | Best for |
|---|---|---|
| Assessment | Fixed, 1–2 weeks | You suspect something is wrong but cannot name it |
| Project | Fixed scope, 4–16 weeks | A migration or platform build with a defined finish line |
| Retained | Monthly, rolling | Ongoing operations alongside your own engineers |
Not an exhaustive list, and not a religious one. We will happily work inside whatever you have already standardised on.
Kubernetes, Nomad, ECS, systemd where it is genuinely simpler.
Terraform, OpenTofu, Pulumi, Ansible, Packer.
GitHub Actions, GitLab CI, Argo CD, Flux, Buildkite.
Prometheus, Grafana, Loki, Tempo, OpenTelemetry, Vector.