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

"Application integrations are offered out-of-the-box, and that is extremely important to us. This is one of the main use cases that we have for it. It is about 60 to 70 percent of the workload in our application today."

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

"It's easy to construct new interfaces like apps and client portals."

"webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization."

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

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

"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."

"Operationally, I consider the solution to be quite good."

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

"On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with."

"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."

"In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."

"The product must add more compatible connectors."

"webMethods Integration Server needs to add more adapters."

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

"It could be more user-friendly."

"The configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."

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

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

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

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

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

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

"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."