Try our new research platform with insights from 80,000+ expert users

IBM DataPower Gateway vs Microsoft Azure API Management 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
12th
Average Rating
8.4
Reviews Sentiment
6.5
Number of Reviews
30
Ranking in other categories
Enterprise Service Bus (ESB) (6th), Application Infrastructure (12th), SOA Application Gateways (1st)
Microsoft Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
82
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2025, in the API Management category, the mindshare of IBM DataPower Gateway is 3.7%, up from 3.7% compared to the previous year. The mindshare of Microsoft Azure API Management is 16.5%, down from 19.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
Microsoft Azure API Management16.5%
IBM DataPower Gateway3.7%
Other79.8%
API Management
 

Featured Reviews

AkshaySawant - PeerSpot reviewer
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.
Praveen_Srivastava - PeerSpot reviewer
Streamlined operations with gateway and authentication features
Azure API Management has helped streamline our operations by acting as a gateway for upstream and downstream applications. It provides authentication and authorization, ensuring that both verified and suspicious users are managed efficiently. The use of analytics within API Management is also valuable for tracking user behavior and ensuring security.

Quotes from Members

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

Pros

"Its initial setup was straightforward."
"I like the API Gateway feature."
"It is a scalable solution."
"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"The most valuable feature is the security appliance, it's very secure."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"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."
"It's high-speed and it can be remotely administered via an API."
"The most valuable feature is the developer portal, which has source code examples in various programming languages to help developers learn the API."
"Everything is already available and ready to operate without a lot of preparation work."
"Easy to integrate API management platform. It is a stable and scalable solution."
"It's a valuable tool for API lifecycle management"
"There were no scalability issues."
"Microsoft Azure API Management is 90 to 99 percent scalable. We have three instances running in parallel."
"The analytics phase of API Management is very beneficial for tracking API usage and identifying suspicious users."
"The price is pretty reasonable for us."
 

Cons

"Scripting needs improvement. It's hard for our customers."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product. Sometimes, when the customer use case is just a very small subset of what's being offered in IBM DataPower Gateway, then the product can be expensive, making my company lose some of the opportunities because of the expensive pricing. A lower price point for IBM DataPower Gateway, even if that results in a less feature-rich version, would be appreciated. In terms of additional features that I'd like to see in the next release of IBM DataPower Gateway, nothing specific comes to mind because IBM constantly improves its standards and provides quarterly updates to the product, so it's quite fine."
"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."
"Additional documentation needs to be provided for complex automations."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"Making it more user-friendly would be an improvement."
"What would make Microsoft Azure API Management better are more APIs. They keep updating their APIs, but it would be better if the solution had more APIs for the services and more integration with other platforms."
"From my understanding, there are some constraints around governance and service-to-service intercommunication managing priorities and our own governance."
"Support for GraphQL could be better."
"Microsoft Azure API Management needs to improve stability."
"The licensing part of Microsoft is always higher than other platforms, like Amazon services and other cloud services. Microsoft should work on reducing the cost."
"Multi-tenant functionalities is missing from the system, especially when it comes to the developer code of features."
"Documentations for implementing certain product features are very difficult to find"
"Microsoft Azure API Management could be improved by enhancing the visual editor of the development portal."
 

Pricing and Cost Advice

"It is an expensive solution."
"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. Then it could compete with other solutions that are available in the market. There's a whole lot of other solutions available that work well and are cheaper than IBM's products."
"The licensing cost is very expensive."
"The solution is expensive in comparison to other products."
"The solution has a return on investment but is a little expensive."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"The tool's initial costing is expensive for small banks and financial institutions."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"Microsoft Azure is an expensive solution not for the large enterprises but for the medium and small."
"We are paying standard fees to use Microsoft Azure API Management."
"Azure is a pay-as-you-go model. You build out your virtual environment and pay a monthly price depending on CPU cores, storage, etc."
"Based on the resources that we are leveraging, the price we are paying to use this solution is slightly higher than other competitors. In a few cases, it has its own advantage in some resources."
"The product pricing is reasonable."
"The price of the solution is reasonable compared to others."
"There are additional costs to the standard licensing fees."
"Compared to other solutions the cost is a seven out of ten."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
867,349 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Insurance Company
9%
Computer Software Company
9%
Manufacturing Company
7%
Financial Services Firm
16%
Computer Software Company
12%
Manufacturing Company
9%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise16
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise52
 

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 would rate the pricing a two out of ten, with one being high price, and ten being low price. It's high-priced for smaller companies. But it is okay for enterprises. So, the price could be more fl...
What needs improvement with IBM DataPower Gateway?
The DCDR process should be less complex. AI should improve developer efficiency and effort. Whenever I am writing code, it should give recommendations automatically by incorporating AI so I can wri...
How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Azure API Management or Amazon API Gateway?
If you use Azure products, API Management is a great solution. It solves many of the problems of externalizing web services. For example, when you need versioning, establish a developer portal and ...
What do you like most about Microsoft Azure API Management?
Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation.
 

Also Known As

WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
Azure API Management, MS Azure API Management
 

Overview

 

Sample Customers

RBL Bank, Availity
adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
Find out what your peers are saying about IBM DataPower Gateway vs. Microsoft Azure API Management and other solutions. Updated: September 2025.
867,349 professionals have used our research since 2012.