Terragrunt is a popular open-source wrapper around OpenTofu and Terraform for keeping many environments DRY. Over the years it often turns into a maze of includes, hooks and dependencies that only one person understands. We review your set-up and tell you plainly what to keep, what to clean up, and what OpenTofu now does natively.
Layers of includes and dependencies that slow every change and scare new engineers.
Review structure, dependencies, versions and CI — and check what OpenTofu does natively now.
A clear recommendation: keep and clean up, simplify, or go native — with effort and price.
terragrunt.hcl files across three folders.run-all plans take a long time and nobody is sure in which order things apply.for_each for providers, which simplifies multi-region set-ups.3We recommend one, with reasons. There is no default.
| Answer | When it fits | What we do |
|---|---|---|
| Keep and clean up | Many environments and accounts; Terragrunt's dependency handling and stacks are used well | Flatten includes, pin versions, speed up run-all, document the layout |
| Simplify | Terragrunt mainly fills backend config and module sources | Move those parts to native OpenTofu; keep Terragrunt only where it helps |
| Go native | A few environments; Terragrunt adds more layers than value | Plain OpenTofu with early evaluation and provider for_each; state moved with a clean plan |
How your units, includes and dependencies actually connect — as a diagram.
Version drift, duplicated config, slow paths, risky hooks, ranked by impact.
Keep, simplify or go native — with the reasons and the effort for each.
For the clean-up or migration, if you want us to do it.
Shown for a typical mid-size setup. Larger platforms take longer; the scope and price are fixed on the first call.
Read-only access to the IaC repositories and CI.
Structure, dependencies, versions, run times, CI.
Report, structure map and walk-through with your team.
Fixed price, agreed on the first call. One invoice after the report.
No. For large multi-account set-ups it often stays the right tool. We look at what yours does today and recommend accordingly.
Yes. Terragrunt supports both OpenTofu and Terraform, so you can switch the engine without dropping Terragrunt.
That is Gruntwork's commercial offer. We can compare it with an open set-up in GitLab — see OpenTofu pipelines in GitLab.
And how many repositories. Enough to confirm the price on a call.