| Aspect | Portkey MCP Gateway | Kong AI Gateway | Docker MCP Gateway |
|--------|----------------------|------------------|--------------------|
| Starting Price | Not clearly published in the public sources reviewed | Commercial/enterprise pricing; public list pricing not clearly visible in the sources reviewed | Open tooling available; infrastructure and operations costs apply (container image available in public registries) |
| Suitable For | Teams seeking a unified governance layer for MCP tools and integrated observability across model and tool usage | Enterprises standardized on Kong for API traffic that want to extend governance to AI traffic | Teams adopting a Docker-centric workflow that want MCP gateway tooling with runnable examples |
| Key Strength | Central MCP registry, RBAC, audit/observability, and runtime policy enforcement designed to work with existing agents and tools | API gateway maturity and governance/metering framework with enterprise ecosystem | Direct Docker integration and examples; lower barrier for Docker-first teams |
| Key Weakness | Community-reported latency and dashboard performance concerns at scale; pricing sensitivity tied to observability; certain enterprise features may be restricted to higher-tier plans | Can be complex to adopt if Kong is not already in use; some features may be enterprise-tier | May not include the same breadth of enterprise governance features (SSO/SCIM/policies/analytics) out of the box |
- Direct competitors and key differentiators
- LiteLLM: Often selected for open-source provider routing breadth; requires more operational effort but offers higher control.
- Cloudflare AI Gateway: Positioned for lightweight analytics and caching; less emphasis on fine-grained team-level governance in vendor positioning.
- TrueFoundry: Positioned as a broader platform for model and tool governance; may be perceived as heavier if only simple routing is required.
- Kong AI Gateway: Differentiates with API-gateway heritage and mature governance/metering concepts.
- Docker MCP Gateway: Differentiates through Docker-native workflows and concrete examples for Docker-centric environments.
- Feature comparison summary
- Where the product is comparatively strong:
- Governance and registry for MCP servers/tools combined with observability and RBAC.
- Integration focus for identity providers and standard auth patterns.
- Where the product faces risks or lags:
- Community reports identify performance and dashboard responsiveness under heavy load as areas of concern.
- Documentation depth for advanced routing scenarios appears limited in community feedback.
- Pricing transparency is limited in public listings, increasing procurement uncertainty.
- Pricing comparison and value proposition
- Public pricing information for Portkey MCP Gateway is limited; open-source alternatives transfer cost to operations and engineering time, while enterprise platforms typically rely on subscription/licensing models.
- Market share and adoption trends
- Public review-platform counts vary by source. Vendor statements about broad adoption exist but were not independently validated in the sources reviewed.
- Reasons customers choose competitors
- Preference for open-source control and self-hosting (LiteLLM and other OSS proxies).
- Existing standardization on Kong for API governance.
- Simpler, lightweight analytics/caching needs (Cloudflare AI Gateway).