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

Layer7 API Management 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

Layer7 API Management
Ranking in API Management
17th
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
14th
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 August 2026, in the API Management category, the mindshare of Layer7 API Management is 1.9%, down from 2.7% compared to the previous year. The mindshare of SwaggerHub is 1.8%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
SwaggerHub1.8%
Layer7 API Management1.9%
Other96.3%
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.
Manish Indupuri - PeerSpot reviewer
senior DevOps engineer at a tech services company with 10,001+ employees
Has streamlined API documentation and integration workflows across cross-functional teams
Documenting SwaggerHub has a standard and consistent structure of API definitions, and it automatically generates interactive documentation which helps the developers to understand everything. There are certain areas where SwaggerHub can go beyond here as formatting options for documentation pages are restricted, and the import and export options of API collections are complex in SwaggerHub. It provides various collaboration tools where we can work and do it. The strong validation against the API maintains conformity and reduces errors. That part is very great in SwaggerHub. Overall, scalability and stability-wise, it varies high compared to the competitors, but there are still certain areas where competitors are providing various customizations. SwaggerHub can understand those aspects and implement them as well. The complex import and export of API calls and collaborations can be challenging in SwaggerHub. If they can make it easier for us, that would be great. Their performance is degraded if there is too much load on the API. The customization and doc formatting options for documentation pages are restricted in SwaggerHub. A few of my teammates have complained that they find the UI unintuitive where it requires multiple clicks for simple tasks. SwaggerHub is a great tool, but these limitations can be addressed to make things better and easier.

Quotes from Members

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

Pros

"Layer 7 completed all of the use cases in one afternoon."
"Containerization and the monetization module are quite unique for an API tool... In addition, the development time and rollout time are pretty quick."
"Compared to other vendors, this product is much faster in coming up with new features, which is good."
"The security checking authentication is our primary use case for this solution."
"Simple to use and easy to develop APIs."
"It can be scaled as we need. And it can be used in different regions. We have different data centers in the U.S. and Beijing. We use it on-premise, on-cloud, and it can be hosted and used at any place and scaled across the regions."
"The mobile access gateway (MAG) is tremendous."
"The scalability has been good; we haven't had to scale up a whole lot, even with all the extra transactions we're running through it, and we're in the area of about 2 and a half million OAuth tokens issued per hour and it's performing fine with that."
"The tool's most valuable feature is licensing."
"SwaggerHub plays a crucial role in order to bring teams and automate things faster and also reduce the man-hours and increase the work efficiency."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"It is a stable solution."
"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 product's initial setup phase was easy and not at all difficult."
"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
"The scalability is endless."
 

Cons

"There is room for improvement in terms of innovation and investment, especially when compared to other leading products in the market."
"There is a thick client for configuration that is not as easy to use as you might like."
"I was hoping that there would be some deeper dive Gateway training than their two day workshop and the self-paced study provided."
"Some problems with response time."
"CA double up portal is a pain. It is something that we are struggling with right now."
"Its ID authentication is a little outdated. They need a multifactor authentication solution for the API layer and the other layers, as well."
"I would like to see more documentation. The current documentation is there, but we do not find it very useful."
"The API Development tool can be made more user-friendly by providing folder properties."
"SwaggerHub could be improved with better integration for tools."
"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."
"At some point, we were missing some tagging of the APIs, and we could not do that."
"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."
"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."
"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."
 

Pricing and Cost Advice

"Do not buy piecemeal."
"The price of Layer7 API Management is too high and should be reduced. However, it is a good solution in the market."
"I think it's competitive. It's not that expensive when you compare CA with the Oracle product."
"I do not have experience with the pricing or licensing of the product."
"CA API Management has a licensing path. If you want more features, it requires more licenses and more installation time."
"There are some costs for maintenance that we are charged, but that seems fair because we get the support."
"Be aware of additional licenses for your warm standby. Ensure you get plenty of non-production licenses."
"This solution is a bit more expensive than competitors."
"It has a yearly subscription, but I am not sure."
"The tool is cheap."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
909,647 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
13%
Financial Services Firm
12%
Marketing Services Firm
7%
Manufacturing Company
6%
Financial Services Firm
13%
Healthcare Company
10%
Manufacturing Company
9%
Computer Software Company
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 Business4
Midsize Enterprise1
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 sometime...
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: August 2026.
909,647 professionals have used our research since 2012.