Home›Services›Terragrunt review

Terragrunt grew with you. Is it still helping?

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.

from $1,800 · fixed price Scope fixed on the first call Read-only access
The problem

Layers of includes and dependencies that slow every change and scare new engineers.

What we do

Review structure, dependencies, versions and CI — and check what OpenTofu does natively now.

The result

A clear recommendation: keep and clean up, simplify, or go native — with effort and price.

Is this you?

What changed around Terragrunt

Three possible answers

We recommend one, with reasons. There is no default.

AnswerWhen it fitsWhat we do
Keep and clean upMany environments and accounts; Terragrunt's dependency handling and stacks are used wellFlatten includes, pin versions, speed up run-all, document the layout
SimplifyTerragrunt mainly fills backend config and module sourcesMove those parts to native OpenTofu; keep Terragrunt only where it helps
Go nativeA few environments; Terragrunt adds more layers than valuePlain OpenTofu with early evaluation and provider for_each; state moved with a clean plan

What you get

Structure map

How your units, includes and dependencies actually connect — as a diagram.

Findings

Version drift, duplicated config, slow paths, risky hooks, ranked by impact.

Recommendation

Keep, simplify or go native — with the reasons and the effort for each.

Fixed quote

For the clean-up or migration, if you want us to do it.

How it goes

Shown for a typical mid-size setup. Larger platforms take longer; the scope and price are fixed on the first call.

  1. Day 1

    Access

    Read-only access to the IaC repositories and CI.

  2. Day 2–3

    Review

    Structure, dependencies, versions, run times, CI.

  3. Day 4–5

    Recommendation

    Report, structure map and walk-through with your team.

What we need from you

  • Read access to the Terragrunt repositories and CI configuration.
  • One engineer who knows the history of the layout.

Not included

  • The clean-up or migration itself — quoted separately.
  • Reviewing the cloud resources themselves — see the IaC Health Check.
from $1,800

Fixed price, agreed on the first call. One invoice after the report.

What changes the price

  • Number of units and environments.
  • Number of repositories.

Questions teams ask

Are you against Terragrunt?

No. For large multi-account set-ups it often stays the right tool. We look at what yours does today and recommend accordingly.

Does Terragrunt work with OpenTofu?

Yes. Terragrunt supports both OpenTofu and Terraform, so you can switch the engine without dropping Terragrunt.

Should we buy Terragrunt Scale?

That is Gruntwork's commercial offer. We can compare it with an open set-up in GitLab — see OpenTofu pipelines in GitLab.

Often done together

Tell us how many environments Terragrunt manages

And how many repositories. Enough to confirm the price on a call.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public announcements, documentation and legal texts, for orientation only; not legal advice. Terragrunt is a trademark of Gruntwork. Terraform is a trademark of HashiCorp, an IBM company.
  1. Terragrunt: official site
  2. OpenTofu blog: OpenTofu 1.8.0 (Jul 29, 2024)
  3. OpenTofu blog: OpenTofu 1.9.0 (Jan 10, 2025)
Book a 30-minute call