No more typing reviews! Try our Samantha, our new voice AI agent.

IBM DataPower Gateway vs WSO2 Enterprise Integrator comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 3, 2025

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 Enterprise Service Bus (ESB)
4th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
32
Ranking in other categories
Application Infrastructure (9th), SOA Application Gateways (1st), API Management (11th)
WSO2 Enterprise Integrator
Ranking in Enterprise Service Bus (ESB)
7th
Average Rating
7.6
Reviews Sentiment
6.8
Number of Reviews
20
Ranking in other categories
Data Integration (28th)
 

Mindshare comparison

As of June 2026, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 5.1%, down from 5.8% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 5.7%, up from 5.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Mindshare Distribution
ProductMindshare (%)
IBM DataPower Gateway5.1%
WSO2 Enterprise Integrator5.7%
Other89.2%
Enterprise Service Bus (ESB)
 

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.
AC
Technical director at Cremete
Effective data transformation and integration in complex environments with high functionality
Something that could be improved in WSO2 Enterprise Integrator is that the problem is not a lack of capability or functionalities. The problem is that it is a very complex environment. To put your hand on this environment is a very demanding task. This is the real problem. The problem is not about the product, but about the complexity to manage, to configure, to decide what to do. I have some experience using SAP R/3. It seems to me something similar. When you have to configure a situation with a client, especially for a client not in an industrial sector, but in a service sector, it is quite usual that you are in trouble for some reason. This is always the story that I found in the implementations I have done. Maybe there are only three or four big problems, in some other cases there are more than that, but this is the situation usually. For WSO2 Enterprise Integrator, not the same, but I must say it is quite often there is a need to put together some pieces and make it work in a coordinated way.

Quotes from Members

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

Pros

"We did not experience any downtime, even if the number of transactions increased heavily."
"Support for PCA and non-PCA services is valuable."
"If you have an API application in your organization that you want to make safe and secure, in addition to your existing WAF or load balancer, this product comes with all those capabilities:"
"What I like most is the stability."
"Since it is a gateway, it provides a lot of security features."
"I recommend this solution; it is a good security application and it incorporates integrations and the latest security controls that are available in the market."
"The most valuable features of this solution are the appliance hardware, the software embedded within the hardware appliance machine, making it one of the best security platforms in the market that is easy to use, easy to install, and resilient for high availability."
"I like that it is very stable, and we never experience any downtime."
"I like the user-friendly system and development of the service-oriented architecture."
"The productivity is the most valuable feature. It is very easy to write remediations."
"It's a very complete product. It allows us to network security and add more layers of security to the system."
"The solution basically conforms to our standards."
"Currently, I find the configuration part quite valuable, where you can easily configure things."
"The built-in connectors help with quick connectivity to the platforms, and we are using this for both our banking and insurance clients."
"The connectors have been the most impactful features for handling integrations. I can use these connectors when I need specific connectivity with a third party, like a core banking system in BFSI. I don't need to do all the development. I take the specific connector, put in the IP address and password, and it takes care of everything."
"It has improved our time management because development is quicker."
 

Cons

"The DCDR process should be less complex."
"New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS."
"They should add features to manage API integrations."
"It is challenging to understand the solution's design and support skills."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"In the next release, I would like to see the product price reduced. It should be cheaper."
"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."
"An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product."
"The integration capabilities need to be improved."
"If I have to buy software, then it becomes expensive for me."
"In my opinion, the administration model and interface, of Carbon, are lacking in terms of its features and user experience."
"One of the reasons that we are looking for a replacement is their way of defining integration. The language of the XML structures that I use to describe the integrations are not that standard, and it's not easy to find people who are familiar with this approach."
"The customization can be a bit difficult."
"We had some challenges with the installation of this solution."
"You cannot include the validation of XPath."
"I would like to see better documentation for the open-source version."
 

Pricing and Cost Advice

"The cost is very high and requires all five components in the API management solution."
"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."
"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 solution is expensive in comparison to other products."
"It is an expensive solution."
"The tool's initial costing is expensive for small banks and financial institutions."
"The licensing cost is very expensive."
"The cost is better than IBM Cloud Pak."
"The open-source, unsupported version is available free of charge."
"The pricing of WSO2 Enterprise Integrator for enterprise subscriptions can be considered expensive, especially from the perspective of someone who prefers open-source software."
"I rate the product price a six on a scale of one to ten, where one is low price and ten is high price."
"It is a low-cost solution."
"The solution costs about 20,000 or 30,000 euros per year, per instance."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
902,456 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
25%
Manufacturing Company
8%
Insurance Company
8%
Government
7%
Financial Services Firm
11%
Comms Service Provider
8%
Construction Company
7%
Manufacturing Company
6%
 

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 Business8
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

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 is your primary use case for IBM DataPower Gateway?
The primary purposes for which IBM DataPower Gateway is used include security purposes, and sometimes you need to put some configurations and mapping into the process.
What needs improvement with WSO2 Enterprise Integrator?
Something that could be improved in WSO2 Enterprise Integrator is that the problem is not a lack of capability or functionalities. The problem is that it is a very complex environment. To put your ...
What is your primary use case for WSO2 Enterprise Integrator?
A typical use case for WSO2 Enterprise Integrator is when I am in an interoperability environment with healthcare facilities and I have to put together a lot of applications that share some HL7 mes...
What advice do you have for others considering WSO2 Enterprise Integrator?
For simpler tasks or simpler use cases, we avoid using WSO2 Enterprise Integrator because it is quite complex. So it is easier to manage some more simple solutions than that. WSO2 Enterprise Integr...
 

Also Known As

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

Overview

 

Sample Customers

RBL Bank, Availity
West
Find out what your peers are saying about IBM DataPower Gateway vs. WSO2 Enterprise Integrator and other solutions. Updated: June 2026.
902,456 professionals have used our research since 2012.