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
18th
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
9th
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) (9th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Mindshare comparison

As of May 2025, in the API Management category, the mindshare of Axway AMPLIFY API Management is 1.6%, up from 1.3% compared to the previous year. The mindshare of webMethods.io is 2.3%, up from 2.0% 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 feature of the solution is security."
"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."
"The API portal capability is a valuable feature."
"This product is a ten when it comes to API management."
"The administration tool for this solution is good."
"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."
"In general, API governance provides a better experience for providers."
"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."
"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."
"The development is very fast. If you know what you're doing, you can develop something very easily and very fast."
"The messaging part is the most valuable feature."
"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."
"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."
"The comprehensiveness and depth of Integration Servers' connectors to packaged apps and custom apps is unlimited. They have a connector for everything. If they don't, you can build it yourself. Or oftentimes, if there is value for other customers as well, you can talk with webMethods about creating a new adapter for you."
"The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation."
"I like the tool's scalability."
 

Cons

"Areas of improvement include marketing and enhancing the data products area by using ETIs."
"The API Mocking tools need to be improved."
"This solution does have some limitations regarding the deployment model."
"It would be great if they have an asset report. It's hard to get support for that."
"Sometimes we find bugs where certain calls are not returning all the data we need."
"The portal still has room for improvement."
"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 installation process is a bit complex and it could be a lot simpler."
"The price should be reduced to make it more affordable."
"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."
"webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience."
"The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. For how long"
"The certifications and learning resources are not exposed openly enough. For instance, they have a trial version which comes with only a few basic features, and I think that community-wise they need to offer more free or open spaces where developers can feel encouraged to experiment."
"Rules engine processes and BPM processes should be improved."
"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."
"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be 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."
"webMethods.io Integration's pricing is high and has yearly subscription costs."
"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."
"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."
"The pricing is a yearly license."
"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."
"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."
"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
18%
Insurance Company
8%
Government
8%
Computer Software Company
13%
Financial Services Firm
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: April 2025.
851,604 professionals have used our research since 2012.