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) (5th), 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 October 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.
Allan Møller - PeerSpot reviewer
Transforms internal APIs with secure, manageable cloud compatibility
Microsoft Azure API Management could be improved by enhancing the preview feature, specifically the workspaces. The feature should allow for better delegation of permissions to specific groups without affecting others. The service is extensive and expensive, and this added flexibility would make it more manageable and less prone to errors.

Quotes from Members

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

Pros

"It's high-speed and it can be remotely administered via an API."
"Since it is a gateway, it provides a lot of security features."
"We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes."
"The solution is straightforward and for large organizations, it functions well."
"The solution is stable."
"The scalability of the solution is good."
"The product's most valuable features are AAA policies and security features."
"What I like most is the stability."
"The user management is pretty seamless."
"The solution is reliable and very stable."
"The most valuable feature is the developer portal, which has source code examples in various programming languages to help developers learn the API."
"I like API Management's sandbox feature. It's an environment where you can test out the API before putting it into production and connecting it to a live environment."
"The most valuable features of Microsoft Azure API Management are the easy configuration and deployment with automation."
"The initial setup is not that complex, but there are certain challenges."
"Azure APIM's best features are its straightforward access management (it's a single point of access for all monitoring and logging and for policy implementation) and its integration with the Azure Cloud infrastructure."
"Most of the features are valuable to me."
 

Cons

"Small and medium-sized companies might look for cloud-hosted applications due to the cost."
"Making it more user-friendly would be an improvement."
"The programming language is only supported in XSLT and Gateway script."
"Scripting needs improvement. It's hard for our customers."
"For the workloads that are not too high, appliance is a little bit expensive."
"The DCDR process should be less complex."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"They should improve the solution's clustering features."
"The developer console for external users could be improved, especially in the testing site."
"The documentation could be improved for the customer."
"Specific to API development, I think Microsoft is still far behind AWS. AWS has grown by leaps and bounds, and Microsoft is a close second. But in terms of features and other stuff they provide, Microsoft's compatibility with publicly available APIs is a little limited. So, that is a little bit of a constraint. But what they provide is good, it's just that they need to build more on their API suite. I think Google is doing a really good job at that."
"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."
"The licensing tiers can be misleading."
"Microsoft Azure API Management's most valuable features are the microservices we used to use. They were API callers to receive communication with the network and building system, to complete the request. The response would be through the processing system."
"The implementation has room for improvement and can be more user-friendly."
"The cloud deployment performance could be better."
 

Pricing and Cost Advice

"It's expensive when you compare it with others."
"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 appliance is a bit on the expensive side for the workloads that are not too high."
"The product is expensive."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"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 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."
"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."
"I rate the solution's pricing between three and four, as it could be more competitive."
"The price is comparable."
"Microsoft Azure is an expensive solution not for the large enterprises but for the medium and small."
"On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a five out of ten."
"The solution appears cheaper because it's a cloud SaaS model."
"Licensing fees are paid on an annual basis."
"It's an expensive solution"
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
869,785 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Insurance Company
9%
Computer Software Company
8%
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?
This product is definitely expensive because if any issue occurs in the live environment or production environment, and our organization faces some issue with the IBM DataPower Gateway, then the IB...
What needs improvement with IBM DataPower Gateway?
I have significant experience with the IBM DataPower Gateway. As a security product, it is very good. However, from the development perspective, it has limitations because it only supports the XSLT...
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.
869,785 professionals have used our research since 2012.