IBM API Connect vs OpenLegacy comparison

Read 5 OpenLegacy reviews

477 Views
316 Comparison Views

80% willing to recommend

IBM API Connect

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

IBM API Connect and OpenLegacy are competing products in the API management category. IBM API Connect appears to have the upper hand with its extensive features and integration capabilities tailored for enterprise environments, while OpenLegacy's modern technology and quick deployment options make it an appealing choice for businesses seeking agility and cost savings.

Features: IBM API Connect offers extensive API lifecycle management, robust security, and in-depth analytics, making it suitable for large enterprises needing comprehensive control and insights. OpenLegacy excels in rapid legacy system integration and microservice generation, which is ideal for organizations focused on modernization and operational streamlining.

Room for Improvement: IBM API Connect could improve its deployment process, which tends to be complex due to its wide range of capabilities, potentially extending initial setup time. Documentation could be more user-friendly to facilitate quicker installations. It would also benefit from enhancing its microservice support further. OpenLegacy can improve upon scalability for very large enterprise demands, expand its analytics capabilities to match those of its larger competitors, and increase its cloud integration features for hybrid environments.

Ease of Deployment and Customer Service: OpenLegacy provides a straightforward deployment model, minimizing time-to-market with streamlined processes suitable for legacy systems, and it focuses on responsive customer service. IBM API Connect offers comprehensive support and documentation but tends to require more setup time due to its extensive capabilities, which can be intricate for users unfamiliar with its system.

Pricing and ROI: IBM API Connect has a perceived higher setup cost; however, it promises a strong ROI for enterprises that can fully leverage its extensive range of features over time. OpenLegacy presents a cost-effective solution with fast ROI, especially attractive to businesses aiming to reduce costs while modernizing efficiently without significant initial investments.

To learn more, read our detailed IBM API Connect vs. OpenLegacy Report (Updated: January 2025).

IBM API Connect vs. OpenLegacy

Download the complete report

Helped 831,265 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 API Connect

Ranking in API Management

5th

Average Rating

8.0

Reviews Sentiment

6.6

Number of Reviews

Ranking in other categories

Integration Platform as a Service (iPaaS) (7th)

OpenLegacy

Ranking in API Management

34th

Average Rating

7.6

Reviews Sentiment

6.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of January 2025, in the API Management category, the mindshare of IBM API Connect is 6.5%, up from 6.4% compared to the previous year. The mindshare of OpenLegacy is 0.2%, down from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.

API Management

Featured Reviews

Shanmugasundaram Shanmuganathan

Solutions Architect at Synechron

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.

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

"The most valuable feature for me is the ability to distribute work among our API developers, so we don't have to do all the work as IBM API Connect administrators and IBM DataPower administrators."

"Our version supports containerized integration. I can write APIs, which can be moved into a testing environment without needing a forklift. It can check if APIs are compliant before moving them into production."

"Policy configurations are pretty easy."

"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 capabilities are very good."

"It is a complete all-in-one solution."

"Security is well organized and managed within the solution."

"The main benefits of IBM API Connect for our API life cycle management are the core API functionalities, the developer's portal, and robust security capabilities. IBM API Connect's security protocols enhance our data protection strategies by offering end-to-end security, mechanisms to counter common attacks like DDoS, and the ability to define policies for API groups to control traffic and prevent unwanted access to our systems."

More IBM API Connect pros

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

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

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

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

"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."

"Opens the door to connect modern web products to an old legacy system."

Cons

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

"Understanding the architecture, deployment criteria, and communication methods of the installation can be time-consuming."

"The developmental process is not quite user-friendly."

"The solution would be better if it had cloud functionalities."

"One thing about API Connect that could be improved is the security schemes. There are so many security schemes, and from a product perspective, IBM could improve the user experience of the configuration security scheme."

"The integration of cloud-based services is where we're looking for improvement in this platform."

"The integration of an API gateway that implements the sidecar pattern, which can be deployed in cloud applications, and expose the microservices directly in each pod, this can be more decentralized components."

"We ran it on top of the Kubernetes cluster, so it wasn't a standalone service. In the worst-case scenario, API Connect couldn't stay online if all the containers went down. We had to restart all the services. We shut down all the containers automatically one by one."

More IBM API Connect cons

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

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

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

"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

"It can be quite expensive. It's okay for large-scale usage but quite expensive for smaller-scale implementations."

"API Connect is quite pricey."

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

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

"It is a pretty expensive tool."

"It would be a good idea to bring down the pricing by at least 20 to 30 percent."

"API Connect is expensive - I'd rate their pricing five out of ten."

"It's an expensive product."

More IBM API Connect pricing and cost advice

"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

831,265 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Educational Organization

21%

Financial Services Firm

18%

Insurance Company

10%

Computer Software Company

Financial Services Firm

33%

Computer Software Company

12%

Insurance Company

11%

Real Estate/Law Firm

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.

See all answers

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.

See all answers

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.

See all answers

Ask a question

Earn 20 points

Comparisons

IBM DataPower Gateway vs IBM API Connect

Compared 25% of the time

Apigee vs IBM API Connect

Compared 22% of the time

Microsoft Azure API Management vs IBM API Connect

Compared 16% of the time

Kong Gateway Enterprise vs IBM API Connect

Compared 6% of the time

MuleSoft API Manager vs IBM API Connect

Compared 6% of the time

More IBM API Connect Competitors

Kong Gateway Enterprise vs OpenLegacy

Compared 44% of the time

MuleSoft API Manager vs OpenLegacy

Compared 22% of the time

webMethods.io vs OpenLegacy

Compared 15% of the time

More OpenLegacy Competitors

Product Reports

IBM API Connect

Download IBM API Connect product report

Download OpenLegacy product report

Learn More

IBM

Overview

IBM API Connect facilitates API management and integration in the financial sector. Companies use it to expose, secure, and manage APIs for banking, insurance, and fintech, deploying it on-premises, in the cloud, or as a hybrid solution.

IBM API Connect focuses on creating and monetizing APIs while enabling seamless transactions and integration with third-party services. It is vital for compliance with regulations and enhances external communication among institutions. With deployment options suitable for different environments, it supports centralized gateway management, robust security features, and comprehensive API lifecycle management. Users benefit from powerful analytics, user-friendly interfaces, and high performance with capabilities in message transformation and efficient monitoring.

What are the most important features?

Centralized Gateway: Manages all APIs through a single entry point.
Robust Security: Ensures API protection with advanced security measures.
Comprehensive API Lifecycle Management: Covers creation, deployment, and retirement of APIs.
User-Friendly Interface: Simplifies API creation and management tasks.
Powerful Analytics: Provides insights into API usage and performance.
Seamless Integration: Connects easily with third-party services and internal systems.
Flexible Deployment Options: Supports on-premises, cloud, and hybrid environments.
High Performance: Optimizes API performance and reduces latency.
Message Transformation: Manipulates and formats messages between different systems.
Visualization Tools: Enables clear and detailed views of API usage statistics.

What benefits or ROI should users look for?

API Monetization: Generates additional revenue streams from APIs.
Enhanced Compliance: Ensures adherence to industry regulations and standards.
Improved External Communication: Facilitates integration and communication among financial institutions.
Technical Support: Benefit from reliable customer support and easy configuration.
Deployment Flexibility: Choose from on-premises, cloud, or hybrid options.

IBM API Connect is extensively implemented in the financial sector, enabling banking, insurance, and fintech services to manage APIs efficiently. Companies use it to ensure secure transactions, integration with third-party services, and compliance with regulatory standards. Its deployment flexibility accommodates different infrastructure needs, making it suitable for a wide range of financial applications.

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.

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

IBM API Connect vs. OpenLegacy