Try our new research platform with insights from 80,000+ expert users

SwaggerHub vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

SwaggerHub
Ranking in API Management
15th
Average Rating
7.8
Reviews Sentiment
7.2
Number of Reviews
10
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in API Management
9th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
93
Ranking in other categories
Business-to-Business Middleware (3rd), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (9th), Cloud Data Integration (7th), Integration Platform as a Service (iPaaS) (5th)
 

Mindshare comparison

As of July 2025, in the API Management category, the mindshare of SwaggerHub is 1.4%, up from 1.3% compared to the previous year. The mindshare of webMethods.io is 2.4%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

SwaminathanSubramanian - PeerSpot reviewer
Facilitating enterprise-wide API governance and management
Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account. The scalability also needs enhancement, as it becomes flaky under increased load. Additionally, the versioning management could be improved to be on par with source code management tools.
MohanPrasad - PeerSpot reviewer
Smooth integration and enhanced deployment with high licensing cost
webMethods.io was used to integrate APIs through the webMethods.io platform, trigger database events, and connect backend APIs through a Java backend. It was used extensively for integration purposes in my organization Integration became smoother, troubleshooting was easier, and deployment and…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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."
"It is a stable solution."
"I rate the solution's stability a ten out of ten."
"The product's initial setup phase was easy and not at all difficult."
"The tool's most valuable feature is licensing."
"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."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use."
"We have found the pricing of the solution to be fair."
"It is a bundled product stack for A2A and B2B usage. It is one of the best products which I have used during my integration career."
"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."
"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."
"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."
"My impression of webMethods.io's drag-and-drop interface to design workflows is actually amazing."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
 

Cons

"We have to use additional tools to test APIs."
"Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account."
"The scalability aspect of SwaggerHub can be improved. It becomes a bit unreliable when the load is increased and isn't up to par with expectations for scalability."
"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'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."
"More integration and usability with the cloud microservices would be nice"
"It could be more intuitive compared to one of its competitors."
"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."
"The solution should include REST API calls."
"Scalability and connectors to different cloud applications is lacking."
"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."
"The price has room for improvement."
"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."
"The price should be reduced to make it more affordable."
"This is a great solution and the vendor could improve the marketing of the solution to be able to reach more clients."
 

Pricing and Cost Advice

"It has a yearly subscription, but I am not sure."
"The tool is cheap."
"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."
"This is an expensive product and we may replace it with something more reasonably priced."
"It is a cost-effective solution."
"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."
"The solution's development license is free for three to six months. We have to pay for other things."
"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
"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."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
861,390 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
14%
Retailer
7%
Government
6%
Financial Services Firm
13%
Computer Software Company
13%
Manufacturing Company
13%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about SwaggerHub?
The tool's most valuable feature is licensing.
What needs improvement with SwaggerHub?
Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account....
What is your primary use case for SwaggerHub?
I started using SwaggerHub in its previous version, SmartMiner, with a tool called SoapUI. I used it to create mock web services to test web services and create test scripts and mock APIs. This usa...
What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
 

Also Known As

No data available
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

Sonic, Zuora, Woolworths, CrowdFlower
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about SwaggerHub vs. webMethods.io and other solutions. Updated: June 2025.
861,390 professionals have used our research since 2012.