WSO2 API Manager vs webMethods.io comparison

"It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things."

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

"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."

"The messaging part is the most valuable feature."

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

"What I like best about webMethods Integration Server is its portfolio of connectors."

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

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

"The main feature — the publication of the API, the management section — is great in general."

"Based on the information I have, the solution's most valuable feature is its capability of implementing custom solutions."

"I think the best part about WSO2 API Manager is that it's highly customizable because it's open-source. The partnership model is quite lucrative for us, it helps us to go and pitch to our customers. You can build a lot of business models yourself that you want to use. You are able to do a lot of the solutions."

"It is a scalable solution because it can be scaled horizontally and vertically."

"WSO2 is very stable."

"Its open-source features are very good, especially for your production work."

"WSO2 API Manager is easy to use."

"The solution is open source and easy to configure."

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

"It is quite expensive."

"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."

"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."

"There should be better logging, or a better dashboard, to allow you to see see the logs of the services."

"Technical support is an area where they can improve."

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

"webMethods Integration Server needs to add more adapters."

"The interface needs to be modernized and made more user friendly so the product continues to have a growing community of users."

"I would like it to be a more convenient development platform with the ability to write orchestrations and so on. Our problem with this product is that in my country, we are the only enterprise that has been using this product. We're missing a lot of knowledge from colleagues to consult with, and we also aren't able to recruit people with relevant skills. It is a big problem. The small team that is maintaining this product is the only team that can actually relate to any technical issue. The support that we're getting from the company is not great. There is also a cultural gap there because they're from Sri Lanka, and it is not easy. They're putting in a lot of effort, but they are not meeting our expectations."

"The solution could be more user friendly for engineers."

"Integration is an area that needs to be improved."

"I would like to see improvements in the speed of the solution as it can be a bit slow compared to other platforms along with addressing memory issues would be beneficial."

"The product hasn’t been updated for some time."

"The solution’s interface should be more user-friendly."

"The pricing models offered by WSO2 API Manager could be more flexible and should offer different options so that more people can access them."

"The product is very expensive."

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

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

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

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

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

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

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

"The solution costs less than 20,000 euros a year. I'm not sure of the exact number."

"We use the open-source version of WSO2 API Manager, there is no cost."

"WSO2 API Manager is quite an expensive tool. I rate the product's pricing a nine on a scale of one to ten, where one is low and ten is high."

"For our projects, we found the pricing to be a little high."

"WSO2 API Manager is a low-cost solution. It is one of the most affordable solutions."

"I think the other competitors that are providing the same solution are quite expensive. WSO2 API Manager is quite cheap."

"There is a subscription-based pricing structure and also the open-sourced version available."

"As far as I'm aware, the costs are not minimal but satisfactory."