Skip to content
DevUtils Online

DevOps

semaphore vs witr

Too close to call · 93.1 to 93.3

A · level

semaphore

93.1

14,420 stars · MIT

B · level

witr

93.3

23,030 stars · Apache-2.0

semaphore versus witr 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 93.1 for semaphore and 93.3 for witr.

witr has 23,030 GitHub stars to semaphore's 14,420, a gap of 8,610 (1.60×). Forks are 1,353 for semaphore and 811 for witr. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 100 versus 93.

Push history: semaphore was last pushed on 17 November 2026 (0 days ago), and witr was last pushed on 23 October 2026 (25 days ago). Open issues stand at 1,075 for semaphore (0.075 per star) and 8 for witr (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 78.

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. witr 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 semaphore and 96 for witr. This is a procurement signal, not legal advice.

In DevOps, both semaphore (14,420 stars) and witr (23,030 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: semaphore is open source, witr is open source.

The lead is split. semaphore is furthest ahead on recent activity (100 to 78), while witr is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.

Composite score: semaphore 93.1, witr 93.3. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.

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.

semaphore versus witr metrics
Signal semaphore witr
GitHub stars 14,420 23,030
Forks 1,353 811
Open issues 1,075 8
Adoption 95 100
Activity 100 78
Community 100 93
Issue health 52 96
License 96 96
Self-hosting 100 100
Composite 93.1 93.3

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, semaphore or witr?

witr has more GitHub stars: 23,030 versus 14,420 for semaphore. The gap is 8,610 stars.

Which was updated more recently, semaphore or witr?

semaphore was pushed more recently: 17 November 2026 versus 23 October 2026 for witr. That is 25 days apart.

Can I self-host both semaphore and witr?

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

Which license is easier to embed in a commercial product, semaphore or witr?

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

Neither tool clears a one-point margin. semaphore scores 93.1 and witr scores 93.3.

Related comparisons