BizFlow vs webMethods.io comparison

"There are so many advantages. First things, like we have a seamless automation capability available here in BizFlow. Totally customizable, UI we can create, and the third-party integration is also achievable. Not with the in-built functionality, but with custom code and all, we can achieve that thing also."

"The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation."

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

"It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."

"The most valuable feature is stability."

"The tool supports gRPC."

"The developer portal is a valuable feature."

"A product with good API and EDI components."

"webMethods API Portal is overall very valuable. It is now a comprehensive API catalogue that serves various purposes, including API assessment and evaluation."

"Nintex provided an in-built functionality. Like integration-related things, so many service types are available. You just have to configure it. So, such kinds of things decrease the timing of development. So, it is missing in Bizflow."

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

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

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

"I would like to have a dashboard where I can see all of the communication between components and the configuration."

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

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

"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."

"The logging capability has room for improvement. That way, we could keep a history of all the transactions. It would be helpful to be able to get to that without having to build a standalone solution to do so."

"Pricing is a main concern for any organization, but some big organizations may find it affordable. For example, in Indian currency, it would be around 1,000 per license for a BizFlow license."

"There is a license needed to use the webMethods Integration Server."

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

"The pricing is a yearly license."

"It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one."

"The price is a little bit high, especially regarding their support."

"Sometimes we don't have a very clear idea what the licensing will entail at first, because it can be very customizable. On one hand, this can be a good thing, because it can be tailored to a specific customer's needs. But on the other hand it can also be an issue when some customer asks, "What's the cost?" and we can't yet give them an accurate answer."

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

"Most of my clients would like the price of the solution to be reduced."