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

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

"What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth."

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

"A product with good API and EDI components."

"The performance is good."

"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."

"How simple it is to create new solutions."

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

"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."

"I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance."

"They should develop clear visibility for the onboarding."

"webMethods Integration Server needs to add more adapters."

"Rules engine processes and BPM processes should be improved."

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

"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."

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

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

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

"Pricing is the number-one downfall. It's too expensive. They could make more money by dropping the price in half and getting more customers. It's the best product there is, but it's too expensive."

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

"This is an expensive product and we may replace it with something more reasonably priced."

"The product is expensive."

"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."

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