Skip to content
DevUtils Online

DevOps

act vs semaphore

act leads by 10.1 · clear

A · leads

act

99.1

72,721 stars · MIT

act versus semaphore 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.0 for semaphore.

act has 72,721 GitHub stars to semaphore's 14,420, a gap of 58,301 (5.04×). Forks are 2,126 for act and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 94.

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

Both act and semaphore 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 semaphore (14,420 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, semaphore 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 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).

act finishes ahead at 99.1 against semaphore at 89.0, a 10.1 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 semaphore metrics
Signal act semaphore
GitHub stars 72,721 14,420
Forks 2,126 1,353
Open issues 318 1,075
Adoption 100 86
Activity 100 100
Community 100 94
Issue health 96 52
License 96 96
Self-hosting 100 100
Composite 99.1 89.0

semaphore

Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, act or semaphore?

act has more GitHub stars: 72,721 versus 14,420 for semaphore. The gap is 58,301 stars.

Which was updated more recently, act or semaphore?

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

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

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

act scores 99.1 and semaphore scores 89.0. This page calls that a clear lead for act.

Related comparisons