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
31st
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
10th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
31
Ranking in other categories
Enterprise Service Bus (ESB) (5th), Application Infrastructure (7th), SOA Application Gateways (1st)
 

Mindshare comparison

As of February 2026, 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.1%, down from 3.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway3.1%
Axway AMPLIFY API Management1.6%
Other95.3%
API Management
 

Featured Reviews

Akash Dalebehera - PeerSpot reviewer
Technical Specialist at BT - British Telecom
High level security, handles large volumes of data, and useful filters
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. If there was a new release of this solution there should be a feature called "Revision History" or "Version Control" that would allow developers to easily navigate and compare different versions of their API flows within the Amplify API Management toolkit. This would save time and effort by eliminating the need to constantly switch between the toolkit and external Git repositories. Additionally, it would provide an added layer of security by allowing developers to quickly revert back to previous versions if a mistake or issue arises.
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

"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"The most valuable features are security enforcement and throttling."
"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."
"In general, API governance provides a better experience for providers."
"We like the portal for documentation a lot."
"This product is a ten when it comes to API management."
"This platform can be highly scalable."
"The API portal capability is a valuable feature."
"I like the API Gateway feature."
"It is a scalable solution."
"IBM DataPower Gateway has positively impacted my organization by allowing me to implement rate limits on the different API usage, which is the benefit."
"Since it is a gateway, it provides a lot of security features."
"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:"
"Its initial setup was straightforward."
"The solution is stable."
"It is easy to use, easy to install, and it's resilient for high availability."
 

Cons

"Sometimes we find bugs where certain calls are not returning all the data we need."
"Team management capabilities could be improved."
"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 installation process is a bit complex and it could be a lot simpler."
"Areas of improvement include marketing and enhancing the data products area by using ETIs."
"This solution does have some limitations regarding the deployment model."
"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 API Mocking tools need to be improved."
"We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option."
"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."
"The programming language is only supported in XSLT and Gateway script."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"The product should be more adapted to the DevOps process."
"It is a costly product."
"They should add features to manage API integrations."
"The user interface or the application development perspective and customization of the tool could be a little better."
 

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 licensing cost is very expensive."
"It's expensive when you compare it with others."
"The solution has a return on investment but is a little expensive."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"The product is expensive."
"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."
"It is an expensive solution."
"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."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
881,360 professionals have used our research since 2012.
 

Top Industries

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

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: December 2025.
881,360 professionals have used our research since 2012.