No more typing reviews! Try our Samantha, our new voice AI agent.

OpenESB 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

OpenESB
Ranking in Enterprise Service Bus (ESB)
14th
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
4
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in Enterprise Service Bus (ESB)
5th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
95
Ranking in other categories
Business-to-Business Middleware (6th), Managed File Transfer (MFT) (14th), API Management (17th), Cloud Data Integration (12th), Integration Platform as a Service (iPaaS) (11th)
 

Mindshare comparison

As of June 2026, in the Enterprise Service Bus (ESB) category, the mindshare of OpenESB is 2.9%, up from 1.5% compared to the previous year. The mindshare of webMethods.io is 7.7%, down from 11.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Mindshare Distribution
ProductMindshare (%)
webMethods.io7.7%
OpenESB2.9%
Other89.4%
Enterprise Service Bus (ESB)
 

Featured Reviews

PP
Integration Architect at Pymma consulting
Easily define choreography and orchestration with this process-oriented solution
We provide contracted services for our customers that include coordinating with providers and implementing the solution.  A current project includes using the solution to deploy 200 microservices.  The process-oriented solution allows you to define choreography and orchestration. This feature…
YM
Developer at a hospitality company with 1,001-5,000 employees
Offers strong integration capabilities and reliable features but needs pricing and scaling improvements
Many things are evolving with the AI buzz in the market. What I would like to see improved or enhanced in webMethods.io in the future is that since webMethods.io is already under IBM, I think IBM will introduce and integrate AI into it. Additionally, regarding what webMethods.io can improve is the license cost. Other cloud players are also providing the same kind of functionality, such as AWS and Azure. webMethods.io is being installed on-premises, but AWS is providing it directly in the cloud. When comparing the license cost and request per minute cost, webMethods.io needs to address that. There are many competitors in the market for this.

Quotes from Members

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

Pros

"OpenESB pushes the organization to clearly define service boundaries and interfaces. So it motives the business and the development teams to clearly define their business services and processes they want to implement. OpenESB supports fine and coarse-grain granularity for the services and supports top-down and bottom-up approaches for the services, processes definition, and composition."
"The process-oriented solution allows you to define choreography and orchestration."
"One of our clients is a signature company and developed on a classic Java enterprise application using OpenESB, and in one year they saved £20,000,000 on development and maintenance."
"Millions of people were connecting every month on the system and there were no issues."
"One of the most valuable features is being able to implement business processes while keeping track of the design from BPMN to a BPEL Implementation."
"The core is very stable."
"ESL Gaming used OpenESB for its scalability and processes 1 billion of messages daily with a large configuration deployed on a private cloud."
"Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine, and we've had a really good experience with webMethods Integration Server."
"CentraSite for governance and life cycle management 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."
"webMethods Integration Server is our primary integration tool across all the solutions that we have in our supply chain."
"Having a product like this is invaluable to any company in terms of the amount of time that IT gets to save in terms of integrating different products as well as having an open way to ensure that these applications are working."
"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."
"I like the stability of the webMethods Integration Server."
"It's a well-settled, mature platform; the stability is good and it can scale."
"How simple it is to create new solutions."
 

Cons

"The documentation needs to be better."
"Cloud deployment is weak and needs to be improved."
"Regarding its management, a web console being able to synchronize distributed instances would be great."
"The documentation of the product must be improved. It could be tricky to find the right documentation on a topic since the documentation is spread in many places. I advise the new joiner to contact the community to get entry points and additional documentation. Tutorial and Video must be present to take up the product."
"The Studio is a good tool based on NetBeans, but some of its features have to be improved, liked local schemas management."
"The documentation needs to be better — maybe they could add more accurate tutorials."
"Regarding the stateful session inbound to ESB (Integration Server), it seems that the stateful session sometimes doesn't die out when the transaction is finished, but waits until the timeout expires (although quite often it doesn't even die after the timeout expires, which eventually would flood the server)."
"This is an expensive product and we may replace it with something more reasonably priced."
"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."
"In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
"At least in SAG Webmethods 8 there was no Data Value Repository tool that would allow to map values/codes from source (in our case HR portal) and transform that into target ERP codes (SAP and PeopleSoft)."
"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."
"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."
 

Pricing and Cost Advice

"The cost for the prediction instrument is high because it is charged per instances based on prediction, but the rest of the solution is free."
"There are two versions. The first is the community version, which is free and contains the last part of the feature, but if you want to get the Enterprise version, you'll have to pay €60,000 which covers support and two instances on production."
"The Community Edition is a full product you can use in production, it does not have limitations like other alternatives."
"Initialy good pricing and good, if it comes to Enterprise license agreements."
"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."
"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."
"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."
"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."
"It is worth the cost."
"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."
"There is a license needed to use the webMethods Integration Server."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
900,838 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Manufacturing Company
14%
Financial Services Firm
12%
Computer Software Company
9%
Construction Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise65
 

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with webMethods Integration Server?
The alignment of on-premise and cloud versions needs improvement.
What needs improvement with webMethods Trading Networks?
webMethods.io does not currently have certain features, and we have to do coding as well. However, they have recently come up with a hybrid application where users will be able to use drag-and-drop...
What is your primary use case for webMethods Trading Networks?
We are primarily focused on IBM webMethods. I am part of the Center of Excellence team, where we involve ourselves in proposals and providing solutions to clients. webMethods.io is a middleware too...
 

Also Known As

No data available
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Information Not Available
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about OpenESB vs. webMethods.io and other solutions. Updated: June 2026.
900,838 professionals have used our research since 2012.