Terragunt Services
Get Support for Terragrunt
Get help with strategy, planning, or troubleshooting.
Work directly with the Terragrunt team.
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.
When is it time to adopt Terragrunt?
You’re scaling environments, regions or clouds.
You need to manage infrastructure across multiple environments, regions, or cloud providers and you need a better way to handle the growing complexity.
You’re scaling total infrastructure surface area
You’re approaching hundreds of instances of OpenTofu/Terraform modules in your estate and managing them all has become a challenge.
You need to enforce company-wide IaC standards.
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.
You need to automate repetitive IaC tasks.
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.
What’s New with Terragrunt
Follow the Road to Terragrunt 1.0
We’re working towards Terragrunt 1.0, which includes exciting new releases like Terragrunt Stacks, first-class support for Terragrunt Units, and a Remote Execution Engine.
Get Commercial Support for Terragrunt
Gruntwork offers commercial and enterprise-grade support for
Terragrunt, including help with the following:
Guidance on best practices
We can advise you on best practices for configuring Terragrunt foundations, and using Terragrunt at scale.
Prioritized features
We’ll work with you to shape your feature request to be useful for the broader Terragrunt community and prioritize it on the Terragrunt roadmap.
Roadmap sharing
We’ll share advance roadmap plans with you and use your feedback to drive our priorities.
Prioritized bug fixes
If you find bugs in Terragrunt and report them to us, we’ll prioritize a fix
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.
With migration assistance, Gruntwork can help you:
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.
Community Case Studies
These write-ups and videos were produced independently by the
Terragrunt community without sponsorship or support from Gruntwork.
Have a compelling Terragrunt migration story to share! Contact us, and we’ll list it here.