We performed a comparison between Apigee 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."The most important feature is the security capabilities and the way it integrates very quickly with other security providers. We have integrated it with Azure and it integrates quite seamlessly."
"The developer portal is very useful to customers."
"The security that you have with Apigee is very good and aligns with compliance."
"It has all the features necessary to work in anything from a basic scenario to advanced applications."
"Its customer service is good."
"I have found the most valuable features to be tracing a proxy, and managing proxy versions and revisions via the Edge UI component."
"It accelerates development and deployment processes."
"There is plenty of support documentation available."
"The product's initial setup phase was easy and not at all difficult."
"The tool's most valuable feature is licensing."
"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."
"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."
"It is a stable solution."
"The scalability is endless."
"Google isn't enthusiastic about supporting older versions. Google is now trying to move all of its clients to X within the cloud."
"Role-based access management needs to be improved. It would also be nice if the solution could be integrated with code versioning systems like Git/Bitbucket."
"Apigee is demanding on the infrastructure so the setup cost is very high for an on-premises deployment."
"I would like to see the support improved. I think the time frame should be shorter for responses when it comes to technical support. This is not the ideal situation you want to be in when you need support."
"The solution’s scalability could be improved."
"The cost of the solution is quite high."
"It is an expensive solution."
"In terms of the functionalities of a typical API gateway, Apigee is actually doing its job, but when it involves integration with backend applications, which some gateways have, I don't believe it has this functionality. You have to do Java or do some other low-level coding before you are able to do the integration. Apigee has a lot of components, which means that management will be a bit difficult. It probably has ten different components, and all of these components leverage open-source utilities, such as NGINX. When those open-source vendors upgrade their utility, Apigee usually lags behind because they need to do a lot of tests and any required development in their own platform. They need to do rigorous testing to make sure that nothing breaks. Because of that, it takes them a while to upgrade whatever components have been upgraded by the open-source vendor that owns the utility. We've been chasing them for a particular upgrade for well over a year and a half, and they have not done that upgrade. It is creating a security risk for us as an enterprise, but that upgrade has not been done, even though the open-source vendor, the owner of the utility, has upgraded it a long time ago."
"SwaggerHub could be improved with better integration for tools."
"We have to use additional tools to test APIs."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"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."
"More integration and usability with the cloud microservices would be nice"
"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."
Apigee is ranked 2nd in API Management with 82 reviews while SwaggerHub is ranked 15th in API Management with 10 reviews. Apigee is rated 8.2, while SwaggerHub is rated 7.8. The top reviewer of Apigee writes "Has a robust community and outstanding performance". On the other hand, the top reviewer of SwaggerHub writes "Simplifies API design and development for developers". Apigee is most compared with Microsoft Azure API Management, IBM API Connect, WSO2 API Manager, Amazon API Gateway and TIBCO Cloud API Management, whereas SwaggerHub is most compared with Microsoft Azure API Management, MuleSoft Anypoint API Manager, Amazon API Gateway, RapidAPI and Stoplight. See our Apigee 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.