We performed a comparison between Amazon API Gateway and SwaggerHub 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 very helpful, with our API-based applications."
"Amazon stack is easy to use in combination with other Amazon services, so it was a logical continuity."
"It's flexible. It was valuable."
"It's easy to integrate and provide support for existing AWS services if I use the AWS API gateway."
"All information and data needs to be sanitized before it enters a private domain and we use this solution to do this."
"Its security feature is the most valuable because it is mainly a security solution. It has easy authentication and authorization, and its integration is also useful."
"The most valuable feature in Amazon API Gateway is the itinerary release."
"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."
"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 most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
"The user interface could be improved, as well as customer support and having a local customer representative in a country."
"The integration could be improved."
"Amazon API Gateway can improve the user interface in some areas it could be more polished."
"From a use cases perspective, you need to have an internal and external gateway. AWS can only handle external traffic so has to be used together with another solution."
"The user interface, in general, can be better. The user interface for the entire Amazon cloud can be more friendly. There are some scenarios that are not really easy to manage and configure through the user interface."
"Monitoring could be improved."
"I am not completely satisfied with Technical Support."
"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 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."
Amazon API Gateway is ranked 8th in API Management with 7 reviews while SwaggerHub is ranked 11th in API Management with 3 reviews. Amazon API Gateway is rated 8.2, while SwaggerHub is rated 8.6. The top reviewer of Amazon API Gateway writes "Secure, easy to use, includes WAF rules, has responsive technical support, and provides excellent documentation". On the other hand, the top reviewer of SwaggerHub writes "Generates a very rich codebase for our APIs, has comprehensive documentation, and is great for collaboration". Amazon API Gateway is most compared with Microsoft Azure API Management, MuleSoft Anypoint API Manager, Apigee, Kong Enterprise and Akana API Management, whereas SwaggerHub is most compared with Microsoft Azure API Management, MuleSoft Anypoint API Manager, Apigee, Apiary and 3scale API Management. See our Amazon API Gateway vs. SwaggerHub 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.
