Skip to content
DevUtils Online

DevOps

apisix vs kong

kong leads by 5.6 · narrow

A

apisix

92.3

17,333 stars · Apache-2.0

B · leads

kong

97.9

44,388 stars · Apache-2.0

apisix versus kong is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Lua. The composite score is 92.3 for apisix and 97.9 for kong.

kong has 44,388 GitHub stars to apisix's 17,333, a gap of 27,055 (2.56×). Forks are 3,004 for apisix and 5,242 for kong. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 94 versus 100.

Push history: apisix was last pushed on 13 November 2026 (4 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 230 for apisix (0.013 per star) and 233 for kong (0.005 per star). Issue-health scores are 84 and 84; activity scores are 92 and 100.

Both apisix and kong 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 apisix (17,333 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: apisix 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 adoption at 9 points (91 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

kong finishes ahead at 97.9 against apisix at 92.3, a 5.6 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.

apisix versus kong metrics
Signal apisix kong
GitHub stars 17,333 44,388
Forks 3,004 5,242
Open issues 230 233
Adoption 91 100
Activity 92 100
Community 94 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 92.3 97.9

Questions this page answers

Which has more GitHub stars, apisix or kong?

kong has more GitHub stars: 44,388 versus 17,333 for apisix. The gap is 27,055 stars.

Which was updated more recently, apisix or kong?

kong was pushed more recently: 17 November 2026 versus 13 November 2026 for apisix. That is 4 days apart.

Can I self-host both apisix and kong?

Yes. This catalog marks both apisix 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, apisix or kong?

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

kong scores 97.9 and apisix scores 92.3. This page calls that a narrow lead for kong.

Related comparisons