The hidden add-on costs of Kong and Apigee (and what you get with Zerq instead)
TCO isn’t only gateway license fees: analytics, observability, and audit-grade signals are often separate SKUs or integrations. How to model them—and where Zerq bundles metrics and audit in-platform.
- comparisons
- enterprise
- procurement
Procurement spreadsheets love a single line item. Real API programs discover second and third line items when they need analytics that product teams actually use, audit evidence security can defend, and AI traffic measured alongside REST. This article stays out of specific dollar amounts—those change by region, commit, and negotiation—but it does map documented packaging from Kong and Google Cloud to the Total Cost of Ownership (TCO) story, and ties that to our Compare matrix where Metrics & audit included is add-ons for Kong and Apigee.
Capabilities and SKUs change—validate in your PoC and with your vendor rep.
TCO layers buyers forget to model
- Gateway / proxy license — the number people compare first.
- Observability and analytics plane — dashboards, exploration, and sometimes LLM usage reporting (increasingly relevant for AI gateways).
- Audit and retention — exporting and retaining evidence for the period your policy requires (often longer than default analytics retention).
- Integration engineering — connecting (2) and (3) to SIEM, ticketing, and partner workflows when they are not native product surfaces.
- Parallel AI stack — if REST and AI/MCP traffic need separate gateways or identity models, you double operational overhead.
Zerq’s pitch is to collapse 1–4 into a single platform deployment for teams that want self-hosted control and a unified path for REST and AI—see Architecture.
Kong: premium analytics as its own product surface
Kong documents Konnect Observability as real-time API and AI analytics, positioned as a premium service within Konnect—including features like custom dashboards and LLM reporting (Kong Docs: Konnect Observability). That language matters for TCO: premium analytics is a deliberate product, not an implicit bundle with every open-source Gateway deployment.
Whether you run Kong Gateway self-managed or through Konnect, your finance team should map which analytics and retention capabilities you are buying—and what you still route to external observability stacks. Our matrix marks Kong add-ons on Metrics & audit included to reflect that buyers often pay separately for a full analytics and audit story versus assuming it is included in the base gateway.
Apigee: API Analytics as a documented paid add-on (Pay-as-you-go)
For Apigee Pay-as-you-go organizations, Google Cloud documents Apigee API Analytics as a paid add-on, enabled per environment, and only in Intermediate or Comprehensive environments—not Base (Manage the Apigee API Analytics add-on). Billing begins when add-on enablement begins; disabling the add-on has retention implications for analytics data documented in the same guide.
That is a textbook hidden line item if your RFP only priced “Apigee” without the analytics SKU your product teams need for partner dashboards and operational reviews.
What “included” means in Zerq’s compare row
In our Compare table, Metrics & audit included is marked true for Zerq because we position metrics, auditability, and operator workflows as part of the platform you evaluate—not a menu of optional add-ons for the same baseline capability. Exact feature coverage should be validated in your environment and against your retention and export requirements.
Related reading
- Zerq vs Kong: regulated enterprises
- Why Apigee, MuleSoft, and AWS API Gateway fall short on full platform control
- The real cost of vendor lock-in in API infrastructure
See the full comparison matrix and request an enterprise demo to model TCO with your team.
Sources (primary documentation)
- Kong — Konnect Observability (accessed 2026-04-06).
- Google Cloud — Manage the Apigee API Analytics add-on (accessed 2026-04-06).