Kong Gateway Enterprise

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 .

What do you like best about the product?

As a Flutter developer, I mainly use Kong Konnect when working with APIs for our mobile app. Having the API routes, traffic, and basic details in one place makes it easier to check if an issue is coming from the app or the API. I also find the logs and monitoring useful when an API request is not working as expected.

What do you dislike about the product?

Some of the settings were a little confusing for me at first, especially because I am more focused on flutter development than backend work. It took some time to understand where to check certain API settings and errors.

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

Before using Kong Konnect, when an API failed from the Flutter app, it was not always easy to know if the problem was in my code or on the API side. Now I check the API status, request details, and logs in one place, which helps me find the issue faster and reduces the time spent going back and forth with the backend team.

What do you like best about the product?

As a Full Stack .NET Developer working extensively with ASP.NET core Web APIs and third-party API integrations, the greatest advantage has been having a single control plane to manage authentication, JWT validation, rate limiting, and routing access all of our environments, eliminating the need to duplicate this logic within every backend service.

This has made our API security policies consistent by design, rather than something we need to audit for after deployment - which matters a lot when you are integrating multiple external APIs alongside our own .NET services.

The real-time analytics dashboard has also proven valuable, allowing us to identify latency spikes and error bursts early rather than discovering issues through a broken Angular frontend experience.

Additionally, RBAC and workspace separation have made it straightforward for different teams to manage their own services independently, and rolling back a problematic configuration change now takes seconds rather than escalating into a full incident.

What do you dislike about the product?

There is a moderate learning curve during initial setup, through it becomes considerably easier to navigate once the team become familiar with the platform.

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

Prior to adopting Kong Konnect, our API logic - including authentication and rate limiting - was distributed across multiple ASP.NET Core services, which complicated audits and led to inconsistent behavior between teams. With Konnect, this logic is now centralized, ensuring that new services inherit the same standards from the outset. Troubleshooting has also become more efficient, as we can review the gateway directly rather than searching through multiple codebases and SQL logs, and we now have significantly clearer visibility into which APIs exist, who owns them, and how they are performing.

What do you like best about the product?

I like most about Kong Konnect is having complete visibility into and control of our API traffic. Administering numerous services in various stages of development across our environments can become cumbersome. Having visibility into and governance of all traffic passing through Kong has been a game changer. API Gateway features, authentication policies, rate limiting, and traffic controls have allowed us to minimize effort from our infrastructure and development teams. It has also been extremely valuable as we ensure consistency of APIs across our environments while enabling modern microservices-based applications.

What do you dislike about the product?

The platform has plenty of power under the hood but does require a good understanding of API gateways, networking, and security rules. Teams new to API management may spend some time initially configuring the gateway and associated policies.

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

What Kong Konnect allows us to do is simplify how we manage API complexity. Previously, gaining visibility into our API traffic and trying to implement uniform security policies between numerous services was more difficult. With Kong Konnect we are able to manage our APIs better, operate them more reliably, and have greater control over how our applications communicate.

What do you like best about the product?

The biggest win for us is having a single control plane to manage authentication, JWT validation, rate limiting, and routing across all our environments, instead of duplicating that logic inside every backend service. It’s made our API security policies consistent by default, rather than something we have to audit after the fact. The real-time analytics dashboard is genuinely useful as well—we can catch latency spikes and error bursts early, instead of finding out from a broken frontend. On top of that, RBAC and workspace separation make it easy for different teams to own their own services without stepping on each other, and rolling back a bad config change takes seconds instead of turning into an incident.

What do you dislike about the product?

There’s a bit of a learning curve when you’re first getting everything set up, but it becomes much easier once you’re familiar with the platform.

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

Before Kong Konnect, API logic such as authentication and rate limiting was scattered across multiple services, which made audits painful and led to inconsistent behavior between teams. Now it’s centralized, so new services automatically inherit the same standards from the start. Troubleshooting is also faster because we can check the gateway first, and we have much clearer visibility into which APIs exist, who owns them, and how they’re performing.

What do you like best about the product?

As a backend engineer, I appreciate how Kong Konnect allows our team to centralize the management, security, and monitoring of APIs across all our services. Gateway configuration is straightforward, and using plugins for authentication, rate limiting, and traffic management saves us the time we would otherwise spend building these features from scratch. This was particularly beneficial when working with microservices-based applications, where managing dozens of individual APIs can be challenging.

What do you dislike about the product?

The initial setup requires a bit of a learning curve, as do some advanced configurations-such as complex routing or multi-environment setups.

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

Kong Konnect enables us to standardize how we implement API security, routing, authentication, and traffic policies, rather than building these features individually into every backend service. This reduces redundant development effort and allows us to maintain our microservices more effectively. Centralized monitoring also helps us quickly identify API errors and performance issues, thereby improving our troubleshooting capabilities and the overall robustness of our applications.

What do you like best about the product?

Running API proxies across distributed environments usually creates a massive management headache, but Kong Konnect handles this cleanly through its separation of data planes from the cloud-managed control plane. Being able to run data nodes directly inside Kubernetes pods while managing configurations through the cloud console keeps request latency down to single-digit milliseconds. The declarative tooling via decK makes synchronizing gateway configurations across staging and production environments predictable and easy to integrate into CI/CD pipelines. Additionally, native plugins for OAuth2/OIDC token validation, upstream health checks, and rate limiting handle heavy networking concerns right at the gateway layer, saving considerable boilerplate code in downstream microservices.

What do you dislike about the product?

Writing custom plugins still requires familiarity with Lua or compiling Go plugins via WebAssembly (Wasm), which slows down onboarding for engineers used to higher-level application languages. When synchronization issues occur between self-hosted data planes and the cloud control plane, inspecting low-level proxy logs to find schema or certificate mismatches can be tedious. Pricing can also scale steeply once you expand into multiple enterprise runtime groups and high-volume traffic tiers.

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

It standardizes traffic management and API security policies across our entire backend footprint. Before adopting the platform, individual engineering squads handled authentication and request throttling inconsistently across separate services. Centralizing these policies at the gateway layer ensures uniform security compliance, simplifies auditing, and allows development teams to focus purely on building business logic rather than reimplementing edge security features.