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.
Kong Gateway Enterprise
Kong | Kong Gateway EnterpriseLinux/Unix, Amazon Linux 2017.03.0 - 64-bit Amazon Machine Image (AMI)
External reviews
External reviews are not included in the AWS star rating for the product.
api gateway service
KONG API MANAGEMENT
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.
User-friendly developer portal but licensing model changes for each geography
What is our primary use case?
We use it to provide API services to our clients.
What is most valuable?
The features I like include ease of operation and implementation in a cloud environment, the dashboarding features for API statistics, and the user-friendly developer portal.
The plugin architecture is simple and easy to implement.
What needs improvement?
There is room for improvement in the licensing model. It charges differently for each geography. If I have to use Kong in two different geographies for the same organization, it charges me twice. When it comes to Azure, it doesn't charge me twice. Azure has a more economical model.
The licensing in the Middle East, where we work. The licensing of Kong and Azure is a lengthy process. It was not readily available. We had to talk to the product owner to make the Kong Gateway available as a solution on the Azure marketplace. The licensing is only as an on-prem or separate product.
The difference between billing on the cloud and outside the cloud is if I purchase Kong outside, I have to pay the AMC every year or so. The purpose of cloud implementation is to have a consolidated billing for all resources purchased on the cloud. You don't need to deal with multiple vendors. If you have purchased five applications on the cloud marketplace, you get a single consolidated bill every month.
The ease of billing is lost when Kong is not available directly on the Azure marketplace. This is one area where they can improve. There could be a problem with the Middle East geography. They may have Kong available on the Azure marketplace in other geographies, but this is how it is in the Middle East.
For how long have I used the solution?
I have been using it for two and a half years.
What do I think about the stability of the solution?
It is a very stable product.
What do I think about the scalability of the solution?
I would rate the scalability a seven out of ten, with one being one scalability and ten being high.
The scalability aspect has a limitation with geography. I can expand it to any country within one region, but not beyond. There are licensing implications.
Technologically, it is scalable to whatever extent required, without any limitations. The limitation is only across geography. It cannot be scaled beyond one region.
There are around 25 technical people using this solution in my organization. We use it daily.
Which solution did I use previously and why did I switch?
Kong is the first API solution we used. We started API solutions with Kong.
How was the initial setup?
I would rate my experience with the initial setup a six out of ten, with one being difficult and ten being easy.
The first implementation took three months.
What about the implementation team?
The deployment was done by a vendor.
What was our ROI?
Kong Gateway doesn't save anything, actually. It is not for that purpose. It's a technological solution, we cannot directly attribute revenue to Kong alone. Multiple applications work together to offer the APIs, and those API solutions have brought in some revenue, but not entirely because of Kong, so I cannot quantify that.
What's my experience with pricing, setup cost, and licensing?
The licensing is expensive. I would rate the pricing an eight out of ten, with one being cheap and ten being expensive.
Which other solutions did I evaluate?
Our parent organization has been using Kong and evaluated all the possibilities. We took their reference. Recently, we did an evaluation and migrated to Azure API Management from Kong.
What other advice do I have?
I would recommend using it. It is a very powerful tool with lots of features. It's stable, user-friendly, and easy to learn.
Overall, I would rate the solution a seven out of ten.
Which deployment model are you using for this solution?
Kong API GW is a popular for managing APIs. It's known for being fast,flexible and easy to set up.
-->Flexibility and ease of use
-->Extensibility with plugins
Management overhead for multiple Gateways
Improved Visibility and Monitoring
Flexibility for Different Deployments
Comes with some ready plug-ins and provides good security and redundancy
What is our primary use case?
Our e-commerce customers use Kong Enterprise.
What is most valuable?
Customers cannot use the public cloud because of regulations. Kong Enterprise can be used in any environment, like the Red Hat and Openshift environments. Kong Enterprise comes with some ready plug-ins, which is very good for the customers. Kong Enterprise supports hierarchy and redundancy.
What needs improvement?
Kong Enterprise has decided not to support the web portal feature anymore, but I think that feature should stay in the on-premises solution.
For how long have I used the solution?
I have been using Kong Enterprise for four to five years.
What do I think about the stability of the solution?
I rate the solution ten out of ten for stability.
How are customer service and support?
The solution's technical support is good and responsive.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup of the solution is very straightforward.
What about the implementation team?
You can install Kong Enterprise in five minutes or half an hour. If the customer is ready for deployment with the Kubernetes or VMware environment, Kong Enterprise's installation is very easy.
What other advice do I have?
The solution's scalability is very nice. Kong Enterprise is a key product in the market with good stability and high availability. Our customers can easily integrate their existing CICD pipelines with Kong Enterprise.
We chose Kong Enterprise because it is a software-based company, and latency and redundancy are very important for our client. Most of the other vendors use the old-school appliance-based solution. Kong Enterprise is very keen to apply the existing CI/CD pipeline. I would recommend Kong Enterprise to other users because of its scalability, security, and redundancy.
Overall, I rate Kong Enterprise ten out of ten.
Which deployment model are you using for this solution?
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.