Repository design
Stacks, modules, environments and ownership boundaries.
DevOps & platform
Infrastructure as code consulting
Organise Terraform, Bicep, CloudFormation or Pulumi so infrastructure change is reviewable and repeatable. Make delivery and operations calmer, more repeatable and easier for the owning team to change.
01 / Scope
Work on the system, not around it.
The engagement starts with the architecture and working constraints already in place. We agree the risky paths, make the changes visible and leave ownership with the team running the system.
State and identity
Backends, locking, execution roles and secret handling.
Delivery
Plan review, policy checks, approvals and drift detection.
Migration
Import unmanaged resources and retire unsafe patterns.
02 / Method
Make delivery and operations calmer, more repeatable and easier for the owning team to change.
Scope and access are agreed before the work begins. Decisions, changes and residual risk remain visible throughout the engagement.
Trace the current path
Start with evidence, owners and the constraints that shape the safe solution.
Build one working pattern
Prioritise by practical impact and implement with the people who operate the system.
Extend it with the team
Test the changed path, document the decision and hand over a backlog that still makes sense.
03 / What remains
- 01IaaC architecture and migration plan
- 02Reusable modules and reference stack
- 03Plan/apply pipeline
- 04Ownership and exception documentation
Related work
Continue with the adjacent problem.
04 / Talk to Gritt
What is happening in the system?
Send the cloud, workload or deadline. An engineer will reply and tell you whether this is the right scope.
email