Layer7 API Management vs SwaggerHub comparison

"The most valuable features of Layer7 API Management are integration, ease of use, building APIs easily, and portal straightforward."

"We definitely get good responses from the technical team and they are quite responsive.​"

"The level of technical support is good."

"There are a couple aspects of performance. One is just speed and uptime, and it's stellar in that regard. The other is, how much effort is it to put it in place in the first place, and then how much effort is it to keep it operational. That's where its real strength is. I'm able to do things quickly and easily that I couldn't do before​."

"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 allows us to keep clear traceability of the changes made in each of our APIs."

"The product documentation helps the client and/or user to evolve quickly while using the tool."

"The most important features of Layer7 API Management are the basic security functionality and validation checks."

"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 scalability is endless."

"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 tool's most valuable feature is licensing."

"You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs."

"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."

"One day, where we can have a microservices gateway and we will not need the classic gateway at all, that is what we want to see."

"The interface should be improved."

"I understand that clients are often concerned about costs. They might be exploring other options due to the high cost associated with our current package."

"As well as the SOA Gateway - that is, the API Gateway; we call it the SOA Gateway - we also are now deploying the developer portal component of the SOA Gateway. That has limitations."

"The development toolkit used for creating APIs should be more online and user-friendly. Deployment and tracking could also be improved. Tools like Apigee provide a complete online experience along with RESTful APIs, to manage all activities. It is a very nice and user-friendly solution compared to CA."

"Layer7 API Management’s price could be reduced."

"Provide complete documentation with examples of usage on its build in assertion/function."

"We have experienced technical difficulties with the product in the past."

"It could be more intuitive compared to one of its competitors."

"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"

"We have to use additional tools to test APIs."

"It has limited functionality...Unfortunately, some of its features are not what we need."

"SwaggerHub could be improved with better integration for tools."

"We weren't comfortable with the pricing of licensing. It was slightly more expensive than its competitors."

"It depends on your use case of course, how much you want to go with that, because it can get pricey and depends on the size of your company."

"It is a pricey product, although not extremely overpriced compared to competitors in the market."

"Licenses are required to operate the product, but I don't know much about the validity periods attached to it."

"If you do a TCO of more than five years, then you will see a big jump in costs for some vendors."

"The product is moderately priced."

"The price of Layer7 API Management is too high and should be reduced. However, it is a good solution in the market."

"At the time we bought the product it was a perpetual users license and there has been no need for additional licensing fees."

"It has a yearly subscription, but I am not sure."

"The tool is cheap."