Kong Gateway Self-Managed

Open-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.

10 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Kong Gateway Enterprise 3.16.0.2 security patch

Enterprise 3.16.0.2 fixes cache leakage across authentication contexts, request-callout cache keys, SAML audience validation, Admin API RBAC bypass, unsafe forwarded paths, and LLM usage-counter SQL injection.

Scope: Kong Gateway Enterprise plugins and features; the listing's separate community/core release snapshot is not replaced by this Enterprise build.

Applicability depends on the enabled Enterprise authentication, cache, SAML, RBAC, forwarded-path, and LLM plugins.

Action: Upgrade Enterprise deployments to 3.16.0.2 or later and retest exact SAML Audience and issuer matching.

Primary source · Reviewed 2026-11-18

Kong Gateway 3.9.5 nginx HTTP/2 fixes

Kong Gateway community/core 3.9.5 applies nginx patches for CVE-2026-123007 and CVE-2026-123633.

Scope: Kong Gateway community/core 3.9 line with affected nginx HTTP/2 code; Enterprise and other branches are separately versioned.

HTTP/2 exposure and the exact bundled nginx build determine applicability.

Action: Upgrade the applicable maintained core branch and separately follow Enterprise guidance for the installed edition.

Primary source · Kong Gateway 3.9.5 · nginx security advisories · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Official Linux packages, Docker images, Helm chart or Kubernetes Operator

  2. Operated by

    Your team

    Customer manages compute or Kubernetes, datastore topology, networking, TLS, plugins, secrets, configuration, monitoring, backups, scaling and upgrades. Enterprise users also manage subscription and license configuration.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial Linux packages, Docker images, Helm chart or Kubernetes Operator
InfrastructureServers / containers
Kong Gateway runs persistent proxy and administration processes on Linux, Docker or Kubernetes, with an optional customer-managed datastore and control-plane services.
Licensing modelOpen Source / Open Core
Kong Gateway's upstream core is Apache-2.0 licensed. Kong Gateway Enterprise adds separately licensed proprietary features and commercial support.
LicenseApache License 2.0 for the open-source core; Enterprise features use separate commercial licensing.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

9 of 12 fields researched (75%) · 8 documented · 1 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

Kong’s Gateway policy names AWS, Azure and Google Cloud marketplaces. The reviewed policy does not identify exact offers, publishers, delivery types or packaged versions. Confirm those records and the Gateway entitlement before treating a Konnect or third-party offer as the self-managed product.

Vendor Marketplace availability statement; exact self-managed offer records remain unverified · Source ↗ · Reviewed 2026-11-16

Sources checked — unresolved · Editor reviewed.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

Self-managed Kong Manager can authenticate administrators through OIDC using the Enterprise-only OpenID Connect plugin. The v3.6+ procedure uses kong.conf and differs from Konnect SSO and from authenticating API consumers.

Kong Gateway Enterprise Manager, v3.6+; not the Apache-licensed core alone · Source ↗ · Enterprise-only OIDC plugin ↗ · Reviewed 2026-11-16

Edition-dependent · Editor reviewed.

Compliance attestations
DocumentedEvidence and scope for Compliance attestations

Kong explicitly says the Gateway FIPS package has not itself been submitted to a NIST testing lab for product validation. Its use of a validated cryptographic provider must not be presented as a certificate for the entire customer deployment.

Vendor-stated product-versus-module validation boundary; not an assessment of other certifications · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Security controls
Edition-dependentEvidence and scope for Security controls

Enterprise v3.14+ offers an AMD64 FIPS 140-3 package using approved algorithms and an OpenSSL FIPS provider. Kong explicitly distinguishes its compliant package from a product submitted for NIST validation; configure the supported distribution and FIPS mode. Current advisory review: Enterprise 3.16.0.2 fixes cache leakage across authentication contexts, request-callout cache keys, SAML audience validation, Admin API RBAC bypass, unsafe forwarded paths, and LLM usage-counter SQL injection. Upgrade Enterprise deployments to 3.16.0.2 or later and retest exact SAML Audience and issuer matching. Current review: Community/core 3.9.5 applies nginx fixes for CVE-2026-123007 and CVE-2026-123633, HTTP/2 memory-corruption and use-after-free vulnerabilities. Upgrade the applicable maintained branch; do not substitute the 3.9 core tag for separately versioned Enterprise guidance.

Kong Gateway community/core 3.9 line with affected nginx HTTP/2 code · Source ↗ · Prior security-controls source ↗ · Prior security-controls source ↗ · 3.9.5 release ↗ · nginx advisories ↗ · Reviewed 2026-11-19

Edition-dependent · Editor reviewed.

Air-gapped operation
DocumentedEvidence and scope for Air-gapped operation

Self-managed Enterprise license validation does not require network connectivity: each node reads a supplied license at startup. This resolves offline license validation, but does not certify every plugin, integration, image source or update workflow as disconnected.

Enterprise offline license validation only; not Konnect or blanket end-to-end air-gap certification · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The upstream Kong Helm chart deploys Gateway on Kubernetes. Select compatible chart, image and database settings; an Enterprise image/license does not follow automatically from installing the chart.

Kong Gateway chart; open-source and Enterprise image entitlements differ · Source ↗ · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-16

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

Kong publishes workload-based sizing rather than a fixed universal minimum. Its small per-node starting example is 1–2 CPU cores and 2–4 GB RAM; database/Redis, enabled plugins, configuration size and traffic must be sized separately.

Self-managed Gateway sizing guidelines, v3.4+; example resources are not throughput guarantees · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Kong Gateway's upstream core is Apache-2.0 licensed. Kong Gateway Enterprise adds separately licensed proprietary features and commercial support.

Kong Gateway Self-Managed: software license terms; infrastructure and operating costs are separate · Source ↗ · Edition and license conditions ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Kong Gateway community/core 3.9.5 was published November 19, 2026. It applies nginx patches for CVE-2026-123007 and CVE-2026-123633. Enterprise releases, plugins and cloud packages remain separately versioned.

Upstream Kong Gateway community/core 3.9 line; Enterprise and deployment packages may differ · Source ↗ · Prior reviewed release context ↗ · 3.9.5 changelog ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (3 not researched)
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry covers self-managed Kong Gateway, not Kong Konnect or Kong-managed cloud gateways. The open-source core and Enterprise distribution have different features and support entitlements. Validate the selected topology, package version, datastore mode and cloud-platform compatibility before deployment. Kong Gateway Enterprise 3.16.0.2 fixes authentication-context cache leakage, request-callout cache keys, SAML audience validation, Admin API RBAC self-protection, unsafe forwarded paths, and LLM usage-counter SQL injection. This Enterprise plugin guidance is separate from the listing's community/core 3.9.4 snapshot; exact SAML Audience and issuer matching may require configuration changes. Kong Gateway community/core 3.9.5 applies nginx patches for CVE-2026-123007 and CVE-2026-123633, HTTP/2 memory-corruption and use-after-free vulnerabilities. Upgrade the applicable maintained core line and separately follow Enterprise guidance for the installed edition.

Community & maintenance

Kong maintains public upstream releases and contributor history for the Apache-licensed Kong Gateway core. This evidence establishes continuing project activity, not Enterprise support or support for every listed cloud topology.

Category fit

Backend platforms
Provides a self-managed API gateway for routing, authentication, traffic control, transformation, observability and extensible API policies.

Compare within Backend platforms

  • Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
    • Northflank
    Customer-operated · Open Source / Open Core
  • Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Heroku
    Customer-operated · Open Source / Open Core
  • Red Hat OpenShift Container PlatformCommercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
    • AWS
    • Azure
    • Google Cloud
    • Alibaba Cloud
    • IBM Cloud
    Customer-operated · Commercial Only

Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Kong Gateway supported public-cloud deployment platforms ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

      Kong lists supported self-managed deployment platforms including Amazon EKS, ECS and Fargate; Azure AKS, Container Instances and Container Apps; and Google GKE, GKE Autopilot and Cloud Run. Edition-specific support entitlements should be confirmed separately.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory