Understand the project
Practical overview
When it fits
Use Kong when API infrastructure needs to cover conventional services alongside AI or LLM traffic, particularly in Linux, Docker, cloud, self-hosted or Kubernetes-oriented environments.
Who it is for
- Teams managing APIs across cloud-native applications
- Engineers handling AI or LLM service traffic
- Organizations building self-hosted gateway infrastructure
- Kubernetes users needing API ingress and management infrastructure
Documented uses
- Route and manage conventional API traffic
- Create a gateway layer for AI and LLM-facing APIs
- Provide API ingress in Kubernetes environments
- Centralize API management for cloud-native services
Before you choose
Requirements & limits
The project is publicly accessible and open source under the Apache-2.0 license. It is identified as active; no account or pricing requirements are documented here.
- Whether the gateway must handle both conventional APIs and AI or LLM traffic
- Whether a self-hosted or cloud-native infrastructure approach is appropriate
- Whether Kubernetes or Kubernetes-ingress support is relevant
- Whether Lua and the Apache-2.0 license fit the technical and licensing requirements
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 30 September 2026
- Original website title
- Kong/kong · Official homepage title · retained in its source language