Kong Konnect gives us one place to manage APIs, gateways, policies, and traffic. The dashboard is clear once everything is set up, and the analytics help us spot errors and performance issues without jumping between several tools. It also works well when APIs run across different cloud environments. For our current usage, the pricing feels fair. It saves us time on gateway management, monitoring, and policy updates. The cost can increase as usage grows, so it is worth checking the pricing carefully before expanding. Review collected by and hosted on G2.com.

The initial setup has a learning curve, especially if you are new to Kong’s terminology and control plane structure. Some settings also take time to find. Review collected by and hosted on G2.com.

I really appreciate how Kong Konnect tightens security and organizes traffic across our services. The ability to route upstream connections cleanly has reduced 502 errors, and the added visibility allows me to trace faults quickly. The dashboard provides a clear view of gateway activity, which is incredibly helpful. What I love most is the deployment flexibility, as I can set it up on-premise, in the cloud, or on Kubernetes clusters without having to change my approach each time. The initial setup was straightforward too, allowing me to start handling traffic with minimal configuration hassle. Review collected by and hosted on G2.com.

I find the documentation unclear, and a fuller set of worked examples would help me save time when configuring something less common. There's also the enterprise wall. The open-source resources are strong, yet the more capable features sit behind the paid tier, which can feel like a barrier when I want to push further. Review collected by and hosted on G2.com.

I primarily use Konnect to validate APIs across our test environments. Having the ability to see services/routes and traffic all in one place is convenient, especially when debugging an API test that suddenly starts failing and wanting to verify if the problem is originating from application or gateway. Request volume, error, and latency analytics are also great to have during regression testing. Review collected by and hosted on G2.com.

Some gateway configuration/settings and plugins were a bit difficult to grasp initially. And when you have lots of services, navigation feels cluttered and I find myself having to use filters to locate the exact API I'm looking for. Review collected by and hosted on G2.com.

I really appreciate how Kong Konnect takes on cross-cutting concerns and lets the gateway manage OAuth2 and rate limiting, which means I don't have to code them into every service. It's incredibly freeing to know that new services can inherit a uniform security posture and be production-ready without my having to code bespoke protections. The speed of Kong Konnect is impressive, and watching the Kong Ingress Controller automate routing configuration through Kubernetes-native resources and GitOps is a real turning point for me. The OIDC and Rate Limiting plugins saved us from a long stretch of custom development and secured new services without affecting performance. I also value the plugin ecosystem, which allows me to extend the gateway's capabilities through configuration rather than code, making enhancements a simple reviewed commit instead of a major project. The setup was pretty smooth overall. Review collected by and hosted on G2.com.

My reservation lies with the drift away from a fully supported open-source model. It nudges teams toward Enterprise and Konnect licensing sooner than planned, and for smaller projects, that shift carries real overhead. Weighing cost against the production-grade features we cannot do without has complicated our longer-term roadmap more than I would like. The pull toward Enterprise licensing forces me to weigh production-grade features against cost earlier than I would like, which means some smaller client environments that could once ride on open source now face a spending decision before they scale, complicating how I sequence fabric rollouts across the roadmap. Review collected by and hosted on G2.com.

For me, the biggest advantage is having one centralized place to manage APIs, security policies, routing, and monitoring. The analytics are also useful because they help me quickly spot performance issues and better understand how our APIs are being used. Review collected by and hosted on G2.com.

There’s a bit of a learning curve for new users, and some of the more advanced settings can take a while to fully understand and configure. I also think the documentation could be more detailed in a few areas to make those parts easier to navigate. Review collected by and hosted on G2.com.

I appreciate Kong Gateway for providing better visibility into APIs and upstream services. The Kong Proxy performs way better than other alternatives like NGINX Proxy. I particularly like the 'Plugin first' approach since the plugins in Kong are modular like legos, making tasks like rate limiting or blacklisting certain APIs much easier without having to write lots of code. The built-in, out-of-the-box plugins reduce latency effectively. The setup process is super easy, thanks to the right scripts and developer documentation available, making installation and setup straightforward. Review collected by and hosted on G2.com.

The support for Custom Plugins needs to be improved even further, a bit more streamlining in terms of building and developing plugins using Lua. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Mostly develop backend APIs myself, and Kong Konnect allows me to manage routing, auth and other API specific configs in one place. Routing/Authentication/ etc could get split across services previously, so having a central location makes things a little easier and saves time when dealing with lots of APIs. Review collected by and hosted on G2.com.

Of course there are many configuration options and can sometimes take awhile troubleshooting an API if it's not behaving when you need to determine if the issue is with Kong's config or the backend service. Review collected by and hosted on G2.com.

It’s useful for securely storing credentials and retrieving them at runtime whenever they’re needed. The user interface is well designed and intuitive, so after a few days of training it feels accessible to just about anyone. I also really like the analytics dashboard; it’s clear and easy to use, and it lets us see who is using our products, which helps guide our decisions on what to develop next. Review collected by and hosted on G2.com.

It’s honestly hard to find anything I dislike—I love everything about Kong, mainly because of its wide range of features. I really don’t have anything negative to say. The documentation is thorough and easy to follow, it requires minimal coding to get started, and the support team is excellent and always ready to help when needed. Review collected by and hosted on G2.com.

simplifies API management by providing a user-friendly platform with strong security, monitoring, and scalability features Review collected by and hosted on G2.com.

it takes time for new users to become fully comfortable with all configuration and Mgt. options and finding some specific settings , troubleshooting issues , time consuming for doing some settings due to multiple screens Review collected by and hosted on G2.com.