Most cloud accounts have resources nobody wrote down: created in the console, changed by hand, understood by one person. We import them into OpenTofu without touching what runs, so every future change is reviewed, repeatable and visible in Git.
Part of your cloud was built by hand and nobody can rebuild it.
Import it into readable OpenTofu modules with import blocks.1
A plan that shows no changes — and every future change reviewed in Git.
plan must show no changes. If it doesn't, we fix the code, never the live resource.Every resource in the agreed accounts and regions, marked as already in code, to import, or to leave alone.
OpenTofu modules organised by environment and purpose, not one generated file of thousands of lines.
State stored in GitLab, a plan with no changes as proof that nothing live was touched.
Plan on every merge request, apply after approval, scheduled drift check.
A short guide to making changes the new way, and a session with your team.
The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.
We list what exists, agree the scope and the final price.
Import blocks and code, account by account, until the plan is clean.
CI pipeline, drift check, guide and session.
Fixed price after the inventory in step 1. Paid on completion.
Importing only writes to state. We then require a plan with no changes before handover, so nothing is modified.
AWS, Azure, Google Cloud and other platforms with an OpenTofu provider.
The approach is the same. We use OpenTofu by default because it is open source; if you prefer Terraform, tell us.
They can, but the drift check will flag every manual change. Most teams switch to merge requests within weeks.
Accounts, regions and a rough number of resources — enough for a price.