A
jenkins
91.3
26,788 stars · MIT
DevOps
kong leads by 5.7 · narrow
A
91.3
26,788 stars · MIT
B · leads
97.0
44,388 stars · Apache-2.0
jenkins versus kong is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. jenkins is written mainly in Java; kong is written mainly in Lua. The composite score is 91.3 for jenkins and 97.0 for kong.
kong has 44,388 GitHub stars to jenkins's 26,788, a gap of 17,600 (1.66×). Forks are 9,837 for jenkins and 5,242 for kong. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 100 versus 93.
Push history: jenkins was last pushed on 17 November 2026 (0 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,618 for jenkins (0.135 per star) and 233 for kong (0.005 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
jenkins 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. 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. License scores in this pair are 96 for jenkins and 96 for kong. This is a procurement signal, not legal advice.
In DevOps, both jenkins (26,788 stars) and kong (44,388 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: jenkins is open source, kong is open source.
The lead is split. jenkins is furthest ahead on fork community (100 to 93), while kong is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
kong finishes ahead at 97.0 against jenkins at 91.3, a 5.7 point narrow 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 | jenkins | kong |
|---|---|---|
| GitHub stars | 26,788 | 44,388 |
| Forks | 9,837 | 5,242 |
| Open issues | 3,618 | 233 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.3 | 97.0 |
Jenkins automation server
🦍 The API and AI Gateway
kong has more GitHub stars: 44,388 versus 26,788 for jenkins. The gap is 17,600 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both jenkins and kong as self-hostable. Confirm each project's deploy docs before you plan a migration.
jenkins 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kong scores 97.0 and jenkins scores 91.3. This page calls that a narrow lead for kong.