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) (9th), API Management (9th), Cloud Data Integration (6th), 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 (31st)
 

Mindshare comparison

As of June 2025, in the Enterprise Service Bus (ESB) category, the mindshare of webMethods.io is 11.0%, up from 9.7% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 5.2%, 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

"I like the stability of the webMethods Integration Server."
"It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console."
"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."
"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."
"The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation."
"The product is very stable."
"The product supports various types of digital documents, including XMLs and EDI."
"webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization."
"The solution's customer service is good."
"It's a consolidated product. It works and it does its job pretty well."
"The customer service executives are very responsive."
"The learning curve for this solution is very good."
"WSO2's analytics capability is good, considering the ELC support they provide."
"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."
"Currently, I find the configuration part quite valuable, where you can easily configure things."
"The solution's technical support is very knowledgeable."
 

Cons

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."
"The price has room for improvement."
"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."
"webMethods Integration Server needs to add more adapters."
"They should develop clear visibility for the onboarding."
"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."
"In terms of scale, I would give it a four out of 10."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
"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."
"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."
"In my opinion, the administration model and interface, of Carbon, are lacking in terms of its features and user experience."
"They should introduce better pricing for small companies."
"They should release upgrades more frequently."
"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."
"The micro integrator should be improved. There is room for enhancement considering alternative integration components."
"You cannot include the validation of XPath."
 

Pricing and Cost Advice

"webMethods.io Integration's pricing is high and has yearly subscription costs."
"It is a cost-effective solution."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
"The solution's development license is free for three to six months. We have to pay for other things."
"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 Trading Networks is a bit costly compared to others solutions."
"Its cost depends on the use cases."
"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."
"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."
"It is a low-cost solution."
"The solution costs about 20,000 or 30,000 euros per year, per instance."
"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."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Financial Services Firm
13%
Manufacturing Company
13%
Retailer
7%
Computer Software Company
23%
Financial Services Firm
17%
Manufacturing Company
6%
Government
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 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: June 2025.
856,873 professionals have used our research since 2012.