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

IBM DataPower Gateway vs OpenLegacy comparison

Why PeerSpot?
 

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

IBM DataPower Gateway
Ranking in API Management
13th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Enterprise Service Bus (ESB) (6th), Application Infrastructure (13th), SOA Application Gateways (1st)
OpenLegacy
Ranking in API Management
32nd
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (62nd)
 

Mindshare comparison

As of October 2026, in the API Management category, the mindshare of IBM DataPower Gateway is 3.9%, up from 3.6% compared to the previous year. The mindshare of OpenLegacy is 1.5%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway3.9%
OpenLegacy1.5%
Other94.6%
API Management
 

Featured Reviews

AkshaySawant - PeerSpot reviewer
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.
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.

Quotes from Members

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

Pros

"If you have an API application in your organization that you want to make safe and secure, in addition to your existing WAF or load balancer, this product comes with all those capabilities:"
"IBM is a huge organization in comparison to most of the competition, it has massive development and offers very high-quality products."
"It is very easy to set up and configure, even for users with no prior experience."
"It is easy to use, easy to install, and it's resilient for high availability."
"The solution is straightforward and for large organizations, it functions well."
"I like that it is very stable, and we never experience any downtime."
"The solution was very stable, we had no issues with it in that sense, it didn't crash or freeze and there were no bugs or glitches."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"The speed of development of production, especially in specific environments like IBM mainframes, has been valuable."
"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."
"OpenLegacy opens the door to connect modern web products to our old legacy system."
"The product has helped our business by allowing us to become more efficient in data handling."
"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."
"Without OpenLegacy, it would take us several months to create the same services."
 

Cons

"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"Traceability could be improved, especially for business operations. The traceability of the transactions could be an improvement point for DataPower to work on. It would be better if they provided JSON support. JSON protocol data has changed format. It started performing internal transformation to JSONx. This might be an additional complexity."
"The product should be more adapted to the DevOps process."
"Additional documentation needs to be provided for complex automations."
"Its support services could be better."
"We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option."
"This solution is not scalable for our environment."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"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."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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."
"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."
 

Pricing and Cost Advice

"The total cost of IBM DataPower Gateway would depend on the configuration, but in my experience, it can amount to 60,000 Euros per box, even for the virtual version. Usually, customers need high availability and a non-production environment, so the total price for IBM DataPower Gateway can be quite a lot. It can be 200,000 Euros or a similar figure."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"It's expensive when you compare it with others."
"It is an expensive solution."
"The tool's initial costing is expensive for small banks and financial institutions."
"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 cost is very high and requires all five components in the API management solution."
"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."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
919,894 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Outsourcing Company
9%
Manufacturing Company
8%
Government
6%
Construction Company
23%
Comms Service Provider
16%
Financial Services Firm
14%
Manufacturing Company
11%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise18
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.
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.
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.
Ask a question
Earn 20 points
 

Also Known As

WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
No data available
 

Overview

 

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...
Find out what your peers are saying about IBM DataPower Gateway vs. OpenLegacy and other solutions. Updated: September 2026.
919,894 professionals have used our research since 2012.