IBM Cloud Pak for Integration vs OpenLegacy comparison

IBM and OpenLegacy are both solutions in the API Management category. IBM is ranked #24 with an average rating of 8.5, while OpenLegacy is ranked #35. IBM holds a 0.4% mindshare in APIM, compared to OpenLegacy’s 0.3% mindshare. Additionally, 100% of IBM users are willing to recommend the solution, compared to 80% of OpenLegacy users who would recommend it.

IBM Cloud Pak for Integration

Read 5 IBM Cloud Pak for Integration reviews

755 Views
553 Comparison Views

100% willing to recommend

OpenLegacy

Read 5 OpenLegacy reviews

450 Views
283 Comparison Views

80% willing to recommend

IBM Cloud Pak for Integration

OpenLegacy

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

OpenLegacy and IBM Cloud Pak for Integration compete in the enterprise integration category, each providing unique benefits tailored to different organizational requirements. OpenLegacy has the upper hand in cost efficiency and minimal disruption during deployment, while IBM Cloud Pak for Integration leads with its comprehensive feature set catering to complex integration needs.

Features: OpenLegacy supports rapid legacy system integration through low-code development and streamlined API creation, optimizing for speed and efficiency. Additionally, it offers straightforward legacy system connectivity and minimizes disruptions. IBM Cloud Pak for Integration boasts a suite that includes API management, data and application integration, messaging services, and event streams, suitable for enterprises needing an all-encompassing integration solution.

Room for Improvement: OpenLegacy could enhance its functionality by expanding integration capabilities to cater to more complex scenarios, diversifying its feature set, and improving scalability options. IBM Cloud Pak for Integration might focus on simplifying its deployment process, reducing its cost barrier, and enhancing the user interface for a more seamless experience.

Ease of Deployment and Customer Service: OpenLegacy offers a straightforward deployment model with minimal learning curves, complemented by excellent customer service. IBM Cloud Pak for Integration, while requiring a more complex setup due to its broad features, provides extensive support resources to aid deployment. OpenLegacy is known for its simplicity and quick implementation, whereas IBM requires a dedicated team due to its intricate nature.

Pricing and ROI: OpenLegacy provides an affordable entry point with a fast return on investment, driven by low initial costs and efficient integration processes. IBM Cloud Pak for Integration necessitates a higher upfront investment, justified by its extensive and scalable capabilities designed for larger enterprises with comprehensive integration needs.

To learn more, read our detailed IBM Cloud Pak for Integration vs. OpenLegacy Report (Updated: March 2025).

Buyer's Guide

IBM Cloud Pak for Integration vs. OpenLegacy

March 2025

Download the complete report

Helped 846,617 peers since 2012

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 Cloud Pak for Integration

Ranking in API Management

24th

Average Rating

8.6

Reviews Sentiment

7.0

Number of Reviews

Ranking in other categories

Cloud Data Integration (15th)

OpenLegacy

Ranking in API Management

35th

Average Rating

7.6

Reviews Sentiment

6.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of April 2025, in the API Management category, the mindshare of IBM Cloud Pak for Integration is 0.4%, down from 0.6% 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

Neelima Golla

Senior Software Engineer at NessPRO Italy

A hybrid integration platform that applies the functionality of closed-loop AI automation

I recommend using it because, in today's context, the cloud plays a significant role. Within the same user interface, you can develop applications and manage multiple applications, making it a more user-friendly option. Moreover, you can explore various other technologies while deploying on the cloud, broadening your knowledge of cloud technologies. In my case, the transition led to my learning of Kubernetes, enabling multi-scaling and expanding my technical skills. It was a valuable experience, and I had the opportunity to learn many new things during the migration process. I can easily rate it an eight or nine out of ten.

Read full review

reviewer1042905

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.

Read full review

Quotes from Members

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

Pros

"It is a stable solution."

"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."

"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."

"Cloud Pak for Integration is definitely scalable. That is the most important criteria."

"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."

"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."

"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."

"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."

Cons

"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."

"Its queuing and messaging features need improvement."

"The initial setup is not easy."

"The pricing can be improved."

"Enterprise bots are needed to balance products like Kafka and Confluent."

"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."

"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."

"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."

"Debugging and logging for programmers could be better."

"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."

Pricing and Cost Advice

"The solution's pricing model is very flexible."

"It is an expensive 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."

See which vendors are best for you

Use our free recommendation engine to learn which API Management solutions are best for your needs.

See recommendations

846,617 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

19%

Computer Software Company

13%

Government

Manufacturing Company

Financial Services Firm

33%

Insurance Company

14%

Computer Software Company

10%

Manufacturing Company

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

Questions from the Community

What do you like most about IBM Cloud Pak for Integration?

The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of ...

See all answers

What needs improvement with IBM Cloud Pak for Integration?

Enterprise bots are needed to balance products like Kafka and Confluent.

See all answers

What is your primary use case for IBM Cloud Pak for Integration?

It manages APIs and integrates microservices at the enterprise level. It offers a range of capabilities for handling APIs, microservices, and various integration needs. The platform supports thousa...

See all answers

Ask a question

Earn 20 points

Comparisons

IBM App Connect vs IBM Cloud Pak for Integration

Compared 45% of the time

IBM API Connect vs IBM Cloud Pak for Integration

Compared 15% of the time

IBM DataPower Gateway vs IBM Cloud Pak for Integration

Compared 7% of the time

IBM InfoSphere DataStage vs IBM Cloud Pak for Integration

Compared 7% of the time

AWS Glue vs IBM Cloud Pak for Integration

Compared 7% of the time

More IBM Cloud Pak for Integration Competitors

Kong Gateway Enterprise vs OpenLegacy

Compared 32% of the time

MuleSoft API Manager vs OpenLegacy

Compared 22% of the time

IBM API Connect vs OpenLegacy

Compared 18% of the time

Amazon API Gateway vs OpenLegacy

Compared 15% of the time

webMethods.io vs OpenLegacy

Compared 13% of the time

More OpenLegacy Competitors

Product Reports

Buyer's Guide

API Management

April 2025

Download IBM Cloud Pak for Integration product report

Buyer's Guide

OpenLegacy

March 2025

Download OpenLegacy product report

Overview

IBM Cloud Pak for Integration gives you complete, flexible integration using capabilities you need to move at today's speed of business, including the tools to help you achieve your application modernization goals as part of your journey to the cloud.

IBM

OpenLegacy helps organizations quickly launch innovative digital services by extending their core back-end systems to the web, mobile and cloud in days or weeks versus months. Our microservice-enabled API integration and management software quickly reduces project backlog by automating and accelerating microservices and API creation, deployment, testing and management from core applications, mainframes and databases. Together, business and IT teams can quickly, easily and securely meet consumer, partner or employee demands for digital services without modernizing or replacing core systems, and without special programming skills or invasive changes to existing systems and architectures. OpenLegacy is designed for ongoing management of microservices APIs and is based on open standards, so our software plays nice with your current technology stack and supports agile, DevOps and continuous development. Learn why leading companies choose OpenLegacy at www.openlegacy.com.

OpenLegacy

Sample Customers

CVS Health Corporation

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...

Buyer's Guide

IBM Cloud Pak for Integration vs. OpenLegacy

March 2025

Free Report: IBM Cloud Pak for Integration vs. OpenLegacy

Find out what your peers are saying about IBM Cloud Pak for Integration vs. OpenLegacy and other solutions. Updated: March 2025.

DOWNLOAD NOW

846,617 professionals have used our research since 2012.

See our IBM Cloud Pak for Integration vs. OpenLegacy report.

See our list of best API Management vendors.

We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.