Our primary use cases for Kong Gateway Enterprise are modernizations, migrations, and digitalizations of financial institutions. These are the primary areas we are looking for.
External reviews
279 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Modernization projects have progressed well but documentation and security guidance still need work
What is our primary use case?
What is most valuable?
I find the price of Kong Gateway Enterprise to be competitive. Price is not a concern for us, but based on our experience working with financial institutions, maintainability and security are the primary concerns and areas they focus on.
What needs improvement?
Bringing in additional features to Kong Gateway Enterprise would not necessarily help it. Improving the existing features, increasing security, and adding robustness would be more beneficial. The focus should be on stabilizing the product, improving it, and increasing the documentation. Kong should focus on how the product can be self-onboarded or self-implemented, as this would ease and help customers significantly.
The necessary deployment of Kong Gateway Enterprise, API management, and guidance on how customers can use it or improve that area would be helpful. Security is a major concern, especially with new security architecture coming into place. These are the areas that should be prioritized. Beyond these areas, I do not see anything lacking. Kong Gateway Enterprise is quite comprehensive.
For how long have I used the solution?
I have been working with Kong Gateway Enterprise for five or six years.
How are customer service and support?
I do not have inputs on the technical support for Kong Gateway Enterprise, as those matters are handled by my architects. I have not heard any negative comments on the technical support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
In my current organization at Ernst & Young, I am not certain whether they are partners with Kong, but I have not heard anything from them. My previous organization was a partner, not a reseller, and we never had any issues or problems.
How was the initial setup?
The initial setup for Kong Gateway Enterprise has been ongoing for some time.
Which other solutions did I evaluate?
Two of our customers are using Kong Gateway Enterprise as well as other API management solutions such as MuleSoft, APIM, Azure, or AWS. These are the major four API management tools being used across the board for our customers.
For us, implementing Kong Gateway Enterprise with existing infrastructures and the cloud in tandem requires more effort than implementing MuleSoft or Azure APIM or AWS. Their integrations, implementations, and documentation are quite comprehensive for us. The learning curve is also slightly higher with Kong than with the other solutions.
What other advice do I have?
I cannot provide detailed information about Kong Gateway Enterprise's security features, but when setting up the entire infrastructure plus the open API framework, we have to set up the infrastructure security as a given.
I cannot provide details on implementations, but we have been using Kong Gateway Enterprise for our customers for some time. Based on my experience and my team's experience, I rate Kong Gateway Enterprise at a seven as a product.
Robust API Management with Impressive Performance and Scalability
What do you like best about the product?
I’m glad to see that this is a robust and well-established choice for API management. Its impressive performance and scalability make it highly efficient, and I particularly value the plugin architecture, which makes it simple to add new features.
What do you dislike about the product?
One persistent issue is that error messages from the proxy or plugin layer are often not sufficiently explicit. This lack of clarity can make it more challenging to debug and determine the underlying cause of a configuration failure.
What problems is the product solving and how is that benefiting you?
Since adopting this platform, we have experienced considerable time savings in both the development and maintenance of our individual applications. Furthermore, it enables us to innovate new features quickly and supports a higher degree of customization.
Flexible, Scalable, and Effortless API Management
What do you like best about the product?
I like that Kong Gateway is incredibly flexible and scales really well, it just handles massive amounts of API traffic without breaking a sweat. The plugin system is a huge plus for me, since it lets me add features like authentication, rate limiting, or monitoring without doing a lot of extra work, and I’ve found the hybrid deployment options super handy when bridging older systems with new cloud apps.
What do you dislike about the product?
What I dislike is that getting started can be rough, especially if you’re new to API gateways; the documentation sometimes leaves you hanging and figuring things out can be frustrating. I also wish more advanced features were available in the open source version, since some really useful stuff is locked behind the enterprise paywall, and the developer portal feels a bit undercooked compared to others I’ve tried
What problems is the product solving and how is that benefiting you?
Kong Gateway is solving the challenge of securely and efficiently managing APIs in a microservices architecture. It helps by centralizing API authentication and authorization, making sure only the right users can access my services, and it protects APIs from abuse through rate limiting and other security tools. With built-in logging, monitoring, and plugin support, it simplifies both managing traffic and troubleshooting issues, all from a single platform.
Great API Gateway but can get better with more Open Sourced community
What do you like best about the product?
Kuma API Gateway by Kong is the most impressive product related to domain im active rn
What do you dislike about the product?
Lesser Open Source practise and lesser istio integration pulls it from an efficient egress solution.
What problems is the product solving and how is that benefiting you?
Its been great for solving up the west east traffic and is a lot efficient from nginx and other gateway solutions but still it needs to be more aligned to istio
New Tool Intro Level for Better Internal ROI
What do you like best about the product?
Has many hybrid API flexible features. Plugin based abilities. Similarities to Kubernates and Boomi as tool.
What do you dislike about the product?
Features require testibg and use real-time for best understanding
What problems is the product solving and how is that benefiting you?
Tougher API challenges for gaps in enablemwnt.
API First Capability for Enterprise Solutions
What do you like best about the product?
Provides scalability and performance with proper requests volume matching. Deployment architecture meets SLA nd RPO-RTO requirements so far. Provides RBACs for security and runtime and management planes can be completely deployed on-prem. Provides monitoring and logging capabilities along with Kubernetes & Container based deployment.
What do you dislike about the product?
Nothing at the moment. Meets our requirement
What problems is the product solving and how is that benefiting you?
Hybrid deployment model, built in analytics, shared policies, ease of migration of legacy API infra.
Reliable API Gateway with room for easier setup
What do you like best about the product?
I find Kong Gateway very reliable once I get it up and running. The performance has been solid in my experience, and it manages high traffic with minimal latency. I really like the flexibility it gives me through plugins and integrations, which makes it easier to adapt to different use cases. I also appreciate the active open-source community and the amount of documentation available, which helped me learn along the way.
What do you dislike about the product?
Getting started with Kong Gateway took a bit of time to figure out. The setup and configuration were a little more involved than I expected, and I had to spend some extra time learning the best approach for my use case. I've also noticed that a few advanced features are only in the enterprise version, which is something to keep in mind.
What problems is the product solving and how is that benefiting you?
I use Kong gateway mainly for API management in a microservices setup. It has helped me centralize traffic routing, enforce authentication, and monitor requests across different services. Before this, managing APIs individually was messy and inconsistent, but Kong gave me a single place to handle rate limiting, security, and observability. This has saved me time on maintenance and made it easier to ensure our APIs stay reliable under heavy load.
Two Years with Kong API Gateway: A Reliable Partner in API Management
What do you like best about the product?
What I like best about Kong Gateway is its flexibility and scalability. It handles high traffic loads efficiently, provides strong security features like authentication and rate-limiting, and integrates seamlessly with monitoring tools like Prometheus. Its hybrid deployment model makes it easy to manage both DC and DR environments, and the plugin ecosystem allows for quick customization without heavy coding. Overall, it’s reliable, developer-friendly, and simplifies API operations at scale.
What do you dislike about the product?
With Kong Gateway Enterprise, the overall experience is excellent. The only area I would point out is that certain advanced configurations can feel complex at first, and some features require deeper expertise to fully leverage. Also, upgrades and version compatibility sometimes need careful planning. That said, the strong documentation, enterprise support, and stability make these challenges much easier to handle
What problems is the product solving and how is that benefiting you?
Kong Gateway Enterprise is helping us centralize and secure API traffic across multiple environments. It simplifies authentication, authorization, rate-limiting, and observability, which are critical for ensuring reliability and compliance. By managing APIs through a single platform, we’ve reduced operational overhead, improved scalability, and ensured high availability in both DC and DR setups. This has not only streamlined day-to-day operations but also given us confidence in handling peak loads and future growth
Reliable, Cloud-Native API Gateway with Strong Security Features
What do you like best about the product?
Kong Gateway is highly performant and cloud-native by design, which makes it an excellent fit for modern microservices and Kubernetes-based environments. I really appreciate its flexibility with plugins for security, observability, and traffic management—especially features like authentication, rate limiting, and service mesh integration. The developer experience is smooth, and the open-source foundation combined with enterprise-grade support ensures scalability and reliability. Its lightweight footprint and API-first approach make it easy to integrate into CI/CD pipelines while maintaining strong security practices.
What do you dislike about the product?
The documentation can sometimes be fragmented, making it difficult to find detailed, end-to-end configuration examples for more complex use cases. The learning curve is a bit steep for teams new to API gateways, and some advanced plugins require enterprise licensing, which may not always be budget-friendly for smaller organizations.
What problems is the product solving and how is that benefiting you?
Kong Gateway helps us centralize API management across different services and environments. It solves the challenges of securing APIs by enforcing authentication, authorization, and rate limiting consistently. It also provides strong observability with logging and monitoring features, which helps us detect issues early and improve performance.
Oustanding, secure Gateway
What do you like best about the product?
First thing is high Performance and Scalability and ease of use. Kong Gateway is a powerful and flexible solution known for its solid performance and ability to scale with growing needs. Second one is: broad API Style Kong supports multiple API styles and data sources, including HTTP, SOAP, WebSocket, gRPC, GraphQL, and Kafka event streams, offering Last thing is strong security: Kong provides robust security features to protect API infrastructure.
What do you dislike about the product?
Only one - Documentation. Users report that the documentation can be poor, lacking depth and sometimes leaving out crucial information
What problems is the product solving and how is that benefiting you?
API monitoring,API management, API security, API anomalys
showing 1 - 10