Skip to content

What we do

Platform Engineering

Terraform and Bicep infrastructure as code, with the governance to keep it from drifting.

  • CAF: Ready, Govern
  • WAF: Operational Excellence, Reliability

The problem

Infrastructure as code solves the deployment problem and creates a governance one. Without module standards, state isolation and policy-as-code in the pipeline, Terraform simply lets drift happen faster and in more places at once.

You probably need this if

  • Every team has its own copy of the same Terraform module, and they have diverged
  • Nobody is confident about what a plan will do until it has been applied
  • State files sit somewhere everyone can reach and nobody has audited
  • Long-lived service principal secrets are in the pipeline because rotating them broke something once

Recognise more than one of those? A CAF readiness assessment gives you a baseline in three to four weeks, before you commit to anything longer.

What the service covers

  • Terraform module library with versioning, and a module registry your teams consume rather than copy
  • Remote state design: isolation boundaries, locking, and least-privilege access to state itself
  • Policy-as-code in the pipeline so non-conformant plans fail before apply, not after deployment
  • Drift detection on a schedule, with reconciliation as a tracked work item rather than a manual fix
  • CI/CD via Azure DevOps or GitHub Actions using workload identity federation, so there are no long-lived service principal secrets to rotate or leak
  • Bicep where it fits better than Terraform, which for Azure-only estates is more often than most consultancies admit

What happens if someone applies straight to production this afternoon?

If the answer depends on who it is, the gate is a person rather than a pipeline. Book a call and we will look at where the controls should sit.