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

IBM DataPower Gateway 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

IBM DataPower Gateway
Ranking in API Management
15th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Enterprise Service Bus (ESB) (7th), Application Infrastructure (12th), SOA Application Gateways (1st)
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 IBM DataPower Gateway is 3.6%, down from 3.8% 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 (%)
SwaggerHub1.8%
IBM DataPower Gateway3.6%
Other94.6%
API Management
 

Featured Reviews

AkshaySawant - PeerSpot reviewer
Manager at CSB Bank Ltd
Security features excel but development limitations emerge
We are using the IBM DataPower Gateway for security purposes. As per the development perspective, there are some limitations with IBM DataPower Gateway because it only supports XML and XSLT language, but it does not support the Java language. This is the only limitation of the IBM DataPower Gateway. For the authentication and authorization purpose, we can use the IBM DataPower Gateway. It's a very good product. We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes. If we are handling the load for a particular server, then we can use the IBM DataPower Gateway. The IBM DataPower Gateway is mostly used for security purposes. If we have some APIs and we are using some security for those APIs, then we can use it. It can also be used as a load balancer. It's also used for certificate management, user management purposes, authentication, and authorization. For routing, the IBM DataPower Gateway has multiple URL-based routing and content-based routing capabilities. If we have multiple URLs, then we can use an XML script. Using the XSLT language, we can configure multiple URLs and implement URL-based routing. Content-based routing means if we have multiple requests, we can route the request to a particular URL. For this, we need to use the XSLT language only. We can't use XML, Java, or other scripting languages. With IBM DataPower Gateway, we are using all the APIs. All APIs have been configured on the gateway. We have configured the particular TLS profile and some TLS client profiles as well. Using that TLS profile, we have configured the APIs and authentication. We have configured some tokens also, including JWT tokens and different types of auth tokens. There is also a rate limiting feature which we use for handling API loads.
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

"I like all of the features in this product and it does what it's supposed to do."
"The product's most valuable features are AAA policies and security features."
"The product is stable...The product is scalable."
"I like the API Gateway feature."
"Since it is a gateway, it provides a lot of security features."
"The MPGW (Multi-Protocol Gateway) is great because it allows you to easily expose services using various protocols – web services, REST (JSON), and others. This flexibility simplifies things."
"The solution is robust."
"The whole purpose of this product is to provide high speed and high performance."
"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 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 scalability is endless."
"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."
"Normally, they publish their APIs on SwaggerHub for seamless integration with SmartBear and ReadyAPI, which allows us to perform detailed end-to-end automation testing."
"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."
"I rate the solution's stability a ten out of ten."
"It is a stable solution."
 

Cons

"API management launched two years back and we consider it quite unstable because we still face a lot of bugs."
"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"The customization of the solution isn't as straightforward as we would like it to be."
"For the workloads that are not too high, appliance is a little bit expensive, especially in the development test and UAT environment, where we can use the virtual version of the product."
"My experience with the pricing of this product is that pricing is too high and should be reduced."
"They should add features to manage API integrations."
"The DCDR process should be less complex."
"I noticed that the Gateway Script libraries could be improved, as they are not covering everything I 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."
"The customization and doc formatting options for documentation pages are restricted in SwaggerHub."
"We have to use additional tools to test APIs."
"In SwaggerHub, I appreciate that it is a powerful platform for API design and collaboration, but currently, the access control is somewhat limited."
"It could be more intuitive compared to one of its competitors."
"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."
"SwaggerHub's UI needs to be improved as it looks very old school."
"SwaggerHub could be improved with better integration for tools."
 

Pricing and Cost Advice

"The solution has a return on investment but is a little expensive."
"The tool's initial costing is expensive for small banks and financial institutions."
"The product is expensive."
"The solution is expensive in comparison to other products."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"The licensing cost is very expensive."
"The cost is very high and requires all five components in the API management solution."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"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.
910,454 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Manufacturing Company
8%
Insurance Company
7%
Government
7%
Financial Services Firm
13%
Healthcare Company
9%
Manufacturing Company
9%
Computer Software Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise18
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise9
 

Questions from the Community

What is your experience regarding pricing and costs for IBM DataPower Gateway?
I don't know if the current licensing cost of IBM DataPower Gateway is high, but I think it's acceptable. I don't have any complaints about it.
What needs improvement with IBM DataPower Gateway?
I noticed that the Gateway Script libraries could be improved, as they are not covering everything I need.
What is your primary use case for IBM DataPower Gateway?
The primary purposes for which IBM DataPower Gateway is used include security purposes, and sometimes you need to put some configurations and mapping into the process.
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.
 

Also Known As

WebSphere DataPower, IBM DataPower, IBM WebSphere DataPower
No data available
 

Overview

 

Sample Customers

RBL Bank, Availity
Sonic, Zuora, Woolworths, CrowdFlower
Find out what your peers are saying about IBM DataPower Gateway vs. SwaggerHub and other solutions. Updated: August 2026.
910,454 professionals have used our research since 2012.