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

"When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use."

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

"This solution has given us a competitive advantage because we have better automation and insight."

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

"We have a reusable code that we can replicate for any new interfaces."

"Ease of implementation and flexibility to hold the business logic are the most valuable features."

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

"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."

"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 price should be reduced to make it more affordable."

"At least in SAG Webmethods 8 there was no Data Value Repository tool that would allow to map values/codes from source (in our case HR portal) and transform that into target ERP codes (SAP and PeopleSoft)."

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

"Support is expensive."

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

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

"The interface needs some work. It is not very user-friendly."

"The product must add more compatible connectors."

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

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

"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."

"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 price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."

"Its cost depends on the use cases."

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

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