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

IBM API Connect vs IBM DataPower Gateway comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Apr 20, 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 API Connect
Ranking in API Management
8th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
76
Ranking in other categories
Integration Platform as a Service (iPaaS) (9th)
IBM DataPower Gateway
Ranking in API Management
12th
Average Rating
8.4
Reviews Sentiment
6.7
Number of Reviews
29
Ranking in other categories
Enterprise Service Bus (ESB) (5th), Application Infrastructure (9th), SOA Application Gateways (1st)
 

Mindshare comparison

As of July 2025, in the API Management category, the mindshare of IBM API Connect is 6.3%, up from 6.3% compared to the previous year. The mindshare of IBM DataPower Gateway is 4.0%, up from 3.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Shanmugasundaram Shanmuganathan - PeerSpot reviewer
Offers basic API orchestration and provides robust security and governance features
While Azure API Management offers configurable scalability, IBM API Connect relies on Kubernetes clusters. This might seem manual and require defining cluster instances upfront, but it's completely customizable and not on-the-fly scaling. It's completely custom-driven, not on-the-fly scaling, which some may consider cumbersome. Overall, I would rate the scalability an eight out of ten. Almost all applications we've been exposing lately go through this middleware, so it's used extensively. There are around sixty applications directly using it, but six Kubernetes clusters serve those applications. It's heavily used for integration, including system-to-system integration and product integrations. Our usage has been increasing year-on-year based on our needs.
Mehdi El Filahi - PeerSpot reviewer
Security features meets compliance needs and offers MPGW (Multi-Protocol Gateway) that simplifies integration efforts
While I like IBM products, I'm not an evangelist. I work with Java, Microsoft ASP.NET, and various technologies. I'm not tied to any specific vendor. However, I do find IBM to be a bit greedy. It's a large, profit-driven company. The support team is mostly based in India, and they follow a very structured process and protocol. Sometimes, it feels like playing ping pong with them – lots of back and forth before the problem gets escalated. You might even have to get your sales rep involved to push things along. For me, the support it could be better. Indian support teams aren't inherently bad, but with IBM, it feels impersonal. They respond, sure. But if it's a complex technical issue, they might ask you a lot of questions that just seem designed to waste your time. Sometimes it feels like they hope you'll get frustrated and solve the problem yourself.

Quotes from Members

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

Pros

"API Connect's most valuable feature is its ability to act as a gateway. It's very easy to configure security and everything else in it. You don't have to kill yourself implementing custom configurations."
"One of the most valuable features of this solution is that it protects our backend system. We are exposing services to external parties and using this solution to protect the backend system, and to have a navigation in between."
"One of the most valuable features is that we can seamlessly and harmoniously expose our capabilities, from a security point of view."
"This product is well integrated with other products. Its ability to interact with IBM Secure Gateway and other integration products is the core feature. Also, the lead time to put it into production is relatively short ."
"It is a very scalable solution."
"It has all of the tools that are needed for the specific mission."
"API Connect is a good product, and everything works fine. All the analytics are good, and it is easy to follow up. I like it in that sense. I'm more focused on following up on analytics by seeing how many API calls we are getting and where we see a lot of problems. I was working on that API level."
"It allows enterprises to expose some of their tech to outside stakeholders."
"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:"
"It's high-speed and it can be remotely administered via an API."
"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."
"It is easy to use, easy to install, and it's resilient for high availability."
"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."
"It is very easy to set up and configure, even for users with no prior experience."
"Its initial setup was straightforward."
 

Cons

"Components, like caching, should be implemented as policies, not requiring dependency on an external solution."
"In terms of what needs improvement, some of the product documentation could be better."
"Possible improvement is mainly around having more of the cloud oriented architecture bringing stability in adding new capabilities around security."
"They seem to have left out a feature for microservices and also a certification module for OIDC."
"There is room for improvement regarding the connectivity of the DevOps."
"Business applications could be exposed to users."
"The documentation needs to be a bit better."
"When comparing API Gateway with DataPower Gateway, several features in DataPower Gateway are absent in the APIC layer. Examples include the lack of connectivity to MQ."
"It is a costly product."
"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 two biggest issues of this solution are the complexity and the maintenance procedures."
"The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively."
"Small and medium-sized companies might look for cloud-hosted applications due to the cost."
"They should add features to manage API integrations."
"I would like the tool to improve its training."
"The programming language is only supported in XSLT and Gateway script."
 

Pricing and Cost Advice

"It is expensive when compared to other products in this class. There were no extra fees for add-ons or technical support."
"I haven't seen anyone go from on-premise to the cloud. In fact, I am seeing people go from the cloud to on-premise because the costs can quickly grow on the cloud."
"API Connect's license cost could be a little lower. But, unfortunately, there aren't many open-source API gateways. Ideally, some new developers could come up with a minimum-functionality open-source solution."
"The price of the solution is very expensive, it can turn many customers away."
"The price of the solution is expensive. However, there are a lot of customization capabilities."
"The pricing is too expensive with IBM. Sometimes, we prefer to go with an open source or something more lightweight."
"There was a need to purchase an upfront license or a one-time license or upfront license, but I cannot remember the details about it clearly."
"It is a pretty expensive tool."
"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."
"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 appliance is a bit on the expensive side for the workloads that are not too high."
"The cost is very high and requires all five components in the API management solution."
"The solution is expensive in comparison to other products."
"Most customers' use case budgets are not inlined with the price of IBM DataPower Gateway. It is too expensive."
"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 product is expensive."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
860,711 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Educational Organization
12%
Insurance Company
12%
Computer Software Company
9%
Financial Services Firm
29%
Insurance Company
10%
Computer Software Company
9%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about IBM API Connect?
Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and potentially billing rules.
What is your experience regarding pricing and costs for IBM API Connect?
Pricing depends on how many instances run across environments. I don't deal with licensing, but compared to other IBM products, the licensing is not significantly higher.
What needs improvement with IBM API Connect?
When comparing API Gateway with DataPower Gateway, several features in DataPower Gateway are absent in the APIC layer. Examples include the lack of connectivity to MQ ( /categories/message-queue-mq...
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...
 

Also Known As

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

Overview

 

Sample Customers

Heineken, Tine, Finologee, Axis Bank
RBL Bank, Availity
Find out what your peers are saying about IBM API Connect vs. IBM DataPower Gateway and other solutions. Updated: June 2025.
860,711 professionals have used our research since 2012.