Skip to content
DevUtils Online

DevOps

kong vs lens

kong leads by 25.8 · decisive

A · leads

kong

97.9

44,388 stars · Apache-2.0

B

lens

72.1

23,248 stars · MIT

kong versus lens 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; lens is written mainly in an unspecified language. The composite score is 97.9 for kong and 72.1 for lens.

kong has 44,388 GitHub stars to lens's 23,248, a gap of 21,140 (1.91×). Forks are 5,242 for kong and 1,466 for lens. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 85.

Push history: kong was last pushed on 17 November 2026 (0 days ago), and lens was last pushed on 11 February 2025 (644 days ago). Open issues stand at 233 for kong (0.005 per star) and 1,165 for lens (0.050 per star). Issue-health scores are 84 and 52; activity scores are 100 and 16.

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. lens 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. License scores in this pair are 96 for kong and 96 for lens. This is a procurement signal, not legal advice.

In DevOps, both kong (44,388 stars) and lens (23,248 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, lens is open source.

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

kong finishes ahead at 97.9 against lens at 72.1, a 25.8 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.

kong versus lens metrics
Signal kong lens
GitHub stars 44,388 23,248
Forks 5,242 1,466
Open issues 233 1,165
Adoption 100 94
Activity 100 16
Community 100 85
Issue health 84 52
License 96 96
Self-hosting 100 100
Composite 97.9 72.1

Questions this page answers

Which has more GitHub stars, kong or lens?

kong has more GitHub stars: 44,388 versus 23,248 for lens. The gap is 21,140 stars.

Which was updated more recently, kong or lens?

kong was pushed more recently: 17 November 2026 versus 11 February 2025 for lens. That is 644 days apart.

Can I self-host both kong and lens?

Yes. This catalog marks both kong and lens 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 lens?

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. lens 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the kong vs lens score?

kong scores 97.9 and lens scores 72.1. This page calls that a decisive lead for kong.

Related comparisons