Skip to content
DevUtils Online

DevOps

act vs terragrunt

act leads by 9.6 · clear

A · leads

act

99.1

72,721 stars · MIT

act versus terragrunt is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 99.1 for act and 89.5 for terragrunt.

act has 72,721 GitHub stars to terragrunt's 9,929, a gap of 62,792 (7.32×). Forks are 2,126 for act and 1,251 for terragrunt. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 93.

Push history: act was last pushed on 16 November 2026 (1 day ago), and terragrunt was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 216 for terragrunt (0.022 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.

Both act and terragrunt are listed as MIT. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In DevOps, both act (72,721 stars) and terragrunt (9,929 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: act is open source, terragrunt is open source.

act is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).

act finishes ahead at 99.1 against terragrunt at 89.5, a 9.6 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

act versus terragrunt metrics
Signal act terragrunt
GitHub stars 72,721 9,929
Forks 2,126 1,251
Open issues 318 216
Adoption 100 82
Activity 100 100
Community 100 93
Issue health 96 70
License 96 96
Self-hosting 100 100
Composite 99.1 89.5

terragrunt

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

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, act or terragrunt?

act has more GitHub stars: 72,721 versus 9,929 for terragrunt. The gap is 62,792 stars.

Which was updated more recently, act or terragrunt?

terragrunt was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.

Can I self-host both act and terragrunt?

Yes. This catalog marks both act and terragrunt as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, act or terragrunt?

act is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. terragrunt is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the act vs terragrunt score?

act scores 99.1 and terragrunt scores 89.5. This page calls that a clear lead for act.

Related comparisons