Skip to content
DevUtils Online

DevOps

act vs infracost

act leads by 7.3 · clear

A · leads

act

99.1

72,721 stars · MIT

B

infracost

91.8

12,622 stars · Apache-2.0

act versus infracost 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 91.8 for infracost.

act has 72,721 GitHub stars to infracost's 12,622, a gap of 60,099 (5.76×). Forks are 2,126 for act and 702 for infracost. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 86.

Push history: act was last pushed on 16 November 2026 (1 day ago), and infracost was last pushed on 16 November 2026 (1 day ago). Open issues stand at 318 for act (0.004 per star) and 4 for infracost (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.

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. infracost is listed as Apache-2.0, 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. License scores in this pair are 96 for act and 96 for infracost. This is a procurement signal, not legal advice.

In DevOps, both act (72,721 stars) and infracost (12,622 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, infracost is open source.

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

act finishes ahead at 99.1 against infracost at 91.8, a 7.3 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 infracost metrics
Signal act infracost
GitHub stars 72,721 12,622
Forks 2,126 702
Open issues 318 4
Adoption 100 84
Activity 100 100
Community 100 86
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 99.1 91.8

Questions this page answers

Which has more GitHub stars, act or infracost?

act has more GitHub stars: 72,721 versus 12,622 for infracost. The gap is 60,099 stars.

Which was updated more recently, act or infracost?

Both were last pushed on 16 November 2026.

Can I self-host both act and infracost?

Yes. This catalog marks both act and infracost 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 infracost?

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. infracost is listed as Apache-2.0, 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 infracost score?

act scores 99.1 and infracost scores 91.8. This page calls that a clear lead for act.

Related comparisons