We performed a comparison between SwaggerHub and Tyk 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."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 most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
"I rate the solution's stability a ten out of ten."
"It is a stable solution."
"The scalability is endless."
"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 tool's most valuable feature is licensing."
"The product's initial setup phase was easy and not at all difficult."
"The feature I find most valuable is that this solution allows us to manage our security."
"The scalability is very good. That was a key factor in the selection, like how it could be pushed to high volume and scalability, which seemed to be very good."
"It is a good product for API management."
"You can set up workflows and write limited pieces of logic."
"The most valuable feature is the load balancing with the circuit-breaker function."
"The portal for developers that this solution provides has great functionality."
"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."
"More integration and usability with the cloud microservices would be nice"
"SwaggerHub could be improved with better integration for tools."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"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. 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."
"I would like to see some additional features like having some extensions for .NET core because we use it for our back-end language."
"Sometimes when new features are released, they are not immediately stable."
"We ran it for a while, but then we decided to move away from Tyk, because Tyk's cloud version, the SaaS version, has a significant limitation of limited flexibility, so you can't program very much."
"In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly better communication with the customer base that would be my main issue with them."
"We would like a better tool for generating documentation for the APIs to be developed."
"It is a young product and does not have the kind of brand recognition that would make it a more popular solution with our clients."
SwaggerHub is ranked 13th in API Management with 5 reviews while Tyk is ranked 16th in API Management with 2 reviews. SwaggerHub is rated 7.8, while Tyk is rated 7.6. 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 Tyk writes "Fastest to get up and running and fewer idiosyncrasies than competitors". SwaggerHub is most compared with Microsoft Azure API Management, Apigee, MuleSoft Anypoint API Manager, Amazon API Gateway and Stoplight, whereas Tyk is most compared with Apache APISIX, Traefik Enterprise, Apigee, Microsoft Azure API Management and IBM DataPower Gateway. See our SwaggerHub vs. Tyk 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.