Zikc2023/kong
stale
significant_divergence
Selected Choose this fork only if its custom debugging or dynamic-behavior patches are the point. If you want current Kong Gateway capabilities, especially newer AI gateway work, upstream is the safer choice.
1harios/kong
stale
significant_divergence
Prefer this fork only if its debugger/runtime patches match a specific internal need. For most adopters, upstream Kong is the safer choice because it is much newer, actively maintained, and more likely to include current AI/MCP and stability fixes.
li-wl/kong
stale
significant_divergence
Choose this fork only if you need its specific legacy customizations; for most adopters, upstream Kong is the safer choice because this fork is far behind, highly divergent, and stale.
nokia/kong
stale
significant_divergence
Choose this fork only if you need a legacy, Nokia-branded Kong branch and are prepared to maintain it yourself. If you want current Kong Gateway capabilities, especially AI/MCP features and ongoing upstream fixes, the upstream project is the better choice.
haifengkao/kong_proxy
stale
significant_divergence
Choose this fork only if you specifically need its legacy behavior and can own the maintenance. For new adopters, upstream Kong is the safer choice because this fork is extremely stale, heavily diverged, and appears to have shed modern features and workflows.
koios-sh/kong
stale
significant_divergence
Choose this fork only if you need its legacy custom behavior and are prepared to own a large stale codebase. For new adopters, upstream Kong is the better default because this fork is far behind and likely missing major current gateway capabilities.
madhupashish/kong
stale
significant_divergence
Prefer this fork only if you need its custom 2023-era gateway changes and can support long-term maintenance yourself. If you want modern Kong Gateway capabilities, active fixes, and AI/MCP progress, upstream is the better default.
bfibitcoin/kong
stale
significant_divergence
Prefer this fork only if you explicitly need its older custom behavior and are prepared to own divergence. If you want current Kong Gateway capabilities, especially AI/MCP features and ongoing maintenance, upstream is the better default.
Amanuttam1192/kong
stale
significant_divergence
Choose this fork only if you need its exact older behavior or custom changes; otherwise the upstream Kong repo is the safer default because it is active, much newer, and includes major API/AI/MCP work this fork lacks.
zhouxiaoxiang/kong
stale
significant_divergence
Prefer upstream unless you specifically need a legacy 2016 Kong baseline. This fork looks too stale and too far behind for new production adoption.