Try our new research platform with insights from 80,000+ expert users

Layer7 API Management 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

Layer7 API Management
Ranking in API Management
11th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
112
Ranking in other categories
No ranking in other categories
OpenLegacy
Ranking in API Management
36th
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 August 2025, in the API Management category, the mindshare of Layer7 API Management is 2.8%, down from 3.2% compared to the previous year. The mindshare of OpenLegacy is 0.5%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

NikhilChaudhari - PeerSpot reviewer
Valued for its drag-and-drop functionalities, the available policy options, and the excellent security features
I work as a PG developer, primarily dealing with Layer7 API Management and MuleSoft API management. My focus is mainly on VM management platforms such as Layer7 and Apigee Layer7 API Management is most valued for its drag-and-drop functionalities, the available policy options, and the excellent…
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 fills our two most important concerns in seeking an API solution by providing a reliable gateway and security options."
"API Enhanced Portal 4.1 looks very promising. API Gateway policy manager for writing policies is excellent. It is the best in the industry for policy writing."
"Tech support is fast and responsive."
"Almost all security features are available out-of-the-box and can be deployed rapidly."
"The most valuable feature was the gateway because it has a good dashboard which shows all the hits, misses, and issues, how often you are viewing, what was the response time, etc. The gateway was very easy to deploy."
"Some of the performance matrix that API Gateway gives off, we monitor them via SNMP traps, and then we tie them into our monitoring system. You can actually monitor some of the latencies and some of the performance aspects of both API Gateways, as well back end services. So having that line of sight surely helps in terms DevOps."
"Simple to use and easy to develop APIs."
"It is a stable product."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"Opens the door to connect modern web products to an old legacy system."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"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."
"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."
"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."
 

Cons

"The solution should prioritize ease of use and align with the growing trend of cloud-native environments."
"The API Development tool can be made more user-friendly by providing folder properties."
"Layer7 API Management’s price could be reduced."
"The only issue we have is that we have to buy an APM license separately for end-to-end monitoring."
"As a SaaS product, control over some configuration elements and environments is lost."
"We are looking for improvements related to integration. We want to see them add integration tools to the CA bundle. That would be helpful."
"I understand that clients are often concerned about costs. They might be exploring other options due to the high cost associated with our current package."
"There are old algorithms that the tool does not support - and it shouldn't, in my opinion. But sometimes customers need old algorithms, from old use cases and old applications, migrated to the platform. At those times, there are hiccups that happen."
"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."
"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."
"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."
"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."
 

Pricing and Cost Advice

"Our customers found the product’s cost a little higher. They are looking for open-source solutions."
"Be aware of additional licenses for your warm standby. Ensure you get plenty of non-production licenses."
"The product is moderately priced."
"I think it's competitive. It's not that expensive when you compare CA with the Oracle product."
"If you do a TCO of more than five years, then you will see a big jump in costs for some vendors."
"CA has great pricing for gateways, so negotiate with your sales team."
"Licenses are required to operate the product, but I don't know much about the validity periods attached to it."
"It is a pricey product, although not extremely overpriced compared to competitors in the market."
"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.
865,164 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
11%
Manufacturing Company
10%
Healthcare Company
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Layer7 API Management?
Pricing is more than average. While I am used to Layer7 API Management ( /products/layer7-api-management-reviews ), seeing other products makes the tool's pricing seem high.
What needs improvement with Layer7 API Management?
Broadcom's push for upgrades from version nine to ten, ten to 10.3, and onwards to twelve needs improvement in migration processes, especially with service dependencies. The migration path sometime...
Ask a question
Earn 20 points
 

Also Known As

CA API Management, CA Live API Creator, Espresso Logic, CA API Gateway
No data available
 

Overview

 

Sample Customers

1. IBM  2. Microsoft  3. Oracle  4. Salesforce  5. SAP  6. Cisco  7. Dell  8. HP  9. Adobe  10. VMware  11. Accenture  12. Capgemini  13. Deloitte  14. PwC  15. Ernst & Young  16. Infosys  17. TCS (Tata Consultancy Services)  18. Wipro  19. Cognizant  20. HCL Technologies  21. Tech Mahindra  22. Fujitsu  23. Hitachi  24. NEC  25. NTT Data  26. Ericsson  27. Nokia  28. Siemens  29. AT&T  30. Verizon  31. Vodafone  32. Orange
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 Layer7 API Management vs. OpenLegacy and other solutions. Updated: July 2025.
865,164 professionals have used our research since 2012.