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.4
Reviews Sentiment
6.6
Number of Reviews
31
Ranking in other categories
Enterprise Service Bus (ESB) (5th), Application Infrastructure (7th), SOA Application Gateways (1st)
SwaggerHub
Ranking in API Management
14th
Average Rating
7.8
Reviews Sentiment
6.0
Number of Reviews
13
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 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 Market Share Distribution
ProductMarket Share (%)
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

"I like the API Gateway feature."
"I like the API Gateway feature."
"The performance is good. It's been very stable."
"The solution is stable."
"The scalability of the solution is good."
"The product's most valuable features are AAA policies and security features."
"IBM DataPower Gateway has positively impacted my organization by allowing me to implement rate limits on the different API usage, which is the benefit."
"The solution is robust."
"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."
"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 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."
"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."
"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
 

Cons

"They should add features to manage API integrations."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"Traceability could be improved, especially for business operations. The traceability of the transactions could be an improvement point for DataPower to work on. It would be better if they provided JSON support. JSON protocol data has changed format. It started performing internal transformation to JSONx. This might be an additional complexity."
"The programming language is only supported in XSLT and Gateway script."
"The DCDR process should be less complex."
"The initial setup isn't so easy, you need who has experience working with the solution to help."
"We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option."
"SwaggerHub could be improved with better integration for tools."
"The customization and doc formatting options for documentation pages are restricted in SwaggerHub."
"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."
"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."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"We have to use additional tools to test APIs."
"SwaggerHub's UI needs to be improved as it looks very old school."
 

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 is very high and requires all five components in the API management solution."
"It's expensive when you compare it with others."
"The solution is expensive in comparison to other products."
"The tool's initial costing is expensive for small banks and financial institutions."
"The solution has a return on investment but is a little expensive."
"The product is expensive."
"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 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.
882,479 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Insurance Company
9%
Manufacturing Company
8%
Computer Software Company
7%
Financial Services Firm
16%
Computer Software Company
13%
Manufacturing Company
8%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise17
By reviewers
Company SizeCount
Small Business3
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?
This product is definitely expensive because if any issue occurs in the live environment or production environment, and our organization faces some issue with the IBM DataPower Gateway, then the IB...
What needs improvement with IBM DataPower Gateway?
The developer portal should be an integrated part of IBM DataPower Gateway to improve it. I think it is fine as is, and maybe no other additional features should be included in the next release. My...
What needs improvement with SwaggerHub?
We have tried automated code generation several times, and I think maybe some people are still using it somewhere, but it is not something that we do as a consolidated practice. At some point, we w...
What is your primary use case for SwaggerHub?
We still use SwaggerHub, but we did not change much in the way we are using it, meaning just limited functionality. For us, SwaggerHub serves as a central place to publish the documentation for our...
What advice do you have for others considering SwaggerHub?
As a technical person, I cannot comment on the money side, but we did not necessarily look to use the whole feature set of SwaggerHub. We do not do editing of the APIs in SwaggerHub; we basically u...
 

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: February 2026.
882,479 professionals have used our research since 2012.