Try our new research platform with insights from 80,000+ expert users

IBM WebSphere Message Broker vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 1, 2026

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

IBM WebSphere Message Broker
Ranking in Enterprise Service Bus (ESB)
9th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
13
Ranking in other categories
Application Infrastructure (17th)
webMethods.io
Ranking in Enterprise Service Bus (ESB)
3rd
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
94
Ranking in other categories
Business-to-Business Middleware (3rd), Managed File Transfer (MFT) (10th), API Management (11th), Cloud Data Integration (9th), Integration Platform as a Service (iPaaS) (8th)
 

Mindshare comparison

As of March 2026, in the Enterprise Service Bus (ESB) category, the mindshare of IBM WebSphere Message Broker is 4.8%, up from 4.0% compared to the previous year. The mindshare of webMethods.io is 8.6%, down from 10.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Mindshare Distribution
ProductMindshare (%)
webMethods.io8.6%
IBM WebSphere Message Broker4.8%
Other86.6%
Enterprise Service Bus (ESB)
 

Featured Reviews

BrajendraKumar - PeerSpot reviewer
Technical Architect at HCL Technologies
Offers large-sized business information processing with a time-saving setup and impressive stability
I primarily use two previews of the product for Dev and two for QA as part of the production process. Whatever tools our company is using, the cost of a license in IBM WebSphere Message Broker is about 80% of all these software or tools. The message routing capabilities satisfy workflow efficiency. The product supports message formats of XML, JSON, and SSID, which are around 24 KB to 50 KB in size. The solution supports communication protocols like STTP and TCP. Features like DataGraph need to be introduced in IBM WebSphere Message Broker. Some of the clients of our organization are using an outdated version of IBM WebSphere Message Broker for which the vendor doesn't provide direct support anymore. For the aforementioned version, our company professionals can solve the queries on their own without seeking support from IBM. During the installation of a prior version of IBM WebSphere Message Broker, sometimes I have to configure the failovers through the cluster, where issues arise, and I often seek help from the support team. The solution is being used by some medicine companies in our organization that receive sales orders from the EDR or JDE. I would not recommend the product to others as its becoming obsolete and they can rather choose a middleware solution from Amazon or Azure. But I would overall rate the product a nine out of ten.
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

"The most valuable feature of IBM WebSphere Message Broker is the ability to facilitate communication with legacy systems, offering a multitude of great capabilities. For example, if there is a mainframe system in place with a web service serving as the front end. In that case, the solution enables efficient protocol transformations to convert all request payloads into a format that the legacy systems can accept, rendering the integration and transformation processes seamless and highly effective."
"The solution has good integration."
"Integration and mapping are easy, which is a major advantage."
"We only use the basic features, but the most valuable one for us is the Publish-subscribe pattern."
"It has many interfaces and you can connect to any backend source that has another format, and convert it to the desired format."
"Straightforward development and deployment."
"Performance-wise, this solution is really good."
"The documentation, performance, stability and scalability of the tool are valuable."
"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."
"It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."
"Time effective by cutting down development time and resource efficient to developer burden, enhance agility and integration between end-to-end applications, platform"
"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."
"It is a bundled product stack for A2A and B2B usage, and it is one of the best products which I have used during my integration career."
"There's hardware, software and application integration, providing hosting flexibility."
"The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging."
"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."
 

Cons

"As our business requirements evolve, we require more dynamic capabilities to adapt and scale our services accordingly."
"The user interface is designed mainly for experts, much in the way a BPM or another integration tool is."
"The product's features are not being upgraded or enhanced by the vendor"
"Stability and pricing are areas with shortcomings that need improvement."
"Technical support is very slow and needs to be improved."
"The solution can add container engines such as docker."
"Technical support is good but they could have a better response time."
"I know that Message Broker was a very tightly copied product with another IBM product, that is, IBM MQ. I would like to have a little bit more decoupling from the IBM MQ because it should not be a prerequisite for IBM WebSphere Message Broker usage."
"Prices should be reduced, ideally by up to 30% for long-term customers like us."
"In 2008, the technical support's response time was much longer than expected."
"The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. For how long"
"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."
"The high price of the product is an area of concern where improvements are required."
"It is an expensive solution and not very suitable for smaller businesses."
"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
 

Pricing and Cost Advice

"The price is very high and it's the main reason that we are searching for alternatives."
"The solution is expensive."
"The licensing cost of IBM WebSphere Message Broker needs to be reduced"
"The solution is expensive."
"This product is more expensive than competing products."
"IBM products are generally more stable and have more features, but also come at a greater cost."
"I feel with IBM, when you want certain functions or features, you have to continuously purchase add-ons. There are always additional fees."
"IBM software can be costly, but having a contract has helped manage and potentially lower costs over time."
"The vendor is flexible with respect to pricing."
"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."
"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."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
"It's a good deal for the money that we pay."
"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
"webMethods.io Integration's pricing is high and has yearly subscription costs."
"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."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
10%
Insurance Company
8%
Transportation Company
7%
Manufacturing Company
13%
Financial Services Firm
11%
Computer Software Company
9%
Energy/Utilities Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Large Enterprise10
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise64
 

Questions from the Community

What is your experience regarding pricing and costs for IBM WebSphere Message Broker?
IBM software can be costly, but having a contract has helped manage and potentially lower costs over time.
What needs improvement with IBM WebSphere Message Broker?
There could be greater flexibility and agility in service creation for the product. As our business requirements evolve, we require more dynamic capabilities to adapt and scale our services accordi...
What is your primary use case for IBM WebSphere Message Broker?
We use the product for exposing services at the application level, integrating with various architectures like WebSphere, and handling static service creation.
What needs improvement with webMethods Integration Server?
The alignment of on-premise and cloud versions needs improvement.
What needs improvement with webMethods Trading Networks?
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 w...
What is your primary use case for webMethods Trading Networks?
I use webMethods.io primarily for the integration of APIs. Could you please describe a few use cases for it?
 

Also Known As

WebSphere Message Broker
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

WestJet, Blue Cross and Blue Shield of North Carolina, Sharp Corporation, Michelin Tire
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about IBM WebSphere Message Broker vs. webMethods.io and other solutions. Updated: March 2026.
884,873 professionals have used our research since 2012.