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

Mindshare comparison

As of January 2026, in the API Management category, the mindshare of IBM API Connect is 5.0%, down from 6.3% compared to the previous year. The mindshare of OpenLegacy is 0.8%, 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 Connect5.0%
OpenLegacy0.8%
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

"The most valuable features are stability and security."
"WSRR is a powerful component for getting the endpoints."
"The solution is very stable."
"The services that I consume through IBM API Connect are beneficial. It can handle multiple API management."
"The functionalities on offer are very good."
"What's best about IBM API Connect is the excellent administration. The development tool that builds the API is also very simple, and user-friendly, and it doesn't consume too much time. Another valuable feature in IBM API Connect is its good reporting feature, particularly for operations, but the most valuable feature of the solution for the customer is security. IBM API Connect provides a DMZ and a security gateway between the external and internal environment, so you can publish your API safely. IBM API Connect can also integrate with any tool or middleware that works on open standards without the need for development or coding, so integration with the solution is easier."
"The technical support is good. Whenever we need anything, we have our IT team work with IBM to change whatever requirement is needed."
"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."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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 mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"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."
"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."
 

Cons

"Components, like caching, should be implemented as policies, not requiring dependency on an external solution."
"Business applications could be exposed to users."
"We have encountered challenges with IBM API Connect, particularly during significant upgrades. These upgrades demand substantial labour and financial resources, including consulting services from IBM. I'd like to see increased flexibility, more frequent updates with new features, an efficient upgrade process, and additional AI capabilities for future releases."
"There are some performance issues and issues related to asynchronous APIs."
"The implementation of IBM API Connect is complex, as it's an enterprise solution with many components that require more than one person. It's not a single product that you work on, and this is an area for improvement, but normally, it's good. Having a more structured model for IBM API Connect support is also room for improvement that would help customers better."
"The design time setup has a lot of customizable fields, but we need certain standard fields to be added, such as what all of the consuming systems are. This needs to be very clearly articulated during the design time."
"In terms of what needs improvement, some of the product documentation could be better."
"The automation and the simplicity could be improved."
"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."
"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."
"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."
 

Pricing and Cost Advice

"The price for IBM API Connect is reasonable. It's $20,000 to $30,000 yearly for a subscription, and the pricing could vary around $40,000 per year, per subscription. Its price is reasonable for customers who have around sixty million API calls yearly for unlimited environments."
"The pricing is too expensive with IBM. Sometimes, we prefer to go with an open source or something more lightweight."
"It is a pretty expensive tool."
"Pricing for IBM API Connect varies, e.g. it could be subscription-based. Deploying it on private cloud also means you have to own most of the software licensing."
"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."
"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."
"The price of the solution is expensive. However, there are a lot of customization capabilities."
"API Connect is quite pricey."
"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,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Insurance Company
12%
Manufacturing Company
8%
Computer Software 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,082 professionals have used our research since 2012.