We performed a comparison between Apigee vs. WSO2 API Manager based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Apigee has the winning edge in this comparison. Apigee has better ratings when it comes to ease of deployment, features, and service and support.
"It has all the features necessary to work in anything from a basic scenario to advanced applications."
"It's a good return on my investment."
"Items around the mobilization of the API interface and the ability to automate validations for our APIs are the most valuable aspects."
"Tracing in Apigee is a very good feature."
"Apigee provides out-of-the-box policies, so it is ready to use with minimal configuration to those policies. You can govern your API and manage the life cycle of the API completely with the Apigee tool."
"Apigee is a very lightweight solution."
"The use case which I have installed serves the intended purpose."
"Its customer service is good."
"WSO2 API Manager has a user-friendly model."
"As far as I am aware this solution is the first API Publisher that allows you to create and publish API and to manage the API lifecycle."
"Yes WSO2 API Manager is scalable"
"WSO2 API Manager is a stable solution."
"The flexibility is definitely a highlight. We have flexible mapping capabilities, allowing us to provide common mappings or create custom ones as needed."
"The solution is open-source."
"The solution is open source and easy to configure."
"It's a good product."
"The initial setup is not straightforward, particularly for hybrid solutions."
"I would like them to add features, such as caching and mediation policies."
"Better functionality for validating inputs and outputs would be helpful."
"In terms of the functionalities of a typical API gateway, Apigee is actually doing its job, but when it involves integration with backend applications, which some gateways have, I don't believe it has this functionality. You have to do Java or do some other low-level coding before you are able to do the integration. Apigee has a lot of components, which means that management will be a bit difficult. It probably has ten different components, and all of these components leverage open-source utilities, such as NGINX. When those open-source vendors upgrade their utility, Apigee usually lags behind because they need to do a lot of tests and any required development in their own platform. They need to do rigorous testing to make sure that nothing breaks. Because of that, it takes them a while to upgrade whatever components have been upgraded by the open-source vendor that owns the utility. We've been chasing them for a particular upgrade for well over a year and a half, and they have not done that upgrade. It is creating a security risk for us as an enterprise, but that upgrade has not been done, even though the open-source vendor, the owner of the utility, has upgraded it a long time ago."
"It is an expensive solution."
"The caching capabilities are somewhat limited. This is more on the developer-oriented capabilities."
"We need better performance monitoring."
"What my clients don't like is that the on-premises solution is not being treated and maintained as well as the cloud solution."
"API Manager is not easy to scale because some of its components lack scalability. It's a difficult point. Especially because companies are so cloud-based these days, microservice scalability is a major thing."
"From what I have experienced from the versions I have tried, they could improve on the multi-tenant environments to allow some kind of SSO single sign-on between tenant."
"We found WSO2 API Manager to be a bit complex."
"Integration is an area that needs to be improved."
"The initial setup can be difficult."
"For fresh graduates and engineers, the setup process can be very difficult."
"I would like it to be a more convenient development platform with the ability to write orchestrations and so on. Our problem with this product is that in my country, we are the only enterprise that has been using this product. We're missing a lot of knowledge from colleagues to consult with, and we also aren't able to recruit people with relevant skills. It is a big problem. The small team that is maintaining this product is the only team that can actually relate to any technical issue. The support that we're getting from the company is not great. There is also a cultural gap there because they're from Sri Lanka, and it is not easy. They're putting in a lot of effort, but they are not meeting our expectations."
"I can say that user management is not really flexible. So, if I want to create 1,000 store users, I can't do it as a publisher. You have to register as a store user using the store URL."
Apigee is ranked 2nd in API Management with 82 reviews while WSO2 API Manager is ranked 8th in API Management with 33 reviews. Apigee is rated 8.2, while WSO2 API Manager is rated 8.0. The top reviewer of Apigee writes "Has a robust community and outstanding performance". On the other hand, the top reviewer of WSO2 API Manager writes "Reliable with good capabilities and good support". Apigee is most compared with Microsoft Azure API Management, IBM API Connect, Amazon API Gateway, Layer7 API Management and MuleSoft Anypoint API Manager, whereas WSO2 API Manager is most compared with Kong Gateway Enterprise, Amazon API Gateway, Microsoft Azure API Management, Apache APISIX and 3scale API Management. See our Apigee vs. WSO2 API Manager report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.