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
31
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.8
Number of Reviews
83
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.
Abdul Ghani Shahzaib - PeerSpot reviewer
Ensures compliance and security in API integrations with a plug and play setup
We are working on almost everything Microsoft Businesses, Dynamics CRM and Dynamics FinOps ERP. We are utilizing Microsoft Azure hosting platform. We are using API service, Azure functions, event grid, API Management, and all types of Azure services on a need basis The integration and API Connect…

Quotes from Members

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

Pros

"It is a scalable solution."
"Since it is a gateway, it provides a lot of security features."
"The solution is straightforward and for large organizations, it functions well."
"The solution is very easy to work with."
"What I like most is the stability."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"The product's most valuable features are AAA policies and security features."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"The integration and API Connect are valuable when we need to connect with web services and REST APIs."
"It's easier to use and has more features than Google."
"The initial setup is not that complex, but there are certain challenges."
"The most valuable feature is its role as a linchpin in AI Hub architecture, enhancing data handling."
"The ability to easily connect back to Service Fabric is the most important for us."
"We're pretty much using all of the monetizations features out of the API manager so we can put up a portal and have a dev portal and then a prod portal and do rate limiting."
"The most valuable features of Microsoft Azure API Management are the easy configuration and deployment with automation."
"Microsoft Azure API Management serves as a gateway for all API management within our tech environment and is a basic part of our DevOps toolchain."
 

Cons

"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 components that they include in the product that are, in fact, a WTX, really need to be removed from the product because they tend to fail."
"From the development perspective, it has limitations because it only supports the XSLT language. It does not support multiple languages."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"The user interface or the application development perspective and customization of the tool could be a little better."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"Scripting needs improvement. It's hard for our customers."
"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."
"The initial setup of Microsoft Azure API Management is somewhat complex, but having eight years of experience, it is simple for me as we use it regularly."
"Expansion to global regions is a point for improvement, as licensing is costly."
"Microsoft Azure API Management could be improved by enhancing the visual editor of the development portal."
"Microsoft Azure API Management could be improved by enhancing the preview feature, specifically the workspaces."
"It could be more user friendly for developers. It would be nice if developers could view things more easily."
"Support for GraphQL could be better."
"In terms of improvement, it would be helpful if they could develop an on-premises option."
"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."
 

Pricing and Cost Advice

"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"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."
"It is an expensive solution."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"The tool's initial costing is expensive for small banks and financial institutions."
"The licensing cost is very expensive."
"The solution is expensive in comparison to other products."
"The product is expensive."
"Compared to other solutions the cost is a seven out of ten."
"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."
"It's free for less than ten users. If you want to go beyond that, it's around $3.50 per user per month. If you want a DevOps integration, it's about $7.50 per user per month. Costs depend on the size, complexity, usage, and what facility you want to integrate. So, we use Microsoft Azure and have the entire DevOps and Visual Studio on the cloud. We get all three flavors for $7.50 per user per month."
"Azure's pricing is very competitive compared to platforms like Apigee and MuleSoft."
"The price of the solution is reasonable compared to others."
"It's pay as you go. The subscription packages have room for different scales. It's calculated by the number of apps or computers you use. You do not have to use the enterprise subscription. These subscriptions have different pricing, so you can find one to meet your needs for scalability."
"The product pricing is reasonable."
"I rate the solution's pricing between three and four, as it could be more competitive."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
872,706 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise17
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise53
 

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.
872,706 professionals have used our research since 2012.