No more typing reviews! Try our Samantha, our new voice AI agent.

Layer7 API Management vs SwaggerHub comparison

Why PeerSpot?
 

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

Layer7 API Management
Ranking in API Management
19th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
112
Ranking in other categories
No ranking in other categories
SwaggerHub
Ranking in API Management
9th
Average Rating
7.8
Reviews Sentiment
6.4
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the API Management category, the mindshare of Layer7 API Management is 1.9%, down from 2.5% compared to the previous year. The mindshare of SwaggerHub is 2.0%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
SwaggerHub2.0%
Layer7 API Management1.9%
Other96.1%
API Management
 

Featured Reviews

Integration capabilities excel and support for varied platforms enhances communication across backend systems
We mainly use REST APIs, and the solution's integration capabilities are excellent. It allows communication with a number of back-end providers and data consolidation. The flexibility to develop APIs for various platforms, from front-end applications to ATM machines, is valuable. Code changes and migration are straightforward, and it supports identity and access management integration.
Coralia Popa - PeerSpot reviewer
Software Architect at Waters Corporation
Centralized API documentation has supported versioned collaboration across our teams
We have tried automated code generation several times, and I think maybe some people are still using it somewhere, but it is not something that we do as a consolidated practice. At some point, we were missing some tagging of the APIs, and we could not do that. We asked the provider, but I do not believe they added that kind of support. However, we somehow gave up a bit because we are now in the process of moving to different platforms ourselves, so most likely we are not going to invest in improving this integration with SwaggerHub or how we are using it. We will just keep it going for the platform we are leaving, and then because our focus is in a different place, we are not looking to change or do other things. I am not using SwaggerHub's OpenAI management feature. We are not looking much at what they added new. We got some notification that they added things, but we have so many other things to do.

Quotes from Members

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

Pros

"The solution has numerous configuration options to increase security in communication."
"The Gateway is most important because it is our strategic front door into the company for all APIs."
"There are a few assertions which are built-in for threat protection. I have used them for vulnerabilities, like for DDoS attacks, XML schema validation, IP restriction, and for cross-domain."
"It has its own language, which make it possible to design and implement the complete flow using existing services and databases, and to create and aggregate fine-and coarse-grained APIs."
"The product, by itself, is great, and the flexibility that CA has given us out of this product is really great."
"The built-in routing platform is the most valuable feature."
"It is a stable product."
"Scalability: API Gateway is easily scalable horizontally and managed easily."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"SwaggerHub is helping with team collaboration, as all the people now know the link, they just go there and get the information they need, and it is really a documentation tool for sharing documentation information about the API we support."
"The best feature that SwaggerHub offers is the collaboration capability that helps us the most across all of our teams, as we have a single API infrastructure but several teams working in different areas of these APIs."
"Since I started using SwaggerHub, it has had a positive impact on our organization due to better collaboration between developers and the quality assurance team, and it has reduced errors because of its automated validation."
"The tool's most valuable feature is licensing."
"Normally, they publish their APIs on SwaggerHub for seamless integration with SmartBear and ReadyAPI, which allows us to perform detailed end-to-end automation testing."
"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

"We'd like to see an updated migration tool. Right now, the migration process works but it is a little clunky because there's not a good tool for migrating it."
"As the number of instances increases, its complexity of installation increases if you do not use the OVA."
"Broadcom's technical support team needs improvement."
"Patching/upgrading is a manual process and should be automated."
"Layer7 API Management should give a clear roadmap of the product and where it is going, and they should not change the underlying layers."
"Following Layer7's acquisition of Broadcom, the technical support and sales teams have not been good and both those areas need to be improved."
"There is a need to automate the process of retrieving the SSL certificate when it has expired. Currently, the product doesn't have this feature automated."
"Based on a lot of the other tools in the marketplace, the user interface itself is more linear and programmatic based."
"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."
"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."
"It could be more intuitive compared to one of its competitors."
"At some point, we were missing some tagging of the APIs, and we could not do that."
"More integration and usability with the cloud microservices would be nice."
"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."
 

Pricing and Cost Advice

"Pricing for Layer7 API Management is excellent, so it's an eight out of ten. The product is less expensive than other solutions. Layer7 API Management charges you based on the number of transactions, so the enterprise-level pricing my company got was excellent."
"The price of Layer7 API Management is reasonable compared to Apigee."
"For what we are after, the pricing is okay. It is competitive."
"Keep in mind the non-product licensing, e.g., if you opt not to use the embedded SQL."
"The price of Layer7 API Management is too high and should be reduced. However, it is a good solution in the market."
"Purchase 4.0 now and wait until they flush out the 4.1 problems."
"I feel that it is costly for medium-sized companies."
"This solution is a bit more expensive than competitors."
"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.
921,665 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
14%
Construction Company
11%
Financial Services Firm
10%
Manufacturing Company
8%
Financial Services Firm
12%
Manufacturing Company
12%
Outsourcing Company
11%
Comms Service Provider
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise13
Large Enterprise84
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise9
 

Questions from the Community

What is your experience regarding pricing and costs for Layer7 API Management?
Pricing is more than average. While I am used to Layer7 API Management ( /products/layer7-api-management-reviews ), seeing other products makes the tool's pricing seem high.
What needs improvement with Layer7 API Management?
Broadcom's push for upgrades from version nine to ten, ten to 10.3, and onwards to twelve needs improvement in migration processes, especially with service dependencies. The migration path some...
What is your primary use case for Layer7 API Management?
I am not the client. I implement Layer7 API Management ( /products/layer7-api-management-reviews ) for the clients. I have worked on multiple projects as a developer, implementing for Hydro Tasmani...
What needs improvement with SwaggerHub?
SwaggerHub can be improved since the API testing features are limited compared to Postman, and it is somewhat expensive for small teams as paid plans cost a lot.
What is your primary use case for SwaggerHub?
My main use case for SwaggerHub is to design and review API specifications, as I test endpoints with the help of Swagger UI, validate the request and the response schemas, and share the API documen...
What advice do you have for others considering SwaggerHub?
Before using SwaggerHub, I advise having basic API knowledge, as those with API knowledge can easily use SwaggerHub. I would rate this review an eight out of ten.
 

Also Known As

CA API Management, CA Live API Creator, Espresso Logic, CA API Gateway
No data available
 

Overview

 

Sample Customers

1. IBM  2. Microsoft  3. Oracle  4. Salesforce  5. SAP  6. Cisco  7. Dell  8. HP  9. Adobe  10. VMware  11. Accenture  12. Capgemini  13. Deloitte  14. PwC  15. Ernst & Young  16. Infosys  17. TCS (Tata Consultancy Services)  18. Wipro  19. Cognizant  20. HCL Technologies  21. Tech Mahindra  22. Fujitsu  23. Hitachi  24. NEC  25. NTT Data  26. Ericsson  27. Nokia  28. Siemens  29. AT&T  30. Verizon  31. Vodafone  32. Orange
Sonic, Zuora, Woolworths, CrowdFlower
Find out what your peers are saying about Layer7 API Management vs. SwaggerHub and other solutions. Updated: November 2026.
921,665 professionals have used our research since 2012.