Cloudflare AI Gateway

Name: Cloudflare AI Gateway
Brand: Cloudflare

Leader

At Cloudflare, we have our eyes set on an ambitious goal — to help build a better Internet.

Est 2009|Valuation $109.4B|Raised $3B

LinkedIn 1.2M|Website|Web traffic 91.2M|FTEs 5,483|HQ San Francisco, CA

MarketsWeb Application & API Protection (WAAP)LLM Observability

01Competitive Landscape

Narrative analysis

Direct competitors and differentiators: - Cloudflare’s differentiated attributes include the company’s edge network and integration with its developer platform. The vendor has described simplified adoption models that may require simple configuration changes, but performance and operational characteristics should be validated through testing. - Kong emphasizes enterprise-grade API management and an ecosystem of plugins that include AI-specific capabilities such as sanitization and semantic caching. - Portkey emphasizes a production AI control plane with features around key management and prompt management. Feature comparison: where Cloudflare tends to provide value - Operational simplicity for organizations already operating on the Cloudflare platform - Edge-based caching and rate limiting with centralized analytics and log export Where Cloudflare tends to lag (based on competitor materials and community feedback) - On-premise or self-host deployment options - Explicitly marketed active PII sanitization and semantic cache features Pricing comparison (high level) - Cloudflare’s inclusion of core gateway features without a separate product fee on published plans can reduce initial adoption friction, but operational plan requirements and log retention needs can drive additional costs - Kong can incur higher costs depending on control plane usage and AI plugin licensing - Portkey lists straightforward SaaS tiers but adds another vendor to operational and security considerations Customer testimonials comparing products - Community posts note portability trade-offs: Cloudflare’s solution is closely tied to its platform capabilities, which affects cross-cloud portability compared to vendor-neutral gateways Market adoption trends - AI gateway adoption is growing; Cloudflare’s vendor-reported usage milestones suggest activity, but independent market share comparisons were not identified in the reviewed sources

	Cloudflare AI Gateway	Kong AI Gateway	Portkey
Starting Price	Core features available without a separate product charge on published plans; persistent log allocations and Logpush usage fees apply	Enterprise pricing; AI-related plugins are licensed as add-ons; costs vary by deployment and traffic	Published free tier and paid tiers; vendor lists published starting pricing for paid tiers
Typical fit	Organizations already using Cloudflare Workers/edge services that want a lightweight gateway with observability, caching, and rate-limiting	Enterprises needing mature API management, RBAC/SSO, and purchasable AI plugins (sanitization, semantic cache)	Teams seeking a purpose-built LLM gateway with prompt management and key management features
Key strengths	Integration with Cloudflare’s global network; edge-based caching and rate limiting; built-in analytics and log export facilities	Mature API platform features and plugin ecosystem focused on enterprise governance	Purpose-built LLM control plane with explicit features for prompt management and key concepts
Key weaknesses	No self-host option; active PII redaction not clearly documented as native; cost metrics are vendor-estimated; public review footprint remains limited	Enterprise complexity and potential cost for large-scale AI workloads; may be heavy if only basic observability is required	Introduces an additional vendor dependency; may not match Cloudflare’s global edge footprint

01Competitive Landscape

Narrative analysis

Direct competitors and differentiators:

Cloudflare’s differentiated attributes include the company’s edge network and integration with its developer platform. The vendor has described simplified adoption models that may require simple configuration changes, but performance and operational characteristics should be validated through testing.
Kong emphasizes enterprise-grade API management and an ecosystem of plugins that include AI-specific capabilities such as sanitization and semantic caching.
Portkey emphasizes a production AI control plane with features around key management and prompt management.

Feature comparison: where Cloudflare tends to provide value

Operational simplicity for organizations already operating on the Cloudflare platform
Edge-based caching and rate limiting with centralized analytics and log export

Where Cloudflare tends to lag (based on competitor materials and community feedback)

On-premise or self-host deployment options
Explicitly marketed active PII sanitization and semantic cache features

Pricing comparison (high level)

Cloudflare’s inclusion of core gateway features without a separate product fee on published plans can reduce initial adoption friction, but operational plan requirements and log retention needs can drive additional costs
Kong can incur higher costs depending on control plane usage and AI plugin licensing
Portkey lists straightforward SaaS tiers but adds another vendor to operational and security considerations

Customer testimonials comparing products

Community posts note portability trade-offs: Cloudflare’s solution is closely tied to its platform capabilities, which affects cross-cloud portability compared to vendor-neutral gateways

Market adoption trends

AI gateway adoption is growing; Cloudflare’s vendor-reported usage milestones suggest activity, but independent market share comparisons were not identified in the reviewed sources

	Cloudflare AI Gateway	Kong AI Gateway	Portkey
Starting Price	Core features available without a separate product charge on published plans; persistent log allocations and Logpush usage fees apply	Enterprise pricing; AI-related plugins are licensed as add-ons; costs vary by deployment and traffic	Published free tier and paid tiers; vendor lists published starting pricing for paid tiers
Typical fit	Organizations already using Cloudflare Workers/edge services that want a lightweight gateway with observability, caching, and rate-limiting	Enterprises needing mature API management, RBAC/SSO, and purchasable AI plugins (sanitization, semantic cache)	Teams seeking a purpose-built LLM gateway with prompt management and key management features
Key strengths	Integration with Cloudflare’s global network; edge-based caching and rate limiting; built-in analytics and log export facilities	Mature API platform features and plugin ecosystem focused on enterprise governance	Purpose-built LLM control plane with explicit features for prompt management and key concepts
Key weaknesses	No self-host option; active PII redaction not clearly documented as native; cost metrics are vendor-estimated; public review footprint remains limited	Enterprise complexity and potential cost for large-scale AI workloads; may be heavy if only basic observability is required	Introduces an additional vendor dependency; may not match Cloudflare’s global edge footprint