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

WSO2 Enterprise Integrator vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 3, 2025

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 Enterprise Service Bus (ESB)
3rd
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Business-to-Business Middleware (3rd), Managed File Transfer (MFT) (10th), API Management (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
WSO2 Enterprise Integrator
Ranking in Enterprise Service Bus (ESB)
7th
Average Rating
7.6
Reviews Sentiment
7.0
Number of Reviews
19
Ranking in other categories
Data Integration (25th)
 

Mindshare comparison

As of April 2025, in the Enterprise Service Bus (ESB) category, the mindshare of webMethods.io is 10.7%, up from 9.5% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 5.0%, down from 5.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB)
 

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.
Ritesh_Shah - PeerSpot reviewer
Decreases the development timeframe and costs
The main issue with the product is pricing. It uses core-based pricing for WSO2 Enterprise Integrator and API Manager. It would be best if you had APIM by default. It provides many connectors for easy integration with third-party systems. Often, customers decide to develop using open-source tools like Spring Boot if there aren't many connectors required to avoid increasing costs. They'll develop this way and then deploy using APIM, the bare minimum needed. It is mainly required for very complicated setups with many connectors. In the implementations I've seen, people often used open-source tools because there weren't many third-party systems involved—just their organization's own systems. From WSO2 Enterprise Integrator, I expect them to bring up more and more connectors in the future. That's the main expectation. Having more connectors in various areas will help us when discussing new requirements. I don't have any specific use case right now, so I can't name a particular connector. But, as new technologies emerge, the relevant connectors should be there for those. WSO2 Enterprise Integrator mainly helps with the integration part, which can be simplified only if you have relevant connectors for whatever you're doing.

Quotes from Members

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

Pros

"It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things."
"Operationally, I consider the solution to be quite good."
"The product is very stable."
"We have a reusable code that we can replicate for any new interfaces."
"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."
"Ease of implementation and flexibility to hold the business logic are the most valuable features."
"One valuable feature is that it is event-driven, so when new data is available on the source it can be quickly processed and displayed. Integration is definitely another useful feature, and B2B is one area where webMethods has its own unique thing going, whereby we can do monitoring of transactions, monitoring of client onboarding, and so on."
"It is a very stable product."
"The solution basically conforms to our standards."
"The installation process is easy."
"The drag-and-drop features for connectors are very valuable."
"The productivity is the most valuable feature. It is very easy to write remediations."
"I like the user-friendly system and development of the service-oriented architecture."
"It was mostly easy to set up the product."
"WSO2's analytics capability is good, considering the ELC support they provide."
"In my opinion, the most valuable aspect of this solution is its extensive range of adaptors and connectors. This feature holds significant importance and provides great value to users."
 

Cons

"​Large file handling is pretty hard comparatively to other middleware tools."
"The logging capability has room for improvement. That way, we could keep a history of all the transactions. It would be helpful to be able to get to that without having to build a standalone solution to do so."
"The market webMethods Integration Server falls under is a very crowded market, so for the product to stand out, Software AG would need to get traction in the open source community by releasing a new version or a base version and open source it, so people can create new custom components and add it to the portfolio."
"It is quite expensive."
"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."
"In terms of scale, I would give it a four out of 10."
"It is an expensive solution and not very suitable for smaller businesses."
"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."
"You cannot include the validation of XPath."
"They should introduce better pricing for small companies."
"WSO2 libraries are not mature enough. For example, if you want to integrate with Kafka using its Kafka library, it often has many bugs."
"They should release upgrades more frequently."
"One of the reasons that we are looking for a replacement is their way of defining integration. The language of the XML structures that I use to describe the integrations are not that standard, and it's not easy to find people who are familiar with this approach."
"I would like to see better documentation for the open-source version."
"The micro integrator should be improved. There is room for enhancement considering alternative integration components."
"The setup can be difficult for those not familiar with the solution."
 

Pricing and Cost Advice

"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."
"There is a license needed to use the webMethods Integration Server."
"The pricing is a yearly license."
"The price is high and I give it a five out of ten."
"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."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."
"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."
"The open-source, unsupported version is available free of charge."
"The pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."
"The cost is better than IBM Cloud Pak."
"It is a low-cost solution."
"I rate the product price a six on a scale of one to ten, where one is low price and ten is high price."
"The solution costs about 20,000 or 30,000 euros per year, per instance."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
849,190 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
12%
Retailer
7%
Computer Software Company
25%
Financial Services Firm
16%
Manufacturing Company
6%
Insurance Company
5%
 

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 Enterprise Integrator?
WSO2's analytics capability is good, considering the ELC support they provide.
What is your experience regarding pricing and costs for WSO2 Enterprise Integrator?
The product has reasonable and competitive pricing for enterprise customers. It is expensive for small businesses especially. They are using the open-source solution, and they find it expensive sin...
What needs improvement with WSO2 Enterprise Integrator?
The main issue with the product is pricing. It uses core-based pricing for WSO2 Enterprise Integrator and API Manager. It would be best if you had APIM by default. It provides many connectors for e...
 

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
West
Find out what your peers are saying about WSO2 Enterprise Integrator vs. webMethods.io and other solutions. Updated: April 2025.
849,190 professionals have used our research since 2012.