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
32nd
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
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)
 

Mindshare comparison

As of September 2025, in the API Management category, the mindshare of Axway AMPLIFY API Management is 1.6%, up from 1.4% compared to the previous year. The mindshare of IBM DataPower Gateway is 3.7%, up from 3.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway3.7%
Axway AMPLIFY API Management1.6%
Other94.7%
API Management
 

Featured Reviews

Sudhanshu Singh - PeerSpot reviewer
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
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

"The API portal capability is a valuable feature."
"In general, API governance provides a better experience for providers."
"This product is a ten when it comes to API management."
"The most valuable features are security enforcement and throttling."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"The most valuable feature of the solution is security."
"We like the portal for documentation a lot."
"This platform can be highly scalable."
"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:"
"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"I like the tool's security. Also, all functionalities are integrated within on platform."
"I like that it is very stable, and we never experience any downtime."
"I like all of the features in this product and it does what it's supposed to do."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"It is a scalable solution."
 

Cons

"The product shows a lack of maturity. The setup is difficult, the tech support and community are lacking, and it is not very stable."
"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."
"Team management capabilities could be improved."
"Sometimes we find bugs where certain calls are not returning all the data we need."
"The portal still has room for improvement."
"The installation process is a bit complex and it could be a lot simpler."
"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 API Mocking tools need to be improved."
"For the workloads that are not too high, appliance is a little bit expensive."
"The IBM community does not have much engagement from the IT community in Saudi Arabia and developers for this solution are difficult to find."
"In terms of OEM support, it is poor. If I raise a CBRT one, as per the SLA, they should respond in one hour, however, sometimes it takes four or five hours to respond."
"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."
"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."
"It is a costly product."
"The DCDR process should be less complex."
"I would like the tool to improve its training."
 

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."
"The solution is expensive in comparison to other products."
"The product is expensive."
"The cost is very high and requires all five components in the API management solution."
"The licensing cost is very expensive."
"The solution has a return on investment but is a little expensive."
"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."
"It's expensive when you compare it with others."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
867,676 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
17%
Government
9%
Insurance Company
8%
Financial Services Firm
29%
Insurance Company
9%
Computer Software Company
8%
Manufacturing 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 Enterprise16
 

Questions from the Community

What is your experience regarding pricing and costs for Axway AMPLIFY API Management?
The solution has a yearly subscription. The solution’s pricing is competitive. Axway makes a significant impression compared to its peers, especially with a sensitive budget. In many instances, it ...
What is your primary use case for Axway AMPLIFY API Management?
We use the solution for ESB and B2B integration between the systems of our business.
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...
 

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: September 2025.
867,676 professionals have used our research since 2012.