Skip to content
DevUtils Online

DevOps

act vs werf

act leads by 12.3 · clear

A · leads

act

99.1

72,721 stars · MIT

B

werf

86.8

4,737 stars · Apache-2.0

act versus werf 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 86.8 for werf.

act has 72,721 GitHub stars to werf's 4,737, a gap of 67,984 (15.35×). Forks are 2,126 for act and 241 for werf. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 72.

Push history: act was last pushed on 16 November 2026 (1 day ago), and werf was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 10 for werf (0.002 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. werf 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 werf. This is a procurement signal, not legal advice.

In DevOps, both act (72,721 stars) and werf (4,737 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, werf 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 fork community at 28 points (100 vs 72), and the tightest is self-hosting at 0 points (100 vs 100).

act finishes ahead at 99.1 against werf at 86.8, a 12.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 werf metrics
Signal act werf
GitHub stars 72,721 4,737
Forks 2,126 241
Open issues 318 10
Adoption 100 76
Activity 100 100
Community 100 72
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 99.1 86.8

werf

A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, act or werf?

act has more GitHub stars: 72,721 versus 4,737 for werf. The gap is 67,984 stars.

Which was updated more recently, act or werf?

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

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

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

act scores 99.1 and werf scores 86.8. This page calls that a clear lead for act.

Related comparisons