HiT Software DBMoto vs webMethods.io comparison

"DBMoto was very simple to set up and move our tables to the Oracle DB."

"The most valuable features are that is easy to install and it is user-friendly."

"The orchestration aspects of APIs, the integration capabilities, and the logging functionalities were the most critical features of our workflow."

"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."

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

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

"The cloud version of the solution is very easy to set up."

"It has a good integration server, designer, and a very good API portal."

"Pricing is an area that needs improvement."

"This product would be improved with additional built-in functions for simpler date conversion, as well as for data type transformations."

"The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. For how long"

"The deployment should be simplified."

"Support is expensive."

"The licensing cost is high compared to other options."

"webMethods.io Integration's installation is complex. It should also improve integration and connectors."

"As webMethods Integration Server is expensive, that's its area for improvement."

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

"The price has room for improvement."

"Customers pay a license fee yearly."

"I found the price to be quite reasonable."

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

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

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

"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."

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

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

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

"It is a cost-effective solution."