Kong

kong: Route and Govern API, LLM, and MCP Traffic

Kong Gateway is a cloud-native, platform-agnostic API, LLM, and MCP gateway built in Lua. It centralizes traffic routing, security, and extensibility for teams running services on their own infrastructure or Kubernetes.

ActiveLuaApache-2.0APIProxyCloud Native
Stars
44.3k
Forks
5.2k
Stars, last 30 days
+112
Last commit
today
Contributors
100+

Our take

Activeregular commits and releases

Health score

58/100

How it is scored
Activity
51
Community
92
Issues
39
Pull requests
50

+112 stars in the last 30 days

  • More contributors than 78% of the projects we track
  • Slower to close issues than 82% of the projects we track

Kong is an actively maintained, extensible gateway for teams that need to manage API and AI traffic through a common layer, with a broad contributor base and recent releases.

Good fit if

  • You need routing, authentication, traffic controls, or observability across APIs or microservices.
  • You want a gateway that supports LLM and MCP traffic as well as conventional APIs.
  • Your deployment needs include Kubernetes, containers, bare metal, or declarative and hybrid configurations.

Look elsewhere if

  • You need a gateway with no operational setup: the documented self-hosted path uses Docker Compose and PostgreSQL, while DB-less operation is a separate option.
  • Your requirements are limited to a single service and do not justify a shared gateway and plugin layer.
  • You cannot meet the obligations of the Apache-2.0 license.
All health signals
Last commit2026-10-19 (today)
Commits, last 90 days15
Releases, last 12 months3 (latest 3.9.4, 2026-10-12)
Contributors100+ (top contributor: 20% of commits)
Issues closed, last 90 days4 (typically closed in 59 days)
Pull requests merged, last 90 days26 (typically merged in 1 day)
Project age11 years

Checked on 2026-10-20 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

44,389

Forks

5,241

Change since Nov 16, 2026: +7 stars·-2 forks

Overview

Kong Gateway is a cloud-native, platform-agnostic API, LLM, and MCP gateway built in Lua. It gives teams a central layer to route and govern traffic between clients, APIs, microservices, and AI systems, with plugin-based extensions for common gateway functions.

It is designed for deployment across cloud, bare-metal, and container environments, and has an official Kubernetes Ingress Controller. Teams can configure it through its Admin API or declarative configuration, and use it in database-backed or DB-less modes.

Key Features

  • Routes traffic and provides load balancing, health checks, proxying, and TLS termination.
  • Adds API authentication and authorization, including JWT, basic authentication, OAuth, and ACLs.
  • Routes LLM requests across providers, including OpenAI, Anthropic, Google Gemini, AWS Bedrock, and Azure AI.
  • Provides MCP traffic governance, security, analytics, and generation of MCP interfaces from REST APIs.
  • Extends gateway behavior with plugins for rate limiting, transformations, logging, monitoring, and other controls.
  • Supports DB-less declarative and hybrid control-plane/data-plane deployments.
  • Integrates with Kubernetes through the official Ingress Controller.

Use Cases

  • Platform teams can provide a shared gateway for routing and securing microservices and APIs.
  • API owners can apply authentication, rate limits, and request or response transformations consistently across services.
  • Teams integrating multiple LLM providers can route AI traffic through a common gateway layer.
  • Organizations exposing tools to MCP clients can manage MCP traffic security and observability centrally.
  • Kubernetes operators can manage ingress traffic with Kong's Ingress Controller.

What you need

Detected in the repository

  • Lua (main language on GitHub)
  • A test suite and automated checks on GitHub Actions

License in plain words

Apache-2.0permissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license, the NOTICE file and a note of your changes
  • Share your changes: no
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

The README's Docker Compose walkthrough starts from the docker-kong repository:

git clone https://github.com/Kong/docker-kong
cd docker-kong/compose
KONG_DATABASE=postgres docker-compose --profile database up

See the README and official installation guide for supported distributions and DB-less setup details.

Alternatives

  • APIPark: APIPark focuses on AI model access and API publishing with a developer portal, while Kong is a broader traffic gateway for APIs, LLMs, and MCP.
  • inference-gateway: Inference Gateway specializes in proxying requests across cloud and local LLM providers, while Kong handles general API traffic as well as LLM and MCP traffic.
ProjectLanguageLicenseStarsStatus
kongLuaApache-2.044.3kActive
APIParkTypeScriptApache-2.01.8kMaintained
inference-gatewayGoApache-2.0215Active

Considerations

Kong is an established project, with regular commits and releases and a large contributor base. Recent issue closure is comparatively limited, while pull requests are merged quickly on median, so teams should assess open issues relevant to their deployment rather than assume every report is addressed promptly. The README describes several deployment modes, but they still require operating and configuring a gateway; its Compose example uses PostgreSQL. The repository is licensed under Apache-2.0, so review that license's terms when incorporating or distributing it.

Found this useful?

Share it with someone who would like kong.

Comparisons