No more typing reviews! Try our Samantha, our new voice AI agent.

Apigee vs SwaggerHub comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Apigee
Ranking in API Management
3rd
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
90
Ranking in other categories
API Testing Tools (12th)
SwaggerHub
Ranking in API Management
14th
Average Rating
7.8
Reviews Sentiment
6.4
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the API Management category, the mindshare of Apigee is 6.8%, down from 12.2% compared to the previous year. The mindshare of SwaggerHub is 1.8%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Apigee6.8%
SwaggerHub1.8%
Other91.4%
API Management
 

Featured Reviews

Amandeep Pawar - PeerSpot reviewer
Senior Engineer at Airy Software Technologies Private Limited
Centralized API gateway has improved microservice security and provided deep traffic analytics
Apigee's API gateway could be improved. There are some limitations for high throughputs, which we can address. Overall, Apigee is a robust API management platform where we can configure centralized traffic management, but there are a few areas for improvement. The developer experience could be more intuitive, especially for configurations and complex API proxies and policies. Debugging production issues can sometimes be challenging, so more detailed diagnostic and easier-to-use troubleshooting tools would be valuable. The analytics dashboard could offer more customization and deeper insights without requiring additional configuration. Simplifying pricing and licensing would make Apigee more accessible for smaller organizations. I would like better support for cloud-native deployments, Kubernetes integrations, and AI-assisted policy recommendations. I would also like to see AI-assisted troubleshooting, more customizable analytics and developer portal, better enterprise documentation, easier policy configuration, and a simplified licensing model to enhance both the developer experience and day-to-day operations.
Manish Indupuri - PeerSpot reviewer
senior DevOps engineer at a tech services company with 10,001+ employees
Has streamlined API documentation and integration workflows across cross-functional teams
Documenting SwaggerHub has a standard and consistent structure of API definitions, and it automatically generates interactive documentation which helps the developers to understand everything. There are certain areas where SwaggerHub can go beyond here as formatting options for documentation pages are restricted, and the import and export options of API collections are complex in SwaggerHub. It provides various collaboration tools where we can work and do it. The strong validation against the API maintains conformity and reduces errors. That part is very great in SwaggerHub. Overall, scalability and stability-wise, it varies high compared to the competitors, but there are still certain areas where competitors are providing various customizations. SwaggerHub can understand those aspects and implement them as well. The complex import and export of API calls and collaborations can be challenging in SwaggerHub. If they can make it easier for us, that would be great. Their performance is degraded if there is too much load on the API. The customization and doc formatting options for documentation pages are restricted in SwaggerHub. A few of my teammates have complained that they find the UI unintuitive where it requires multiple clicks for simple tasks. SwaggerHub is a great tool, but these limitations can be addressed to make things better and easier.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Anyone with basic knowledge can build an API."
"I would recommend this solution to others who are interested in using it."
"Lifecycle management."
"Apigee has better scalability than WSA."
"I like implementing different policies, for example, rate-limiting policy."
"This solution is much easier to set up compared to any of the other API gateway solutions."
"A simple platform that's easier to work with than IBM API Connect. Support for it is really good and gives it advantage over other providers."
"I would definitely recommend this product over any other products available in the market in this category."
"The tool's most valuable feature is licensing."
"I rate the solution's stability a ten out of ten."
"The scalability is endless."
"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."
"SwaggerHub has significantly improved how my organization designs, documents, and manages APIs, centralizing API management so that all API definitions are stored in one location, which makes it easy for stakeholders, developers, QA, DevOps, and products to access the latest version."
"SwaggerHub is helping with team collaboration, as all the people now know the link, they just go there and get the information they need, and it is really a documentation tool for sharing documentation information about the API we support."
"It is a stable solution."
 

Cons

"It is a bit on the expensive side. Its licensing cost is a bit high, and that's where we've seen people going back on their decisions."
"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."
"One feature they have to invest time into is the developer portal they use."
"There is room for improvement in v-logging for each transaction."
"I would like to see a long-term direction for the overall architecture (similar to what WSO2 has done), in that all three areas — pub/sub, events, and APIs — are treated as part of a continuum, instead of treating each as separate topics."
"The integration could be improved within the solution. There is a need to pay more attention to this."
"Compared to its competitors, such as Axway AMPLIFY API Management and Layer7 API Management, Apigee could benefit from having more policies to cater to various use cases. This would reduce the need for writing custom JavaScripts. If more features come straight out of the box, we can leverage them instead of writing custom code to achieve the same functionality."
"The pricing for the product was a bit higher. I also found it challenging to manage sometimes."
"The scalability aspect of SwaggerHub can be improved. It becomes a bit unreliable when the load is increased and isn't up to par with expectations for scalability."
"SwaggerHub could be improved with better integration for tools."
"In SwaggerHub, I appreciate that it is a powerful platform for API design and collaboration, but currently, the access control is somewhat limited."
"SwaggerHub can be improved since the API testing features are limited compared to Postman, and it is somewhat expensive for small teams as paid plans cost a lot."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"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."
"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."
 

Pricing and Cost Advice

"The tool is extremely expensive."
"The current version of Apigee is not too expensive, but we are currently in talks with Google to understand their roadmap for Apigee X. However, we anticipate that with the introduction of Apigee X, the pricing will likely increase."
"It was fairly expensive. I don't know what the standard pricing is. I want to say that it's something like $80,000 for 800 million requests (approximately) a year."
"Pricing options need to be chosen on a case-by-case basis."
"The solution’s pricing could be more competitive."
"Its price is reasonable for the features they provide and the maturity of the platform."
"Compared to other products, Apigee had higher pricing."
"The prices are comparable."
"The tool is cheap."
"It has a yearly subscription, but I am not sure."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
911,493 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Manufacturing Company
10%
Computer Software Company
8%
Insurance Company
6%
Financial Services Firm
13%
Manufacturing Company
9%
Healthcare Company
9%
Outsourcing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise9
Large Enterprise67
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise9
 

Questions from the Community

How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Apigee or Amazon API Gateway?
Amazon API Gateway is a platform that supports the creation and publication of API for web applications. The platform can support thousands of simultaneous API calls, and it provides monitoring, ma...
What needs improvement with Apigee?
Apigee's API gateway could be improved. There are some limitations for high throughputs, which we can address. Overall, Apigee is a robust API management platform where we can configure centralized...
What needs improvement with SwaggerHub?
SwaggerHub can be improved since the API testing features are limited compared to Postman, and it is somewhat expensive for small teams as paid plans cost a lot.
What is your primary use case for SwaggerHub?
My main use case for SwaggerHub is to design and review API specifications, as I test endpoints with the help of Swagger UI, validate the request and the response schemas, and share the API documen...
What advice do you have for others considering SwaggerHub?
Before using SwaggerHub, I advise having basic API knowledge, as those with API knowledge can easily use SwaggerHub. I would rate this review an eight out of ten.
 

Comparisons

 

Overview

 

Sample Customers

Adobe, advance.net, Amadeus, AT&T, Bechtel, Belly, Burberry, Chegg, Citrix, Dell, eBay, Equifax, GameStop, First Data, Globe, HCSC, Intralinks, Kao, Meredith, Mitchell, Orange, Pearson
Sonic, Zuora, Woolworths, CrowdFlower
Find out what your peers are saying about Apigee vs. SwaggerHub and other solutions. Updated: August 2026.
911,493 professionals have used our research since 2012.