Skip to content
DevUtils Online

DevOps

kong vs opensre

kong leads by 4.4 · narrow

A · leads

kong

97.9

44,388 stars · Apache-2.0

B

opensre

93.5

12,838 stars · Apache-2.0

kong versus opensre 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; opensre is written mainly in Python. The composite score is 97.9 for kong and 93.5 for opensre.

kong has 44,388 GitHub stars to opensre's 12,838, a gap of 31,550 (3.46×). Forks are 5,242 for kong and 1,884 for opensre. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 88.

Push history: kong was last pushed on 17 November 2026 (0 days ago), and opensre was last pushed on 17 November 2026 (0 days ago). Open issues stand at 233 for kong (0.005 per star) and 11 for opensre (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.

Both kong and opensre are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In DevOps, both kong (44,388 stars) and opensre (12,838 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, opensre is open source.

The lead is split. kong is furthest ahead on fork community (100 to 88), while opensre is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.

kong finishes ahead at 97.9 against opensre at 93.5, a 4.4 point narrow 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 opensre metrics
Signal kong opensre
GitHub stars 44,388 12,838
Forks 5,242 1,884
Open issues 233 11
Adoption 100 88
Activity 100 100
Community 100 88
Issue health 84 96
License 96 96
Self-hosting 100 100
Composite 97.9 93.5

Questions this page answers

Which has more GitHub stars, kong or opensre?

kong has more GitHub stars: 44,388 versus 12,838 for opensre. The gap is 31,550 stars.

Which was updated more recently, kong or opensre?

Both were last pushed on 17 November 2026.

Can I self-host both kong and opensre?

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

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. opensre 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 kong vs opensre score?

kong scores 97.9 and opensre scores 93.5. This page calls that a narrow lead for kong.

Related comparisons