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

IBM API Connect vs OpenLegacy 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 API Connect
Ranking in API Management
8th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
77
Ranking in other categories
Integration Platform as a Service (iPaaS) (9th)
OpenLegacy
Ranking in API Management
36th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the API Management category, the mindshare of IBM API Connect is 6.0%, down from 6.3% compared to the previous year. The mindshare of OpenLegacy is 0.5%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM API Connect6.0%
OpenLegacy0.5%
Other93.5%
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.
reviewer1042905 - PeerSpot reviewer
The biggest advantage is how simple the technology was.
I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be. OpenLegacy handles the bread-and-butter TP monitoring stuff, but I am working for one of the six banks in the United States still using the Hogan mainframe, which has a slightly proprietary mechanism. But OpenLegacy currently doesn't have a connector for Hogan. So it would help if they could build one. That would appeal to financial institutions that still use Hogan, like US Bank, Wells Fargo, KeyBank, and Vanguard.

Quotes from Members

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

Pros

"The most valuable feature of IBM API Connect is the security of the protocol."
"It is quite stable. We've not had any problem. It has made for a good buy because we are finding that other companies that have similar set ups go down maybe once a month."
"DataPower Gateway holds significant value for us as it serves as the cornerstone of our enterprise security controls."
"The interface is very nice. It makes the solution easy to use and navigate."
"The most valuable feature is the security we get from this solution. I know of a bank that uses it to ensure that everything is secure. The second feature I like is the retail environment, where we actually want to be able to provide as many suppliers and consumers with APIs as possible. If you are well-trained in the writing of RESTful API's, you can actually publish an API in a matter of minutes, test it, and publish it."
"Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and potentially billing rules."
"Its speed and performance are valuable."
"The main benefits of IBM API Connect for our API life cycle management are the core API functionalities, the developer's portal, and robust security capabilities. IBM API Connect's security protocols enhance our data protection strategies by offering end-to-end security, mechanisms to counter common attacks like DDoS, and the ability to define policies for API groups to control traffic and prevent unwanted access to our systems."
"The biggest advantage of OpenLegacy was how simple the technology was. We were able to build out the OpenLegacy parts very quickly. We put together a couple hundred APIs in six months."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"Opens the door to connect modern web products to an old legacy system."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
 

Cons

"The administration of the user interface and the technical documentation are areas of concern in the solution where improvements are required."
"Installation is weak."
"The only downside where improvements are needed is probably on the licensing side."
"There are issues with upgrading in the cloud version. The cloud version is extremely buggy. We prefer to use the on-premise version."
"The solution is overly complex."
"Due to bugs in integration, we have to look for workaround on fixing and using DataPower as gateway."
"IBM API Connect could improve the security of the application and the integration."
"It would be nice to have a SaaS solution that can be deployed into the cloud."
"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."
"Debugging and logging for programmers could be better."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
 

Pricing and Cost Advice

"It is quite an expensive product."
"API Connect is quite pricey."
"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 is expensive - I'd rate their pricing five out of ten."
"This is a licensed product. If your company is looking to obtain a license, you have to work with IBM partners."
"It is expensive when compared to other products in this class. There were no extra fees for add-ons or technical support."
"We pay for the IBM API Connect monthly. We only need to pay the standard licensing fee."
"It's an expensive product."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
869,883 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Insurance Company
12%
Computer Software Company
10%
Manufacturing Company
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise10
Large Enterprise59
No data available
 

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...
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

Heineken, Tine, Finologee, Axis Bank
Many of openLegacy's global customers are among the Global 100 companies. Review case studies in these industries: Agriculture, Airport Authority, Automotive, Auto, Finance, Insurance, Government, Healthcare, Manufacturing, and Retailwww.openlegacy.com/case-studie...
Find out what your peers are saying about IBM API Connect vs. OpenLegacy and other solutions. Updated: September 2025.
869,883 professionals have used our research since 2012.