OpenText MBPM vs webMethods.io comparison

"Not just the solution's automation capabilities, but we like everything about it since we are more of a system integrator."

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

"I like the tool's scalability."

"The most valuable feature of webMethods Integration Server is all the capabilities it provides. We leverage most of the features, that they have offered to us. Our vendor has made some additional features on top of the webMethods Integration Server and we use all the features together."

"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."

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

"High throughput and excellent scalability."

"The most valuable feature of the webMethods Integration Server is the built-in monitoring, auditing, RETS, and SOAP services."

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

"The user interface could be better in OpenText MBPM."

"There are shortcomings in the solution's support and documentation part."

"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."

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

"Other products have been using AI and cloud enhancements, but webMethods Integration Server is still lagging in that key area."

"The price should be reduced to make it more affordable."

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

"This solution could be improved by offering subscription based licensing."

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

"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."

"On a scale of one to ten, where one is cost-efficient, and ten is expensive, I rate the pricing somewhere between nine and ten since it is a costly solution."

"There is an annual license to use OpenText MBPM."

"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."

"Some of the licensing is "component-ized," which is confusing to new users/customers."

"I am not involved in the licensing side of things."

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

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

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

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

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