What it does
Kong Gateway is a reverse proxy for routing and managing requests to APIs. Teams can configure it through an API, a web interface, or declarative configuration, then extend traffic handling with plugins for authentication, security, transformations, and analytics. The gateway can run in traditional, hybrid, or database-less mode and is designed for distributed, hybrid, and multicloud architectures. Kong offers an open-source edition as well as enterprise and Kong Konnect options, which have different management and support models.
Place a gateway between clients and API services
Kong Gateway is the traffic layer in front of one or more APIs. A basic deployment defines upstream services and routes, then adds the plugins needed for authentication, request transformation, or other policies. The official documentation explains the gateway as a reverse proxy and points to installation and deployment-mode guides. Teams can manage configuration through an API, a UI, or declarative files, making the product suitable for infrastructure-as-code and CI/CD workflows as well as manual setup.
The deployment model affects operations. Kong documents traditional, hybrid, and database-less modes, and the product page describes use across cloud, Kubernetes, serverless, and on-premises environments. A Kubernetes team can pair the gateway with Kong Ingress Controller; a team using declarative configuration can version changes and promote them through environments. Plugins provide extension points, but selecting, configuring, and operating the gateway remain the team's job when it is self-managed.
Kong Gateway's repository is licensed under Apache 2.0, while the vendor also offers enterprise capabilities and a managed control plane through Kong Konnect. Those are related but separate commercial offerings: Konnect can manage gateway data planes, but it is not another name for the open-source gateway. Choose the edition and control-plane arrangement deliberately, particularly if support, access controls, or centralized operations are requirements. No gateway was installed or configured for this entry.
Strengths
- Supports API-based and declarative configuration that can be integrated with CI/CD workflows.
- A plugin model adds traffic policies such as authentication, security, transformations, and analytics.
- The gateway supports traditional, hybrid, database-less, Kubernetes, cloud, and on-premises deployment patterns.
Watch out for
- A self-managed deployment still requires the team to install, configure, update, and operate gateway infrastructure.
- Open-source Gateway, Kong Enterprise, and the managed Kong Konnect control plane are separate offerings with different capabilities and operating models.
Best for
- Platform teams routing multiple APIs through a configurable reverse proxy.
- Kubernetes and microservice environments that need gateway policies and declarative configuration.
- Organizations evaluating a self-managed Apache-licensed gateway before choosing enterprise or managed controls.
Sources
- Kong Gateway: API Connectivity Foundation for AI | Kong Inc. (Oct 25, 2026)
- Kong Gateway | Kong Docs (Oct 25, 2026)
- kong/LICENSE at master · Kong/kong · GitHub (Oct 25, 2026)