A · leads
kong
97.9
44,388 stars · Apache-2.0
DevOps
kong leads by 9.0 · clear
A · leads
97.9
44,388 stars · Apache-2.0
B
88.9
14,420 stars · MIT
kong versus semaphore is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. kong is written mainly in Lua; semaphore is written mainly in Go. The composite score is 97.9 for kong and 88.9 for semaphore.
kong has 44,388 GitHub stars to semaphore's 14,420, a gap of 29,968 (3.08×). Forks are 5,242 for kong and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 84.
Push history: kong was last pushed on 17 November 2026 (0 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 233 for kong (0.005 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
kong 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. 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. License scores in this pair are 96 for kong and 96 for semaphore. This is a procurement signal, not legal advice.
In DevOps, both kong (44,388 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: kong is open source, semaphore is open source.
kong 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 32 points (84 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
kong finishes ahead at 97.9 against semaphore at 88.9, a 9.0 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | kong | semaphore |
|---|---|---|
| GitHub stars | 44,388 | 14,420 |
| Forks | 5,242 | 1,353 |
| Open issues | 233 | 1,075 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 88.9 |
🦍 The API and AI Gateway
Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.
kong has more GitHub stars: 44,388 versus 14,420 for semaphore. The gap is 29,968 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both kong and semaphore as self-hostable. Confirm each project's deploy docs before you plan a migration.
kong 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. 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.
kong scores 97.9 and semaphore scores 88.9. This page calls that a clear lead for kong.