We performed a comparison between Apigee and webMethods API Gateway based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."A simple platform that's easier to work with than IBM API Connect. Support for it is really good and gives it advantage over other providers."
"API/proxy lifecycle workflow for API providers is quite good and one of Apigee's strongest features."
"The pricing is okay."
"Apigee makes proxy management very simple."
"Easy interface to monetize and deliver APIs with very easy integration for third-party development environments/delivery."
"The stability of the solution is good. There aren't issues surrounding bugs or glitches. We don't find that it crashes or freezes. It's pretty reliable."
"The ability to convert from language to language using a single tool."
"The capabilities are very powerful."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"It's a good tool, and it has a stable messaging broker."
"This solution has given us a competitive advantage because we have better automation and insight."
"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."
"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."
"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."
"The cloud version of the solution is very easy to set up."
"I like the solution's policies, transformation, mediation, and routing features."
"Proxy versioning seems a bit confusing/buried in the publishing experience, especially for the URI-based versioning approach."
"The cost of the solution is quite high."
"Access restrictions can be improved."
"I see some lagging in regards to integration capacity"
"Compared to its competitors, such as Axway AMPLIFY API Management and Layer7 API Management, Apigee could benefit from having more policies to cater to various use cases. This would reduce the need for writing custom JavaScripts. If more features come straight out of the box, we can leverage them instead of writing custom code to achieve the same functionality."
"The pricing of the solution could be improved upon. We'd like it if it was less costly."
"What my clients don't like is that the on-premises solution is not being treated and maintained as well as the cloud solution."
"Technical support model for OPDK should be more exposed and mature in terms of providing support during installation, run, and debug of Apigee in production on OPDK mode."
"The price has room for improvement."
"They should develop clear visibility for the onboarding."
"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"It is an expensive solution and not very suitable for smaller businesses."
"Understanding the overall architecture is difficult."
"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."
"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."
Apigee is ranked 2nd in API Management with 82 reviews while webMethods API Gateway is ranked 11th in API Management with 10 reviews. Apigee is rated 8.2, while webMethods API Gateway is rated 8.2. The top reviewer of Apigee writes "Has a robust community and outstanding performance". On the other hand, the top reviewer of webMethods API Gateway writes "We developed several services in the cloud using a sandbox environment for our last hackathon". Apigee is most compared with Microsoft Azure API Management, IBM API Connect, Amazon API Gateway, WSO2 API Manager and Layer7 API Management, whereas webMethods API Gateway is most compared with webMethods.io Integration, Kong Gateway Enterprise, webMethods Microgateway, 3scale API Management and CentraSite. See our Apigee vs. webMethods API Gateway 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.