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

Axway AMPLIFY API Management vs IBM DataPower Gateway 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

Axway AMPLIFY API Management
Ranking in API Management
30th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
12
Ranking in other categories
No ranking in other categories
IBM DataPower Gateway
Ranking in API Management
10th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
31
Ranking in other categories
Enterprise Service Bus (ESB) (5th), Application Infrastructure (6th), SOA Application Gateways (1st)
 

Mindshare comparison

As of March 2026, in the API Management category, the mindshare of Axway AMPLIFY API Management is 1.6%, up from 1.5% compared to the previous year. The mindshare of IBM DataPower Gateway is 3.1%, down from 3.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway3.1%
Axway AMPLIFY API Management1.6%
Other95.3%
API Management
 

Featured Reviews

Sudhanshu Singh - PeerSpot reviewer
Associate Software Engineer at a tech services company with 10,001+ employees
We get stability, scalability, and security
Axway provides good documentation that newcomers can easily follow, but I believe the initial setup would be tough for someone new. Experienced employees know where everything is and how to do their job, so it would be difficult for a new hire to get up to speed. For an experienced person, I give the initial setup a ten out of ten. Deployment can be considered a hundred lines of code and some a thousand lines. For a simple deployment, it takes 10-15 seconds. And if the environment connectivity is good enough to respond and there is some heavy code that is being deployed, it takes around 30-60 seconds max, if we are referring to the cloud, where the connectivity for the long duration of the calls is there. The total deployment time is one minute to finish up. From the industrial point of view, Europe has a major chunk of users followed by, the US, and then Australia or the Asia-Pacific region.
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.

Quotes from Members

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

Pros

"There's drag and drop functionality so that you do not need to have a senior expert developer to make use of the tool. You can get more of your staff trained up to be able to use it as it's not overly technical."
"The administration tool for this solution is good."
"We like the portal for documentation a lot."
"In general, API governance provides a better experience for providers."
"This platform can be highly scalable."
"This product is a ten when it comes to API management."
"The most valuable feature of the solution is security."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"You don't have to have a separate DMC proxy because DataPower Gateway is an appliance and will take care of a lot of security features. These include data validations, encryption, as well as XML or any type of scripting or security threats that are present."
"Support for PCA and non-PCA services is valuable."
"I like that it is very stable, and we never experience any downtime."
"Its initial setup was straightforward."
"The product's most valuable features are AAA policies and security features."
"The scalability of the solution is good."
"It is easy to use, easy to install, and it's resilient for high availability."
"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."
 

Cons

"This solution does have some limitations regarding the deployment model."
"In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better."
"Sometimes we find bugs where certain calls are not returning all the data we need."
"It would be great if they have an asset report. It's hard to get support for that."
"Areas of improvement include marketing and enhancing the data products area by using ETIs."
"The portal still has room for improvement."
"Team management capabilities could be improved."
"The areas for enhancement should be improving certain filters within the solution. Although they are generally functional, there are occasional problems that could be more precisely adjusted. Additionally, the solution performs well within its workload limitations, but it may not be suitable for scaling up or managing a larger volume of transactions through the gateway. To address this, it may be necessary to adopt a unique architecture rather than relying on traditional pre-packaged options."
"The programming language is only supported in XSLT and Gateway script."
"The IBM community does not have much engagement from the IT community in Saudi Arabia and developers for this solution are difficult to find."
"Small and medium-sized companies might look for cloud-hosted applications due to the cost."
"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."
"I would like the tool to improve its training."
"My experience with the pricing of this product is that pricing is too high and should be reduced."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
 

Pricing and Cost Advice

"The solution is expensive. When you acquire a license you have full access to the solution, unlike other competitors such as Apigee X, where there are fragmented licenses. Some licenses only allow access to certain features while others allow access to more features. Upon procuring this solution's license, you will have full access to the solution, allowing you to experiment with all of its features."
"It's expensive when you compare it with others."
"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."
"It is an expensive solution."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"The licensing cost is very expensive."
"As far as I know, they have a perpetual license for this product. They are paying perpetual fees rather than an annual subscription or annual pricing."
"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."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
883,011 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
16%
Insurance Company
8%
Government
8%
Financial Services Firm
28%
Insurance Company
9%
Manufacturing Company
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise7
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise17
 

Questions from the Community

Ask a question
Earn 20 points
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?
The developer portal should be an integrated part of IBM DataPower Gateway to improve it. I think it is fine as is, and maybe no other additional features should be included in the next release. My...
 

Also Known As

Vordel Application Gateway, Axway API Management Plus, Axway API Management, AMPLIFY API Management
WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
 

Overview

 

Sample Customers

Engie Group, Allianz
RBL Bank, Availity
Find out what your peers are saying about Axway AMPLIFY API Management vs. IBM DataPower Gateway and other solutions. Updated: February 2026.
883,011 professionals have used our research since 2012.