Skip to content
DevUtils Online

DevOps

act vs chef

act leads by 8.9 · clear

A · leads

act

98.8

72,721 stars · MIT

B

chef

89.9

8,268 stars · Apache-2.0

act versus chef is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. act is written mainly in Go; chef is written mainly in Ruby. The composite score is 98.8 for act and 89.9 for chef.

act has 72,721 GitHub stars to chef's 8,268, a gap of 64,453 (8.80×). Forks are 2,126 for act and 2,520 for chef. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 98 versus 100.

Push history: act was last pushed on 16 November 2026 (1 day ago), and chef was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 408 for chef (0.049 per star). Issue-health scores are 96 and 70; 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. chef 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 chef. This is a procurement signal, not legal advice.

In DevOps, both act (72,721 stars) and chef (8,268 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, chef is open source.

The lead is split. act is furthest ahead on issue health (96 to 70), while chef is furthest ahead on fork community (100 to 98). Choose the dimension a rollout cannot compromise on.

act finishes ahead at 98.8 against chef at 89.9, a 8.9 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 chef metrics
Signal act chef
GitHub stars 72,721 8,268
Forks 2,126 2,520
Open issues 318 408
Adoption 100 81
Activity 100 100
Community 98 100
Issue health 96 70
License 96 96
Self-hosting 100 100
Composite 98.8 89.9

chef

Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, act or chef?

act has more GitHub stars: 72,721 versus 8,268 for chef. The gap is 64,453 stars.

Which was updated more recently, act or chef?

chef 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 chef?

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

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. chef 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 chef score?

act scores 98.8 and chef scores 89.9. This page calls that a clear lead for act.

Related comparisons