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

Axway AMPLIFY API Management vs MuleSoft API Manager 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
MuleSoft API Manager
Ranking in API Management
4th
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
60
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 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 MuleSoft API Manager is 4.2%, down from 4.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
MuleSoft API Manager4.2%
Axway AMPLIFY API Management1.6%
Other94.2%
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.
D.Rajesh Kumar - PeerSpot reviewer
Enterprise Architect at a consultancy with 10,001+ employees
Improved Integration Efficiency and Potential for Further Enhancements in Monitoring and User Experience
The policies in MuleSoft API Manager are significant features. We get the policies by default, with more than 25 out-of-the-box policies. If any additional requirement exists specific to the customer, there is a custom policy framework. We can build the policy according to our requirement, and deploy and enable it at the API Manager level to consume across different business groups, environments, or organizations altogether within the platform. Developing the custom policy is not challenging; you just need to follow the custom policy framework to implement. The custom policy and the different levels of SLAs of the API Manager are notable. Regarding the monitoring side of the API Manager, MuleSoft provides substantial monitoring with logs, offering search capability, raw data accessibility, and different subscriptions. With the top tier, integration with third-party platforms such as ELK or Splunk becomes unnecessary because all search capabilities, dashboards, and functional monitoring can be built within the platform itself. This is excellent from the monitoring perspective, and there have been recent improvements focusing on observability. For DevOps, if you want to make your continuous integration and continuous deployment effective, irrespective of the tool, there are options to integrate. For example, you can use the Maven plugin, platform APIs, or CLI to build your end-to-end DevOps cycle.

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"
"In general, API governance provides a better experience for providers."
"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."
"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."
"Axway is a good product according to Gartner which is why we started to adopt it."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"This product is a ten when it comes to API management."
"The administration tool for this solution is good."
"We have not seen many tickets which tells us it is very stable."
"We're using MuleSoft API Manager to integrate with an endpoint in our backend system to import much information into Salesforce. Other tools didn't allow for as many API calls, so we used it to create a new endpoint."
"The initial setup was straightforward."
"The tool has a private area. It also has a cloud deployment option."
"The solution has a feature called Flex, which is a low-latency API layer for passthrough APIs where you want data mapping but with very low latency and high scalability."
"Mulesoft is great in terms of reusability."
"The onboarding process significantly contributes to faster market access, and the effort reduced by 30 to 40% directly leads to savings in IT time and costs."
"Technical support has been helpful."
 

Cons

"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 portal still has room for improvement."
"Sometimes we find bugs where certain calls are not returning all the data we need."
"Team management capabilities could be improved."
"They should also improve the way that we upgrade from one version to another. In our case, it's been very troublesome."
"Axway's queuing messages could be enhanced."
"This solution does have some limitations regarding the deployment model."
"The API Mocking tools need to be improved."
"They should develop on MuleSoft as it would be a good way of improving API monetization."
"Rather than focusing on numbers, they should focus more on the customer support service."
"The upgrade is a very messy process; Mule 3.X to 4 or 4.2 requires you have to rewrite the APIs, and it is not just upgrading the build pack with a runtime."
"Anypoint could be improved by making it more open and configurable for small companies, who tend not to consider the solution as it's expensive and requires a lot of costs upfront."
"The product is highly priced compared to other advanced software."
"When it comes to pricing, I find it always expensive. The pricing is high, which is the biggest point where some customers are hesitant about adopting it, and their deployment strategy is also more costly due to containerization."
"The solution is missing a monetization module."
"We have issues with the tool's pricing. The product seemed to have most of the features required for the tasks I was working on. I didn't feel the need for additional features. However, one aspect that could be improved is making the platform more user-friendly for non-technical users. While it's not necessarily complex, it does require some familiarity. Unlike open-source tools available online, accessing and using this product may not be as straightforward. It needs to offer training to its users."
 

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 looks more expensive on the surface because it builds all the functions into one core component or into an integrated suite of components."
"Pricing can be improved."
"The product is expensive."
"The licensing model is based on how many cores are used. It is a very simple licensing scheme."
"It's not very expensive, reasonably priced. There are no additional costs."
"The pricing is very expensive, although you get a lot of power from the product."
"I think that it is pretty expensive."
"It is extremely high, and I would rate it one out of ten."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

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

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 Business17
Midsize Enterprise5
Large Enterprise44
 

Questions from the Community

What is your experience regarding pricing and costs for Axway AMPLIFY API Management?
Regarding the licensing, I don't fully understand it because there's an additional fee about it. The license was covered by the vendor, and we just paid for the API that we used.
What needs improvement with Axway AMPLIFY API Management?
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. I'm not certain how accurate it is. The API is not...
What is your primary use case for Axway AMPLIFY API Management?
I can describe the use cases for what it can be used for because I was a project manager. We share APIs, modify, and check whether the API already sent it. They receive something, and when we modif...
How does Kong Enterprise compare with Mulesoft Anypoint API Manager?
The Mulesoft Anypoint API Manager was designed with its users in mind. Though it is a reasonably complex piece of software, it is easy to install and upgrade. While there are different things that ...
How does Mulesoft Anypoint API Manager compare with Amazon API Gateway?
I have found that Mulesoft Anypoint API Manager is the best integration tool out there for API management. It is easy to implement and learn; it provides several options for deployment, (including ...
What is your experience regarding pricing and costs for Mulesoft Anypoint API Manager?
When it comes to pricing, I find it always expensive. The pricing is high, which is the biggest point where some customers are hesitant about adopting it, and their deployment strategy is also more...
 

Also Known As

Vordel Application Gateway, Axway API Management Plus, Axway API Management, AMPLIFY API Management
Anypoint API Manager
 

Overview

 

Sample Customers

Engie Group, Allianz
Coca-Cola, Splunk, Citrix, UCSF, Vertu, State of Colorado, National Post, TiVo, Deakin, LLS, Oldcastle Precast, ParcelPoint, Justice Systems, Ube, Sumitomo Corporation, PacificComp, University of Witwatersrand, Groupe Initiatives, Camelot, Panviva
Find out what your peers are saying about Axway AMPLIFY API Management vs. MuleSoft API Manager and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.