A · leads
kong
97.9
44,388 stars · Apache-2.0
DevOps
kong leads by 8.7 · clear
A · leads
97.9
44,388 stars · Apache-2.0
B
89.2
23,030 stars · Apache-2.0
kong versus witr 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; witr is written mainly in Go. The composite score is 97.9 for kong and 89.2 for witr.
kong has 44,388 GitHub stars to witr's 23,030, a gap of 21,358 (1.93×). Forks are 5,242 for kong and 811 for witr. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 78.
Push history: kong 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 233 for kong (0.005 per star) and 8 for witr (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 78.
Both kong and witr are listed as Apache-2.0. 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 kong (44,388 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: kong is open source, witr is open source.
The lead is split. kong is furthest ahead on recent activity (100 to 78), while witr is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
kong finishes ahead at 97.9 against witr at 89.2, a 8.7 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 | witr |
|---|---|---|
| GitHub stars | 44,388 | 23,030 |
| Forks | 5,242 | 811 |
| Open issues | 233 | 8 |
| Adoption | 100 | 94 |
| Activity | 100 | 78 |
| Community | 100 | 78 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 89.2 |
🦍 The API and AI Gateway
Why is this running? Trace any process, port, container, or file back to what started it - CLI + TUI.
kong has more GitHub stars: 44,388 versus 23,030 for witr. The gap is 21,358 stars.
kong was pushed more recently: 17 November 2026 versus 23 October 2026 for witr. That is 25 days apart.
Yes. This catalog marks both kong and witr 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. 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.
kong scores 97.9 and witr scores 89.2. This page calls that a clear lead for kong.