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

"The product is robust."

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

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

"A product with good API and EDI components."

"We have found the pricing of the solution to be fair."

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

"It has a good integration server, designer, and a very good API portal."

"The stability is good."

"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."

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

"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."

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

"webMethods Integration Server needs to add more adapters."

"For code version control, you need to use some external software."

"webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience."

"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."

"Understanding the overall architecture is difficult."

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

"wM SAP Adapter User Guide - Example, like Message Broker setup was unclear, leading to issues during Testing and we had refer the internet forums to understand that there is a Message Broker Cleanup utility and that needs to be setup as well."

"This solution could be improved by offering subscription based licensing."

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

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

"The product is not expensive."

"The product is expensive."

"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."

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

"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."

"The product is very expensive."

"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."

"The price is high and I give it a five out of ten."

"Some who consider this solution often avoid it due to its high price."