Axway AMPLIFY Application Integration vs webMethods.io comparison

"Axway AMPLIFY Application Integration is very easy to use."

"The product is robust."

"The most valuable feature is that API Gateway is extremely flexible for any feature, such as connecting to Active Directory to pull the users and their authentication information. There are three ways to connect to Active Directory, and the reason for this is that the computing environments of our customers are very different. Every feature in API Gateway has got multiple methodologies for accomplishing those tasks, which is important because customers are constantly changing their security models, IT models, networks, etc. API Gateway is very flexible. It is not a one size fits all sort of situation where it is very rigid, and you can only use these pull-down menus, and that's all it ever does. It is much more open than that. It can give you fabulous reports on your users, usage, security issues, and the data sets that are going through there. You'll suddenly have visibility on the movement of data within or between your organization and other organizations. The other thing is that you're connecting API to API, which is machine to machine. The things that were done manually in an Excel spreadsheet before exchanging data through email are now done machine to machine and server to server. It speeds up the velocity of your business."

"Axway AMPLIFY Application Integration is quite a stable solution."

"Operationally, I consider the solution to be quite good."

"webMethods API Portal is overall very valuable. It is now a comprehensive API catalogue that serves various purposes, including API assessment and evaluation."

"What I like best about webMethods Integration Server is its portfolio of connectors."

"The most valuable feature of the webMethods Integration Server is the built-in monitoring, auditing, RETS, and SOAP services."

"It's easy to construct new interfaces like apps and client portals."

"The Software AG Designer has been great. It's very intuitive."

"The performance is good."

"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."

"The most important point to improve is the capability to deploy in large enterprises."

"Axway AMPLIFY Application Integration is an expensive solution."

"Because it is so flexible, you really need someone who knows Axway Gateway or has been through the training and is certified. Just because you know APIs doesn't mean you're going to walk into that API Gateway and understand what to click on. If you're going to get something done quickly, you need to find an engineer from a company who has some experience with it. It is easy to learn, but if you're doing on-the-job training, it is going to take you longer to get your project accomplished."

"The product must improve its visibility and scalability."

"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."

"Need to see more API portal features like monetizing APIs and private cloud readiness."

"The deployment should be simplified."

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."

"The licensing cost is high compared to other options."

"Support is expensive."

"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."

"Prices should be reduced, ideally by up to 30% for long-term customers like us."

"API Gateway is priced on the number of transactions you run through it. API Gateway is free, and you can install as many API Gateways as you like or are necessary for your network. For example, if all of the data is inside your network or firewall, you may just need one API Gateway. If you have external customers trying to come into your organization through your firewall, you're going to need one API Gateway outside the firewall and one inside the firewall. If you have a lot of remote offices, you may want to put API Gateway in some of those offices as well. They only charge you for your usage of it. In other words, the number of transactions going through it. That's a good benefit."

"The product is not expensive."

"Users need to pay an annual licensing fee for the solution."

"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."

"The product is expensive."

"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."

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."

"Its cost depends on the use cases."

"The vendor is flexible with respect to pricing."

"Some of the licensing is "component-ized," which is confusing to new users/customers."