Kong Gateway Enterprise

What do you like best about the product?

The console is clean and easy to navigate, and is slotted into our existing microservices setup without friction thanks to its plugin ecosystem. It held up well under real traffic with solid latency, and support has been fast and genuinely knowledgeable, which made onboarding smooth.

What do you dislike about the product?

Pricing is usage-based, so it takes some upfront modeling of your traffic to forecast costs accurately. The AI Gateway and KAi assistant are still new additions, so I'd treat them as promising rather than production-proven just yet.

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

It consolidated our gateway, mesh, and observability needs into one Platform, cutting down real operational overhead and freeing up time to focus on building instead of maintaining plumbing.

What do you like best about the product?

What I like the most about Kong Konnect comes down to the fact that, it is a middleware between my backend and client, so it naturally fits between everything I already work with. It works with Ai APIs, other paid APIs, which otherwise you'd have to manage yourself. Coming to performance, I like the Kong Gateway as it can easily handle high API traffic efficiently, without massive overhead when applying policies and plugins. Pricing is genuinely interesting because it centralizes a lot of things into one platform, from analytics to rules to security, basically instead of managing everything yourself, Kong can do it for you in one platform. UI is clean and modern, its easy to use, even for a beginner, which is very important for something this important, because UI should not be confusing for a platform which sits between your backend and your client. Onboarding process was also smooth, they offer one month free trial for starting up, and also offer buying with AWS marketplace, easy to onboard, load your workload and start using. Ai is the USP of this platform, and very very important in 2026, API costs of Ai can be massive, Kong allows us to set rate limits, auth, etc. on the same platform, which is very smooth and convenient.

What do you dislike about the product?

Things I dislike about Kong comes down to limitations, pricing and learning curve rather than features, like pricing can scale quickly as the usage grows, similarly being an enterprise platform, the learning curve can be steep as availability of hands on reviews and documentations across developer community is limited.

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

Security and protection of core APIs from abuse is one of the most important problem Kong solves, as being in logistics business, core APIs play an important role across warehouses, customer side, seller side, aggregator side, trucks, tracking, logging, we can't afford digital downtime, which can have serious consequence. Second thing I would mark is management ease, since Kong brings down everything to one platform, instead of managing tens of different micro services individually. Visiblity and analytics would be an addition I would note because too many individual micro services make analytics and reporting difficult, kong brings them down to single dashboard.

What do you like best about the product?

What I like most about Kong Konnect is that it gives us one centralized place to manage, secure, and monitor our API gateways across different environments. I also like the separation between the cloud control plane and local data planes, which makes deployment easier without adding latency to our backend traffic. Setting up things like OAuth2, rate limiting, and mTLS using the available plugins is also quite straightforward. The service catalog and Developer Portal are useful as well, especially when multiple teams are working with different APIs.

What do you dislike about the product?

Getting onboarded took longer than expected because the documentation mixes Konnect cloud concepts with self-hosted Kong Gateway setup, which caused some initial confusion. The user interface can also occasionally feel sluggish when managing large numbers of services and routes. Finally, the pricing jumps quite a bit between tiers once your API call volume begins scaling up.

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

We struggled with inconsistent API security and manual gateway maintenance across distributed environments. Kong Konnect centralized our API management into a single dashboard, allowing us to enforce global security policies, authentication, and rate-limiting seamlessly. This has freed up valuable developer hours from managing infrastructure, improved our API uptime, and made onboarding new services much faster.

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.