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
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)
Tyk
Ranking in API Management
18th
Average Rating
7.8
Reviews Sentiment
6.3
Number of Reviews
7
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 Tyk is 2.0%, up from 2.0% 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%
Tyk2.0%
Other94.9%
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.
reviewer2113719 - PeerSpot reviewer
Technical Support Analyst at a tech vendor with 10,001+ employees
Internal API gateway has improved security frameworks and now provides unified API visibility
The best features Tyk offers are highly customizable options, effective traffic management, and security, making it easy to configure and use. The customizability of Tyk is evident in our validation of the token—specifically with our internal identity and access management. There were challenges on the network side and in managing token validity and the public key, but Tyk allowed us to configure these aspects effectively. I believe those are the standard out-of-the-box capabilities provided by Tyk that we are using, particularly regarding traffic management and security. Tyk has positively impacted my organization by providing standard API management capabilities, such as a single view for all APIs, discoverability, and role-based access control for overseeing who can see which APIs.

Quotes from Members

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

Pros

"Since it is a gateway, it provides a lot of security features."
"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 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 tool's security. Also, all functionalities are integrated within on platform."
"The scalability of the solution is good."
"IBM DataPower Gateway has positively impacted my organization by allowing me to implement rate limits on the different API usage, which is the benefit."
"I like all of the features in this product and it does what it's supposed to do."
"The solution is very easy to work with."
"Customer support is excellent, and their support personnel, along with professional services, know the product really well, resulting in a good experience dealing with them."
"The portal for developers that this solution provides has great functionality."
"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."
"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."
"You can set up workflows and write limited pieces of logic."
"It is a good product for API management."
 

Cons

"The two biggest issues of this solution are the complexity and the maintenance procedures."
"One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases."
"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 IBM community does not have much engagement from the IT community in Saudi Arabia and developers for this solution are difficult to find."
"Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition."
"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."
"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."
"We would like a better tool for generating documentation for the APIs to be developed."
"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."
"Compared to Apigee or Kong, I find they excel beyond Tyk, which is the reason for my score."
"I would like to see some additional features like having some extensions for .NET core because we use it for our back-end language."
"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."
"Sometimes when new features are released, they are not immediately stable."
"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."
 

Pricing and Cost Advice

"It's expensive when you compare it with others."
"The licensing cost is very expensive."
"The solution is expensive in comparison to other products."
"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 appliance is a bit on the expensive side for the workloads that are not too high."
"The product is expensive."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"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."
"The price is low compared to other products of a similar type."
"There are different versions and plans available depending on the requirements, so there is flexibility in terms of the pricing."
"We are using the open-source version of this product, so there are no licensing costs for its use."
"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."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
882,606 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
23%
Computer Software Company
10%
Comms Service Provider
9%
Manufacturing Company
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 Business5
Large Enterprise2
 

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 Tyk?
Tyk can improve in terms of AI capabilities, and the developer portal could benefit from enhancements such as user onboarding workflows. The developer community could be better, especially compared...
What is your primary use case for Tyk?
My main use case for Tyk is for internal API gateway. For a banking customer, I have internal APIs and external APIs, where internal APIs are mostly on Kubernetes. For internal API gateway, we have...
What advice do you have for others considering Tyk?
While we could not quantify any commercial improvement, developer experience has definitely improved. I would rate Tyk around an eight on a scale of one to ten because I have worked with other API ...
 

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