The whole area of API and AI management is quite complex, with so many different ways of being able to do things. I think a positive of Kong is that it's so configurable and extendable, but that is also a con because there are so many ways of achieving the same thing that I think often people are either confused or struggle to get going as to how to solve a particular problem. In my mind, a more opinionated deployment of Kong itself or even how to solve certain use cases would be something I would like to see, so a more opinionated use of their products and configuration of their products on how to solve the most common use cases. That's probably the main thing about needed improvements for Kong Konnect. It's a pretty fully-fledged platform; there obviously are portions of it that could be improved. But I think overall as a platform, it's really good, and I think it can help the majority of organizations looking to manage their throughput of APIs or AI traffic. The majority of what I've said before probably covers the improvements needed for Kong Konnect. There probably are some API Ops and AI Ops changes that could be improved, which is not necessarily the Kong Konnect product, but some of the toolchains around it. I'm thinking around, especially if it's API Ops, about topics like better GitOps processes and the ways of being able to roll back changes when there are issues. At the moment, a lot of that is either non-existent or is hand-cranked. I would like to see the ability to roll back configurations when there are issues being added to the product.
Kong Konnect can be improved by enhancing documentation and increasing support, as token integration presents challenges and has implementation complexities that need addressing. I do not rate Kong Konnect a nine out of ten because the configuration can be complex and not beginner-friendly. The UI is acceptable but not the best since many features are managed through CLI and YAML, and full enterprise power comes only with a high paid subscription.
I wish Kong Konnect could improve by having a built-in notification system whenever any APIs get pinged so that we can receive alerts and send them to the developer.
API Technical Architect at Independent API Consultant
Real User
Top 5
Oct 28, 2025
When comparing documentation, Kong's documentation is not on par with Google, Amazon, or other cloud providers. If a new person joins a team and wants to start using Kong's product and their associated tools, they would find it difficult initially compared to Google, Amazon, or Microsoft products, or even Azure from the deployment perspective. Kong has been working on their documentation and has developed a separate portal for the documentation. They are trying to improve that area.
IT Soulutoin Expert at a tech vendor with 10,001+ employees
Real User
Top 10
Apr 25, 2025
Kong Konnect's RBAC needs to evolve more, as they currently offer only one or two levels of RBAC in terms of organization and teams. Additionally, the licensing model could be simplified, especially in how they charge and track usage. There are also some technical restrictions around exposing GRPC APIs, but I have not explored this yet.
Kong Konnect facilitates efficient management and integration of APIs, providing a streamlined experience for developers to manage their services with high scalability. Kong Konnect is a comprehensive platform tailored for API development and management. It offers an intuitive interface that simplifies the process of connecting, managing, and securing APIs. Organizations benefit from its scalable architecture, ensuring it meets diverse operational demands and optimizes service delivery,...
The whole area of API and AI management is quite complex, with so many different ways of being able to do things. I think a positive of Kong is that it's so configurable and extendable, but that is also a con because there are so many ways of achieving the same thing that I think often people are either confused or struggle to get going as to how to solve a particular problem. In my mind, a more opinionated deployment of Kong itself or even how to solve certain use cases would be something I would like to see, so a more opinionated use of their products and configuration of their products on how to solve the most common use cases. That's probably the main thing about needed improvements for Kong Konnect. It's a pretty fully-fledged platform; there obviously are portions of it that could be improved. But I think overall as a platform, it's really good, and I think it can help the majority of organizations looking to manage their throughput of APIs or AI traffic. The majority of what I've said before probably covers the improvements needed for Kong Konnect. There probably are some API Ops and AI Ops changes that could be improved, which is not necessarily the Kong Konnect product, but some of the toolchains around it. I'm thinking around, especially if it's API Ops, about topics like better GitOps processes and the ways of being able to roll back changes when there are issues. At the moment, a lot of that is either non-existent or is hand-cranked. I would like to see the ability to roll back configurations when there are issues being added to the product.
Kong Konnect can be improved by enhancing documentation and increasing support, as token integration presents challenges and has implementation complexities that need addressing. I do not rate Kong Konnect a nine out of ten because the configuration can be complex and not beginner-friendly. The UI is acceptable but not the best since many features are managed through CLI and YAML, and full enterprise power comes only with a high paid subscription.
I wish Kong Konnect could improve by having a built-in notification system whenever any APIs get pinged so that we can receive alerts and send them to the developer.
When comparing documentation, Kong's documentation is not on par with Google, Amazon, or other cloud providers. If a new person joins a team and wants to start using Kong's product and their associated tools, they would find it difficult initially compared to Google, Amazon, or Microsoft products, or even Azure from the deployment perspective. Kong has been working on their documentation and has developed a separate portal for the documentation. They are trying to improve that area.
Pricing might be a topic to consider regarding improvements. I may advise Proofpoint to adjust marketing solutions based on each country itself.
Kong Konnect's RBAC needs to evolve more, as they currently offer only one or two levels of RBAC in terms of organization and teams. Additionally, the licensing model could be simplified, especially in how they charge and track usage. There are also some technical restrictions around exposing GRPC APIs, but I have not explored this yet.