Cleo Integration Cloud Platform vs webMethods.io comparison

"The most valuable feature of the solution is the ease of use it provides. Cleo Integration Cloud Platform is a straightforward and simple product."

"ActiveTransfer lets us maintain the file in the staging area before we transfer it. After that, we can remove the file to make sure that the reconciliation process is done. Sometimes we will zip and unzip the files, but if we have a GKB file, we often ignore it."

"One valuable feature is that it is event-driven, so when new data is available on the source it can be quickly processed and displayed. Integration is definitely another useful feature, and B2B is one area where webMethods has its own unique thing going, whereby we can do monitoring of transactions, monitoring of client onboarding, and so on."

"The tool supports gRPC."

"webMethods.io is a comprehensive box that provides multiple functionalities; I appreciate it because we can integrate many applications and any kind of API we want to integrate."

"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."

"EDI is robust and integration with SAP is good."

"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."

"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."

"Currently, the solution fails to provide users with additional protocol assistance and API integrations, so the aforementioned areas need to be considered for improvement."

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

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

"I would like the solution to provide bi-weekly updates."

"I would like to see the price improve."

"webMethods Integration Server needs to add more adapters."

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

"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 patching of infrastructure is not very smooth and improved authentication should be added in the next feature."

"I learned that the product's price is reasonable based on the interactions I had with my company's purchase team."

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

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

"I would like to see better pricing for the license."

"The solution's development license is free for three to six months. We have to pay for other 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."

"It is worth the cost."

"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."

"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."