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

"The best feature of Axway Amplify API Management is its exceptional level of security, which is highly reassuring, coupled with its remarkable capacity to handle substantial volumes of data in impressively efficient turnaround times."
"The most valuable features are security enforcement and throttling."
"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."
"The most valuable feature of the solution is security."
"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."
"In general, API governance provides a better experience for providers."
"We like the portal for documentation a lot."
"It is a scalable solution."
"The product's most valuable features are AAA policies and security features."
"What I like most is the stability."
"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."
"The scalability of the solution is good."
"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."
"The advantages of IBM DataPower Gateway, which I personally appreciate, are the security features that you can manipulate according to your company policies."
 

Cons

"The portal still has room for improvement."
"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."
"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 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."
"Team management capabilities could be improved."
"Its support services could be better."
"The user interface or the application development perspective and customization of the tool could be a little better."
"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."
"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 programming language is only supported in XSLT and Gateway script."
"The DCDR process should be less complex."
"Additional documentation needs to be provided for complex automations."
"The initial setup isn't so easy, you need who has experience working with the solution to help."
 

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."
"The licensing cost is very expensive."
"It is an expensive solution."
"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."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"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 is very high and requires all five components in the API management solution."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
884,706 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
17%
Government
8%
Insurance Company
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,706 professionals have used our research since 2012.