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

Apigee vs SwaggerHub comparison

 

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

"Deploying Apigee is straightforward and does not involve significant difficulties."
"The API moderation, administration monitoring, product architecture, infrastructure, and overall quality is good."
"Apigee has proven to be one of the best of the breed."
"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."
"Apigee's customer support is excellent."
"The most valuable feature is monetization."
"Apigee provides good documentation."
"Before using Apigee, we used to have file transfer integrations; with Apigee in place, we are directly integrating or exposing our APIs to our partners who can access our services directly in real time."
"Since I started using SwaggerHub, it has had a positive impact on our organization due to better collaboration between developers and the quality assurance team, and it has reduced errors because of its automated validation."
"The tool's most valuable feature is licensing."
"SwaggerHub plays a crucial role in order to bring teams and automate things faster and also reduce the man-hours and increase the work efficiency."
"The scalability is endless."
"The best feature that SwaggerHub offers is the collaboration capability that helps us the most across all of our teams, as we have a single API infrastructure but several teams working in different areas of these APIs."
"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."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
 

Cons

"The company needs to better support webhooks. It used to support webhooks and their policies and they have since stopped. They had some issues in the product and they abandoned the support for them. It's not come back since."
"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."
"Apigee is costlier compared to other solutions. For government organizations, especially those that do not want cloud-based solutions and prefer on-premise implementations, we recommend WSO2 due to its cost-effectiveness and suitability for private cloud environments."
"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 installation and management of this product are still a clumsy task."
"The Apigee cloud admin UI could be more user-friendly by adding a few more features."
"What my clients don't like is that the on-premises solution is not being treated and maintained as well as the cloud solution."
"The developer portal's adoption of the OpenAPI standard needs to be improved. In the latest version of the developer portal, they have adopted the OpenAPI standard. This feature, however, can be improved by supporting more characteristics of the OpenAPI standard."
"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."
"SwaggerHub could be improved with better integration for tools."
"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 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."
"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."
"It could be more intuitive compared to one of its competitors."
"The customization and doc formatting options for documentation pages are restricted in SwaggerHub."
"More integration and usability with the cloud microservices would be nice."
 

Pricing and Cost Advice

"If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution."
"Since it was acquired by Google, we can get a license based on our requirements and the cost level will depend on cloud access and support."
"It is more expensive when you compare to open-source products or other vendors."
"Compared to other products, Apigee had higher pricing."
"Apigee is slightly expensive, but again, it can depend on the type of usage. All things considered, it is slightly expensive."
"Apigee has several different licenses you can obtain depending on your needs."
"The iicense is subscription-based."
"Apigee is subject to licensing fees."
"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.
908,877 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
14%
Healthcare Company
9%
Manufacturing Company
9%
Computer Software Company
8%
 

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 Business4
Midsize Enterprise1
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?
There is room for improvement with Apigee as OPDK private cloud enhancements have stopped, focusing only on Apigee hybrid and Apigee X, with Google no longer adding new features to OPDK private clo...
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.
908,877 professionals have used our research since 2012.