# gruntwork-io/terragrunt

Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.

Repository: https://github.com/gruntwork-io/terragrunt
Canonical: https://ross.abutalabs.com/products/terragrunt
Homepage: https://terragrunt.com
Language: Go
License: MIT
License Family: permissive
Topics: terraform, devops, cli, aws, developer-tools, opentofu
Last push: 2026-08-26T21:38:21+00:00

## Health v2 (maintenance only)
Score: 94/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 99, release rhythm 85, longevity 100
- inputs: {"age_days": 3754, "days_push": 7, "days_rel": 20, "gap_med": 1.0, "n_releases_24m": 235}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 9808, forks 1221 (observed 2026-08-28T04:10:37.296115+00:00)

## What it is
Terragrunt is a flexible orchestration tool that lets Infrastructure as Code written in OpenTofu/Terraform scale, adding a configuration and orchestration layer on top of tofu/terraform commands. It organizes infrastructure into independently operable units and stacks, manages remote state and DRY shared configuration, and runs operations in dependency order via its Run Queue.

## Use cases
- orchestrate terraform and opentofu deployments across many environments
- keep terraform backend and remote state configuration DRY
- run terraform apply across multiple modules in dependency order
- reduce blast radius by splitting monolithic terraform into units
- bootstrap s3 and dynamodb state backends for terraform
- codify pre and post hooks around terraform runs
- manage multi-account aws infrastructure with terraform

## When to choose
- you manage many terraform/opentofu modules across multiple environments and accounts
- you want DRY shared configuration and automatic remote state setup
- you need dependency-aware orchestration and controlled run ordering
- you want to codify hooks and error handling around IaC runs

## When to avoid
- you have a single small terraform project with simple needs
- your team prefers plain terraform/opentofu workflows without an extra wrapper layer
- you rely on tooling tightly coupled to terraform-native features terragrunt wraps differently

## Facets
- artifact type: cli-tool
- maturity: stable
- function: infrastructure-as-code, deployment, configuration-management, cli, ci-cd
- domain: infrastructure-as-code, cloud-computing, developer-tools
- platform: cli, windows, go, cloud
- tags: terraform, opentofu, iac-orchestration, remote-state, hcl, gruntwork, run-queue, blast-radius, aws, devops, automation, linux, macos

## Member repositories
- gruntwork-io/terragrunt (main) score 94

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:37.296115+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:20:58.142571+00:00, confidence not recorded.
  - readme: https://github.com/gruntwork-io/terragrunt (fetched 2026-08-28T04:10:37.296115+00:00, sha abb36598d691)
  - homepage: https://terragrunt.com (fetched 2026-08-29T08:20:36.665245+00:00, sha 2fb6ad46125f)
  - site_page: https://docs.terragrunt.com (fetched 2026-08-29T08:20:36.675023+00:00, sha 4359038f559f)
  - site_page: https://docs.terragrunt.com/getting-started/quick-start (fetched 2026-08-29T08:20:36.677858+00:00, sha 4359038f559f)
  - site_page: https://terragrunt.com/faqs-overview (fetched 2026-08-29T08:20:36.680521+00:00, sha 8523eb83c5e9)
- Data as of 2026-08-30T08:39:29.467469+00:00.