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."Amazon stack is easy to use in combination with other Amazon services, so it was a logical continuity."
"It's easy to integrate and provide support for existing AWS services if I use the AWS API gateway."
"It's flexible. It was valuable."
"The solution is stable."
"All information and data needs to be sanitized before it enters a private domain and we use this solution to do this."
"One of the most valuable aspects of API Gateway is its native integration with AWS services."
"t is easy for integrations if it is deployed in AWS Services."
"Integrating API Gateway with other AWS services was easy. It worked out of the box, so it worked perfectly."
"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."
"The product's initial setup phase was easy and not at all difficult."
"I rate the solution's stability a ten out of ten."
"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 tool's most valuable feature is licensing."
"The scalability is endless."
"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."
"We faced a few issues with the documentation."
"Monitoring could be improved."
"Their support services come at a considerable cost, leaving room for improvement."
"Amazon API Gateway can improve the user interface in some areas it could be more polished."
"It's hard to configure. There's a lot of options but it's very hard, it's very confusing."
"When working with XML payloads, there can be issues due to the lack of a seamless connection between API Gateway and Lambda functions."
"Like most Amazon services, and this one's the same, you're expected to effectively do your own support, and any other support is by emails, so it's quite limited."
"SwaggerHub's UI needs to be improved as it looks very old school."
"It could be more intuitive compared to one of its competitors."
"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."
"We have to use additional tools to test APIs."
"More integration and usability with the cloud microservices would be nice"
"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."
"It has limited functionality...Unfortunately, some of its features are not what we need."
Amazon API Gateway is ranked 3rd in API Management with 37 reviews while SwaggerHub is ranked 15th in API Management with 10 reviews. Amazon API Gateway is rated 8.2, while SwaggerHub is rated 7.8. The top reviewer of Amazon API Gateway writes "Easy initial setup and highly stable solution". On the other hand, the top reviewer of SwaggerHub writes "Simplifies API design and development for developers". Amazon API Gateway is most compared with Microsoft Azure API Management, MuleSoft Anypoint API Manager, Apigee, WSO2 API Manager and Kong Gateway Enterprise, whereas SwaggerHub is most compared with Microsoft Azure API Management, Apigee, MuleSoft Anypoint API Manager, RapidAPI and Stoplight. 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.