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

Workato vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 17, 2024

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 Integration Platform as a Service (iPaaS)
5th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
91
Ranking in other categories
Business-to-Business Middleware (4th), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), API Management (9th), Cloud Data Integration (8th)
Workato
Ranking in Integration Platform as a Service (iPaaS)
9th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
9
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Integration Platform as a Service (iPaaS) category, the mindshare of webMethods.io is 9.7%, up from 8.5% compared to the previous year. The mindshare of Workato is 3.8%, down from 4.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Integration Platform as a Service (iPaaS)
 

Featured Reviews

Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
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. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.
Rohit Sircar - PeerSpot reviewer
Great automation and strong workflows useful for integration
The initial setup is quite straightforward. When connecting Workato with your on-premises system, you have to install the Workato agent on your network. It was not complex but a long process to configure and settle. Workato has not gone live for us yet, so only the developers are currently using it. But in terms of users, we will have close to 250 and maybe 30 additional direct users. We are seeing a lot of different use cases where we can add new recipes because we started small, and there are many different areas where we can implement Workato for automation.

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 webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."
"The developer portal is a valuable feature."
"It integrates well with various servers."
"It's a good tool, and it has a stable messaging broker."
"We have found the pricing of the solution to be fair."
"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."
"webMethods API Portal is overall very valuable. It is now a comprehensive API catalogue that serves various purposes, including API assessment and evaluation."
"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."
"Their automation and workflows are very strong, and you can build the workflows very easily and quickly."
"It is very easy to use. It takes complex workloads away, and it provides very smooth integration. It has got a lot of out-of-the-box connectors. It has got a lot of out-of-the-box APIs, which makes it really easy to integrate with applications for different use cases, whether it is in finance, HR, or customer operations. It is by far our favorite integration product."
"Stability-wise, I rate the solution a ten out of ten."
"It is easier to use than other technical open-source technologies."
"Workato is low code, intuitive, and easy to use."
"The most valuable features are easy integration, quick tab to develop, quick tab to market, and interactive integration platform."
"It's easy to understand, makes flows and is efficient."
 

Cons

"As webMethods Integration Server is expensive, that's its area for improvement."
"webMethods.io Integration's installation is complex. It should also improve integration and connectors."
"Understanding the overall architecture is difficult."
"The licensing cost is high compared to other options."
"wM SAP Adapter User Guide - Example, like Message Broker setup was unclear, leading to issues during Testing and we had refer the internet forums to understand that there is a Message Broker Cleanup utility and that needs to be setup as well."
"The initial setup of the webMethods Integration Server is not easy but it gets easier once you know it. It is tiresome but not difficult."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
"When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods."
"It is tedious to make a tailor-fit function."
"From the deployment point of view, our customers encounter platform downtime where it does not serve the actual request on the systems."
"The only minor drawback would be if there was a UI at the front of it, for apps and for a portal as well, it would make it really easy. It would be really useful if there were more apps capabilities."
"Workato's Extract, transform, and load (ETL) and extract, load, and transform (ELT) are not very strong and could be improved for very complex transformations."
"A limitation is that their cloud presence is only in North America and Europe."
"The management dashboard in the solution is an area with shortcomings that needs improvement."
"I would like to see the dashboarding and reporting processes improved."
 

Pricing and Cost Advice

"The pricing is a yearly license."
"The vendor is flexible with respect to pricing."
"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
"Initialy good pricing and good, if it comes to Enterprise license agreements."
"I am not involved in the licensing side of things."
"It's a good deal for the money that we pay."
"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
"Workato is an expensive solution."
"On a scale of one to ten, the pricing is around a six. We have a consumption model and the pricing is higher. If you are using any kind of ML-based approach, machine learning, or some advanced analytics, you may have to pay more."
"Speaking about price, I would say that it's market-related. Also, there are costs in addition to the standard license fees since different add-ons depend on what you require."
report
Use our free recommendation engine to learn which Integration Platform as a Service (iPaaS) solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Computer Software Company
13%
Manufacturing Company
13%
Energy/Utilities Company
6%
Educational Organization
43%
Computer Software Company
8%
Financial Services Firm
8%
Manufacturing Company
5%
 

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 Workato?
Workato is low code, intuitive, and easy to use.
What needs improvement with Workato?
Workato's Extract, transform, and load (ETL) and extract, load, and transform (ELT) are not very strong and could be improved for very complex transformations. Workato's licensing model is a bit co...
What is your primary use case for Workato?
We use Workato for iPaaS, which is like a middleware enterprise service bus. We use it for transformation, quick data migrations from one platform to another, and building connectivity. It's got ov...
 

Also Known As

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

Learn More

Video not available
 

Overview

 

Sample Customers

Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Panera Bread, Berkshire Hathaway, Salesforce, Box, Splunk, ComScore, IBM, Complex Media, Microsoft, Home Depot, Cisco, News Corp, Braille Institute
Find out what your peers are saying about Workato vs. webMethods.io and other solutions. Updated: December 2024.
831,265 professionals have used our research since 2012.