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

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 March 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

"The solution is stable."
"The appliance has great security and reliability."
"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"I like the API Gateway feature."
"What I like most is the stability."
"The support for IBM DataPower Gateway has been exceptional."
"My company has a good impression of IBM DataPower Gateway. What I like about it is that because it's an appliance, it's a turnkey solution that's very fast and out of the box. Compared to other gateways, I also like that IBM DataPower Gateway is function-rich. For example, for one of the projects, there was a need for specific transformation and security features available in IBM DataPower Gateway out of the box, so my team just needed to configure the appliance. There was no need for separate development, and I found it quite neat. Another valuable feature of IBM DataPower Gateway is that it's easy to integrate with other products."
"From a technical point of view, IBM DataPower Gateway performs quite well, so my team had no concerns at all in terms of performance, reliability, and stability."
"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."
"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 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."
"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 scalability is endless."
"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."
"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

"Its support services could be better."
"They should improve the solution's clustering features."
"The IBM community does not have much engagement from the IT community in Saudi Arabia and developers for this solution are difficult to find."
"The DCDR process should be less complex."
"Traceability could be improved, especially for business operations."
"I would like the tool to improve its training."
"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."
"Scripting needs improvement. It's hard for our customers."
"At some point, we were missing some tagging of the APIs, and we could not do that."
"We have to use additional tools to test APIs."
"The customization and doc formatting options for documentation pages are restricted in SwaggerHub."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"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."
"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."
"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."
"More integration and usability with the cloud microservices would be nice."
 

Pricing and Cost Advice

"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."
"The appliance is a bit on the expensive side for the workloads that are not too high."
"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 licensing cost is very expensive."
"The solution has a return on investment but is a little expensive."
"It's expensive when you compare it with others."
"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 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.
885,286 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Insurance Company
8%
Manufacturing Company
8%
Government
7%
Financial Services Firm
14%
Computer Software Company
10%
Manufacturing Company
8%
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,286 professionals have used our research since 2012.