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 (2nd), Managed File Transfer (MFT) (9th), API Management (11th), Cloud Data Integration (8th), Integration Platform as a Service (iPaaS) (7th)
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 (29th)
 

Mindshare comparison

As of September 2025, in the Enterprise Service Bus (ESB) category, the mindshare of webMethods.io is 11.1%, up from 10.0% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 5.6%, up from 5.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Market Share Distribution
ProductMarket Share (%)
webMethods.io11.1%
WSO2 Enterprise Integrator5.6%
Other83.3%
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

"The tool supports gRPC."
"A product with good API and EDI components."
"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."
"The comprehensiveness and depth of Integration Servers' connectors to packaged apps and custom apps is unlimited. They have a connector for everything. If they don't, you can build it yourself. Or oftentimes, if there is value for other customers as well, you can talk with webMethods about creating a new adapter for you."
"We needed a tool that was able to orchestrate and help us configure our APIs so that we could maintain and see the heartbeat, traffic, trends, etc."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
"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."
"The Software AG Designer has been great. It's very intuitive."
"I like the user-friendly system and development of the service-oriented architecture."
"The solution's technical support is very knowledgeable."
"The customer service executives are very responsive."
"The solution has two main parts: integration and transformation. It's very user-friendly and easy to understand for everyone."
"The solution's customer service is good."
"WSO2's analytics capability is good, considering the ELC support they provide."
"Currently, I find the configuration part quite valuable, where you can easily configure things."
"The productivity is the most valuable feature. It is very easy to write remediations."
 

Cons

"The orchestration is not as good as it should be."
"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."
"Need to see more API portal features like monetizing APIs and private cloud readiness."
"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."
"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."
"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."
"The interface needs some work. It is not very user-friendly."
"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."
"WSO2 libraries are not mature enough. For example, if you want to integrate with Kafka using its Kafka library, it often has many bugs."
"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."
"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 administration side is complex and could use significant improvements to enhance the solution's functionality."
"I would like to see them bring back a feature, from earlier versions, that was very useful in debugging and finding issues."
"The server is very specific and it is very difficult to get experience with it."
"You cannot include the validation of XPath."
 

Pricing and Cost Advice

"The price is high and I give it a five out of ten."
"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."
"The product is expensive."
"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."
"The solution’s pricing is too high."
"Some who consider this solution often avoid it due to its high price."
"I would like to see better pricing for the license."
"Initialy good pricing and good, if it comes to Enterprise license agreements."
"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."
"The solution costs about 20,000 or 30,000 euros per year, per instance."
"It is a low-cost solution."
"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."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
867,370 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
14%
Computer Software Company
12%
Financial Services Firm
11%
Retailer
6%
Financial Services Firm
16%
Computer Software Company
16%
Government
6%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise63
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise2
Large Enterprise11
 

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?
Something that could be improved in WSO2 Enterprise Integrator is that the problem is not a lack of capability or functionalities. The problem is that it is a very complex environment. To put your ...
 

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: September 2025.
867,370 professionals have used our research since 2012.