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

Axway AMPLIFY API Management vs IBM Cloud Pak for Integration 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
18th
Average Rating
7.8
Reviews Sentiment
6.3
Number of Reviews
15
Ranking in other categories
No ranking in other categories
IBM Cloud Pak for Integration
Ranking in API Management
27th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
Cloud Data Integration (19th)
 

Mindshare comparison

As of May 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 Cloud Pak for Integration is 0.9%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Axway AMPLIFY API Management1.6%
IBM Cloud Pak for Integration0.9%
Other97.5%
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.
Igor Khalitov - PeerSpot reviewer
Owner/Full Stack Software Engineer at Maraphonic, Inc.
Manages APIs and integrates microservices with redirection feature
IBM Cloud Pak for Integration includes monitoring capabilities to track the performance and health of your integrations. You can quickly roll back to a previous version if an issue arises. Additionally, it supports incremental deployments, allowing you to shift traffic to a new version of an API gradually. For example, you can start by directing 10% of traffic to the new version while the rest continue using the legacy version. If everything works as expected, you can gradually increase the traffic to the new version over time. IBM Cloud Pak for Integration has a client base that includes numerous organizations using AI and machine learning technologies. We leverage an open-source machine learning framework and integrate it with Kafka to help create and manage various products and data retrieval processes. For companies with private data, the framework first retrieves relevant data from a GitHub database, which is then combined with the final request before being sent to a language model like GPT. This ensures that the language model uses your specific data to generate responses. Kafka plays a key role by streaming real-time data from file systems and databases like Oracle and Microsoft SQL. This data is published to Kafka topics, then vectorized and used with artificial intelligence to enhance the overall process. It's like an old-fashioned approach. The best way is to redesign it with products such as Kafka. Overall, I rate the solution an eight out of ten.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I would recommend the solution for other people who want to start using it."
"Its flexibility allows us to adapt to different scenarios."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"In general, API governance provides a better experience for providers."
"This product is a ten when it comes to API management."
"It provides very strong security functionality to protect information in an easier way."
"The administration tool for this solution is good."
"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 aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"It is a stable solution."
"Cloud Pak for Integration is definitely scalable; that is the most important criteria."
"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"In general, the solution works very, very well."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."
 

Cons

"The installation process is a bit complex and it could be a lot simpler."
"It would be great if they have an asset report. It's hard to get support for that."
"Axway's queuing messages could be enhanced."
"They should also improve the way that we upgrade from one version to another. In our case, it's been very troublesome."
"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."
"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."
"The portal still has room for improvement."
"Its queuing and messaging features need improvement."
"The initial setup is not easy."
"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."
"Enterprise bots are needed to balance products like Kafka and Confluent."
"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated."
"The pricing can be improved."
"What needs to be improved is the restriction that they have on 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 solution's pricing model is very flexible."
"It is an expensive solution."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
895,151 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
13%
Insurance Company
7%
Government
7%
Financial Services Firm
15%
Government
11%
Manufacturing Company
9%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise9
No data available
 

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 needs improvement with IBM Cloud Pak for Integration?
Enterprise bots are needed to balance products like Kafka and Confluent.
What is your primary use case for IBM Cloud Pak for Integration?
It manages APIs and integrates microservices at the enterprise level. It offers a range of capabilities for handling APIs, microservices, and various integration needs. The platform supports thousa...
What advice do you have for others considering IBM Cloud Pak for Integration?
IBM Cloud Pak for Integration includes monitoring capabilities to track the performance and health of your integrations. You can quickly roll back to a previous version if an issue arises. Addition...
 

Also Known As

Vordel Application Gateway, Axway API Management Plus, Axway API Management, AMPLIFY API Management
No data available
 

Overview

 

Sample Customers

Engie Group, Allianz
CVS Health Corporation
Find out what your peers are saying about Axway AMPLIFY API Management vs. IBM Cloud Pak for Integration and other solutions. Updated: April 2026.
895,151 professionals have used our research since 2012.