No more typing reviews! Try our Samantha, our new voice AI agent.

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
20th
Average Rating
7.8
Reviews Sentiment
6.3
Number of Reviews
16
Ranking in other categories
No ranking in other categories
IBM DataPower Gateway
Ranking in API Management
15th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Enterprise Service Bus (ESB) (7th), Application Infrastructure (12th), SOA Application Gateways (1st)
 

Mindshare comparison

As of August 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.6%, 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.6%
Axway AMPLIFY API Management1.6%
Other94.8%
API Management
 

Featured Reviews

AnkitSingh6 - PeerSpot reviewer
Senior Lead Analytics Engineer at a outsourcing company with 5,001-10,000 employees
Comprehensive API management has improved monetization and streamlined secure integrations
Axway AMPLIFY API Management could be improved in terms of user interface and navigation, as it could be more user-friendly. There are no helping resources such as question marks or help icons to easily identify elements, making it difficult for new users to learn the platform without some form of training. The configuration and policy setups also require multiple steps, which complicates the process, and it would be easier if some steps could be skipped. Better analytics and reporting capabilities should provide improved trackability for API performance and consumer behavior. Documentation for advanced use cases would help reduce the learning curve. However, when trying to integrate with third parties, it can be quite difficult and requires a lot of authentication and authorization, which is better for security but poses challenges for new users trying to connect with a third party to transfer data between platforms. Additionally, the customization options for the dashboard are very limited, which restricts my ability to customize the entire dashboard meaningfully.
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

"Centralized API Platform allow us better reusability and monitoring"
"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."
"The most valuable features are security enforcement and throttling."
"Its flexibility allows us to adapt to different scenarios."
"My advice for others considering Axway AMPLIFY API Management is that if you want a comprehensive API management solution that includes a good dashboard with analytics, log functionality, monetization, and security, everything comes under one roof, making Axway AMPLIFY API Management a solid choice."
"Axway is a good product according to Gartner which is why we started to adopt it."
"For what we do, the API portal capability is the most valuable feature."
"The solution was very stable, we had no issues with it in that sense, it didn't crash or freeze and there were no bugs or glitches."
"The solution is straightforward and for large organizations, it functions well."
"I like all of the features in this product and it does what it's supposed to do."
"Its initial setup was straightforward."
"The whole purpose of this product is to provide high speed and high performance."
"I like the tool's security. Also, all functionalities are integrated within on platform."
"The product's most valuable features are AAA policies and security features."
"The solution is stable."
 

Cons

"It would be great if they have an asset report. It's hard to get support for that."
"We sometimes have issues with some of the functions because they do not work very well."
"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."
"Axway's queuing messages could be enhanced."
"The portal still has room for improvement."
"They should also improve the way that we upgrade from one version to another. In our case, it's been very troublesome."
"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."
"I would improve performance because most of the time we have to send the API several times and then get the notification that the API is received."
"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."
"The initial setup isn't so easy, you need who has experience working with the solution to help."
"It is a costly product."
"The customization of the solution isn't as straightforward as we would like it to be."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"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."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"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."
"The solution is expensive in comparison to other products."
"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."
"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 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 licensing cost is very expensive."
"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.
909,948 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
11%
Outsourcing Company
7%
Insurance Company
7%
Financial Services Firm
23%
Manufacturing Company
8%
Insurance Company
7%
Government
7%
 

Company Size

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

Questions from the Community

What is your experience regarding pricing and costs for Axway AMPLIFY API Management?
The pricing for Axway AMPLIFY API Management is quite high for small companies, organizations, or teams. The setup cost is also high, and licensing is very limited. They should restructure everythi...
What needs improvement with Axway AMPLIFY API Management?
Axway AMPLIFY API Management could be improved in terms of user interface and navigation, as it could be more user-friendly. There are no helping resources such as question marks or help icons to e...
What is your primary use case for Axway AMPLIFY API Management?
I have used Axway AMPLIFY API Management to expose and manage APIs across different internal and external applications, which helps secure the API, monitor traffic, and control access through polic...
What is your experience regarding pricing and costs for IBM DataPower Gateway?
I don't know if the current licensing cost of IBM DataPower Gateway is high, but I think it's acceptable. I don't have any complaints about it.
What needs improvement with IBM DataPower Gateway?
I noticed that the Gateway Script libraries could be improved, as they are not covering everything I need.
What is your primary use case for IBM DataPower Gateway?
The primary purposes for which IBM DataPower Gateway is used include security purposes, and sometimes you need to put some configurations and mapping into the process.
 

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: August 2026.
909,948 professionals have used our research since 2012.