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.
