Infrastructure as Code & CI/CD
A real infrastructure delivery framework, not a folder of Terraform files.
Most teams start with a Terraform repo and stop there — no environment structure, no branching rules, no review discipline, and pipelines that just run apply and hope. I build the framework around the code: how changes are structured, reviewed, tested and promoted, so infrastructure delivery holds up as the team and the codebase grow.
What’s included
- Terraform & Terragrunt foundations — DRY, environment-aware structure instead of copy-pasted modules per environment
- Branching & review rules — a workflow that matches your team’s risk tolerance, from trunk-based to environment-gated promotion
- CI/CD pipelines — GitHub Actions or GitLab CI for plan/apply workflows, with the right approvals and guardrails at each stage
- Claude Code skills for infrastructure — custom skills that help maintain the codebase and review pull requests against your own conventions, not generic linting
- Module & state hygiene — versioned modules, remote state, and drift detection so the codebase stays trustworthy over time
Who this is for
Teams who already have Terraform but have outgrown “one engineer runs apply from their laptop,” and want infrastructure changes to be reviewed, repeatable and safe to hand off — without hiring a dedicated platform team to build the framework first.