Kong

Name: Kong
Brand: Kong

Leader

The Unified API and AI Platform. Unleash Intelligence.

Est 2009|Valuation $2.1B|Raised $363.6M|24 Ref Customers

LinkedIn 79K|Web traffic 170K|FTEs 896|HQ San Francisco, CA

MarketsWeb Application & API Protection (WAAP)API Management

Platform CoversFirewalls

Published Oct 15, 2026

01Common complaints

1) Need for certain advanced authentication features but limited ability to purchase enterprise plugins - Community discussions indicate some auth-related plugins may be paid, which can be a constraint for budgets limited to OSS-only deployments. 2) Preference for the simplest managed gateway within an AWS-only stack - AWS API Gateway may be operationally simpler and sufficient for common REST/HTTP needs in AWS-centric environments. 3) Very small teams without capacity to absorb operational complexity - Configuring, debugging, and managing hybrid setups can require engineering expertise and operational investment. 4) Requirement for strict alignment with Kubernetes Gateway API and CNCF-first governance - Envoy Gateway or other CNCF-aligned projects may better serve teams prioritizing upstream governance and neutrality. 5) Need for highly predictable, flat billing - Konnect pricing can involve multiple variables (control planes, bandwidth, API requests, add-ons); some alternatives present flatter pricing models. Procurement red flags to monitor: - Ambiguity about OSS vs enterprise artifact behavior and upgrade effects - Unclear total cost under high traffic, multiple regions, and add-ons

Deal disqualifiers (poor fit)

Organizations seeking a business-user-friendly API management suite that requires minimal engineering involvement
Organizations requiring a single, simple flat price with minimal billing dimensions
Organizations that cannot justify enterprise spend for specific advanced features that are gated behind paid tiers

Commonly reported limitations

Documentation clarity and availability of advanced configuration examples.
Troubleshooting and visibility into plugin errors and gateway internals.
Complexity in hybrid/multi-cluster setups.

Ecosystem / licensing friction signals

Community conversations highlight concerns about licensing and packaging changes and potential confusion between OSS and enterprise behavior. Even if a specific deployment is unaffected, these signals increase perceived vendor risk and warrant due diligence.

Compliance/controls limitations to confirm

Audit log retention: Konnect documentation lists a 7-day retention for some logs; enterprises may require longer retention and different SIEM export capabilities.
Verify SSO/SAML/SCIM availability and other administrative controls by plan, since advanced features may be gated in higher tiers.

02Why they buy

Unique selling points supported by customer feedback

Runtime performance and scalability are frequently cited in customer reviews.
Plugin architecture (breadth and support for custom plugin development) is commonly identified as a differentiator.

Unique selling points that should be validated through proof-of-concept

Vendor-published performance figures (for example, high throughput per node) should be validated against customer workloads and policy sets.

Areas where competitors have clear advantages

Apigee: broader out-of-the-box enterprise API management program features
AWS API Gateway: operational simplicity within AWS environments
Gravitee: simpler priced packages and event/async API support
APISIX: some capabilities available without commercial gating depending on the feature set

03Field reports

Review platforms (G2, Capterra, Trustpilot)

G2 (Kong Gateway) - Positive themes commonly cited by reviewers: - Performance and scalability are frequently mentioned. - Plugin architecture flexibility. - Kubernetes and cloud-native alignment. - Negative themes commonly cited: - Documentation gaps (fragmented, lacking end-to-end examples). - Troubleshooting/debugging friction (plugin errors, tracing). - Some features/plugins require enterprise licensing. Representative reviewer language: some reviewers reported strong performance and scalability under heavy traffic; others requested more detailed, example-rich documentation for advanced configurations. Capterra (Kong Enterprise / Konnect listings) - Positive themes: - Functional and stable in Kubernetes traffic management scenarios in several reviews. - Perceived value in several reviews. - Critical themes: - Product appears developer-focused rather than business-user-friendly in some reviews. Representative reviewer language: one reviewer characterized the product as more developer-oriented than business-user-oriented. Trustpilot (konghq.com) - Limited review volume at the time of capture; should not be overweighted. Some reviewers provided strong positive feedback for Insomnia and Kong Gateway.

Community discussions (Reddit)

Community and forum threads contain operational discussions and concerns about packaging/licensing changes in recent discussions. Some threads reported that certain deployment options or behaviors changed in recent Kong Gateway releases, leading to confusion over free vs enterprise modes. Other participants disputed interpretations and distinguished OSS vs enterprise artifacts. This indicates messaging ambiguity and buyer confusion in some community channels.

Why customers choose Kong over alternatives (as implied by reviews)

Reputation for runtime performance and the plugin ecosystem
Kubernetes/microservices fit
Support for hybrid/multi-cloud deployment patterns

Why some customers leave / consider leaving

Common churn drivers identified from reviews and community posts:

Licensing boundaries and paid plugins prompting evaluation of alternatives
Complexity for advanced deployments and the associated learning curve
Documentation and troubleshooting limitations

Vendor-published case study claims (examples)

On Kong’s product pages, vendor-published case studies include quantified outcomes such as reported cost reductions and resource-efficiency improvements for specific customers: - Example claims: a reported reduction in costs for a regional property exchange; reported reductions in gateway overhead and reported resource-efficiency improvements for a large healthcare organization; and a report of managing a large API portfolio for a global manufacturer. Critical evaluation: - These metrics are vendor-published and generally lack full methodology details (baseline, measurement period, confounders). They can be directionally informative for buyer storytelling but should not be treated as independently validated ROI. - Recommended follow-up: request architecture diagrams, before/after infrastructure cost details, traffic levels, and parity of policy/plugin sets.

Independent performance comparison claims

Kong publishes competitor comparison pages with benchmark-like claims (throughput/latency) and references to third-party testing or analysis in some cases. Buyers should request the original third-party reports and verify test configurations, scenario parity, and relevance to their expected workload.

04Best fit

Company size

Common fit: mid-market to enterprise with platform engineering resources. Smaller organizations can use Kong OSS, but the learning curve and operational ownership can be significant.

Industries

Financial services, healthcare, logistics, e-commerce, and other organizations with:
- High API traffic
- Strong security requirements
- Hybrid/multi-cloud constraints

Roles/personas

Decision makers: VP of Engineering, Head of Platform, CISO/security architect, enterprise architects
Power users: SREs, platform engineers, Kubernetes operators, API platform engineers

Pain points Kong addresses

Standardizing API security and policy enforcement across many services
Reducing bespoke gateway logic per service through central policies
Managing traffic across heterogeneous environments

Qualification criteria (good fit)

Organizations that require plugin extensibility and have staff to operate it (or plan to use Konnect)
Organizations with a defined API platform roadmap (portals, analytics, governance)
Teams that expect hybrid or multi-cloud deployment needs

05The pitch

What the product does (objective value proposition)

Kong is an API connectivity platform centered on Kong Gateway (an API gateway / reverse proxy) and Kong Konnect (a SaaS control plane for managing gateways and related API lifecycle capabilities). It is used to: - Route, secure, and govern API traffic (authentication/authorization, rate limiting, transformations, observability hooks) - Support hybrid / multi-cloud deployments with centralized management - Extend behavior via a plugin architecture (built-in, commercial, and community/custom plugins) - In many deployments, act as a Kubernetes-native ingress / gateway layer via Kong’s Kubernetes integrations Kong describes itself as cloud-native, performance-oriented, and extensible (plugin-centric), with an open-core heritage and enterprise add-ons.

Target market and positioning

Primary buyers: platform engineering, SRE, security engineering, API platform teams, and enterprise architecture.
Best-fit environments: microservices, Kubernetes, hybrid/multi-cloud, and organizations standardizing an internal API platform.
Positioning theme: run-anywhere deployment flexibility, performance orientation, and extensibility.

Get a comprehensive analysis of Kong including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Need for certain advanced authentication features but limited ability to purchase enterprise plugins

Community discussions indicate some auth-related plugins may be paid, which can be a constraint for budgets limited to OSS-only deployments.

Preference for the simplest managed gateway within an AWS-only stack

AWS API Gateway may be operationally simpler and sufficient for common REST/HTTP needs in AWS-centric environments.

Very small teams without capacity to absorb operational complexity

Configuring, debugging, and managing hybrid setups can require engineering expertise and operational investment.

Requirement for strict alignment with Kubernetes Gateway API and CNCF-first governance

Envoy Gateway or other CNCF-aligned projects may better serve teams prioritizing upstream governance and neutrality.

Need for highly predictable, flat billing

Konnect pricing can involve multiple variables (control planes, bandwidth, API requests, add-ons); some alternatives present flatter pricing models.

Procurement red flags to monitor:

Ambiguity about OSS vs enterprise artifact behavior and upgrade effects
Unclear total cost under high traffic, multiple regions, and add-ons

Deal disqualifiers (poor fit)

Organizations seeking a business-user-friendly API management suite that requires minimal engineering involvement
Organizations requiring a single, simple flat price with minimal billing dimensions
Organizations that cannot justify enterprise spend for specific advanced features that are gated behind paid tiers

Commonly reported limitations

Documentation clarity and availability of advanced configuration examples.
Troubleshooting and visibility into plugin errors and gateway internals.
Complexity in hybrid/multi-cluster setups.

Ecosystem / licensing friction signals

Community conversations highlight concerns about licensing and packaging changes and potential confusion between OSS and enterprise behavior. Even if a specific deployment is unaffected, these signals increase perceived vendor risk and warrant due diligence.

Compliance/controls limitations to confirm

Audit log retention: Konnect documentation lists a 7-day retention for some logs; enterprises may require longer retention and different SIEM export capabilities.
Verify SSO/SAML/SCIM availability and other administrative controls by plan, since advanced features may be gated in higher tiers.

02Why they buy

Unique selling points supported by customer feedback

Runtime performance and scalability are frequently cited in customer reviews.
Plugin architecture (breadth and support for custom plugin development) is commonly identified as a differentiator.

Unique selling points that should be validated through proof-of-concept

Vendor-published performance figures (for example, high throughput per node) should be validated against customer workloads and policy sets.

Areas where competitors have clear advantages

Apigee: broader out-of-the-box enterprise API management program features
AWS API Gateway: operational simplicity within AWS environments
Gravitee: simpler priced packages and event/async API support
APISIX: some capabilities available without commercial gating depending on the feature set

03Field reports

Review platforms (G2, Capterra, Trustpilot)

G2 (Kong Gateway)

Positive themes commonly cited by reviewers:
- Performance and scalability are frequently mentioned.
- Plugin architecture flexibility.
- Kubernetes and cloud-native alignment.
Negative themes commonly cited:
- Documentation gaps (fragmented, lacking end-to-end examples).
- Troubleshooting/debugging friction (plugin errors, tracing).
- Some features/plugins require enterprise licensing.

Representative reviewer language: some reviewers reported strong performance and scalability under heavy traffic; others requested more detailed, example-rich documentation for advanced configurations.

Capterra (Kong Enterprise / Konnect listings)

Positive themes:
- Functional and stable in Kubernetes traffic management scenarios in several reviews.
- Perceived value in several reviews.
Critical themes:
- Product appears developer-focused rather than business-user-friendly in some reviews.

Representative reviewer language: one reviewer characterized the product as more developer-oriented than business-user-oriented.

Trustpilot (konghq.com)

Limited review volume at the time of capture; should not be overweighted. Some reviewers provided strong positive feedback for Insomnia and Kong Gateway.

Community discussions (Reddit)

Why customers choose Kong over alternatives (as implied by reviews)

Reputation for runtime performance and the plugin ecosystem
Kubernetes/microservices fit
Support for hybrid/multi-cloud deployment patterns

Why some customers leave / consider leaving

Common churn drivers identified from reviews and community posts:

Licensing boundaries and paid plugins prompting evaluation of alternatives
Complexity for advanced deployments and the associated learning curve
Documentation and troubleshooting limitations

Vendor-published case study claims (examples)

On Kong’s product pages, vendor-published case studies include quantified outcomes such as reported cost reductions and resource-efficiency improvements for specific customers:

Example claims: a reported reduction in costs for a regional property exchange; reported reductions in gateway overhead and reported resource-efficiency improvements for a large healthcare organization; and a report of managing a large API portfolio for a global manufacturer.

Critical evaluation:

These metrics are vendor-published and generally lack full methodology details (baseline, measurement period, confounders). They can be directionally informative for buyer storytelling but should not be treated as independently validated ROI.
Recommended follow-up: request architecture diagrams, before/after infrastructure cost details, traffic levels, and parity of policy/plugin sets.

Independent performance comparison claims

04Best fit

Company size

Common fit: mid-market to enterprise with platform engineering resources. Smaller organizations can use Kong OSS, but the learning curve and operational ownership can be significant.

Industries

Financial services, healthcare, logistics, e-commerce, and other organizations with:
- High API traffic
- Strong security requirements
- Hybrid/multi-cloud constraints

Roles/personas

Decision makers: VP of Engineering, Head of Platform, CISO/security architect, enterprise architects
Power users: SREs, platform engineers, Kubernetes operators, API platform engineers

Pain points Kong addresses

Standardizing API security and policy enforcement across many services
Reducing bespoke gateway logic per service through central policies
Managing traffic across heterogeneous environments

Qualification criteria (good fit)

Organizations that require plugin extensibility and have staff to operate it (or plan to use Konnect)
Organizations with a defined API platform roadmap (portals, analytics, governance)
Teams that expect hybrid or multi-cloud deployment needs

05The pitch

What the product does (objective value proposition)

Route, secure, and govern API traffic (authentication/authorization, rate limiting, transformations, observability hooks)
Support hybrid / multi-cloud deployments with centralized management
Extend behavior via a plugin architecture (built-in, commercial, and community/custom plugins)
In many deployments, act as a Kubernetes-native ingress / gateway layer via Kong’s Kubernetes integrations

Kong describes itself as cloud-native, performance-oriented, and extensible (plugin-centric), with an open-core heritage and enterprise add-ons.

Target market and positioning

Primary buyers: platform engineering, SRE, security engineering, API platform teams, and enterprise architecture.
Best-fit environments: microservices, Kubernetes, hybrid/multi-cloud, and organizations standardizing an internal API platform.
Positioning theme: run-anywhere deployment flexibility, performance orientation, and extensibility.

Get a comprehensive analysis of Kong including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →