Kong Gateway Enterprise

What do you like best about the product?

From a testing perspective, having a centralized layer to observe API traffic has made it much easier to debug failed test runs. I can see exactly which requests and responses passed through, instead of having to dig through individual service logs. The rate-limiting and throttling plugins have also been useful for load and stress testing scenarios, and the request/response transformation plugins make it easier to simulate different payloads for stronger negative test coverage.

What do you dislike about the product?

The learning curve is pretty steep if you’re coming from a QA background without much infrastructure exposure—concepts like services, routes, and plugins take time to get comfortable with. Automating tests against the gateway also adds some friction, since you have to manage auth tokens and consumer credentials just to get CI pipelines running smoothly. The documentation tends to lean more toward admin-focused use cases as well, which leaves a noticeable gap when you’re looking for QA-specific workflows.

What problems is the product solving and how is that benefiting you?

It’s given us a single, consistent place to validate authentication and security policies, rather than having to test each API’s custom implementation separately, which was often inconsistent and time-consuming. Because traffic flows through one observable layer, integration issues show up earlier, and we’ve seen fewer flaky test failures caused by mismatched rate-limiting or authentication behavior across environments.

What do you like best about the product?

The API security and authentication features are the strongest part of the platform for us. Setting up OAuth, API key policies, and rate limiting per consumer has given us a much tighter grip on who's accessing what across our services. Managing auth centrally instead of building it into every individual API has saved a lot of duplicated effort, and the audit trial for API access has been genuinely useful when troubleshooting or reviewing security posture.

What do you dislike about the product?

The learning curve is steep, especially early on. There is lot of terminology and moving pieces (services, routes, plugins consumes) that take time to fully understand, and the initial setup wasn't as intuitive as I expected. Documentation helps, but getting the security policies configured exactly right the first time took more trial and error that I'd have liked. It would benefit from clearer guided setup for common auth scenarios.

What problems is the product solving and how is that benefiting you?

Before adopting Konnect, authentication and authorization logic was inconsistent across our APIs, with each service handling it slightly different, which made auditing and securing everything harder. Centralizing auth policies through Konnect has given us consistent security enforcement across the board, reduced the risk of gaps or misconfigurations, and made onboarding new APIs into our ecosystem significantly faster since the security groundwork is already standardized.

What do you like best about the product?

The API gateway and traffic management side of things has been solid for us. Rate limiting, load balancing, and routing rules are straightforward to configure once you get the hang of the platform, and it scales well without a lot of babysitting. The centralized visibility into API traffic across services has made it much easier to spot issues before they become bigger problems. Onboarding new APIs into the gateway is fairly quick once the initial setup is done.

What do you dislike about the product?

Support response time has been the main pain point for us. When we've run into issues that actually needed help (not just documentation lookups), turnaround has been slower than I'd like, especially for anything time-sensitive.

What problems is the product solving and how is that benefiting you?

Before Konnect, managing traffic and rate limits across our APIs was scattered and inconsistent, which made troubleshooting slow and error-prone. Having a single place to manage gateway policies has cut down the time we spend chasing down traffic issues and given us much better visibility into what's actually happening across our API layer. It's made scaling our API infrastructure less of a headache overall.

What do you like best about the product?

Managing API routing across a distributed microservices environment requires strict consistency, and Kong Konnect's hybrid architecture handles this exceptionally well. The SaaS control plane provides a unified view for configuring services, while the self-hosted data plane instances run locally near our Kubernetes workloads to keep proxy latency negligible. Implementing edge concerns—such as OAuth2 token validation, rate-limiting, and request transformation—via out-of-the-box plugins offloads significant overhead from our application code. Furthermore, managing the gateway state declaratively using the decK CLI seamlessly integrates into our GitOps pipelines, making deployment changes across staging and production environments predictable and fully version-controlled.

What do you dislike about the product?

Developing custom plugin logic still requires working with Lua or building WebAssembly modules, which introduces extra friction for development teams accustomed to higher-level languages like Python or Go. When troubleshooting synchronization mismatches between the SaaS management console and self-hosted runtime groups, navigating low-level proxy logs to isolate SSL certificate or schema errors can be time-consuming. Additionally, licensing costs scale up quickly as request throughput and the number of active runtime instances expand across enterprise environments.

What problems is the product solving and how is that benefiting you?

It eliminates fragmented traffic management and inconsistent security policies across independent backend services. Prior to adopting the gateway, individual teams implemented their own authentication layers and throttling mechanisms, creating maintenance debt and audit risks. Centralizing policy enforcement at the gateway level establishes uniform security standards across all endpoints while freeing developers to focus entirely on domain-specific business logic.

What do you like best about the product?

what i like most about Kong Konnect is that it gives me a clear place to manage APIs, routes, services, and plugins. The interface is fairly easy to navigate, and having everything in one dashboard makes managing and monitoring the gateway much more convenient

What do you dislike about the product?

The main downside for me is that it can take some time to understand where everything is especially when you re new to API gateways. There are quite a few options and settings , so the initial learning curve can feel a little steep.

What problems is the product solving and how is that benefiting you?

Kong Konnect helps simplify the management of APIs and services by putting routing , plugins and gateways configuration in one place. This makes it easier to keep APIs organized, apply policies consistently, and spend less time managing different pieces separately .