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
10th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Enterprise Service Bus (ESB) (4th), Application Infrastructure (7th), SOA Application Gateways (1st)
SwaggerHub
Ranking in API Management
13th
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 May 2026, in the API Management category, the mindshare of IBM DataPower Gateway is 3.1%, down from 3.9% compared to the previous year. The mindshare of SwaggerHub is 1.7%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway3.1%
SwaggerHub1.7%
Other95.2%
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

"The solution is very easy to work with."
"The solution is robust, and we use the appliance version, which comes with good security features and troubleshooting tools, so we are happy with IBM DataPower."
"You don't have to have a separate DMC proxy because DataPower Gateway is an appliance and will take care of a lot of security features. These include data validations, encryption, as well as XML or any type of scripting or security threats that are present."
"Since it is a gateway, it provides a lot of security features."
"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."
"Its initial setup was straightforward."
"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"The tool's most valuable feature is licensing."
"It is a stable solution."
"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."
"It is quite a useful tool, quite good with the validation of the spec, works quite well in terms of errors and conformity to the OpenAPI standard, and 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."
"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."
 

Cons

"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"In the next release, I would like to see the product price reduced. It should be cheaper."
"It is challenging to understand the solution's design and support skills."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"The components that they include in the product that are, in fact, a WTX, really need to be removed from the product because they tend to fail."
"The user interface or the application development perspective and customization of the tool could be a little better."
"For the workloads that are not too high, appliance is a little bit expensive."
"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."
"One of the most difficult things about SwaggerHub is the user interface and its usability, as it can feel quite complex and require too many clicks for simple actions."
"It could be more intuitive compared to one of its competitors."
"We have to use additional tools to test APIs."
"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."
"At some point, we were missing some tagging of the APIs, and we could not do that."
"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."
 

Pricing and Cost Advice

"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"The cost of this product varies from customer to customer and the relationship with IBM, including how many offerings from IBM are already being used."
"It is an expensive solution."
"The product is expensive."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"The licensing cost is very expensive."
"The tool's initial costing is expensive for small banks and financial institutions."
"IBM DataPower Gateway is quite expensive to get resources to work on this product. If the price could be cheaper, I think that will make it a little bit better and easily accessible to smaller clients. Then it could compete with other solutions that are available in the market. There's a whole lot of other solutions available that work well and are cheaper than IBM's products."
"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.
893,164 professionals have used our research since 2012.
 

Top Industries

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

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 Business4
Midsize Enterprise1
Large Enterprise9
 

Questions from the Community

What do you like most about IBM DataPower Gateway?
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.
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 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: April 2026.
893,164 professionals have used our research since 2012.