IBM DataPower Gateway vs OpenLegacy comparison

Read 5 OpenLegacy reviews

1,847 Views
1,164 Comparison Views

80% willing to recommend

IBM DataPower Gateway

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

IBM DataPower Gateway and OpenLegacy operate within the enterprise integration sphere. IBM DataPower Gateway is recognized for its robust security features, while OpenLegacy offers a more innovative approach to legacy modernization, making it preferable in certain contexts.

Features: IBM DataPower Gateway provides significant security capabilities, protocol mediation, and threat protection. Its integration with various security services is comprehensive. OpenLegacy focuses on seamless integration with legacy systems, ease of API generation, and deployment supporting agile modernization strategies.

Room for Improvement: IBM DataPower Gateway could improve in reducing complexity and enhancing user-friendliness during deployment. Greater agility in updates might also be beneficial. OpenLegacy may need enhanced documentation for deeper technical insights and could benefit from extended integration with new, emerging technologies.

Ease of Deployment and Customer Service: IBM DataPower Gateway's deployment can be challenging due to its intricate security configurations, requiring specialized expertise. However, it provides extensive documentation and a strong support network. OpenLegacy excels in simplifying the connection with legacy systems, offering speedy deployment and responsive customer service.

Pricing and ROI: IBM DataPower Gateway demands significant initial investment, contributing to higher ROI in security-focused environments. OpenLegacy's subscription-based model offers cost-effectiveness, providing quicker ROI through reduced complexity and faster integration timelines, especially in efficiency-focused scenarios.

To learn more, read our detailed IBM DataPower Gateway vs. OpenLegacy Report (Updated: June 2026).

IBM DataPower Gateway vs. OpenLegacy

Download the complete report

Helped 902,495 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

IBM DataPower Gateway

Ranking in API Management

11th

Average Rating

8.2

Reviews Sentiment

6.5

Number of Reviews

Ranking in other categories

Enterprise Service Bus (ESB) (4th), Application Infrastructure (9th), SOA Application Gateways (1st)

OpenLegacy

Ranking in API Management

32nd

Average Rating

7.6

Reviews Sentiment

6.2

Number of Reviews

Ranking in other categories

AI Software Development (94th)

Mindshare comparison

As of June 2026, in the API Management category, the mindshare of IBM DataPower Gateway is 3.3%, down from 4.0% compared to the previous year. The mindshare of OpenLegacy is 1.3%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.

API Management Mindshare Distribution
Product	Mindshare (%)
IBM DataPower Gateway	3.3%
OpenLegacy	1.3%
Other	95.4%

API Management

Featured Reviews

AkshaySawant

Manager at CSB Bank Ltd

Security features excel but development limitations emerge

We are using the IBM DataPower Gateway for security purposes. As per the development perspective, there are some limitations with IBM DataPower Gateway because it only supports XML and XSLT language, but it does not support the Java language. This is the only limitation of the IBM DataPower Gateway. For the authentication and authorization purpose, we can use the IBM DataPower Gateway. It's a very good product. We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes. If we are handling the load for a particular server, then we can use the IBM DataPower Gateway. The IBM DataPower Gateway is mostly used for security purposes. If we have some APIs and we are using some security for those APIs, then we can use it. It can also be used as a load balancer. It's also used for certificate management, user management purposes, authentication, and authorization. For routing, the IBM DataPower Gateway has multiple URL-based routing and content-based routing capabilities. If we have multiple URLs, then we can use an XML script. Using the XSLT language, we can configure multiple URLs and implement URL-based routing. Content-based routing means if we have multiple requests, we can route the request to a particular URL. For this, we need to use the XSLT language only. We can't use XML, Java, or other scripting languages. With IBM DataPower Gateway, we are using all the APIs. All APIs have been configured on the gateway. We have configured the particular TLS profile and some TLS client profiles as well. Using that TLS profile, we have configured the APIs and authentication. We have configured some tokens also, including JWT tokens and different types of auth tokens. There is also a rate limiting feature which we use for handling API loads.

Read full review

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

Quotes from Members

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

Pros

"The solution is robust, and we use the appliance version, which comes with good security features and troubleshooting tools, so we are happy with IBM DataPower."

"If you are an enterprise customer, I would definitely advise that it is better to go for IBM DataPower, because you won't need to have a proxy or any other security measures required in the DMC, and it is easy to implement and easy to maintain and scale."

"It is very easy to set up and configure, even for users with no prior experience."

"The most valuable feature is the security appliance, it's very secure."

"The API Connect gateway service and the SQL injection feature is good."

"The product's most valuable features are AAA policies and security features."

"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."

"I like the API Gateway feature."

More IBM DataPower Gateway pros

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

"Without OpenLegacy, it would take us several months to create the same services."

"The biggest advantage of OpenLegacy was how simple the technology was, and we were able to build out the OpenLegacy parts very quickly, putting together a couple hundred APIs in six months."

"The product has helped our business by allowing us to become more efficient in data handling."

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

"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 speed of development of production, especially in specific environments like IBM mainframes, has been valuable."

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

More OpenLegacy pros

Cons

"Making it more user-friendly would be an improvement."

"It is challenging to understand the solution's design and support skills."

"In terms of OEM support, it is poor. If I raise a CBRT one, as per the SLA, they should respond in one hour, however, sometimes it takes four or five hours to respond."

"For the workloads that are not too high, appliance is a little bit expensive, especially in the development test and UAT environment, where we can use the virtual version of the product."

"From the development perspective, it has limitations because it only supports the XSLT language. It does not support multiple languages."

"IBM DataPower Gateway is quite big for smaller organizations, looking at different types of clients who are virtually assisted in this, I would say it's not really a good product for smaller firms."

"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product."

"The initial setup isn't so easy, you need who has experience working with the solution to help."

More IBM DataPower Gateway 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."

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

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

"Debugging and logging for programmers could be better."

"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."

Pricing and Cost Advice

"It's expensive when you compare it with others."

"The cost of this product varies from customer to customer and the relationship with IBM, including how many offerings from IBM are already being used."

"The appliance is a bit on the expensive side for the workloads that are not too high."

"The cost is very high and requires all five components in the API management solution."

"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."

"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."

"As far as I know, they have a perpetual license for this product. They are paying perpetual fees rather than an annual subscription or annual pricing."

"The solution has a return on investment but is a little expensive."

More IBM DataPower Gateway 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."

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

902,495 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

25%

Manufacturing Company

Insurance Company

Government

Construction Company

23%

Financial Services Firm

13%

Comms Service Provider

11%

Manufacturing Company

10%

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	11
Midsize Enterprise	2
Large Enterprise	18

No data available

Questions from the Community

What is your experience regarding pricing and costs for IBM DataPower Gateway?

I don't know if the current licensing cost of IBM DataPower Gateway is high, but I think it's acceptable. I don't have any complaints about it.

See all answers

What needs improvement with IBM DataPower Gateway?

I noticed that the Gateway Script libraries could be improved, as they are not covering everything I need.

See all answers

What is your primary use case for IBM DataPower Gateway?

The primary purposes for which IBM DataPower Gateway is used include security purposes, and sometimes you need to put some configurations and mapping into the process.

See all answers

Ask a question

Earn 20 points

Comparisons

IBM API Connect vs IBM DataPower Gateway

Compared 29% of the time

Apigee vs IBM DataPower Gateway

Compared 5% of the time

NGINX Plus vs IBM DataPower Gateway

Compared 4% of the time

webMethods.io vs IBM DataPower Gateway

Compared 3% of the time

IBM Integration Bus vs IBM DataPower Gateway

Compared 3% of the time

More IBM DataPower Gateway Competitors

Pipedream vs OpenLegacy

Compared 10% of the time

IBM API Connect vs OpenLegacy

Compared 9% of the time

MuleSoft API Manager vs OpenLegacy

Compared 8% of the time

Fiorano API Management vs OpenLegacy

Compared 8% of the time

PokitDok vs OpenLegacy

Compared 7% of the time

More OpenLegacy Competitors

Product Reports

IBM DataPower Gateway

Download IBM DataPower Gateway product report

Download OpenLegacy product report

Also Known As

WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower

No data available

Overview

IBM DataPower Gateway provides advanced security, multi-protocol transformation, and API management, ensuring appliance-based stability and performance. It supports enterprise-level traffic, facilitating seamless integration and deployment, though it may pose challenges in terms of pricing and user complexity.

IBM DataPower Gateway integrates as an enterprise service bus and API management platform, effectively securing APIs and managing authentication and authorization. Serving large banks and enterprises, it supports B2B transactions with data security and compliance, especially for sectors requiring GDPR adherence. Users benefit from high performance and stability, despite its premium cost and complex configuration needs. Cloud integration, user-friendliness enhancements, and improved documentation are areas where it can advance. It meets the demands of sectors like BFSI by protecting against security threats and supporting significant traffic volumes.

What are key features of IBM DataPower Gateway?

Advanced security functionalities: Comprehensive tools for authentication, authorization, and certificate management.
Multi-protocol transformation: Facilitates seamless conversions across different protocols.
Appliance-based stability: Provides a stable platform for handling enterprise traffic.
API management: Capable of managing APIs efficiently with rate-limiting and other controls.
Efficient troubleshooting tools: Streamlines issue resolution and system maintenance.

What benefits or ROI can users expect?

High performance: Capable of handling large-scale enterprise traffic efficiently.
Easy integration and configuration: Simplifies connecting with existing systems.
Regulatory compliance: Supports adherence to regulations like GDPR.
Protects against security threats: Offers robust security measures for data protection.

IBM DataPower Gateway is prominent in industries requiring rigorous data security and efficient integration, such as BFSI. Large enterprises leverage it for B2B transactions, ensuring regulatory compliance and high-performance standards. It's also implemented in environments demanding robust API security and management.

IBM

OpenLegacy integrates legacy customer data with REST APIs, speeding up mobile transactions and code updates while simplifying API development. Its open-source platform offers flexibility, benefiting mainframe environments and Tomcat server deployments.

OpenLegacy is crucial for organizations aiming to integrate modern web applications with legacy systems. The platform is widely used in financial and logistics sectors to enable quick access to customer data and transactions, effectively monetizing mainframe assets. By facilitating the rapid creation of numerous APIs, OpenLegacy supports seamless interactions between applications, allowing modern web form inputs into legacy systems. Its flexibility and extensive capabilities simplify API development and deployment, proving valuable for those managing day-to-day banking and transaction data. However, room for improvement includes better debugging, logging, SSL integration, flexible pricing options, and support availability, especially for Hogan mainframe users.

What features define OpenLegacy?

REST API Integration: Facilitates integration with mobile transactions.
Faster Code Updates: Delivers efficiency in code changes for mainframe environments.
Open-Source Flexibility: Offers customization and broad capabilities.
Tomcat Deployment: Supports straightforward deployment via Tomcat servers.
Rapid API Development: Enables swift creation of multiple APIs.

What ROI benefits should users expect?

Legacy System Monetization: Transforms mainframe assets into profit.
Improved Integration: Enhances access to critical customer data and transactions.
Efficient Operations: Streamlines daily banking and transaction management.
Cost-Effectiveness: Flexibility and open-source nature reduce expenses.
Enhanced Interoperability: Allows seamless interaction between old and new applications.

Financial and logistics companies leverage OpenLegacy to link web applications with legacy systems, ensuring quick customer data and transaction access. This integration supports rapid solution building and efficient management of banking and transaction data, particularly benefiting institutions like US Bank and Wells Fargo needing comprehensive Hogan mainframe connectors.

Sample Customers

RBL Bank, Availity

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

IBM DataPower Gateway vs. OpenLegacy