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

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)
6th
Average Rating
8.4
Reviews Sentiment
6.5
Number of Reviews
30
Ranking in other categories
Application Infrastructure (12th), SOA Application Gateways (1st), API Management (12th)
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 (29th)
 

Mindshare comparison

As of September 2025, in the Enterprise Service Bus (ESB) category, the mindshare of IBM DataPower Gateway is 6.3%, up from 5.8% compared to the previous year. The mindshare of WSO2 Enterprise Integrator is 5.6%, up from 5.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB) Market Share Distribution
ProductMarket Share (%)
IBM DataPower Gateway6.3%
WSO2 Enterprise Integrator5.6%
Other88.1%
Enterprise Service Bus (ESB)
 

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.
Ritesh_Shah - PeerSpot reviewer
Decreases the development timeframe and costs
The main issue with the product is pricing. It uses core-based pricing for WSO2 Enterprise Integrator and API Manager. It would be best if you had APIM by default. It provides many connectors for easy integration with third-party systems. Often, customers decide to develop using open-source tools like Spring Boot if there aren't many connectors required to avoid increasing costs. They'll develop this way and then deploy using APIM, the bare minimum needed. It is mainly required for very complicated setups with many connectors. In the implementations I've seen, people often used open-source tools because there weren't many third-party systems involved—just their organization's own systems. From WSO2 Enterprise Integrator, I expect them to bring up more and more connectors in the future. That's the main expectation. Having more connectors in various areas will help us when discussing new requirements. I don't have any specific use case right now, so I can't name a particular connector. But, as new technologies emerge, the relevant connectors should be there for those. WSO2 Enterprise Integrator mainly helps with the integration part, which can be simplified only if you have relevant connectors for whatever you're doing.

Quotes from Members

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

Pros

"I like all of the features in this product and it does what it's supposed to do."
"I like the API Gateway feature."
"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."
"You don't have to have a separate DMC proxy because DataPower Gateway is an appliance and will take care of a lot of security features. These include data validations, encryption, as well as XML or any type of scripting or security threats that are present."
"The product is stable...The product is scalable."
"It can look for the various security threats, productions, payload scanning, and perform routing based on the content type."
"Its initial setup was straightforward."
"The stability is excellent."
"It was mostly easy to set up the product."
"In my opinion, the most valuable aspect of this solution is its extensive range of adaptors and connectors. This feature holds significant importance and provides great value to users."
"It's a consolidated product. It works and it does its job pretty well."
"I like the user-friendly system and development of the service-oriented architecture."
"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."
"The solution basically conforms to our standards."
"The solution has two main parts: integration and transformation. It's very user-friendly and easy to understand for everyone."
 

Cons

"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."
"It is a costly product."
"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."
"The product's cost for data appliances or hardware is quite high. It needs improvement."
"IBM DataPower Gateway is quite big for smaller organizations, looking at different types of clients who are virtually assisted in this, I would say it's not really a good product for smaller firms."
"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."
"The integration capabilities need to be improved."
"In my opinion, the administration model and interface, of Carbon, are lacking in terms of its features and user experience."
"They should release upgrades more frequently."
"I would like to see better documentation for the open-source version."
"The setup can be difficult for those not familiar with the solution."
"You cannot include the validation of XPath."
"They should introduce better pricing for small companies."
"The product's price is an area of concern where improvements are required."
 

Pricing and Cost Advice

"It is an expensive solution."
"The cost is very high and requires all five components in the API management solution."
"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."
"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 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."
"This product is a bit expensive as IBM products are costly assets. However, for enterprise customers it is a worthwhile investment."
"The solution costs about 20,000 or 30,000 euros per year, per instance."
"It is a low-cost solution."
"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."
"The cost is better than IBM Cloud Pak."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
867,676 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
16%
Computer Software Company
16%
Government
6%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise2
Large Enterprise16
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise2
Large Enterprise11
 

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 would rate the pricing a two out of ten, with one being high price, and ten being low price. It's high-priced for smaller companies. But it is okay for enterprises. So, the price could be more fl...
What needs improvement with IBM DataPower Gateway?
The DCDR process should be less complex. AI should improve developer efficiency and effort. Whenever I am writing code, it should give recommendations automatically by incorporating AI so I can wri...
What do you like most about WSO2 Enterprise Integrator?
WSO2's analytics capability is good, considering the ELC support they provide.
What is your experience regarding pricing and costs for WSO2 Enterprise Integrator?
The product has reasonable and competitive pricing for enterprise customers. It is expensive for small businesses especially. They are using the open-source solution, and they find it expensive sin...
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 ...
 

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: September 2025.
867,676 professionals have used our research since 2012.