/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

Kong/kong

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T20:06:56.996Z

1mo ago

Kong/kong

Kong/kong is the main Kong Gateway repository: a cloud-native, platform-agnostic API and AI Gateway with plugin-based extensibility. It is active, widely used, and still receiving recent commits as of 2026-03-27. For fork interest, this is a large, mature upstream with a broad surface area around traffic routing, API management, and AI/MCP gateway features.

Loading tags...

Stars43,067

Forks5,105

Default branchmaster

Last pushed2026-03-27T17:42:51Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

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.

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.

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.

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.

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.

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.

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.

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.

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.

Prefer upstream unless you specifically need a legacy 2016 Kong baseline. This fork looks too stale and too far behind for new production adoption.

Fork comparison

Zikc2023/kong

38/100

stale

significant_divergence

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.

Likely purpose

A customized Kong Gateway build for teams that want to instrument, debug, and patch gateway behavior locally instead of tracking upstream closely.

Best for

Platform engineers who need to instrument or alter Kong internals.; Teams maintaining a long-lived internal gateway fork.; Developers debugging Lua/OpenResty behavior across multiple workers.; Users who value fork-specific patches over staying current with upstream releases.

Additional features

Dynamic hook support and related docs/workflows.
Emmy Lua debugger support for busted and multi-worker debugging.
A patched OpenResty/ngx_lua path that suggests custom upstream keepalive behavior.
Custom proxy-cache behavior around the `age` parameter.
Fork-specific default configuration and test harness changes for local gateway development.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.

Missing features

Upstream Kong commits and fixes after the fork point, including recent AI-proxy and Gemini/OpenAI conversion fixes.
Current upstream AI/LLM/MCP gateway improvements and related docs.
Recent CI, docs, and refactoring updates from upstream maintenance.
Anything that depends on the newer upstream codebase shape is likely harder to adopt because this fork is ~200 commits behind and has large structural drift.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.

Strengths

Useful if you need deep control over gateway internals.
Likely better for debugging and local experimentation than vanilla upstream.
May preserve behavior that upstream later removed or simplified.

Risks

Large divergence from upstream means rebasing or upgrading will be expensive.
Stale activity increases the chance of unpatched bugs and security gaps.
Missing recent upstream AI and gateway fixes can matter in production.
Custom patches may make troubleshooting and support harder.