We performed a comparison between Microsoft Azure API Management 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 easy to use."
"It's very well integrated with the Azure environment."
"The most valuable feature of Microsoft Azure API Management is monitoring. When compared with Apigee, I prefer Microsoft Azure API Management."
"The most valuable feature is the developer portal, which has source code examples in various programming languages to help developers learn the API."
"The documentation and configuration of APIs."
"The tool's most valuable feature is the integration of CI/CD with the API gateway."
"The ability to easily connect back to Service Fabric is the most important for us."
"I like the stability and the ease of use."
"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 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 product's initial setup phase was easy and not at all difficult."
"I rate the solution's stability a ten out of ten."
"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
"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 external policies are impossible to look at and configure."
"There is room for improvement in the user interface and workflow for hosting APIs, especially third-party APIs."
"The hybrid part could be improved because API Management is entirely cloud-based, but some of our resources are on-prem, so formatting is an issue. Our goal is dual implementation."
"The API gateway can be very complex."
"Performance issues from this platform need to be sorted out."
"There is always room for improvement. There should be more analytics abilities so you can know how much traffic there is. Log Analyzer isn't well integrated with this solution."
"If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be."
"The licensing tiers can be misleading."
"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 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."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"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."
"It could be more intuitive compared to one of its competitors."
"We have to use additional tools to test APIs."
"SwaggerHub could be improved with better integration for tools."
More Microsoft Azure API Management Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 68 reviews while SwaggerHub is ranked 16th in API Management with 10 reviews. Microsoft Azure API Management is rated 7.8, while SwaggerHub is rated 7.8. The top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". On the other hand, the top reviewer of SwaggerHub writes "Simplifies API design and development for developers". Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and IBM DataPower Gateway, whereas SwaggerHub is most compared with Apigee, MuleSoft Anypoint API Manager, Amazon API Gateway, RapidAPI and Stoplight. See our Microsoft Azure API Management 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.