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

Axway AMPLIFY API Management vs webMethods.io 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
14
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in API Management
16th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
94
Ranking in other categories
Business-to-Business Middleware (6th), Enterprise Service Bus (ESB) (5th), Managed File Transfer (MFT) (13th), Cloud Data Integration (11th), Integration Platform as a Service (iPaaS) (11th)
 

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 webMethods.io is 2.7%, up from 2.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
webMethods.io2.7%
Axway AMPLIFY API Management1.6%
Other95.7%
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.
YM
Developer at a hospitality company with 1,001-5,000 employees
Offers strong integration capabilities and reliable features but needs pricing and scaling improvements
Many things are evolving with the AI buzz in the market. What I would like to see improved or enhanced in webMethods.io in the future is that since webMethods.io is already under IBM, I think IBM will introduce and integrate AI into it. Additionally, regarding what webMethods.io can improve is the license cost. Other cloud players are also providing the same kind of functionality, such as AWS and Azure. webMethods.io is being installed on-premises, but AWS is providing it directly in the cloud. When comparing the license cost and request per minute cost, webMethods.io needs to address that. There are many competitors in the market for this.

Quotes from Members

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

Pros

"The UI and UX are quite good and easy to understand."
"We like the portal for documentation a lot."
"Its flexibility allows us to adapt to different scenarios."
"We like the portal for documentation a lot."
"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."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"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 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."
"Product is easy to use and work on, very interesting and very helpful."
"We needed a tool that was able to orchestrate and help us configure our APIs so that we could maintain and see the heartbeat, traffic, trends, etc."
"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."
"Operationally, I consider the solution to be quite good."
"Overall, it's a really good product."
"The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)"
"It is good for communicating between the systems and for publishing and subscribing."
"It has a good integration server, designer, and a very good API portal."
 

Cons

"The portal still has room for improvement."
"Areas of improvement include marketing and enhancing the data products area by using ETIs."
"The product shows a lack of maturity. The setup is difficult, the tech support and community are lacking, and it is not very stable."
"Ultimately, from a very high-level overview, cloud platforms or Kong could have a slight advantage when compared to Axway AMPLIFY API Management."
"Team management capabilities could be improved."
"I think that the program's team management capabilities can be better as far as working in groups."
"We sometimes have issues with some of the functions because they do not work very well."
"Axway's queuing messages could be enhanced."
"This solution could be improved by offering subscription based licensing."
"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."
"Regarding the stateful session inbound to ESB (Integration Server), it seems that the stateful session sometimes doesn't die out when the transaction is finished, but waits until the timeout expires (although quite often it doesn't even die after the timeout expires, which eventually would flood the server)."
"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."
"They keep producing new versions at a rate that we cannot keep up with. That is a problem for us because they have a very small set of supported versions."
"Rapid application development has to be considered, especially for UI, where user interference is crucial."
"There should be better logging, or a better dashboard, to allow you to see see the logs of the services."
"I would like to see the price improve."
 

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."
"webMethods.io Integration's pricing is high and has yearly subscription costs."
"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."
"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."
"The price is high and I give it a five out of ten."
"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."
"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."
"It's a good deal for the money that we pay."
"It is a cost-effective solution."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
893,244 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
13%
Government
8%
Insurance Company
7%
Manufacturing Company
13%
Financial Services Firm
11%
Computer Software Company
9%
Comms Service Provider
5%
 

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 Business23
Midsize Enterprise11
Large Enterprise64
 

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 webMethods Integration Server?
The alignment of on-premise and cloud versions needs improvement.
What needs improvement with webMethods Trading Networks?
Many things are evolving with the AI buzz in the market. What I would like to see improved or enhanced in webMethods.io in the future is that since webMethods.io is already under IBM, I think IBM w...
What is your primary use case for webMethods Trading Networks?
I use webMethods.io primarily for the integration of APIs. Could you please describe a few use cases for it?
 

Also Known As

Vordel Application Gateway, Axway API Management Plus, Axway API Management, AMPLIFY API Management
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Engie Group, Allianz
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Axway AMPLIFY API Management vs. webMethods.io and other solutions. Updated: April 2026.
893,244 professionals have used our research since 2012.