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
19th
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 (11th), SOA Application Gateways (1st)
 

Mindshare comparison

As of July 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.4%, down from 3.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway3.4%
Axway AMPLIFY API Management1.6%
Other95.0%
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

"Its flexibility allows us to adapt to different scenarios."
"This product is reliable and stable."
"In general, API governance provides a better experience for providers."
"This platform can be highly scalable."
"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."
"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."
"The administration tool for this solution is good."
"The UI and UX are quite good and easy to understand."
"IBM DataPower Gateway has positively impacted my organization by allowing me to implement rate limits on the different API usage, which is the benefit."
"Its initial setup was straightforward."
"Since it is a gateway, it provides a lot of security features."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"It is easy to use, easy to install, and it's resilient for high availability."
"DataPower Gateway is a perfect product, and I would recommend using it because it provides a lot of benefits."
"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."
"The support for IBM DataPower Gateway has been exceptional."
 

Cons

"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."
"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."
"It would be great if they have an asset report. It's hard to get support for that."
"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."
"They should also improve the way that we upgrade from one version to another. In our case, it's been very troublesome."
"I think that the program's team management capabilities can be better as far as working in groups."
"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."
"Axway's queuing messages could be enhanced."
"The product should be more adapted to the DevOps process."
"The customization of the solution isn't as straightforward as we would like it to be."
"This solution is not scalable for our environment."
"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."
"IBM DataPower Gateway is quite big for smaller organizations, looking at different types of clients who are virtually assisted in this, I would say it's not really a good product for smaller firms."
"The user interface or the application development perspective and customization of the tool could be a little better."
"They should improve the solution's clustering features."
"The programming language is only supported in XSLT and Gateway script."
 

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."
"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."
"The cost is very high and requires all five components in the API management 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 cost of this product varies from customer to customer and the relationship with IBM, including how many offerings from IBM are already being used."
"It's expensive when you compare it with others."
"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 solution is expensive in comparison to other products."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
903,182 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
11%
Insurance Company
7%
Government
6%
Financial Services Firm
24%
Manufacturing Company
8%
Insurance Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise10
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: June 2026.
903,182 professionals have used our research since 2012.