Skip to content
DevUtils Online

DevOps

kong vs wtf

kong leads by 8.1 · clear

A · leads

kong

97.9

44,388 stars · Apache-2.0

B

wtf

89.8

17,154 stars · MPL-2.0

kong versus wtf 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; wtf is written mainly in Go. The composite score is 97.9 for kong and 89.8 for wtf.

kong has 44,388 GitHub stars to wtf's 17,154, a gap of 27,234 (2.59×). Forks are 5,242 for kong and 866 for wtf. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 79.

Push history: kong was last pushed on 17 November 2026 (0 days ago), and wtf was last pushed on 14 November 2026 (3 days ago). Open issues stand at 233 for kong (0.005 per star) and 107 for wtf (0.006 per star). Issue-health scores are 84 and 84; 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for kong and 78 for wtf. This is a procurement signal, not legal advice.

In DevOps, both kong (44,388 stars) and wtf (17,154 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, wtf is open source.

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

kong finishes ahead at 97.9 against wtf at 89.8, a 8.1 point clear 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.

kong versus wtf metrics
Signal kong wtf
GitHub stars 44,388 17,154
Forks 5,242 866
Open issues 233 107
Adoption 100 91
Activity 100 100
Community 100 79
Issue health 84 84
License 96 78
Self-hosting 100 100
Composite 97.9 89.8

Questions this page answers

Which has more GitHub stars, kong or wtf?

kong has more GitHub stars: 44,388 versus 17,154 for wtf. The gap is 27,234 stars.

Which was updated more recently, kong or wtf?

kong was pushed more recently: 17 November 2026 versus 14 November 2026 for wtf. That is 3 days apart.

Can I self-host both kong and wtf?

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

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

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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the kong vs wtf score?

kong scores 97.9 and wtf scores 89.8. This page calls that a clear lead for kong.

Related comparisons