OpenLegacy vs webMethods.io comparison

OpenLegacy and IBM are both solutions in the API Management category. OpenLegacy is ranked #36, while IBM is ranked #9 with an average rating of 8.1. OpenLegacy holds a 0.4% mindshare in APIM, compared to IBM’s 2.4% mindshare. Additionally, 80% of OpenLegacy users are willing to recommend the solution, compared to 94% of IBM users who would recommend it.

OpenLegacy

Read 5 OpenLegacy reviews

452 Views
235 Comparison Views

80% willing to recommend

webMethods.io

Read 93 webMethods.io reviews

2,771 Views
1,536 Comparison Views

94% willing to recommend

OpenLegacy

webMethods.io

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

OpenLegacy and webMethods.io are enterprise-focused integration solutions, with webMethods.io often seen as having superior technological capabilities, offering advanced features that many organizations find beneficial despite its potentially higher cost.

Features: OpenLegacy enables effective modernization with rapid API development, seamless integration with mainframes, and a user-friendly API development environment. webMethods.io offers comprehensive integration features, cloud-based capabilities, and extensive connector support, making it versatile for various integration needs.

Room for Improvement: OpenLegacy could enhance its cloud integration capabilities, improve scalability in complex enterprise environments, and expand its connector library. webMethods.io could streamline its deployment process, reduce complexity in its user interface, and refine its pricing model for better competitiveness.

Ease of Deployment and Customer Service: OpenLegacy offers a straightforward deployment process, especially suited for legacy systems, supported by dedicated customer assistance. webMethods.io provides a flexible hybrid deployment model, combining cloud and on-premise options, alongside robust global customer support, offering high versatility across environments.

Pricing and ROI: OpenLegacy generally provides lower setup costs with quick ROI for organizations focusing on legacy integration. webMethods.io might involve higher initial costs but delivers ROI through its extensive feature set and adaptability, appealing to enterprises with broader integration demands.

To learn more, read our detailed OpenLegacy vs. webMethods.io Report (Updated: June 2025).

Buyer's Guide

OpenLegacy vs. webMethods.io

June 2025

Download the complete report

Helped 860,592 peers since 2012

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

36th

Average Rating

7.6

Reviews Sentiment

6.2

Number of Reviews

Ranking in other categories

No ranking in other categories

webMethods.io

Ranking in API Management

9th

Average Rating

8.0

Reviews Sentiment

6.8

Number of Reviews

Ranking in other categories

Business-to-Business Middleware (3rd), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (9th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)

Mindshare comparison

As of July 2025, in the API Management category, the mindshare of OpenLegacy is 0.4%, up from 0.2% compared to the previous year. The mindshare of webMethods.io is 2.4%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.

API Management

Featured Reviews

reviewer1042905

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.

Read full review

MohanPrasad

Senior Consultant at Brillio

Smooth integration and enhanced deployment with high licensing cost

webMethods.io was used to integrate APIs through the webMethods.io platform, trigger database events, and connect backend APIs through a Java backend. It was used extensively for integration purposes in my organization Integration became smoother, troubleshooting was easier, and deployment and…

Read full review

Quotes from Members

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

Pros

"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."

"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."

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

"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."

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

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

"It is possible to solve larger legacy API issues on an enterprise level with this product."

"Most of the work in our organization can be more easily done using the tool."

"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."

"The comprehensiveness and depth of Integration Servers' connectors to packaged apps and custom apps is unlimited. They have a connector for everything. If they don't, you can build it yourself. Or oftentimes, if there is value for other customers as well, you can talk with webMethods about creating a new adapter for you."

"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."

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

"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)."

"Our use case is for integration factory for SAP. It is mostly for SAP integration."

"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."

More webMethods.io pros

Cons

"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. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."

"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."

"I would like to have a dashboard where I can see all of the communication between components and the configuration."

"It could be more user-friendly."

"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."

"Rules engine processes and BPM processes should be improved."

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."

"Support is expensive."

"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."

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

More webMethods.io cons

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

"The pricing is a yearly license."

"Its cost depends on the use cases."

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

"This is an expensive product and we may replace it with something more reasonably priced."

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

"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."

"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."

More webMethods.io pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which API Management solutions are best for your needs.

See recommendations

860,592 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

27%

Insurance Company

16%

Computer Software Company

10%

Real Estate/Law Firm

Computer Software Company

13%

Financial Services Firm

13%

Manufacturing Company

12%

Retailer

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

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.

See all answers

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.

See all answers

What needs improvement with Built.io Flow?

webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.

See all answers

Comparisons

Kong Gateway Enterprise vs OpenLegacy

Compared 28% of the time

IBM API Connect vs OpenLegacy

Compared 15% of the time

MuleSoft API Manager vs OpenLegacy

Compared 14% of the time

Amazon API Gateway vs OpenLegacy

Compared 13% of the time

SEEBURGER Business Integration Suite vs OpenLegacy

Compared 9% of the time

More OpenLegacy Competitors

IBM App Connect vs webMethods.io

Compared 8% of the time

Apigee vs webMethods.io

Compared 7% of the time

IBM Integration Bus vs webMethods.io

Compared 7% of the time

IBM Sterling B2B Integration Services vs webMethods.io

Compared 4% of the time

Boomi iPaaS vs webMethods.io

Compared 4% of the time

More webMethods.io Competitors

Product Reports

Buyer's Guide

OpenLegacy

June 2025

Download OpenLegacy product report

Buyer's Guide

webMethods.io

June 2025

Download webMethods.io product report

Also Known As

No data available

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

Overview

OpenLegacy helps organizations quickly launch innovative digital services by extending their core back-end systems to the web, mobile and cloud in days or weeks versus months. Our microservice-enabled API integration and management software quickly reduces project backlog by automating and accelerating microservices and API creation, deployment, testing and management from core applications, mainframes and databases. Together, business and IT teams can quickly, easily and securely meet consumer, partner or employee demands for digital services without modernizing or replacing core systems, and without special programming skills or invasive changes to existing systems and architectures. OpenLegacy is designed for ongoing management of microservices APIs and is based on open standards, so our software plays nice with your current technology stack and supports agile, DevOps and continuous development. Learn why leading companies choose OpenLegacy at www.openlegacy.com.

OpenLegacy

webMethods.io Integration is a powerful integration platform as a service (iPaaS) that provides a combination of capabilities offered by ESBs, data integration systems, API management tools, and B2B gateways.

IBM

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

Buyer's Guide

OpenLegacy vs. webMethods.io

June 2025

Free Report: OpenLegacy vs. webMethods.io

Find out what your peers are saying about OpenLegacy vs. webMethods.io and other solutions. Updated: June 2025.

DOWNLOAD NOW

860,592 professionals have used our research since 2012.

See our OpenLegacy vs. webMethods.io report.

See our list of best API Management vendors and best Cloud Data Integration vendors.

We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.