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
5th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
75
Ranking in other categories
Integration Platform as a Service (iPaaS) (7th)
OpenLegacy
Ranking in API Management
35th
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 April 2025, in the API Management category, the mindshare of IBM API Connect is 6.4%, up from 6.2% compared to the previous year. The mindshare of OpenLegacy is 0.3%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

KavitaChavan - PeerSpot reviewer
Quite flexible and provides excellent performance for API gateway
The only disadvantage I can see is that it requires heavy hardware support, which can be considered quite expensive. In terms of new functionality, I think the analytics can be improved in V10. The analytics feature was better in the older version, 2.18. But in V10, it's not as flexible. When exporting analytics as KSP or JSON, it's not well formatted. They can work on enhancing the analytics part. Additionally, they can focus on reducing the hardware cost.
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 solution is very stable."
"The centralized management: this provides a management module that can deploy and apply security policies to all APIs, including all the gateways that are deployed on-premises and on any cloud because the gateway component can run at a VMware or in a Kubernetes cluster."
"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."
"We really like the runtime capabilities of IBM API Connect. The creation of products and the control of the monetization and hit rate are some of the features which we've found very valuable."
"The most valuable feature of IBM API Connect is the security of the protocol."
"I have found IBM API Connect to be highly secure, efficient, easy to deploy, and has a great GUI. It can operate and integrate well with other vendors, such as Amazon, Google, and Microsoft."
"The support is good and active. I rate the technical support a nine out of ten."
"The interface is very nice. It makes the solution easy to use and navigate."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"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 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."
 

Cons

"Installation is weak."
"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."
"I would like to see support for non-Java based services. We struggle a bit to be able to deploy and connect our .NET services because of things like data types. We had to map a couple of things. For one solution provider, we had to move them to .NET Core before we could use it properly. I would like to see more agnostic tool service platforms rather than moving it more towards Java or open source."
"Different versions of the same thing can mean unnecessary duplication."
"It needs to be less taxing on compute resources."
"The administration of the user interface and the technical documentation are areas of concern in the solution where improvements are required."
"It is expensive within this class of products."
"Due to bugs in integration, we have to look for workaround on fixing and using DataPower as gateway."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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 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."
"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."
 

Pricing and Cost Advice

"This is a licensed product. If your company is looking to obtain a license, you have to work with IBM partners."
"We pay for the IBM API Connect monthly. We only need to pay the standard licensing fee."
"It is expensive when compared to other products in this class. There were no extra fees for add-ons or technical support."
"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."
"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."
"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."
"It would be a good idea to bring down the pricing by at least 20 to 30 percent."
"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.
845,040 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
23%
Financial Services Firm
18%
Insurance Company
10%
Computer Software Company
9%
Financial Services Firm
36%
Insurance Company
13%
Computer Software Company
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
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?
Price depends on many factors like size of the deal, competitive factors, timing, customer profile or where the pricing for API Calls is very competitive comparing to any of the leader players.
What needs improvement with IBM API Connect?
The only downside where improvements are needed is probably on the licensing side. Scalability is an issue with IBM API Connect, making it an area where improvements are required.
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: March 2025.
845,040 professionals have used our research since 2012.