Services / Infrastructure as code
02
Infrastructure your team can review, repeat and roll back.
We bring existing cloud resources under Terraform or OpenTofu, set up remote state and delivery pipelines, and leave you with modules and documentation your team owns.
Who it is for
- Teams whose infrastructure was built by hand in the cloud console
- Companies that need a second environment (staging, a new region, a dedicated client stack) and cannot reproduce the first
- Teams whose Terraform has drifted, or that only one person understands
Signs you need it
- Nobody knows exactly how production was built
- Creating a new environment takes weeks
- Changes happen in the console and are not tracked
- A Terraform plan shows changes nobody made
What is included
Import and codify
Existing resources brought under Terraform without downtime, using import blocks and careful plan reviews.
State and structure
Remote state with locking, clean separation between environments, and a module layout that fits the size of your team.
Pipelines for infrastructure
Plan on every pull request, apply on merge, with an approval step before production.
Keyless authentication
OIDC from GitHub Actions or GitLab to AWS and Azure, so no long-lived cloud keys are stored in CI.
Guardrails
Tagging, cost limits and security rules checked automatically before a change reaches production.
What you get
- Terraform repository with reusable modules
- Delivery pipelines for infrastructure changes
- Runbook for common changes
- Handover session with your engineers
Timeline
- Week 1
Inventory of what exists and design of the target layout
- Weeks 2–4
Import, refactor and pipelines (typical; depends on size)
- Final week
Documentation and handover
Scoped per project after a short inventory. Often follows a cloud review.
Common questions
Terraform or OpenTofu?
Either. We recommend one based on your licensing preferences and existing tooling; the code is nearly identical.
Will importing cause downtime?
No. Importing only records existing resources in state. Every plan is reviewed so nothing is replaced unexpectedly.
We already use CloudFormation, Bicep or Pulumi.
We can work within those, or migrate if there is a good reason to.
OTHER SERVICES