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
93
Ranking in other categories
Business-to-Business Middleware (3rd), Managed File Transfer (MFT) (9th), API Management (9th), 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
6.8
Number of Reviews
20
Ranking in other categories
Data Integration (32nd)
 

Mindshare comparison

As of August 2025, in the Enterprise Service Bus (ESB) category, the mindshare of webMethods.io is 11.1%, up from 9.8% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 5.4%, up from 5.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB)
 

Featured Reviews

MohanPrasad - PeerSpot reviewer
Smooth integration and enhanced deployment with high licensing cost
webMethods.io was used to integrate APIs through the webMethods.io platform, trigger database events, and connect backend APIs through a Java backend. It was used extensively for integration purposes in my organization Integration became smoother, troubleshooting was easier, and deployment and…
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

"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."
"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."
"The most valuable feature of the webMethods Integration Server is its reliability. It has a lot of great documentation from the service providers. Additionally, it is easy to use."
"The tool supports gRPC."
"There were no complexities involved in the setup phase...The product is able to meet my company's API protection needs."
"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."
"There's hardware, software and application integration, providing hosting flexibility."
"webMethods platform is used to build an EAI platform, enabling communication between many internal systems and third-party operators."
"The stability is excellent."
"It's a consolidated product. It works and it does its job pretty well."
"The solution basically conforms to our standards."
"It's a very complete product. It allows us to network security and add more layers of security to the system."
"I like the user-friendly system and development of the service-oriented architecture."
"The customer service executives are very responsive."
"The learning curve for this solution is very good."
"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."
 

Cons

"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."
"Rules engine processes and BPM processes should be improved."
"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."
"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."
"The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that."
"webMethods.io Integration's installation is complex. It should also improve integration and connectors."
"Some things could be improved, especially how ActiveTransfer handles third-party file transfers. It would be nice to have a native file-watching mechanism for when you're scheduling jobs with a third-party scheduler. Currently, we are using an outside file watcher solution to check the files before the file transfer. It checks the location to see if the file is there. If the file is there, it will prepare it for transfer. If the file isn't available, it will send an email it can create a ticket send it now. We recommended adding this file watcher mechanism."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"The administration side is complex and could use significant improvements to enhance the solution's functionality."
"The integration capabilities need to be improved."
"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 introduce better pricing for small companies."
"In my opinion, the administration model and interface, of Carbon, are lacking in terms of its features and user experience."
"I would like to see them bring back a feature, from earlier versions, that was very useful in debugging and finding issues."
"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."
"You cannot include the validation of XPath."
 

Pricing and Cost Advice

"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"The pricing is a yearly license."
"The product is very expensive."
"Some of the licensing is "component-ized," which is confusing to new users/customers."
"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."
"The product is expensive."
"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."
"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."
"It is a low-cost solution."
"The cost is better than IBM Cloud Pak."
"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 solution costs about 20,000 or 30,000 euros per year, per instance."
"The open-source, unsupported version is available free of charge."
"I rate the product price a six on a scale of one to ten, where one is low price and ten is high price."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
864,155 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
13%
Computer Software Company
12%
Financial Services Firm
12%
Retailer
6%
Financial Services Firm
17%
Computer Software Company
16%
Manufacturing Company
7%
Government
7%
 

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: July 2025.
864,155 professionals have used our research since 2012.