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

Fiorano ESB 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

Fiorano ESB
Ranking in Enterprise Service Bus (ESB)
12th
Average Rating
9.0
Reviews Sentiment
8.1
Number of Reviews
5
Ranking in other categories
No ranking in other categories
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 (5th), Managed File Transfer (MFT) (11th), API Management (11th), Cloud Data Integration (10th), Integration Platform as a Service (iPaaS) (9th)
 

Mindshare comparison

As of February 2026, in the Enterprise Service Bus (ESB) category, the mindshare of Fiorano ESB is 3.0%, up from 1.4% compared to the previous year. The mindshare of webMethods.io is 8.8%, down from 10.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Market Share Distribution
ProductMarket Share (%)
webMethods.io8.8%
Fiorano ESB3.0%
Other88.2%
Enterprise Service Bus (ESB)
 

Featured Reviews

reviewer987933 - PeerSpot reviewer
Sr.Manager - Programming and software development at a financial services firm with 1,001-5,000 employees
Scalable and easy to maintain
One of the most valuable features is the scalability. Whenever it's required, we can add more servers and scale. We can actually use specific servers for specific stuff. Unlike in other solutions, now we can implement one server purely dedicated to core-banking-related API. This is very important when it comes to the PCI DSS certification.
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

"One of the most valuable features is the scalability. Whenever it's required, we can add more servers and scale. We can actually use specific servers for specific stuff. Unlike in other solutions, now we can implement one server purely dedicated to core-banking-related API. This is very important when it comes to the PCI DSS certification."
"The ability to compliment out-of-the-box integration components with small custom code."
"The platform's most valuable feature is data transformation."
"webMethods Trading Networks is a stable solution."
"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."
"High throughput and excellent scalability."
"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."
"EDI is robust and integration with SAP is good."
"We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting."
"We have a reusable code that we can replicate for any new interfaces."
"It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine)."
 

Cons

"Fiorano ESB could be improved by becoming more user-friendly. Most of the pages and generated reports on API usage are already there, but they could be more user-friendly. There could be more selections added to generate reports. Overall, though, Fiorano suits all our needs and has good functionality."
"Error logging is not very user-friendly. It requires the error logging to be configured in many different places."
"Fiorano ESB's logging feature and data availability need improvement."
"The market webMethods Integration Server falls under is a very crowded market, so for the product to stand out, Software AG would need to get traction in the open source community by releasing a new version or a base version and open source it, so people can create new custom components and add it to the portfolio."
"The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."
"As webMethods Integration Server is expensive, that's its area for improvement."
"I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance."
"​Large file handling is pretty hard comparatively to other middleware tools."
"It could be more user-friendly."
"Some of the things that we use cannot be done in this solution. For these things, we have to either use a Java service or a util service. There is no predefined or existing service that we can use. So, we have to work on the util service and write on top of it. Its price can also be better. It is pretty costly because they charge us for each transmission."
"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."
 

Pricing and Cost Advice

"I rate the product's pricing a five out of ten."
"The pricing is a yearly license."
"It is worth the cost."
"The price is a little bit high, especially regarding their support."
"Most of my clients would like the price of the solution to be reduced."
"webMethods Trading Networks is a bit costly compared to others solutions."
"I would like to see better pricing for the license."
"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 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."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
881,707 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Manufacturing Company
13%
Financial Services Firm
11%
Computer Software Company
10%
Energy/Utilities Company
7%
 

Company Size

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

Questions from the Community

Ask a question
Earn 20 points
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.
 

Also Known As

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

Overview

 

Sample Customers

Polaris Transport, Harris Exelis, Aboitiz Power, Dyckerhoff AG, Gamma-Dynacare, DHL, Bajaj Finserv, Ecole hételire de Lausanne, Northern California Power Agency, Federal Bank, Commercial Bank of Africa, EasyPay, SSP, General American Corporation, Forex, Beijing Shubei Software Technology, City of Canton, Kent County Council, SJS District, County of Tulare, US Coast Guard, ZUNYI, Fraikin, Nilkamal, Posco, Toyota, UB Group
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Fiorano ESB vs. webMethods.io and other solutions. Updated: February 2026.
881,707 professionals have used our research since 2012.