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

IBM DataPower Gateway vs Tyk 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
12th
Average Rating
8.4
Reviews Sentiment
6.5
Number of Reviews
30
Ranking in other categories
Enterprise Service Bus (ESB) (5th), Application Infrastructure (12th), SOA Application Gateways (1st)
Tyk
Ranking in API Management
17th
Average Rating
7.6
Reviews Sentiment
6.5
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the API Management category, the mindshare of IBM DataPower Gateway is 3.7%, up from 3.7% compared to the previous year. The mindshare of Tyk is 2.1%, up from 1.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway3.7%
Tyk2.1%
Other94.2%
API Management
 

Featured Reviews

AkshaySawant - PeerSpot reviewer
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.
MarkDoherty - PeerSpot reviewer
Fastest to get up and running and fewer idiosyncrasies than competitors
In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly better communication with the customer base that would be my main issue with them. But as a product, it's very difficult to find any major faults.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Its initial setup was straightforward."
"The scalability of the solution is good."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"I like the API Gateway feature."
"I like the tool's security. Also, all functionalities are integrated within on platform."
"What I like most is the stability."
"It is very easy to set up and configure, even for users with no prior experience."
"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 feature I find most valuable is that this solution allows us to manage our security."
"The most valuable feature is the load balancing with the circuit-breaker function."
"It is a good product for API management."
"The portal for developers that this solution provides has great functionality."
"You can set up workflows and write limited pieces of logic."
"The scalability is very good. That was a key factor in the selection, like how it could be pushed to high volume and scalability, which seemed to be very good."
 

Cons

"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"From the development perspective, it has limitations because it only supports the XSLT language. It does not support multiple languages."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product. Sometimes, when the customer use case is just a very small subset of what's being offered in IBM DataPower Gateway, then the product can be expensive, making my company lose some of the opportunities because of the expensive pricing. A lower price point for IBM DataPower Gateway, even if that results in a less feature-rich version, would be appreciated. In terms of additional features that I'd like to see in the next release of IBM DataPower Gateway, nothing specific comes to mind because IBM constantly improves its standards and provides quarterly updates to the product, so it's quite fine."
"In terms of OEM support, it is poor. If I raise a CBRT one, as per the SLA, they should respond in one hour, however, sometimes it takes four or five hours to respond."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"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."
"Making it more user-friendly would be an improvement."
"It is a costly product."
"In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly better communication with the customer base that would be my main issue with them."
"We would like a better tool for generating documentation for the APIs to be developed."
"We ran it for a while, but then we decided to move away from Tyk, because Tyk's cloud version, the SaaS version, has a significant limitation of limited flexibility, so you can't program very much."
"Sometimes when new features are released, they are not immediately stable."
"It is a young product and does not have the kind of brand recognition that would make it a more popular solution with our clients."
"I would like to see some additional features like having some extensions for .NET core because we use it for our back-end language."
 

Pricing and Cost Advice

"The solution is expensive in comparison to other products."
"It is an expensive solution."
"The cost is very high and requires all five components in the API management 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."
"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."
"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 solution has a return on investment but is a little expensive."
"There are different versions and plans available depending on the requirements, so there is flexibility in terms of the pricing."
"The cost curve is far smoother, both in terms of volume and the number of calls it's running on, compared to most competitors. So it's a tad more expensive at the very low end, but the curve is nothing like Apigee or some of the others."
"It had a free version, which suited many of our needs, but not all, but we were happy to go ahead with the licensed version as well, which is the paid version."
"We are using the open-source version of this product, so there are no licensing costs for its use."
"The price is low compared to other products of a similar type."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
868,759 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Insurance Company
9%
Computer Software Company
8%
Manufacturing Company
7%
Financial Services Firm
24%
Computer Software Company
14%
Comms Service Provider
9%
Manufacturing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise16
No data available
 

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?
I have significant experience with the IBM DataPower Gateway. As a security product, it is very good. However, from the development perspective, it has limitations because it only supports the XSLT...
What do you like most about Tyk?
The scalability is very good. That was a key factor in the selection, like how it could be pushed to high volume and scalability, which seemed to be very good.
What is your experience regarding pricing and costs for Tyk?
The pricing is actually quite competitive. In Azure environments, it gets beaten by Microsoft API Gateway, but on the other hand, it offers some features that Microsoft lacks. So it really comes do...
What needs improvement with Tyk?
In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly ...
 

Also Known As

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

Overview

 

Sample Customers

RBL Bank, Availity
Trip Advisor, Juniper Networks, AT&T
Find out what your peers are saying about IBM DataPower Gateway vs. Tyk and other solutions. Updated: September 2025.
868,759 professionals have used our research since 2012.