Axway AMPLIFY Application Integration vs webMethods.io comparison

"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 very easy to use."

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

"The product is robust."

"All of the components are very independent but are tied together to give the business value."

"The core product can be used not only for automatic file transfers between applications, but also as an Enterprise Service Bus (ESB)."

"I like the stability of the webMethods Integration Server."

"The tool supports gRPC."

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

"The solution is scalable."

"The stability is good."

"Most of the work in our organization can be more easily done using the tool."

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

"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."

"As webMethods Integration Server is expensive, that's its area for improvement."

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

"The on-premises setup can be difficult."

"There should be better logging, or a better dashboard, to allow you to see see the logs of the services."

"webMethods Integration Server needs to add more adapters."

"The price has room for improvement."

"The learning curve is a little steep at first."

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

"The product is not expensive."

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

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

"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."

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

"The price is a little bit high, especially regarding their support."

"I am not involved in the licensing side of things."

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

"The solution’s pricing is too high."

"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."