CentraSite vs webMethods.io comparison

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

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

"webMethods Integration Server is an easy-to-use solution and does not require a lot of coding."

"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."

"It’s fairly easy to view, move, and mange access across different components. Different component types are categorized and can be viewed in a web based administration console."

"Ease of implementation and flexibility to hold the business logic are the most valuable features."

"Application integration, business process integration, and B2B partner integration are valuable. But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed."

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

"The product supports various types of digital documents, including XMLs and EDI."

"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 product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution."

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

"webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience."

"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 solution should include REST API calls."

"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."

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

"Need to see more API portal features like monetizing APIs and private cloud readiness."

"It's a good deal for the money that we pay."

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

"webMethods Integration Server is expensive, and there's no fixed price on it because it has a point pricing model. You can negotiate, which makes it interesting."

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

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

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

"Some who consider this solution often avoid it due to its high price."

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