Integration across Kong Enterprise features One thing I like best about Konnect is that it centralizes how we manage APIs. We have several teams splitting their time across different services. Having one place to manage gateways, APIs, and access is very helpful. I also like how developers can self-serve a good amount of what they need without having to rely on the platform team. Review collected by and hosted on G2.com.

Setting Konnect up is not as simple as pressing a button. We had to spend a decent amount of time thinking through how we wanted things structured. This was especially true for team organization, permissions, and separating out environments. Other pieces also feel overcomplicated for simple tasks. Once you get accustomed to using it though, it becomes easier. Review collected by and hosted on G2.com.

Working mostly on the front end, I mainly interact with the APIs Kong Konnect manages, and it's made life easier just from a consumption side. The dev portal gives clear docs for each endpoint, so I am not constantly pinging the backend team to ask what a field means or what status code to expect. Response caching set up at the gateway level has also helped page load times noticeably on some of our data-heavy views without us touching the frontend code at all. Review collected by and hosted on G2.com.

Sometimes when an API call fails, the error message coming back through the gateway is a bit generic, so I still have to loop in a backend dev to figure out the actual cause. It would help if error responses gave a bit more context by default.

Also, the interface takes a little getting used to if you are not the one managing configs day to day. Review collected by and hosted on G2.com.

Best for AI models and management in one place. Review collected by and hosted on G2.com.

It is very difficult for a new user to set up, and the price feels very high for most of the features. Also, once we submit a request, it still needs to go through another process or gateway, which adds another layer of complexity. Review collected by and hosted on G2.com.

Onboarding a new team onto Kong Konnect has been smoother than I expected. RBAC and workspace separation let different team manage their own services without stepping on each other, which matters a lot once you scale past a handful of squads. Version control for APIs is also solid - rolling back a bad config change takes seconds instead of a whole incident response. CI/CD integration was straightforward too, so pushing gateway config changes through our existing pipeline didn't need a separate process. Review collected by and hosted on G2.com.

Support response times can vary depending on the issue's complexity - simple questions get answered fast, but anything touching hybrid mode sync took longer than I'd like. Also, when we hit a scaling point with a larger number of consumers and routes, the dashboard started feeling a bit sluggish. Nothing that broke functionality, just slower load times that added friction to daily use. Review collected by and hosted on G2.com.

I like that it allows us to have a central hub to manage APIs, routes, authentication, and policies. I feel like this would save me time debugging not having to go into each application to ensure these things are configured since I only work with consuming services. Utilizing the panel you can also view the current state of your APIs and help troubleshoot what may be failing. Review collected by and hosted on G2.com.

Learning some of the gateway / service configurations was a bit confusing to me when initially creating them. You have to take time to read through all your options to determine what should be where. Review collected by and hosted on G2.com.

I love that I can now centrally configure authentication, JWT validation, rate limiting, and traffic routing for all my development and staging environments from the Konnect control plane without embedding any repetitive code in my backend services. I also can take advantage of features such as the developer portal and real-time analytics dashboard. Monitoring latency metrics, catching error bursts, and verifying throughput metrics across all my APIs has never been easier. Review collected by and hosted on G2.com.

The biggest thing that took me a little while to learn was writing Lua or Go plugins. Additionally,I was tripped up by not being able to see what stage my config sync was at if there was an issue. Sometimes you have to look at gateway logs to figure out where a sync got hung up. Review collected by and hosted on G2.com.

The biggest advantage of implementing Kong Konnect is how easily it handles cross-cutting concerns like OAuth2 and rate limiting at the gateway level. My engineering team no longer has to code custom authentication logic into every single microservice we deploy. The speed and API latency reduction are noticeable immediately, especially when our endpoints are handling millions of requests. I also heavily rely on the plugin ecosystem; securing a new service with the OIDC plugin is just a simple configuration commit rather than a multi-week engineering project. Review collected by and hosted on G2.com.

The initial setup and configuration can be overly complex, especially if your engineering team does not have prior API gateway experience. The documentation, while adequate, is not quite on par with major cloud providers like AWS or Google, which makes the learning curve steeper than necessary. Additionally, there are often multiple ways to achieve the same routing task, which can lead to confusion and inconsistent configurations across different development teams. Review collected by and hosted on G2.com.

The new Global Service Catalog Integration is an absolute game-changer for anyone dealing with a messy, multi-cloud microservices architecture. Honestly, keeping an API registry up to date is usually an administrative nightmare. With this feature, microservices running literally anywhere across our infrastructure are automatically discovered and cataloged into Konnect's central registry with minimal manual configuration. It completely eliminates the drift between what's actually running in production and what’s documented in our control plane. It just works, saving our engineering team massive amounts of manual overhead. Review collected by and hosted on G2.com.

While the platform’s feature velocity is incredible—especially with the new AI gateway and catalog capabilities—the documentation can sometimes feel a bit text-heavy when you're trying to implement complex topologies quickly. To match how fast these features are dropping, I'd really love to see Kong enhance their learning resources by providing more advanced video guides for the various features. Walking through deep-dive configuration scenarios visually would make onboarding these advanced capabilities significantly smoother. Review collected by and hosted on G2.com.

One thing I’ve really liked about Kong Konnect is how much easier it makes managing APIs across different environments. The centralized control plane gives good visibility into services and traffic without adding a lot of operational overhead. I’ve also found the developer portal and analytics features to be much more polished than before, making it easier for both API consumers and platform teams to work effectively. The cloud-managed approach reduces maintenance effort, which lets us focus more on building and improving APIs rather than managing infrastructure. Review collected by and hosted on G2.com.

While Kong Konnect is a strong platform overall, there are a few areas that could be improved. Some workflows in the UI can feel a bit complex, especially when managing larger numbers of services and routes. I’d also like to see more built-in guidance for troubleshooting configuration issues, as diagnosing problems sometimes requires digging through multiple logs and settings. Better visibility into request flows and dependencies would make day-to-day operations easier. Finally, simplifying the setup process for hybrid and multi-environment deployments would help reduce the learning curve for new users. Review collected by and hosted on G2.com.

What I liked most about Kong Konnect is that it’s centralized and makes it easy to connect and manage API platforms. The built-in analytics and the developer portal are especially useful for monitoring API usage, and they also make APIs easier for developers to discover and consume. Review collected by and hosted on G2.com.

The main thing about Kong Konnect is the learning curve. Some settings also require navigating through multiple screens, and the pricing can feel high once premium features, plugins, or enterprise support are added. Review collected by and hosted on G2.com.