DevOps

Releases that are quick, repeatable and boring.

Talk to an engineer
Problems we solve
“Deploys take an afternoon and one specific person.”
“Infrastructure was clicked together in the console.”
“Pipelines fail for reasons nobody understands.”

What we do

Advise

DevOps consultancy

An assessment of your DevOps setup, with findings ranked by risk and effort.

Build

DevOps delivery

We design and build it with your team, in your accounts, documented as we go.

Run

DevOps support

Monitoring, patching and upgrades, with incident response agreed per contract.

Teach

DevOps training

Workshops and pairing on DevOps, built around your own systems.

Tools we work with

CI/CD

  • GitHub Actions
  • GitLab CI
  • Jenkins
  • CircleCI
  • Bitbucket Pipelines
  • Azure Pipelines
  • Argo Workflows

Releases & deployment

  • Argo CD
  • Flux
  • Helm
  • Argo Rollouts
  • Spinnaker
  • feature flags

Infrastructure as code

  • Terraform
  • Terragrunt
  • OpenTofu
  • Pulumi
  • CloudFormation
  • Bicep

Configuration

  • Ansible
  • Packer
  • cloud-init

Containers & artefacts

  • Docker
  • BuildKit
  • Harbor
  • Artifactory
  • ECR
  • Artifact Registry

Quality & security gates

  • SonarQube
  • Trivy
  • Semgrep
  • Dependabot
  • Renovate
  • pre-commit

Secrets

  • Vault
  • AWS Secrets Manager
  • Azure Key Vault
  • SOPS

Observability

  • New Relic
  • Prometheus
  • Grafana
  • Loki
  • OpenTelemetry
  • Datadog
  • Sentry

How an engagement runs

  1. 1 A call. 30 minutes with an engineer to understand the problem.
  2. 2 A look. Read-only access or a walkthrough, so we scope from facts.
  3. 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
  4. 4 The work. In your accounts and repositories, alongside your team.
  5. 5 A handover. Documentation and a session with your team, so you’re not dependent on us.

Proof

A recent DevOps engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.

See our work
Case study · anonymised
UK software company
Challenge
Deploys take an afternoon and one specific person. That was how the client put it on the first call.
Approach
We put infrastructure into Terraform, rebuilt the pipelines so they were readable, and made every deploy a single reviewed change.
Stack
GitHub Actions · Terraform · Docker
Result
Anyone on the team can release, and a deploy takes minutes.

Questions

Do you work in our accounts or yours?

Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.

Can you work alongside our own team?

Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.

How is this priced?

Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.

Tell us what’s broken, slow or expensive.