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) (5th), Application Infrastructure (6th), SOA Application Gateways (1st)
SwaggerHub
Ranking in API Management
12th
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 April 2026, in the API Management category, the mindshare of IBM DataPower Gateway is 3.1%, down from 3.8% compared to the previous year. The mindshare of SwaggerHub is 1.5%, up from 1.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway3.1%
SwaggerHub1.5%
Other95.4%
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

"For me, its most valuable features include: the fact that it's high-speed, its ability to be remotely administered via an API, the fact that it can deal with multiple protocols, and it's very quick to make changes to the setup."
"It is very easy to set up and configure, even for users with no prior experience."
"The solution is straightforward and for large organizations, it functions well."
"The solution is very easy to work with."
"The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution."
"We did not experience any downtime, even if the number of transactions increased heavily."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"The solution is straightforward and for large organizations, it functions well."
"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."
"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."
"I rate the solution's stability a ten out of ten."
"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."
"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 product's initial setup phase was easy and not at all difficult."
"You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs."
"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

"Making it more user-friendly would be an improvement."
"It is a costly product."
"For the workloads that are not too high, appliance is a little bit expensive."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"It is challenging to understand the solution's design and support skills."
"IBM DataPower Gateway is a great solution but when based on utilizations in the different streams others feel that this is an expensive product for one simple use case."
"The product should be more adapted to the DevOps process."
"API management launched two years back and we consider it quite unstable because we still face a lot of bugs."
"SwaggerHub could be improved with better integration for tools."
"More integration and usability with the cloud microservices would be nice."
"The customization and doc formatting options for documentation pages are restricted in SwaggerHub."
"It could be more intuitive compared to one of its competitors."
"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."
"In SwaggerHub, I appreciate that it is a powerful platform for API design and collaboration, but currently, the access control is somewhat limited."
"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"
 

Pricing and Cost Advice

"The total cost of IBM DataPower Gateway would depend on the configuration, but in my experience, it can amount to 60,000 Euros per box, even for the virtual version. Usually, customers need high availability and a non-production environment, so the total price for IBM DataPower Gateway can be quite a lot. It can be 200,000 Euros or a similar figure."
"The cost is very high and requires all five components in the API management solution."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"It is an expensive solution."
"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."
"The tool's initial costing is expensive for small banks and financial institutions."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"As far as I know, they have a perpetual license for this product. They are paying perpetual fees rather than an annual subscription or annual pricing."
"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.
885,880 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
9%
Healthcare Company
7%
 

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: March 2026.
885,880 professionals have used our research since 2012.