Skip to content
DevUtils Online

DevOps

devops-exercises vs kong

kong leads by 22.1 · decisive

B · leads

kong

94.0

44,388 stars · Apache-2.0

devops-exercises versus kong is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. devops-exercises is written mainly in Python; kong is written mainly in Lua. The composite score is 71.9 for devops-exercises and 94.0 for kong.

devops-exercises has 86,874 GitHub stars to kong's 44,388, a gap of 42,486 (1.96×). Forks are 20,674 for devops-exercises and 5,242 for kong. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 86.

Push history: devops-exercises was last pushed on 27 December 2025 (325 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 59 for devops-exercises (0.001 per star) and 233 for kong (0.005 per star). Issue-health scores are 96 and 84; activity scores are 36 and 100.

devops-exercises 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. 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 30 for devops-exercises and 96 for kong. This is a procurement signal, not legal advice.

Only kong is marked self-hostable here (44,388 stars, deploy score 100). devops-exercises is not (86,874 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: devops-exercises is unpriced in this catalog, kong is open source.

The lead is split. devops-exercises is furthest ahead on fork community (100 to 86), while kong is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

kong finishes ahead at 94.0 against devops-exercises at 71.9, a 22.1 point decisive 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.

devops-exercises versus kong metrics
Signal devops-exercises kong
GitHub stars 86,874 44,388
Forks 20,674 5,242
Open issues 59 233
Adoption 100 94
Activity 36 100
Community 100 86
Issue health 96 84
License 30 96
Self-hosting 35 100
Composite 71.9 94.0

devops-exercises

Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, devops-exercises or kong?

devops-exercises has more GitHub stars: 86,874 versus 44,388 for kong. The gap is 42,486 stars.

Which was updated more recently, devops-exercises or kong?

kong was pushed more recently: 17 November 2026 versus 27 December 2025 for devops-exercises. That is 325 days apart.

Can I self-host both devops-exercises and kong?

Only kong is marked self-hostable. devops-exercises is not.

Which license is easier to embed in a commercial product, devops-exercises or kong?

devops-exercises 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. 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.

Who wins the devops-exercises vs kong score?

kong scores 94.0 and devops-exercises scores 71.9. This page calls that a decisive lead for kong.

Related comparisons