Try our new research platform with insights from 80,000+ expert users

Apigee vs IBM API Connect vs SwaggerHub comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Mindshare comparison

As of September 2025, in the API Management category, the mindshare of Apigee is 11.5%, down from 15.3% compared to the previous year. The mindshare of IBM API Connect is 6.1%, down from 6.4% compared to the previous year. The mindshare of SwaggerHub is 1.4%, up from 1.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
Apigee11.5%
IBM API Connect6.1%
SwaggerHub1.4%
Other81.0%
API Management
 

Featured Reviews

ShawkyFoda  - PeerSpot reviewer
Provides high visibility and control with good traffic monitoring
Analytics is one of the areas needing enhancement, specifically more visibility and control over traffic to improve capacity management and high availability. The replication process between Master and Slave for disaster recovery takes too long. Dependencies on analytics impact the performance of the user interface, which should be separate. The complex setup process on-premises, especially with multi-node installations, could also be improved. Additional control in product declarations, based on operations like POST and GET, is needed.
Shanmugasundaram Shanmuganathan - PeerSpot reviewer
Offers basic API orchestration and provides robust security and governance features
While Azure API Management offers configurable scalability, IBM API Connect relies on Kubernetes clusters. This might seem manual and require defining cluster instances upfront, but it's completely customizable and not on-the-fly scaling. It's completely custom-driven, not on-the-fly scaling, which some may consider cumbersome. Overall, I would rate the scalability an eight out of ten. Almost all applications we've been exposing lately go through this middleware, so it's used extensively. There are around sixty applications directly using it, but six Kubernetes clusters serve those applications. It's heavily used for integration, including system-to-system integration and product integrations. Our usage has been increasing year-on-year based on our needs.
SwaminathanSubramanian - PeerSpot reviewer
Facilitating enterprise-wide API governance and management
Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account. The scalability also needs enhancement, as it becomes flaky under increased load. Additionally, the versioning management could be improved to be on par with source code management tools.

Quotes from Members

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

Pros

"Apigee provides good documentation."
"The most valuable feature is monetization."
"Apigee's best features are flexibility and breadth of capabilities."
"It's stable."
"The most valuable feature of Apigee is its simplicity of deploying an API and restricting access, like rate limit, with the API."
"Its flexibility allows seamless management of different products, showcasing scalability to handle extensive solutions."
"Technical support has been decent."
"The initial setup was easy - there was an onboarding document with steps that we followed."
"Policy configurations are pretty easy."
"It acts as a central gateway for both external APIs and underlying systems. It's basically a central middleware for hosting APIs to the internet and consuming APIs from internal systems. It provides central governance for any APIs going outside the network, ensuring security and a common contract for API definitions."
"WSRR is a powerful component for getting the endpoints."
"The technical support is good. Whenever we need anything, we have our IT team work with IBM to change whatever requirement is needed."
"The solution offers a pretty good SLA."
"The solution provides a common place for all APIs, allowing for easy sharing and exchange of information between internal and external stakeholders."
"The gateway is the most valuable aspect of this solution."
"It is easy to use and stable."
"The tool's most valuable feature is licensing."
"It is a stable solution."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"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 product's initial setup phase was easy and not at all difficult."
"I rate the solution's stability a ten out of ten."
"The scalability is endless."
 

Cons

"Apigee's user interface could be more straightforward and have more options. Also, it would be nice if it were ready to work out of the box without so much configuration."
"They need to work on the cost of the solution."
"We need better performance monitoring."
"There should be an integrated continuous integration and continuous deployment approach with Apigee. Currently, for development at a more integrated level, you have set it up yourself."
"The initial setup for the on-prem solution is a little complex."
"They have an external developer platform that was a little bit painful."
"It is an expensive solution."
"GCP is improving the regular version control. There have been some challenges when we talk about the hybrid deployment model. For example, some runtime services' data was available only on the cloud, but financial institutions and other customers have requested more on-site data storage. This is especially important in regions where Google data centers are unavailable, such as certain areas in Africa, Asia, and the Middle East."
"Components, like caching, should be implemented as policies, not requiring dependency on an external solution."
"Like any typical IBM infrastructure setup, you need to learn to set it up yourself. It's not one of those simple zip files or an archive unzip and you're up and running in some few minutes. Knowledge to set it up is key."
"It should be cheaper."
"In the next version, I don't know if they've already been included it or not, but the designer and all the tools should be on the cloud. I don't want any external installation or local installation."
"Due to bugs in integration, we have to look for workaround on fixing and using DataPower as gateway."
"The developmental process is not quite user-friendly."
"The automation and the simplicity could be improved."
"There is room for improvement regarding the connectivity of the DevOps."
"We have to use additional tools to test APIs."
"SwaggerHub could be improved with better integration for tools."
"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."
"More integration and usability with the cloud microservices would be nice"
"It has limited functionality...Unfortunately, some of its features are not what we need."
"Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account."
"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."
 

Pricing and Cost Advice

"You do not necessarily pay for the license. The cloud solution is based more on transactions. So, you pay for it either way."
"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."
"Pricing options need to be chosen on a case-by-case basis."
"The cost of the licensing is based on the number of API calls that are made."
"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."
"They need to work on the cost of the solution."
"I would like to see the implementation of further options for billing because as it is now, the opportunities you have in terms of a package are limited."
"The solution is a bit expensive. It's not for organizations in the early stages of their lifecycle but is more suited for mid- to enterprise-level platforms. Pricing varies by deployment model, with SaaS being the cheapest, costing around $100,000 per year for a subscription. For hybrid and on-prem deployments, the price increases. The on-prem model includes a license and additional installation and configuration professional service costs, which can be at least $40,000 to $60,000 for the initial setup. While it's not cheap, it offers long-term value and can be worthwhile."
"API Connect is quite pricey."
"We pay for the IBM API Connect monthly. We only need to pay the standard licensing fee."
"I rate the product price a seven on a scale of one to ten, where one is a low price, and ten is a high price."
"This is a licensed product. If your company is looking to obtain a license, you have to work with IBM partners."
"IBM API Connect could be cheaper."
"It's an expensive product."
"The price for IBM API Connect is reasonable. It's $20,000 to $30,000 yearly for a subscription, and the pricing could vary around $40,000 per year, per subscription. Its price is reasonable for customers who have around sixty million API calls yearly for unlimited environments."
"API Connect's license cost could be a little lower. But, unfortunately, there aren't many open-source API gateways. Ideally, some new developers could come up with a minimum-functionality open-source solution."
"It has a yearly subscription, but I am not sure."
"The tool is cheap."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
868,275 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
11%
Manufacturing Company
8%
Insurance Company
7%
Financial Services Firm
19%
Insurance Company
12%
Computer Software Company
11%
Manufacturing Company
7%
Financial Services Firm
18%
Computer Software Company
13%
Manufacturing Company
7%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise9
Large Enterprise65
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise10
Large Enterprise58
By reviewers
Company SizeCount
Small Business3
Large Enterprise7
 

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 clou...
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...
What do you like most about IBM API Connect?
Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and poten...
What is your experience regarding pricing and costs for IBM API Connect?
Pricing depends on how many instances run across environments. I don't deal with licensing, but compared to other IBM...
What needs improvement with IBM API Connect?
When comparing API Gateway with DataPower Gateway, several features in DataPower Gateway are absent in the APIC layer...
What do you like most about SwaggerHub?
The tool's most valuable feature is licensing.
What needs improvement with SwaggerHub?
Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, ...
What is your primary use case for SwaggerHub?
I started using SwaggerHub in its previous version, SmartMiner, with a tool called SoapUI. I used it to create mock w...
 

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
Heineken, Tine, Finologee, Axis Bank
Sonic, Zuora, Woolworths, CrowdFlower
Find out what your peers are saying about Microsoft, Amazon Web Services (AWS), Google and others in API Management. Updated: August 2025.
868,275 professionals have used our research since 2012.