SwaggerHub vs webMethods API Gateway comparison

Cancel
You must select at least 2 products to compare!
Comparison Buyer's Guide
Executive Summary

We performed a comparison between SwaggerHub and webMethods API Gateway based on real PeerSpot user reviews.

Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed SwaggerHub vs. webMethods API Gateway Report (Updated: March 2024).
765,234 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"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.""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.""The product's initial setup phase was easy and not at all difficult.""It is a stable solution.""The tool's most valuable feature is licensing.""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.""The scalability is endless."

More SwaggerHub Pros →

"This solution has given us a competitive advantage because we have better automation and insight.""The cloud version of the solution is very easy to set up.""I like the solution's policies, transformation, mediation, and routing features.""The developer portal is a valuable feature.""In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature.""It's a good tool, and it has a stable messaging broker.""The most valuable aspect of this solution for me has been the configuration-based UI. Once you get the hang of it, it enables you to easily develop an API. In addition, it has many in-built policies that are quite handy.""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."

More webMethods API Gateway Pros →

Cons
"SwaggerHub could be improved with better integration for tools.""We have to use additional tools to test APIs.""It could be more intuitive compared to one of its competitors.""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.""SwaggerHub's UI needs to be improved as it looks very old school.""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.""More integration and usability with the cloud microservices would be nice""It has limited functionality...Unfortunately, some of its features are not what we need."

More SwaggerHub Cons →

"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.""It is an expensive solution and not very suitable for smaller businesses.""With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved.""Understanding the overall architecture is difficult.""There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere.""They should develop clear visibility for the onboarding.""The price has room for improvement.""In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."

More webMethods API Gateway Cons →

Pricing and Cost Advice
  • "It has a yearly subscription, but I am not sure."
  • "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 tool is cheap."
  • More SwaggerHub Pricing and Cost Advice →

  • "I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."
  • "This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."
  • "The price is high and I give it a five out of ten."
  • "The product is very expensive."
  • More webMethods API Gateway Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which API Management solutions are best for your needs.
    765,234 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:The tool's most valuable feature is licensing.
    Top Answer:We have to use additional tools to test APIs.
    Top Answer:The company I work for purchased SwaggerHub with the intent to use it for a certain period of time. I use SwaggerHub in my company for testing purposes, especially testing the APIs.
    Top Answer:What I like the most about the solution is that it comes with ready-made tools like handling security tokens and OAuth.
    Top Answer:It is an expensive solution and not very suitable for smaller businesses.
    Top Answer:One area for improvement in webMethods API Gateway is orchestration. Currently, API Gateway lacks built-in orchestration capabilities, so organizations may need to rely on other applications for this… more »
    Ranking
    13th
    out of 64 in API Management
    Views
    4,039
    Comparisons
    3,109
    Reviews
    5
    Average Words per Review
    286
    Rating
    7.6
    12th
    out of 64 in API Management
    Views
    1,608
    Comparisons
    979
    Reviews
    6
    Average Words per Review
    601
    Rating
    7.8
    Comparisons
    Learn More
    Overview

    SwaggerHub is an integrated API Development platform, built for teams, that brings the core capabilities of the Swagger framework to design, build, document and deploy APIs. SwaggerHub enables development teams to collaborate and coordinate the entire lifecycle of an API with the flexibility to integrate with the toolset of your choice.

    Once your APIs are “out there,” hackers have a “way in” to your business. Lock that door! Protect your data, applications—even your company’s reputation—with robust API runtime security. The right API gateway will keep out wrong-doers and welcome only authorized consumers.

    With cybercrime costs surging to $2 trillion by 2019, look for the most impermeable API gateway you can find. You’ll need basic security features, like authentication, authorization, digital encryption and digital signatures. You’ll get that with Software AG’s end-to-end API management solution—and another lock on top.

    Our webMethods API Gateway uses reverse invoke, or inside-out, service invocations. This protective technique reduces the need to open holes in your firewall. It’s one more way we help you lock down your APIs—and protect your business from malicious attacks.

    Sample Customers
    Sonic, Zuora, Woolworths, CrowdFlower
    Information Not Available
    Top Industries
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company14%
    Government8%
    Manufacturing Company6%
    VISITORS READING REVIEWS
    Computer Software Company15%
    Financial Services Firm14%
    Retailer13%
    Government7%
    Company Size
    REVIEWERS
    Small Business38%
    Large Enterprise63%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise14%
    Large Enterprise69%
    REVIEWERS
    Small Business14%
    Midsize Enterprise14%
    Large Enterprise71%
    VISITORS READING REVIEWS
    Small Business15%
    Midsize Enterprise11%
    Large Enterprise74%
    Buyer's Guide
    SwaggerHub vs. webMethods API Gateway
    March 2024
    Find out what your peers are saying about SwaggerHub vs. webMethods API Gateway and other solutions. Updated: March 2024.
    765,234 professionals have used our research since 2012.

    SwaggerHub is ranked 13th in API Management with 8 reviews while webMethods API Gateway is ranked 12th in API Management with 9 reviews. SwaggerHub is rated 7.8, while webMethods API Gateway is rated 8.0. The top reviewer of SwaggerHub writes "An easy-to-use solution for the entry point of API documentation that needs to introduce some regulatory controls". On the other hand, the top reviewer of webMethods API Gateway writes "We developed several services in the cloud using a sandbox environment for our last hackathon". SwaggerHub is most compared with Microsoft Azure API Management, Apigee, MuleSoft Anypoint API Manager, Amazon API Gateway and RapidAPI, whereas webMethods API Gateway is most compared with Apigee, webMethods.io Integration, Kong Enterprise, webMethods Microgateway and CentraSite. See our SwaggerHub vs. webMethods API Gateway report.

    See our list of best API Management vendors.

    We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.