Skip to content
DevUtils Online

DevOps

semaphore vs sentry

semaphore leads by 5.5 · narrow

A · leads

semaphore

88.9

14,420 stars · MIT

B

sentry

83.4

45,789 stars · license n/a

semaphore versus sentry is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. semaphore is written mainly in Go; sentry is written mainly in Python. The composite score is 88.9 for semaphore and 83.4 for sentry.

sentry has 45,789 GitHub stars to semaphore's 14,420, a gap of 31,369 (3.18×). Forks are 1,353 for semaphore and 4,980 for sentry. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 85 versus 100.

Push history: semaphore was last pushed on 17 November 2026 (0 days ago), and sentry was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,075 for semaphore (0.075 per star) and 2,213 for sentry (0.048 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.

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. sentry is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for semaphore and 30 for sentry. This is a procurement signal, not legal advice.

Only semaphore is marked self-hostable here (14,420 stars, deploy score 100). sentry is not (45,789 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: semaphore is open source, sentry is unpriced in this catalog.

The lead is split. semaphore is furthest ahead on license flexibility (96 to 30), while sentry is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.

semaphore finishes ahead at 88.9 against sentry at 83.4, a 5.5 point narrow 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.

semaphore versus sentry metrics
Signal semaphore sentry
GitHub stars 14,420 45,789
Forks 1,353 4,980
Open issues 1,075 2,213
Adoption 89 100
Activity 100 100
Community 85 100
Issue health 52 70
License 96 30
Self-hosting 100 35
Composite 88.9 83.4

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

sentry has more GitHub stars: 45,789 versus 14,420 for semaphore. The gap is 31,369 stars.

Which was updated more recently, semaphore or sentry?

Both were last pushed on 17 November 2026.

Can I self-host both semaphore and sentry?

Only semaphore is marked self-hostable. sentry is not.

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

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. sentry is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the semaphore vs sentry score?

semaphore scores 88.9 and sentry scores 83.4. This page calls that a narrow lead for semaphore.

Related comparisons