Product family
Kong, product by product
Kong's full product surface, line by line — the gateway platform, the AI gateway, and Insomnia are judged in arenas of their own; the mesh, event, and Konnect service lines have no arena where they honestly compete yet.
3 of 12 lines judged in an arena · flagship: Kong in API platforms
Kong Gateway & Konnect
JudgedAPI gateway (open-source core plus Enterprise) and the Konnect SaaS control plane that runs it: routing, auth, rate limiting, declarative config, analytics.
AI Gateway
JudgedLLM gateway proxying 15+ model providers behind one OpenAI-compatible API: load balancing and fallbacks, token rate limits, semantic caching, prompt guards, and MCP/A2A traffic governance.
Insomniaacquired
JudgedOpen-source desktop API client for designing, debugging, and testing APIs: collections, environments, mock servers, Git sync, and the inso CLI for CI.
Kong Mesh
Not yet judgedEnterprise service mesh built on CNCF Kuma: mTLS, service discovery, and traffic management across Kubernetes and VMs.
No service-mesh arena — nothing honest to rank it against.
Event Gateway
Not yet judgedKafka-native proxy between clients and clusters: virtual clusters, policy enforcement, schema validation, and topic-level auth (Konnect-only).
developer.konghq.com/event-gateway/ ↗
No event-streaming arena.
Ingress Controller & Operator
Not yet judgedKubernetes packaging of the gateway: Ingress/Gateway API resources translated into Kong config; new features now land in Kong Operator.
developer.konghq.com/kubernetes-ingress-controller/ ↗
A deployment form of Kong Gateway, judged inside Kong's api-platforms entry — not a separate competitor.
Dev Portal
Not yet judgedCustomizable API developer portal: publish OpenAPI/AsyncAPI plus Markdown docs with self-service credentials (Konnect-only).
developer.konghq.com/dev-portal/ ↗
A Konnect platform service; the generate-publish-api-docs story is judged inside Kong's api-platforms entry.
Service Catalog & MCP Registry
Not yet judgedInventory and governance of APIs, AI models, agents (beta), and MCP servers (tech preview) across the organization (Konnect-only).
developer.konghq.com/catalog/ ↗
A Konnect platform service; the internal-api-catalog story is judged inside Kong's api-platforms entry. MCP Registry is tech preview.
Kong Identity
Not yet judgedOAuth 2.0 authorization server centralizing token issuance for APIs fronted by Kong runtimes (Konnect-only).
developer.konghq.com/identity/ ↗
Auth for Kong-managed API traffic, not standalone developer login infrastructure — the auth-platforms arena (Auth0, Clerk, WorkOS) does a different job.
decK & kongctl
Not yet judgedDeclarative-config CLI for the gateway (decK) and the Konnect platform CLI (kongctl) for APIs, portals, AI Gateway, and catalog resources.
Tooling for the platform, judged inside Kong's api-platforms entry (official-CLI, headless, and declarative-config stories).
Metering & Billingacquired
Not yet judgedUsage-based metering and monetization of APIs, LLM tokens, and event streams inside Konnect, built from OpenMeter.
developer.konghq.com/metering-and-billing/ ↗
No API-monetization/usage-billing arena.
Volcano SDK
Not yet judgedOpen-source TypeScript agent SDK: MCP-native, multi-provider (OpenAI, Anthropic, Bedrock, Vertex...), with parallel/branch/loop flows and OpenTelemetry.
github.com/kong/volcano-agent-sdk ↗
Launched late 2025 — a young entrant next to the agent-frameworks arena's incumbents; watchlist bring-up candidate, not judged in this mapping.
A judged line competes in its arena on the same stories as every rival — family membership never affects scoring. Lines without a fitting arena stay unscored until one exists. See the methodology.