SwaggerHub vs webMethods.io comparison

"The scalability is endless."

"You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs."

"The product's initial setup phase was easy and not at all difficult."

"The tool's most valuable feature is licensing."

"Code generation is one of the important features of SwaggerHub. We design our API, and we can generate a very rich codebase and add to it. The code generation feature is very valuable."

"It is quite a useful tool. It is quite good with the validation of the spec. It works quite well in terms of errors and conformity to the OpenAPI standard. It is better than Visual Studio Code in terms of editing."

"I rate the solution's stability a ten out of ten."

"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."

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

"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."

"The Software AG Designer has been great. It's very intuitive."

"With webMethods, the creation of servers and the utilization of Trading Networks facilitate B2B integration. It resolves any related issues effectively."

"webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization."

"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."

"We have a reusable code that we can replicate for any new interfaces."

"Operationally, I consider the solution to be quite good."

"It could be more intuitive compared to one of its competitors."

"SwaggerHub's UI needs to be improved as it looks very old school."

"It has limited functionality...Unfortunately, some of its features are not what we need."

"SwaggerHub lacks in terms of integrations. They have APIs integrated, and they also have some connectors, but they don't have integration with many of the things that we use. For example, for connecting with SVN, we had to implement external scripts. So, they should work on the integration because currently, we have to work on the integration with our DevOps, continuous delivery, or continuous deployment. It would be great if these integrations are built-in. Mainly, we would like it to integrate with SVN and Jira."

"More integration and usability with the cloud microservices would be nice"

"We have to use additional tools to test APIs."

"The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism. They support some comments, but it is really hard to manage those comments. We would like to use the full request. Therefore, we are now looking to integrate with repositories. It has integration with Bitbucket and GitHub, but we have some internal constraints, and we need to move some of the repositories to GitHub. Our source code is on-premise in Bitbucket, and it was a bit of a problem for us to integrate. Now we are transitioning our repositories to GitHub, and hopefully, we can enable the integration. This will probably solve the problem with the review and approval. Its customization should also be improved. There are limitations around the support for the developer portal. There should be more customization options for the website that you can use as a developer portal. Currently, it has only Swagger UI with minimal customization. You cannot actually add additional pages and documentation for explaining concepts and general things. That's why we have started to look around to see what other tools are doing. They should also allow tagging on the API. We would like to add some tagging on the API to reflect certain things. Currently, any metadata that you would like to have has to be a part of the spec. You cannot do anything else. It should also have support for Open API 3.1, which was released at the beginning of the year. It would be great to be able to switch to that."

"SwaggerHub could be improved with better integration for tools."

"They should develop clear visibility for the onboarding."

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

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."

"The installation process should be simplified for first time users and be made more user-friendly."

"The price has room for improvement."

"In terms of scale, I would give it a four out of 10."

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

"On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with."

"It has a yearly subscription, but I am not sure."

"The tool is cheap."

"The management considers it a bit expensive. At first, we wanted to purchase a license for 100 users, but we went for a license for only 15 users. Its cost is $10,220 per year."

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

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

"The price is high and I give it a five out of ten."

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

"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 solution’s pricing is too high."

"The pricing is a yearly license."

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