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

IBM DataPower Gateway vs OpenLegacy 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

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

Mindshare comparison

As of March 2026, in the API Management category, the mindshare of IBM DataPower Gateway is 3.1%, down from 3.8% compared to the previous year. The mindshare of OpenLegacy is 0.9%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway3.1%
OpenLegacy0.9%
Other96.0%
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

"My company has a good impression of IBM DataPower Gateway. What I like about it is that because it's an appliance, it's a turnkey solution that's very fast and out of the box. Compared to other gateways, I also like that IBM DataPower Gateway is function-rich. For example, for one of the projects, there was a need for specific transformation and security features available in IBM DataPower Gateway out of the box, so my team just needed to configure the appliance. There was no need for separate development, and I found it quite neat. Another valuable feature of IBM DataPower Gateway is that it's easy to integrate with other products."
"The solution's technical support is excellent."
"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."
"The product is stable...The product is scalable."
"For me, its most valuable features include: the fact that it's high-speed, its ability to be remotely administered via an API, the fact that it can deal with multiple protocols, and it's very quick to make changes to the setup."
"The advantages of IBM DataPower Gateway, which I personally appreciate, are the security features that you can manipulate according to your company policies."
"The solution is straightforward and for large organizations, it functions well."
"What I like most is the stability."
"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."
"The product has helped our business by allowing us to become more efficient in data handling."
"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."
"The speed of development of production, especially in specific environments like IBM mainframes, has been valuable."
"Opens the door to connect modern web products to an old legacy system."
"Without OpenLegacy, it would take us several months to create the same services."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
 

Cons

"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"We are always looking for more features wherein it could be easily integrated with cloud applications."
"Scripting needs improvement. It's hard for our customers."
"IBM DataPower Gateway is quite expensive to get resources to work on this product. If the price could be cheaper, I think that will make it a little bit better and easily accessible to smaller clients."
"Traceability could be improved, especially for business operations."
"I noticed that the Gateway Script libraries could be improved, as they are not covering everything I need."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"The customization of the solution isn't as straightforward as we would like it to be."
"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."
"Debugging and logging for programmers could be better."
"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."
"Debugging and logging for programmers could be better."
"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."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing."
 

Pricing and Cost Advice

"The solution has a return on investment but is a little expensive."
"It is an expensive solution."
"The licensing cost is very expensive."
"The product is expensive."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"The solution is expensive in comparison to other products."
"The cost is very high and requires all five components in the API management solution."
"The tool's initial costing is expensive for small banks and financial institutions."
"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.
885,311 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Insurance Company
8%
Manufacturing Company
8%
Government
7%
Construction Company
27%
Insurance Company
12%
Financial Services Firm
11%
Comms Service Provider
8%
 

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 do you like most about IBM DataPower Gateway?
The MPGW (Multi-Protocol Gateway) is great because it allows you to easily expose services using various protocols – web services, REST (JSON), and others. This flexibility simplifies things.
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.
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: March 2026.
885,311 professionals have used our research since 2012.