Try our new research platform with insights from 80,000+ expert users

WSO2 API Manager vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

webMethods.io
Ranking in API Management
10th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Business-to-Business Middleware (3rd), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
WSO2 API Manager
Ranking in API Management
9th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
40
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the API Management category, the mindshare of webMethods.io is 2.1%, up from 1.9% compared to the previous year. The mindshare of WSO2 API Manager is 4.8%, up from 4.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.
VishalSingh14 - PeerSpot reviewer
Easy to deploy APIs and easy to manage CORS configuration
I have used WSO2 Store and WSO2 API Manager at the architecture level. I worked on two versions, namely WSO2 API Manager 2.6.0 and 5.7.0. I have also worked with WSO2 Identity Server versions 5.7 and 5.11. There are certain things that Apigee handles better than WSO2 API Manager. The user interface of WSO2 API Manager is much easier than that of Apigee. The scope of flexibility was much greater in Apigee. In WSO2 API Manager, we had little flexibility and were restricted to a specific software or tool. On the other hand, we had the scope of customization in Apigee.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"ActiveTransfer lets us maintain the file in the staging area before we transfer it. After that, we can remove the file to make sure that the reconciliation process is done. Sometimes we will zip and unzip the files, but if we have a GKB file, we often ignore it."
"The most valuable feature of webMethods Integration Server is all the capabilities it provides. We leverage most of the features, that they have offered to us. Our vendor has made some additional features on top of the webMethods Integration Server and we use all the features together."
"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."
"Currently, we're using this solution for the integration server which helps us to integrate with the mainframe."
"Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine. We've had a really good experience with webMethods Integration Server."
"I like the tool's scalability."
"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."
"I like the solution's policies, transformation, mediation, and routing features."
"Most of the time, we need to install a plug-in without having any lapse in services or restarting the application. The WSO2 platform can do all deployments without any downtime."
"Based on the information I have, the solution's most valuable feature is its capability of implementing custom solutions."
"WSO2 API Manager has a user-friendly model."
"WSO2 is very stable."
"A complete integration suite and a good platform."
"One of the great things about WSO2 API Manager is that it is so easy to adopt. And because it's an open source solution, we're able to extend the implementation any time to suit our company needs better."
"WSO2 API Manager provides strong internal API security, including token-based authentication and HTTPS support for various formats like REST. However, the newer API security features that are emerging are not available yet. They might be in development, but for now, internal API security is well-covered."
"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."
 

Cons

"wM SAP Adapter User Guide - Example, like Message Broker setup was unclear, leading to issues during Testing and we had refer the internet forums to understand that there is a Message Broker Cleanup utility and that needs to be setup as well."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"The certifications and learning resources are not exposed openly enough. For instance, they have a trial version which comes with only a few basic features, and I think that community-wise they need to offer more free or open spaces where developers can feel encouraged to experiment."
"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."
"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."
"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."
"The price has room for improvement."
"Understanding the overall architecture is difficult."
"The price and the complexities attached to the solution are two areas of concern where improvements are required."
"The professional support and licensing aspects of WSO have been a challenge."
"Basically, mTLS is a certificate-based communication protocol that WSO2 API Manager doesn't support."
"We found WSO2 API Manager to be a bit complex."
"The initial setup can be difficult."
"The user interface could be a bit better."
"WSO2 API Manager could improve by adding external API security features, which is one area where there is room for enhancement. Internally, API security is strong, and all other necessary features are already available. It has a solid marketplace, supports both Docker and standalone setups, and offers great enterprise integration. The developer portal has greatly improved the user experience, making it simple and user-friendly wherever we’ve implemented it. Overall, it’s not as complicated as other API gateways."
"The stability is pretty good, but it could be improved."
 

Pricing and Cost Advice

"It's a good deal for the money that we pay."
"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."
"The solution's development license is free for three to six months. We have to pay for other things."
"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."
"It is worth the cost."
"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
"The vendor is flexible with respect to pricing."
"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."
"As far as I'm aware, the costs are not minimal but satisfactory."
"We use the open-source version of WSO2 API Manager, there is no cost."
"WSO2 API Manager is an open-source solution."
"The solution costs less than 20,000 euros a year. I'm not sure of the exact number."
"It is costly, around ten thousand per year, per instance"
"The challenge is the increasing pricing, which has led some customers to consider alternatives, like using Spring Boot solutions instead. The rising costs, especially as cores and usage increase, have been a concern, prompting some to migrate to other products."
"It's not expensive, but it could be cheaper."
"We have not opted for the paid version of WSO2 but we have implemented the free and open source WSO2 software to a great extent and it is working as per our expectation."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
842,767 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
13%
Retailer
7%
Computer Software Company
18%
Financial Services Firm
18%
Government
7%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
What do you like most about WSO2 API Manager?
It is possible to scale up and scale down with the solution...I can say that I have not seen any issues related to scalability.
What needs improvement with WSO2 API Manager?
One area for improvement is monitoring. Dashboards for application monitoring of the APIs would be beneficial, allowing us to check for faulty APIs.
What is your primary use case for WSO2 API Manager?
We use WSO2 API Manager for our microservices and our APIs, both internally and externally.
 

Also Known As

Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
No data available
 

Overview

 

Sample Customers

Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
1. eBay 2. StubHub 3. Cisco 4. Verizon 5. T-Mobile 6. Vodafone 7. Orange 8. BT Group 9. Telstra 10. Deutsche Telekom 11. Swisscom 12. AT&T 13. Sprint 14. Telefonica 15. O2 16. British Airways 17. Lufthansa 18. Emirates 19. Qatar Airways 20. Etihad Airways 21. Air France 22. KLM 23. American Express 24. Visa 25. Mastercard 26. PayPal 27. Western Union 28. Citibank 29. HSBC 30. Barclays 31. Santander 32. Goldman Sachs
Find out what your peers are saying about WSO2 API Manager vs. webMethods.io and other solutions. Updated: March 2025.
842,767 professionals have used our research since 2012.