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

"Segregation of deployment for the environments is the most valuable feature of the solution."

"The cloud version of the solution is very easy to set up."

"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."

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

"webMethods Trading Networks is a stable solution."

"webMethods Integration Server is an easy-to-use solution and does not require a lot of coding."

"The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)"

"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."

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

"The solution should include REST API calls."

"Support is expensive."

"The deployment should be simplified."

"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."

"One area that needs improvement is the version upgrade process. Many customers I've worked with encounter challenges when transitioning from their current version, such as x or 9, to a newer version. The process is not smooth, and they must shift their entire website."

"Some things could be improved, especially how ActiveTransfer handles third-party file transfers. It would be nice to have a native file-watching mechanism for when you're scheduling jobs with a third-party scheduler. Currently, we are using an outside file watcher solution to check the files before the file transfer. It checks the location to see if the file is there. If the file is there, it will prepare it for transfer. If the file isn't available, it will send an email it can create a ticket send it now. We recommended adding this file watcher mechanism."

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

"In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."

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

"There is a license needed to use the webMethods Integration Server."

"The pricing is a yearly license."

"Its cost depends on the use cases."

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

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

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

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

"The product is expensive."