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

Mindshare comparison

As of April 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.9% 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 most valuable feature of the solution is security."
"The API portal capability is a valuable feature."
"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 valuable features are security enforcement and throttling."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"This platform can be highly scalable."
"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 UI and UX are quite good and easy to understand."
"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."
"Its initial setup was straightforward."
"The performance is good, it's been very stable, and the product is easy to integrate."
"The solution is straightforward and for large organizations, it functions well."
"What I like most is the stability."
"It's high-speed and it can be remotely administered via an API."
"I like the API Gateway feature."
"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 API Mocking tools need to be improved."
"Areas of improvement include marketing and enhancing the data products area by using ETIs."
"We sometimes have issues with some of the functions because they do not work very well."
"Ultimately, from a very high-level overview, cloud platforms or Kong could have a slight advantage when compared to Axway AMPLIFY API Management."
"The product shows a lack of maturity. The setup is difficult, the tech support and community are lacking, and it is not very stable."
"The installation process is a bit complex and it could be a lot simpler."
"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."
"Team management capabilities could be improved."
"The initial setup isn't so easy, you need who has experience working with the solution to help."
"Small and medium-sized companies might look for cloud-hosted applications due to the cost."
"Making it more user-friendly would be an improvement."
"IBM DataPower Gateway is a great solution but when based on utilizations in the different streams others feel that this is an expensive product for one simple use case."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product."
"The user interface or the application development perspective and customization of the tool could be a little better."
"Additional documentation needs to be provided for complex automations."
"For the workloads that are not too high, appliance is a little bit expensive, especially in the development test and UAT environment, where we can use the virtual version of the product."
 

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 tool's initial costing is expensive for small banks and financial institutions."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"The solution is expensive in comparison to other products."
"The licensing cost is very expensive."
"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'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.
886,426 professionals have used our research since 2012.
 

Top Industries

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

What is your experience regarding pricing and costs for Axway AMPLIFY API Management?
Regarding pricing for Axway AMPLIFY API Management, I cannot say definitively because it depends on the transactional volume expected by customers. I would not be able to give the final answer, but...
What needs improvement with Axway AMPLIFY API Management?
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 everythi...
What is your primary use case for Axway AMPLIFY API Management?
I am currently working on Axway AMPLIFY API Management, which is the Axway API platform. The main requirement for API management is that the API platform provides security to the different APIs whi...
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 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.
 

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.
886,426 professionals have used our research since 2012.