The product seems to be good, especially in terms of API creation and management. The tool is seamlessly easy to use, and offers ease of configuration and management. The tool has some very good options for infusing some API security parts. The tool also offers some readily available connectors as well. From an overall perspective, I am handling both B2B integrations and cloud integrations. In our company, we had multiple products in place of Kong Gateway Enterprise.
External reviews
External reviews are not included in the AWS star rating for the product.
Premium and trusted open source API gateway
Reasonably priced and offers ease of integration to users
What is our primary use case?
What is most valuable?
Kong Gateway Enterprise enhances our company's API security in a strong way, and it is compliant with most of the security compliance issues, which is good from an assurance standpoint and acts as a strong point when it comes to the product. In terms of ease of configuration and maintenance of the APIs, the tool offers a very good dashboard, specifically API dashboards, which can provide you insights into how you can use the dashboard for monetizing your solution. For example, for some of the APIs that accompany the product and become a part of the ecosystem, be it for opening new services with different partners, the tool is able to provide good insights in terms of integration touchpoints, which not only caters to the internal ecosystem but also into a partner ecosystem, giving an agnostic view. Depending on the exact need of the hour and based on the requirements, Kong Gateway Enterprise is useful in terms of integration, ease of use, and dashboard.
Though I have not tested the tool, I can say that the product supports AI-driven applications. Nowadays, in most language models, especially when we talk about the edge deployment model, any of the platforms provide you with seamless integration, which is advantageous because most of the applications are consumed by end users. It also boils down to the fact associated with the latencies. For some of the services and requirements, it doesn't always have to be some public cloud infrastructure that one needs to experience. I believe that I will be better off with edge deployment, where things can be run on a nearby location where the customer proximity is there. A combination of AI and edge deployment will be an advantage.
What needs improvement?
The ease of integration offered by the tool is strong. The security is being built in the tool. In terms of the connectivity part of the tool, I haven't had a chance to comment on the challenges since we have not tried it on a large enterprise.
With Kong Gateway Enterprise, since users want more readily available connectors that can be used in head offices or back offices, it is an area that needs to be considered for improvement. For example, if I give out a setup tomorrow for the systems in head offices or back offices, like SAP or ERP systems, then you should be able to provide connectors, and it is an area where my company has not been able to test the product yet. The aforementioned features should not only be available in Kong Gateway Enterprise but also across the product stack offered by others.
From an improvement perspective, the product should offer more readily available connectors and also allow for more seamless AI integrations. Most of the products nowadays are becoming more AI-native because of the needs of the industry. The introduction of GenAI and the use of the integration part to make the tool more of an industry-based solution can make a difference.
For how long have I used the solution?
I have been using Kong Gateway Enterprise for two to three years.
What do I think about the scalability of the solution?
Speaking about scalability, I would say that I would not be able to comment on it since the product is not used in large enterprises from a scalability standpoint. The way the tool has been built and the way the API integrations are happening on the cloud solutions, I think it should not have a problem scaling up, but my company has not tested it. To see if the product can be scalable, my company needs to test it in large enterprises with the help of agents. I don't think the scalability part of the product will be an issue, but only if I deal with larger implementations can I be in a better position to comment on the scalability part.
How are customer service and support?
The solution's technical support is good and fast in terms of responsiveness and problem-solving skills. I rate the technical support a nine out of ten.
How would you rate customer service and support?
Positive
What's my experience with pricing, setup cost, and licensing?
The product is reasonably priced because it goes by the SaaS model. When it comes to Kong Gateway Enterprise, I don't see much of a price point difference from other tools in the market.
What other advice do I have?
I rate the tool a nine out of ten.
Has monitoring features but UX needs improvement
What is most valuable?
Kong enterprise has significantly enhanced our ability to manage and secure our Microservices. Its most valuable feature is monitoring.
What needs improvement?
The tool needs improvement in UX.
For how long have I used the solution?
I have been using the product for six months.
What do I think about the stability of the solution?
I rate the solution's stability an eight out of ten.
What do I think about the scalability of the solution?
I rate the tool's scalability an eight out of ten. My company has five to seven users.
How are customer service and support?
I have encountered communication issues.
How would you rate customer service and support?
Neutral
How was the initial setup?
I rate the tool's deployment a ten out of ten, and it took a few hours to complete.
What's my experience with pricing, setup cost, and licensing?
Kong Enterprise's pricing is reasonable for our company size.
What other advice do I have?
I rate the overall solution an eight out of ten.
Which deployment model are you using for this solution?
Improves performance and comes with rate limiting features
What is our primary use case?
My company is a financial company involved in credit card processing. We use the solution for internal IT secure gateway.
What is most valuable?
The tool's feature that I find most beneficial is rate limiting. In our usage, especially in the financial sector, we prioritize limiting API usage. This is crucial because we provide APIs to other companies and must ensure they adhere to their allocated usage limits. Without rate limiting, there's a risk of excessive usage, which could result in significant costs.
The solution has improved our organization's performance.
What needs improvement?
Kong Enterprise needs to improve its pricing, which starts at hundreds of thousands of dollars. Pricing should be based on API usage rather than monthly. It should improve its documentation as well.
For how long have I used the solution?
I have been using the product for six months.
What do I think about the stability of the solution?
I rate the tool's stability a nine out of ten.
What do I think about the scalability of the solution?
The solution is horizontally scalable and very useful. My company has one customer for Kong Enterprise. I rate its scalability a ten out of ten.
How are customer service and support?
I haven't contacted technical support yet.
How was the initial setup?
The product is easy to deploy and gets completed in one hour.
What's my experience with pricing, setup cost, and licensing?
Kong Enterprise is cheaper than Apigee. I rate its pricing as four out of ten.
What other advice do I have?
Kong Enterprise can connect with other tools easily. It has features like APIs and logging that programmers can use to link it up with different systems. I haven't used its integration features much, but I know its possibilities. I rate the tool an eight out of ten.
Which deployment model are you using for this solution?
Best Cloud Native API Platform
Robust API management solution offering scalability, resilience, cloud-agnostic deployment capabilities and powerful and adaptable gateway services
What is our primary use case?
It serves as an API gateway and microservices management platform, facilitating the creation, deployment, and oversight of APIs and microservices. It serves as a solution for measuring requests, managing upstreams, and handling internal APIs within the bank.
What is most valuable?
It is an excellent tool for managing data. It boasts remarkable speed and stability, and these qualities, particularly the gateway's resilience, are standout features for me. The shared features are also commendable. One of the aspects I appreciate is the effective rate limiting, achieved through the use of the throttling plugin for our APIs. Additionally, the straightforward automated deployment process for the gateway makes it exceptionally easy for everyone on the team to adapt without complications.
What needs improvement?
I find that expressing information can be a bit challenging, especially for those who are new to installing email configs or using it for the first time. Understanding the configurations and knowing what needs to be done can be a bit difficult initially.
For how long have I used the solution?
It is a crucial part of my daily workflow.
What do I think about the stability of the solution?
I encounter no issues with deployments, and it reliably performs its duties on a daily basis. It proves to be both resilient and stable.
What do I think about the scalability of the solution?
It's scalable to your needs, and if you have the financial resources, you can scale it as much as you want.
Which solution did I use previously and why did I switch?
Before adopting Kong, I utilized X-ray, which is another API gateway. I believe the strength of Kong lies in its agnostic nature. It allows deployment across various cloud environments, providing flexibility for implementation in any infrastructure. It is inherently cloud-native, enabling deployment and maintenance on platforms such as AWS, Azure, and Google Cloud. This sets it apart from other gateways that may not offer the same level of versatility.
How was the initial setup?
The initial setup is relatively easy, but it requires a clear idea of your objectives.
What about the implementation team?
When it comes to deployment, my team and I handle the entire process. We are responsible for managing all aspects of it. It is possible to deploy it within ten minutes in a cloud-native environment using our current CI process.
What other advice do I have?
My advice is to approach it with careful consideration. While it is a powerful tool, gaining expertise is crucial. It's essential to try it out firsthand, build confidence that Kong aligns with your requirements, and recognize its reliability as a gateway. In my experience, it has proven to be a top choice. If you encounter challenges, I recommend visiting the website and delving into the documentation, as it often holds solutions for various scenarios. Overall, I would rate it eight out of ten.
Unlocking Seamless API Management
Its scalability features enables us to handle large API traffic volumes, which ensures optimal performance of our api services. It's load balancing capabilities contribute to our improved system scalability and resilience.
DevOps and Cloud Native API Gateway
The hybrid installation via Kong Konnect is very quick and powerful and allows you to outsource all management except for the dataplanes which are installed on-premise and managed remotely. The on-premise version is easy to install. It can eb configured both via web interface and through a declarative configuration as well. In terms of support, the Enterprise version offers very fast and efficient support.
It supports native CLI tools to launch test and deploy configuration in your CI/CD pipelines
For the Enterprise version the licensing model is a bit complicated because it depends on the number of invocations but also on the concept of gateway service, which is not always easy to keep under control.
Kong API Gateway: Robust and Flexible API Management
Excellent working exposure with Kong API gateway
Good Customer Support,Ease of Implementation,Ease of Use, good for Frequency of Use,
Number of Features