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.3
Number of Reviews
14
Ranking in other categories
No ranking in other categories
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)
 

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 Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway3.1%
Axway AMPLIFY API Management1.6%
Other95.3%
API Management
 

Featured Reviews

reviewer2081667 - PeerSpot reviewer
Associate Software Engineer at a tech vendor with 10,001+ employees
Centralized gateway has strengthened API security and provides deep traffic analytics
Potential areas of improvement or lack of functions in Axway AMPLIFY API Management is a challenging question because even after working for almost six years, I have not been able to touch everything this tool offers. This tool is very comprehensive and useful. However, from my opinion, when there are different dashboards on which the API platform shows monitoring, I expect Axway AMPLIFY API Management to be more visible in terms of showing pre-historic data. In other words, if there is a very large volume or very large number of transactions going on live in production, sometimes it purges the previous data very quickly, leaving only one or two hours of data. When there is very low volume, it can sustain data up to five days. The visibility of the previous historic database is a feature that could be improved. Different tools can be used to empower this capability, such as Splunk or the ELK stack, which includes Elastic. There are different features that could be used, but Axway as an organization would likely implement their specific products. I am simply providing a very basic opinion anonymously and do not want to sound like I am against this organization.
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

"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"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."
"We like the portal for documentation a lot."
"This product is a ten when it comes to API management."
"Axway AMPLIFY API Management is niche technology that people prefer because it has emerged beautifully and has very nice support and enterprise-level features which are not provided by cloud Azure or AWS."
"The most useful features in Axway AMPLIFY API Management, in my opinion, primarily involve the security aspect of the product, which provides us very good methods of securing the network."
"This platform can be highly scalable."
"In general, API governance provides a better experience for providers."
"It is very easy to set up and configure, even for users with no prior experience."
"I like the tool's security. Also, all functionalities are integrated within on platform."
"I like all of the features in this product and it does what it's supposed to do."
"The scalability of the solution is good."
"The most valuable feature is the security appliance, it's very secure."
"It's high-speed and it can be remotely administered via an API."
"Support for PCA and non-PCA services is valuable."
"If you have an API application in your organization that you want to make safe and secure, in addition to your existing WAF or load balancer, this product comes with all those capabilities:"
 

Cons

"The API Mocking tools need to be improved."
"Ultimately, from a very high-level overview, cloud platforms or Kong could have a slight advantage when compared to Axway AMPLIFY API Management."
"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."
"This solution does have some limitations regarding the deployment model."
"The portal still has room for improvement."
"The product shows a lack of maturity. The setup is difficult, the tech support and community are lacking, and it is not very stable."
"Sometimes we find bugs where certain calls are not returning all the data we need."
"A significant area of improvement for Axway AMPLIFY API Management is the Amplify Central portal, which should help expose APIs on a webpage for potential customers."
"For the workloads that are not too high, appliance is a little bit expensive."
"Scripting needs improvement. It's hard for our customers."
"They should add features to manage API integrations."
"DataPower isn't the most user-friendly tool. It is not an easy tool to use. Some things could use better wizards to guide you through processes."
"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."
"I would like the tool to improve its training."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"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."
 

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."
"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."
"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."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"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."
"The solution has a return on investment but is a little expensive."
"The solution is expensive in comparison to other products."
"The tool's initial costing is expensive for small banks and financial institutions."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
884,328 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise9
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise18
 

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: March 2026.
884,328 professionals have used our research since 2012.