Kong Konnect Pricing: 2026 Cost Guide and Alternatives
March 10, 2025
Kong Konnect pricing is not a single per-request number. The total can include a gateway control plane, request volume, dedicated-cloud bandwidth, analytics, developer portals, published APIs, AI models, identity tokens, or other platform modules. Deployment choices also determine which infrastructure and operations costs remain with the customer.
This guide explains the public Kong pricing structure, shows how to model a realistic bill, and identifies questions to ask when comparing Konnect with self-managed open source gateways or another enterprise API management platform.
Pricing snapshot: public prices and limits in this article were checked against Kong's official pricing page on August 25, 2026. Vendors can change prices, packaging, limits, and regional availability. Confirm the current rate card and your order form before making a purchasing decision.
Key Takeaways
- Konnect Plus combines a monthly gateway charge with included and metered platform usage.
- Serverless, hybrid, and dedicated cloud gateways have different cost and operating boundaries.
- Enterprise pricing is custom and billed annually; public Plus prices are not a substitute for an enterprise quote.
- Request volume is only one cost driver. Portals, analytics, network transfer, support, and customer-operated infrastructure can be material.
- Compare products using the same architecture, regions, availability target, traffic profile, and support scope.
What Is Kong Konnect?
Kong Konnect is Kong's software-as-a-service API platform. Kong hosts the Konnect control plane. Depending on the selected gateway type, the data plane can be serverless, dedicated in a supported cloud environment, or operated by the customer and connected to Konnect as a hybrid gateway.
That distinction matters for both architecture and cost:
- With a serverless gateway, Kong operates the gateway infrastructure within the product's stated limits.
- With a dedicated cloud gateway, Kong operates isolated gateway infrastructure and charges for the control plane and bandwidth according to the public rate card.
- With a hybrid gateway, the customer operates data-plane capacity while Konnect supplies the hosted management plane.
- A fully self-hosted Kong Gateway Enterprise deployment, in which the customer hosts both control and data planes, is listed separately with custom pricing.
Konnect also includes or offers modules for developer portals, service catalog, analytics, AI gateway capabilities, metering and billing, identity, and governance. The exact entitlement depends on the plan.
flowchart LR
U[Platform team] --> CP[Kong-hosted Konnect control plane]
CP --> S[Serverless gateway]
CP --> D[Dedicated cloud gateway]
CP --> H[Customer-operated hybrid gateway]
C[API clients] --> S
C --> D
C --> H
S --> A[Upstream APIs]
D --> A
H --> A
Current Konnect Plans
Kong's public page describes three commercial entry points:
| Plan | Billing approach | Public positioning |
|---|---|---|
| Free trial | $0 for 30 days | Evaluation with temporary access to enterprise functionality |
| Plus | Monthly, charged by gateway and usage | Smaller organizations starting an API program |
| Enterprise | Custom pricing, billed annually | Higher-volume and business-critical API, AI, and event traffic |
Konnect Plus publishes self-service prices and limits. Enterprise includes higher or customizable limits and additional governance and support capabilities, but the final commercial terms come from an order form. Do not estimate an Enterprise contract by multiplying Plus list prices unless Kong confirms that method.
Konnect Plus Gateway Charges
The official public rate card on August 25, 2026 lists these gateway control-plane charges:
| Gateway type | Plus list price | Selected Plus limit | Data-plane responsibility |
|---|---|---|---|
| Serverless API gateway | $25 per month per control plane | Up to 5 | Kong-operated serverless environment |
| Hybrid API gateway | $200 per month per control plane | Up to 2 | Customer operates data planes |
| Dedicated cloud gateway | $500 per month per control plane | Up to 2 | Kong-operated dedicated gateway |
The dedicated cloud option also lists bandwidth at $0.15 per GB for Plus. The public page describes a 99.99% SLA for dedicated cloud gateways. The hybrid data plane is self-managed, so its runtime availability depends on the customer's architecture and operations rather than the hosted control-plane fee alone. Serverless is listed without an SLA in the Plus comparison.
These are control-plane or gateway charges, not the whole monthly total. A hybrid deployment still needs compute, networking, load balancing, storage where required, monitoring, backups, and engineering time in the customer's environment.
API Request Charges and Limits
Konnect Plus includes 1 million API requests per month and lists $200 per additional 1 million requests per month, with a public maximum of 10 million requests per month for Plus. Enterprise request commitments and discounts are customizable.
This request charge should be modeled with the gateway charge rather than treated as an alternative to it. For example, a team using one hybrid control plane and 4 million total monthly requests would have these public-price components:
- one hybrid control plane;
- 1 million included requests;
- 3 million additional requests;
- customer-operated data-plane infrastructure and operations;
- any optional modules or overages used by the organization.
This article deliberately does not present the sum as a quote. Proration, taxes, negotiated terms, product changes, traffic classification, and account-specific entitlements can change the invoice. Use Kong's billing view or a written quote for the authoritative calculation.
Other Public Konnect Cost Drivers
The public pricing page exposes several dimensions beyond gateway traffic. The following examples show why an inventory is necessary before estimating total cost.
Developer Portals and Published APIs
Konnect Plus includes limits for portals and published APIs. The August 25, 2026 page lists one included developer portal, up to two portals, and $200 per month for an additional portal. It lists two included published APIs and tiered charges for additional published APIs, subject to a maximum of 20 on Plus.
Count actual API products and portal environments. A company may need separate internal and external experiences, but separate portal instances should not be assumed until requirements are clear.
Analytics and Data Retention
The Plus plan lists advanced analytics for the first 1 million requests and $20 per 1 million analytics requests above that level, with a 10 million monthly Plus limit. The pricing comparison shows 14 months of data retention.
Ask what counts as an analytics request and whether every gateway request needs the same retention and analysis. Exporting telemetry to another platform can also create ingestion, storage, and egress costs.
Dedicated Cloud Bandwidth
Dedicated cloud gateways list bandwidth separately. Model both request and response bytes, protocol overhead where relevant, and traffic growth. A request-count estimate alone can be misleading when responses contain large files or when streaming connections stay open.
AI Gateway, Metering, and Identity
The public Plus rate card lists separate dimensions for unique LLM models used by paid AI gateway capabilities, metering events and billing volume, and access tokens for Kong Identity. These modules solve different problems and should only be included when the architecture actually uses them.
Support and Governance
Plus lists email support with a two-business-day service level. Enterprise presents custom support and adds governance capabilities such as SSO and audit logging on the public comparison. Evaluate the support response target, coverage hours, named contacts, training, and professional services that your production risk requires.
A Better Way to Estimate Kong Konnect Cost
Build a workload sheet before selecting a plan. Use measured data when available.
1. Inventory Gateway Topology
Record:
- number and type of gateway control planes;
- regions and environments;
- production, staging, and disaster-recovery topology;
- customer-operated data-plane nodes for hybrid deployments;
- required portals and published APIs.
Do not assume one gateway represents the whole organization. Isolation, residency, team ownership, or change cadence may require more than one control plane.
2. Model Traffic, Not Just Monthly Calls
Capture:
- average and peak requests per second;
- monthly requests and expected growth;
- request and response sizes;
- streaming or long-lived connections;
- retry behavior;
- analytics coverage and retention.
Retries are especially important. A client, gateway, and service mesh can each retry a failing request, increasing both load and metered events. Bound retries based on idempotency and an end-to-end deadline.
3. Add Customer-Operated Costs
For hybrid gateways, include:
- compute and autoscaling headroom;
- load balancers and network transfer;
- metrics, logs, and traces;
- secrets and certificate management;
- backups and disaster recovery;
- upgrades, vulnerability response, and on-call work.
The same method applies to any self-managed gateway. Open source software can remove a license fee, but it does not remove production infrastructure or labor.
4. Add Commercial Requirements
List required controls and confirm which tier includes them:
- SSO, RBAC, and audit logs;
- data residency and private connectivity;
- support response and availability commitments;
- developer portal scale;
- custom plugins;
- AI, service catalog, or metering modules.
Request a quote using this fixed scope, then ask every vendor to price the same scope. Otherwise, a small self-service configuration may be compared with a multi-region enterprise architecture and produce a meaningless result.
Example Cost Worksheet
Use a table like this instead of a single requests-times-rate formula:
| Cost category | Input | Source of evidence |
|---|---|---|
| Gateway control planes | Type, count, hours | Target architecture |
| API requests | Included and additional volume | Production telemetry |
| Network transfer | Ingress/egress by region | Cloud billing export |
| Data-plane infrastructure | Nodes, load balancers, storage | Capacity test |
| Portal and API catalog | Instances and published APIs | API inventory |
| Analytics | Events and retention | Observability policy |
| Security and identity | Required capabilities and tokens | Threat model |
| Support | Coverage and response target | Operational risk |
| Engineering | Operation, upgrades, incidents | Team history |
Run at least three cases: expected demand, a sustained growth case, and a failure or campaign spike. Include the cost of unused capacity required to meet reliability targets.
Konnect Trade-offs to Evaluate
Konnect can reduce the work of operating a management plane and can offer managed data-plane choices. A fair evaluation should also examine these trade-offs without assuming they are universal drawbacks.
Multi-Dimensional Billing
Multiple meters can make forecasting harder than one flat subscription. The same dimensions can also let a smaller team start with a limited configuration. The practical question is whether your FinOps process can measure and forecast those meters and whether the plan limits fit expected growth.
Hosted Control Plane Dependency
Hybrid data planes can continue serving traffic according to their product behavior when the control plane is unavailable, but teams still depend on Konnect for management functions. Confirm documented failure behavior, configuration propagation, backup or export options, and operational access during a control-plane incident.
Plus Limits and Enterprise Transition
Plus has published limits for gateways, requests, portals, APIs, and other modules. Model when the organization would cross them and obtain an Enterprise quote before that point. The price step can be more important than the initial self-service bill.
Migration Effort
Every mature gateway accumulates configuration, plugins, analytics workflows, and operational knowledge. Migration cost is not unique to Kong. Reduce switching cost by keeping API contracts portable, using standard telemetry where possible, documenting custom plugins, and testing configuration export and recovery.
Comparing Kong Konnect with API7 and Apache APISIX
Apache APISIX is an Apache-licensed open source API gateway that teams can operate themselves. API7 Enterprise adds enterprise management and support around Apache APISIX deployments. These options have a different commercial and operating model from a Konnect Plus configuration.
Use these questions for a fair comparison:
| Question | Why it matters |
|---|---|
| Who operates the control and data planes? | Determines infrastructure and on-call ownership |
| What unit drives the license or subscription? | Affects growth sensitivity |
| Which plugins and governance features are included? | Prevents feature-mismatched quotes |
| Can the gateway run in required networks and regions? | Affects compliance and latency |
| How are configuration and telemetry exported? | Affects operations and portability |
| What support and SLA apply to each component? | Aligns price with production risk |
API7 Enterprise pricing is quote-based. Obtain current written terms rather than reusing historical API7 Cloud numbers. For self-managed APISIX, include the same infrastructure, observability, and engineering categories used in the Konnect model.
The objective is not to declare one platform cheapest for every organization. A managed option may save a small platform team more engineering time than its subscription cost. A larger team with established infrastructure automation may prefer greater runtime control. The workload and operating model decide.
Frequently Asked Questions
How much does Kong Konnect cost?
Konnect offers a 30-day trial, a monthly Plus plan with public gateway and usage prices, and a custom annually billed Enterprise plan. The total depends on gateway type and count, requests, bandwidth, modules, and customer-operated infrastructure. Check Kong's current official page for the authoritative rate card.
Is Kong Gateway open source free to use?
Kong maintains an open source gateway distribution, while Kong Gateway Enterprise and Konnect have commercial terms. A self-managed open source deployment still incurs infrastructure, operations, security, and support costs.
Does Konnect charge only by API request?
No. The public Plus model includes gateway control-plane charges and can include other meters such as bandwidth, analytics, portals, published APIs, AI models, metering events, or identity tokens.
Is a hybrid gateway fully managed by Kong?
Konnect hosts the control plane, while the customer operates hybrid data planes. Responsibility for runtime capacity, infrastructure availability, patching, and surrounding observability should be confirmed in the product documentation and support agreement.
Conclusion
Kong Konnect pricing becomes understandable when it is separated into gateway topology, usage, optional modules, and customer-operated cost. The public Plus rate card is useful for an initial model, but it is not an Enterprise quote and it should not be compared with another platform using a different architecture.
Build the workload sheet first, verify current vendor prices, and request like-for-like proposals. Whether the final choice is Konnect, API7 Enterprise, or a self-managed open source gateway, the best decision is the one that meets the required security, reliability, deployment, and support outcomes at a total cost the organization can operate predictably.
