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
9th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
77
Ranking in other categories
Integration Platform as a Service (iPaaS) (10th)
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 November 2025, in the API Management category, the mindshare of IBM API Connect is 5.8%, down from 6.2% 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 Connect5.8%
OpenLegacy0.5%
Other93.7%
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 functionalities on offer are very good."
"It acts as a central gateway for both external APIs and underlying systems. It's basically a central middleware for hosting APIs to the internet and consuming APIs from internal systems. It provides central governance for any APIs going outside the network, ensuring security and a common contract for API definitions."
"Overall, I rate it nine out of ten."
"It offers enhanced security features to protect APIs, enforce access control, and secure sensitive data."
"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."
"The management of the API and API portal is good."
"The support is good and active. I rate the technical support a nine out of ten."
"The gateway is the most valuable aspect of this solution."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"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."
"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."
"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."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
 

Cons

"The solution is overly complex."
"The automation and the simplicity could be improved."
"Improving the documentation would be beneficial as it currently presents navigation challenges. Incorporating a step-by-step guide could facilitate the integration or migration of various systems, including databases. The existing documentation only comprises plain text, hence incorporating more interactive instructions could enhance its usefulness."
"The solution could improve security and performance."
"They seem to have left out a feature for microservices and also a certification module for OIDC."
"Understanding the architecture, deployment criteria, and communication methods of the installation can be time-consuming."
"It should be cheaper."
"The product's setup phase and its setup for the users in different environments, along with DevOps integration, are areas of concern where there is a need for improvement."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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."
"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."
"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."
 

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."
"It is an expensive solution. The licensing model is based on a per-subscription and per-subscriber end-user basis, meaning the price is determined by the end-users of the platform."
"We pay for the IBM API Connect monthly. We only need to pay the standard licensing fee."
"IBM API Connect could be cheaper."
"It's an expensive product."
"I rate the product price a seven on a scale of one to ten, where one is a low price, and ten is a high price."
"API Connect is expensive - I'd rate their pricing five out of ten."
"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 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.
873,085 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?
I have not worked on pricing, setup cost, or licensing for IBM API Connect; that part is handled by the architect.
What needs improvement with IBM API Connect?
To improve IBM API Connect, based on customer experience, you could work on latency. You can increase scalability and availability. If you're connecting with any other cloud, it connects to the inf...
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.
873,085 professionals have used our research since 2012.