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

"The product is very stable."
"High throughput and excellent scalability."
"It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine)."
"Most of the work in our organization can be more easily done using the tool."
"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."
"How simple it is to create new solutions."
"It's easy to construct new interfaces like apps and client portals."
"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 installation process is easy."
"Currently, I find the configuration part quite valuable, where you can easily configure things."
"The connectors have been the most impactful features for handling integrations. I can use these connectors when I need specific connectivity with a third party, like a core banking system in BFSI. I don't need to do all the development. I take the specific connector, put in the IP address and password, and it takes care of everything."
"The solution has two main parts: integration and transformation. It's very user-friendly and easy to understand for everyone."
"The solution's technical support is very knowledgeable."
"WSO2's analytics capability is good, considering the ELC support they provide."
"The customer service executives are very responsive."
"It's a consolidated product. It works and it does its job pretty well."
 

Cons

"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."
"We'd like for them to open up to a more cloud-based solution that could offer more flexibility and maybe a better rules engine or more integration with rules engines."
"As webMethods Integration Server is expensive, that's its area for improvement."
"I'd like to see the admin portal for managing the integration server go up a level, to have more capabilities and to be given a more modern web interface."
"The solution should include REST API calls."
"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."
"The learning curve is a little steep at first."
"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."
"There are a lot of security settings that when you apply you have to re-apply again every time you modify a setting. It is something that really needs to be enhanced."
"I would like to see them bring back a feature, from earlier versions, that was very useful in debugging and finding issues."
"The integration capabilities need to be improved."
"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."
"You cannot include the validation of XPath."
"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."
"In my opinion, the administration model and interface, of Carbon, are lacking in terms of its features and user experience."
"WSO2 libraries are not mature enough. For example, if you want to integrate with Kafka using its Kafka library, it often has many bugs."
 

Pricing and Cost Advice

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."
"The solution’s pricing is too high."
"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."
"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."
"Initialy good pricing and good, if it comes to Enterprise license agreements."
"I am not involved in the licensing side of things."
"The open-source, unsupported version is available free of charge."
"It is a low-cost solution."
"The cost is better than IBM Cloud Pak."
"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."
"The pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
845,040 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
24%
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: March 2025.
845,040 professionals have used our research since 2012.