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

01Competitive Landscape

Narrative analysis (where alternatives excel)

- Apigee vs Kong: Apigee is commonly selected for organizations prioritizing end-to-end API program management (monetization, analytics, governance workflows) and those standardized on Google Cloud. Kong is frequently selected for teams focused on runtime performance and extensibility in cloud-native environments. - AWS API Gateway vs Kong: AWS API Gateway is often operationally simpler for AWS-centric teams and fits many low-to-moderate complexity use cases. Kong is frequently used when teams need richer gateway policies, custom plugins, or hybrid/multi-cloud capabilities. - Gravitee vs Kong: Gravitee promotes simpler flat pricing for some packages and emphasizes async/event API support, which may appeal to buyers seeking pricing simplicity and event-native posture. - Apache APISIX / Envoy Gateway vs Kong: These are common open-source alternatives when teams want to avoid paid-plugin gating or prefer alignment with the Kubernetes Gateway API and CNCF governance.

Market adoption signals

Kong’s GitHub repository is active, reflecting developer awareness. Kong’s marketing materials claim broad adoption; these vendor claims were not independently verified in the materials reviewed.

	Kong (Konnect/Kong Gateway)	Google Apigee	AWS API Gateway
Starting Price	Konnect Plus examples include per-control-plane, bandwidth, and request-based charges; Enterprise pricing requires vendor engagement	Subscription tiers with add-ons and metered analytics	Pay-as-you-go per API call and data transfer; limited free tier options for certain APIs
Best For	Kubernetes/microservices teams needing extensibility and hybrid/multi-cloud patterns	Enterprises prioritizing broader API management features and GCP integration	Teams building primarily on AWS that prefer a managed gateway for common REST/HTTP use cases
Key Strength	Plugin-based extensibility and deployment flexibility; active open-source ecosystem	Mature enterprise API management features and integrated analytics	Tight AWS integration, simple consumption model, managed setup
Key Weakness	Complexity and documentation gaps; paid plugins/feature gating; multi-dimensional pricing	Can be complex and costly for some use cases; may be heavyweight for simple gateway needs	Less flexible for advanced policy patterns without additional custom compute; potential vendor lock-in

01Competitive Landscape

Narrative analysis (where alternatives excel)

Apigee vs Kong: Apigee is commonly selected for organizations prioritizing end-to-end API program management (monetization, analytics, governance workflows) and those standardized on Google Cloud. Kong is frequently selected for teams focused on runtime performance and extensibility in cloud-native environments.
AWS API Gateway vs Kong: AWS API Gateway is often operationally simpler for AWS-centric teams and fits many low-to-moderate complexity use cases. Kong is frequently used when teams need richer gateway policies, custom plugins, or hybrid/multi-cloud capabilities.
Gravitee vs Kong: Gravitee promotes simpler flat pricing for some packages and emphasizes async/event API support, which may appeal to buyers seeking pricing simplicity and event-native posture.
Apache APISIX / Envoy Gateway vs Kong: These are common open-source alternatives when teams want to avoid paid-plugin gating or prefer alignment with the Kubernetes Gateway API and CNCF governance.

Market adoption signals

Kong’s GitHub repository is active, reflecting developer awareness. Kong’s marketing materials claim broad adoption; these vendor claims were not independently verified in the materials reviewed.

	Kong (Konnect/Kong Gateway)	Google Apigee	AWS API Gateway
Starting Price	Konnect Plus examples include per-control-plane, bandwidth, and request-based charges; Enterprise pricing requires vendor engagement	Subscription tiers with add-ons and metered analytics	Pay-as-you-go per API call and data transfer; limited free tier options for certain APIs
Best For	Kubernetes/microservices teams needing extensibility and hybrid/multi-cloud patterns	Enterprises prioritizing broader API management features and GCP integration	Teams building primarily on AWS that prefer a managed gateway for common REST/HTTP use cases
Key Strength	Plugin-based extensibility and deployment flexibility; active open-source ecosystem	Mature enterprise API management features and integrated analytics	Tight AWS integration, simple consumption model, managed setup
Key Weakness	Complexity and documentation gaps; paid plugins/feature gating; multi-dimensional pricing	Can be complex and costly for some use cases; may be heavyweight for simple gateway needs	Less flexible for advanced policy patterns without additional custom compute; potential vendor lock-in