TIBCO iProcess Suite vs webMethods.io comparison

"It's very simple to use and the integration features between Java and other services within the workflow are very easy."

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

"​Broker and UM are the best features."

"The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy."

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

"I like the solution's policies, transformation, mediation, and routing features."

"My impression of webMethods.io's drag-and-drop interface to design workflows is actually amazing."

"The most valuable feature is stability."

"It's very flexible and a good platform to use."

"Our customers and developers have complained that the UI is a little bit confusing."

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

"Support is expensive."

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."

"The licensing cost is high compared to other options."

"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."

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

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

"In terms of scale, I would give it a four out of 10."

"The price could definitely be lower."

"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."

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

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

"It is worth the cost."

"The solution's development license is free for three to six months. We have to pay for other things."

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

"Initialy good pricing and good, if it comes to Enterprise license agreements."

"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."