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

OpenLegacy vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 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

OpenLegacy
Ranking in API Management
33rd
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (101st)
webMethods.io
Ranking in API Management
16th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
94
Ranking in other categories
Business-to-Business Middleware (6th), Enterprise Service Bus (ESB) (5th), Managed File Transfer (MFT) (13th), Cloud Data Integration (11th), Integration Platform as a Service (iPaaS) (11th)
 

Mindshare comparison

As of May 2026, in the API Management category, the mindshare of OpenLegacy is 1.2%, up from 0.3% compared to the previous year. The mindshare of webMethods.io is 2.7%, up from 2.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
webMethods.io2.7%
OpenLegacy1.2%
Other96.1%
API Management
 

Featured Reviews

reviewer1042905 - PeerSpot reviewer
VP, Chief Enterprise Integration Architect at a financial services firm with 10,001+ employees
The biggest advantage is how simple the technology was.
I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be. OpenLegacy handles the bread-and-butter TP monitoring stuff, but I am working for one of the six banks in the United States still using the Hogan mainframe, which has a slightly proprietary mechanism. But OpenLegacy currently doesn't have a connector for Hogan. So it would help if they could build one. That would appeal to financial institutions that still use Hogan, like US Bank, Wells Fargo, KeyBank, and Vanguard.
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

"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"Opens the door to connect modern web products to an old legacy system."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
"The biggest advantage of OpenLegacy was how simple the technology was. We were able to build out the OpenLegacy parts very quickly. We put together a couple hundred APIs in six months."
"Without OpenLegacy, it would take us several months to create the same services."
"The speed of development of production, especially in specific environments like IBM mainframes, has been valuable."
"The product has helped our business by allowing us to become more efficient in data handling."
"The performance is good."
"webMethods Integration Server provides a single hybrid integration platform for all our needs."
"Operationally, I consider the solution to be quite good."
"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."
"webMethods Integration Server has a very good API gateway."
"Integration Server does our business-to-business integrations, and its adapters and connectors provide the fastest way to build an integration because we can immediately connect to backend systems without creating a lot of our own custom code, while the vendor’s full support for these adapters brings long-term stability to our services."
"webMethods' technical support is excellent."
"Time effective by cutting down development time and resource efficient to developer burden, enhance agility and integration between end-to-end applications, platform"
 

Cons

"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"Debugging and logging for programmers could be better."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"Some things could be improved, especially how ActiveTransfer handles third-party file transfers."
"For code version control, you need to use some external software."
"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."
"The price should be reduced to make it more affordable."
"The solution should include REST API calls."
"In terms of scale, I would give it a four out of 10."
"webMethods Trading Networks is a bit costly compared to others solutions."
"I would like the solution to provide bi-weekly updates."
 

Pricing and Cost Advice

"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"webMethods.io Integration's pricing is high and has yearly subscription costs."
"I would like to see better pricing for the license."
"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."
"The product is expensive."
"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"The price is high and I give it a five out of ten."
"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
"It is worth the cost."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
26%
Comms Service Provider
13%
Financial Services Firm
12%
Insurance Company
11%
Manufacturing Company
13%
Financial Services Firm
11%
Computer Software Company
9%
Comms Service Provider
5%
 

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

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

Overview

 

Sample Customers

Many of openLegacy's global customers are among the Global 100 companies. Review case studies in these industries: Agriculture, Airport Authority, Automotive, Auto, Finance, Insurance, Government, Healthcare, Manufacturing, and Retailwww.openlegacy.com/case-studie...
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about OpenLegacy vs. webMethods.io and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.