CentraSite vs webMethods.io comparison

"The governance is powerful, and you can look up services very easily, which may reduce some development cycle time."

"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."

"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."

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

"The main assets are its flow language, debugging, and Broker. Flow language is far better and more flexible for debugging."

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

"The tool supports gRPC."

"It integrates well with various servers."

"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."

"The setup is mild. It's not so simple and not very difficult. You can make it happen with some configuration, but it's not easy for non-professional people."

"The high price of the product is an area of concern where improvements are required."

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

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

"The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."

"We got the product via a reseller, and the support from the reseller has been less than desirable."

"It is quite expensive."

"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."

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

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

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

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

"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 am not involved in the licensing side of things."

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

"The product is expensive."

"The vendor is flexible with respect to pricing."