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
8.0
Reviews Sentiment
6.5
Number of Reviews
79
Ranking in other categories
Integration Platform as a Service (iPaaS) (14th)
OpenLegacy
Ranking in API Management
36th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (83rd)
 

Mindshare comparison

As of February 2026, in the API Management category, the mindshare of IBM API Connect is 4.9%, down from 6.2% compared to the previous year. The mindshare of OpenLegacy is 0.9%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM API Connect4.9%
OpenLegacy0.9%
Other94.2%
API Management
 

Featured Reviews

SM
Works at a outsourcing company with 5,001-10,000 employees
Have addressed performance challenges while benefiting from flexible subscription models and reliable user access
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 infrastructure which needs to be managed with the customers and cloud providers, so if you have a setup, we can handle it easily. I have faced latency issues on the server, related to our management. If you need to stabilize your server based on peak traffic, you need to configure the scalability model. You need to know when traffic peaks, so use auto-scaling when traffic comes. If the application is not in use, the value should be zero, and it starts from zero. Based on customer experience, the value will increase, and when there is no customer servicing, the peak would be reduced, making the value remain zero. Following this approach, you should be able to optimize costs and satisfy customer experience.
reviewer1042905 - PeerSpot reviewer
VP, Chief Enterprise Integration Architect at a financial services firm with 10,001+ employees
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

"It has all of the tools that are needed for the specific mission."
"IBM API Connect has a designer and CLI features which can be used to completely automate the API, so if a business analyst has a basic understanding of what the input and output payload is, they can directly create the API."
"The services that I consume through IBM API Connect are beneficial. It can handle multiple API management."
"The solution offers a pretty good SLA."
"Using API Connect allows us to quickly create proxy APIs and saves time on end-to-end testing, which lets us deliver quickly to clients."
"API Connect is a very good platform for the development of APIs."
"The capabilities are very good."
"Since it runs on top of Datapower, all Datapower based custom policies can be utilized and exported to API connect but its not straightforward/simple process."
"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."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"Opens the door to connect modern web products to an old legacy system."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
 

Cons

"The initial setup and installation could be easier."
"The implementation process could benefit from improvements, as it may take some time to become accustomed to the deployment."
"The installation process could use improvement. I hope that in the next release, the installation process is easier."
"Installation is weak."
"Our main pain points are in these two areas: creating a better developer portal and improving stability in terms of synchronization and monetization."
"The only downside where improvements are needed is probably on the licensing side."
"Like any typical IBM infrastructure setup, you need to learn to set it up yourself. It's not one of those simple zip files or an archive unzip and you're up and running in some few minutes. Knowledge to set it up is key."
"I have faced latency issues on the server, related to our management."
"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."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"Debugging and logging for programmers could be better."
"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."
"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."
 

Pricing and Cost Advice

"The price of the solution is very expensive, it can turn many customers away."
"IBM API Connect could be cheaper."
"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."
"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."
"The price of the solution is expensive. However, there are a lot of customization capabilities."
"API Connect was highly expensive for us, but the decision to switch was made before I joined the company. It seems like the company bought it, but they didn't know how to use it. After two years, they decided to reevaluate and conduct some cost estimates."
"It is expensive when compared to other products in this class. There were no extra fees for add-ons or technical support."
"The pricing is too expensive with IBM. Sometimes, we prefer to go with an open source or something more lightweight."
"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.
881,665 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Insurance Company
11%
Computer Software Company
8%
Manufacturing Company
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise10
Large Enterprise61
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 do not handle the pricing, setup cost, and licensing details.
What needs improvement with IBM API Connect?
We are relatively new to IBM API Connect, so I do not have significant improvements to suggest at this time.
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: December 2025.
881,665 professionals have used our research since 2012.