Skip to content
DevUtils Online

DevOps

cli vs kong

kong leads by 19.3 · decisive

A

cli

78.6

38,719 stars · BSD-3-Clause

B · leads

kong

97.9

44,388 stars · Apache-2.0

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

kong has 44,388 GitHub stars to cli's 38,719, a gap of 5,669 (1.15×). Forks are 4,123 for cli and 5,242 for kong. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 97 versus 100.

Push history: cli was last pushed on 17 December 2024 (700 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 365 for cli (0.009 per star) and 233 for kong (0.005 per star). Issue-health scores are 84 and 84; activity scores are 16 and 100.

cli is listed as BSD-3-Clause, 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 cli and 96 for kong. This is a procurement signal, not legal advice.

In DevOps, both cli (38,719 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: cli is open source, kong is open source.

kong is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 84 points (16 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

kong finishes ahead at 97.9 against cli at 78.6, a 19.3 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.

cli versus kong metrics
Signal cli kong
GitHub stars 38,719 44,388
Forks 4,123 5,242
Open issues 365 233
Adoption 99 100
Activity 16 100
Community 97 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 78.6 97.9

cli

🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cli or kong?

kong has more GitHub stars: 44,388 versus 38,719 for cli. The gap is 5,669 stars.

Which was updated more recently, cli or kong?

kong was pushed more recently: 17 November 2026 versus 17 December 2024 for cli. That is 700 days apart.

Can I self-host both cli and kong?

Yes. This catalog marks both cli and kong as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, cli or kong?

cli is listed as BSD-3-Clause, 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.

Who wins the cli vs kong score?

kong scores 97.9 and cli scores 78.6. This page calls that a decisive lead for kong.

Related comparisons