Terragrunt

Why use Terragrunt?

One of the key lessons from nearly a decade of working with OpenTofu and Terraform is that when you scale environments, regions, or overall surface area, complexity can overwhelm you. 

Terragrunt let you manage complexity by working in small, deployable units of infrastructure.

What is Terragrunt?

Terragrunt sits on top of either OpenTofu or Terraform and serves as your primary tool for deploying infrastructure. 

With Terragrunt, you launch all infrastructure as an instance of an OpenTofu or Terraform module. Each such instance is known as a unit of infrastructure, or simply “unit”, and is represented as a single terragrunt.hcl file.

Terragrunt features

Terragrunt gives you the ability to configure and work in “units of infrastructure” so that you can:

Handle dependencies between units

Plan or apply multiple units at once

Define a global variables “hierarchy” to configure units

Manage common, repeated patterns of units

Dynamically configure Terraform/OpenTofu providers

Terragrunt vs. OpenTofu/Terraform

Terraform and OpenTofu work well for defining reusable infrastructure patterns. But when it comes to deploying those patterns, teams need a different set of facilities to support working in small units of infrastructure, which is where Terragrunt shines.

While it’s possible to scale with OpenTofu or Terraform alone, we’ve found consistent success when using each tool at what it’s best for.

Support

Get commercial support  for

Terragrunt

Gruntwork offers commercial and enterprise-grade support for
Terragrunt, including help with the following:

Guidance on best practices

Get recommendations on best practices for using OpenTofu at scale.

Roadmap sharing

We’ll share advance roadmap plans with you and use your feedback to drive our priorities.

Prioritized features

Get help troubleshooting OpenTofu issues, and get priority fixes for any bugs you find in OpenTofu.

Prioritized bug fixes

Spotlight your feature requests to the OpenTofu community and prepare it for consideration by the Technical Steering Committee.

Contact Sales

MIGRATION

Migrate to

Terragrunt

Many teams hit the limits of plain Terraform or OpenTofu as they scale to
hundreds or thousands of “deployable units” of infrastructure.

Audit your current Devops estate

You need to manage infrastructure across multiple regions, multiple environments, or multiple cloud providers and you need a better way to handle the growing complexity.

Set a Migration plan

You’re approaching hundreds of instances of OpenTofu/Terraform modules in your estate and managing them all has become a challenge.

Train your team on Terragrunt

You’re supporting a large number of developers with a growing sprawl of patterns across your infrastructure code base and need to enforce a common set of standards.

Complete a migration

You have common “collections” of OpenTofu/Terraform code for standing up new customers, environments or teams that have dependencies among the component parts, and you’re having trouble maintaining it all.

Contact Sales

Platform

Services

Open Source

Resources

Company