Try our new research platform with insights from 80,000+ expert users

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
16th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
12
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in API Management
10th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
92
Ranking in other categories
Business-to-Business Middleware (3rd), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Mindshare comparison

As of April 2025, in the API Management category, the mindshare of Axway AMPLIFY API Management is 1.5%, up from 1.3% compared to the previous year. The mindshare of webMethods.io is 2.1%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Sudhanshu Singh - PeerSpot reviewer
We get stability, scalability, and security
Axway provides good documentation that newcomers can easily follow, but I believe the initial setup would be tough for someone new. Experienced employees know where everything is and how to do their job, so it would be difficult for a new hire to get up to speed. For an experienced person, I give the initial setup a ten out of ten. Deployment can be considered a hundred lines of code and some a thousand lines. For a simple deployment, it takes 10-15 seconds. And if the environment connectivity is good enough to respond and there is some heavy code that is being deployed, it takes around 30-60 seconds max, if we are referring to the cloud, where the connectivity for the long duration of the calls is there. The total deployment time is one minute to finish up. From the industrial point of view, Europe has a major chunk of users followed by, the US, and then Australia or the Asia-Pacific region.
Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.

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 features are security enforcement and throttling."
"The best feature of Axway Amplify API Management is its exceptional level of security, which is highly reassuring, coupled with its remarkable capacity to handle substantial volumes of data in impressively efficient turnaround times."
"This product is a ten when it comes to API management."
"In general, API governance provides a better experience for providers."
"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."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"The administration tool for this solution is good."
"The API portal capability is a valuable feature."
"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."
"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."
"The product is very stable."
"It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console."
"It's a good tool, and it has a stable messaging broker."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
"The product supports various types of digital documents, including XMLs and EDI."
"Operationally, I consider the solution to be quite good."
 

Cons

"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."
"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 portal still has room for improvement."
"In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better."
"It would be great if they have an asset report. It's hard to get support for that."
"Team management capabilities could be improved."
"The interface needs some work. It is not very user-friendly."
"I would like the solution to provide bi-weekly updates."
"The deployment should be simplified."
"Prices should be reduced, ideally by up to 30% for long-term customers like us."
"The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
"The logging capability has room for improvement. That way, we could keep a history of all the transactions. It would be helpful to be able to get to that without having to build a standalone solution to do so."
"Rapid application development has to be considered, especially for UI, where user interference is crucial."
 

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."
"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."
"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
"This is an expensive product and we may replace it with something more reasonably priced."
"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."
"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."
"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."
"Its cost depends on the use cases."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
844,944 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
18%
Insurance Company
8%
Manufacturing Company
7%
Financial Services Firm
14%
Computer Software Company
13%
Manufacturing Company
13%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Axway AMPLIFY API Management?
In general, API governance provides a better experience for providers.
What is your experience regarding pricing and costs for Axway AMPLIFY API Management?
The solution has a yearly subscription. The solution’s pricing is competitive. Axway makes a significant impression compared to its peers, especially with a sensitive budget. In many instances, it ...
What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
 

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: March 2025.
844,944 professionals have used our research since 2012.