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

OpenLegacy vs SwaggerHub 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

OpenLegacy
Ranking in API Management
35th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
No ranking in other categories
SwaggerHub
Ranking in API Management
14th
Average Rating
7.8
Reviews Sentiment
7.2
Number of Reviews
10
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the API Management category, the mindshare of OpenLegacy is 0.3%, up from 0.2% compared to the previous year. The mindshare of SwaggerHub is 1.3%, down from 1.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

reviewer1042905 - PeerSpot reviewer
The biggest advantage is how simple the technology was.
I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be. OpenLegacy handles the bread-and-butter TP monitoring stuff, but I am working for one of the six banks in the United States still using the Hogan mainframe, which has a slightly proprietary mechanism. But OpenLegacy currently doesn't have a connector for Hogan. So it would help if they could build one. That would appeal to financial institutions that still use Hogan, like US Bank, Wells Fargo, KeyBank, and Vanguard.
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.

Quotes from Members

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

Pros

"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"The biggest advantage of OpenLegacy was how simple the technology was. We were able to build out the OpenLegacy parts very quickly. We put together a couple hundred APIs in six months."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
"Opens the door to connect modern web products to an old legacy system."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
"It is a stable solution."
"The product's initial setup phase was easy and not at all difficult."
"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."
"I rate the solution's stability a ten out of ten."
 

Cons

"Debugging and logging for programmers could be better."
"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."
"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"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 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."
"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."
"SwaggerHub's UI needs to be improved as it looks very old school."
"It could be more intuitive compared to one of its competitors."
"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"
"We have to use additional tools to test APIs."
 

Pricing and Cost Advice

"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"The tool is cheap."
"It has a yearly subscription, but I am not sure."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
847,625 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
33%
Insurance Company
14%
Computer Software Company
10%
Manufacturing Company
8%
Financial Services Firm
21%
Computer Software Company
14%
Retailer
7%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
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...
 

Comparisons

 

Overview

 

Sample Customers

Many of openLegacy's global customers are among the Global 100 companies. Review case studies in these industries: Agriculture, Airport Authority, Automotive, Auto, Finance, Insurance, Government, Healthcare, Manufacturing, and Retailwww.openlegacy.com/case-studie...
Sonic, Zuora, Woolworths, CrowdFlower
Find out what your peers are saying about OpenLegacy vs. SwaggerHub and other solutions. Updated: March 2025.
847,625 professionals have used our research since 2012.