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
16th
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
AI Software Development (83rd)
 

Mindshare comparison

As of February 2026, in the API Management category, the mindshare of Layer7 API Management is 2.2%, down from 3.0% compared to the previous year. The mindshare of OpenLegacy is 0.9%, 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 (%)
Layer7 API Management2.2%
OpenLegacy0.9%
Other96.9%
API Management
 

Featured Reviews

Integration capabilities excel and support for varied platforms enhances communication across backend systems
We mainly use REST APIs, and the solution's integration capabilities are excellent. It allows communication with a number of back-end providers and data consolidation. The flexibility to develop APIs for various platforms, from front-end applications to ATM machines, is valuable. Code changes and migration are straightforward, and it supports identity and access management integration.
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

"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."
"It is flexible in how it creates custom policies and uses builds with impressive methods."
"Compared to other vendors, this product is much faster in coming up with new features, which is good."
"Easy to use, nice UI, and good search functionality."
"The actual management of APIs is fundamental to us, as we're a heavy API user/provider. So, obviously, a centralised management platform is important."
"We are able to go to market very quickly and deploy our functionalities very quickly."
"The solution's technical support is good."
"The Mobile API Gateway is also great."
"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."
"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."
"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."
"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 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."
 

Cons

"It is not possible for clients to migrate to a newer version."
"​There is still room for improvement for the CA API Developer Portal. It is still not on par with what the competencies are."
"I feel there is a lot to improve in terms of providing plug-and-play functionalities, as at the moment it requires a lot of coding in their specific language for implementing a medium-complexity use case."
"The architecture of the solution does not allow for flexibility in using different components for the gateway architecture."
"There is a need for the migration of policies, better reporting, and monitoring integration."
"Provide complete documentation with examples of usage on its build in assertion/function."
"The development portal could be improved."
"They should incorporate deeper monitoring features into the solution to make the offering more complete. Doing so would help to showcase traffic patterns and usage to better engage customers and partners proactively. It would also help with API management and capacity planning."
"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."
"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."
"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."
"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."
 

Pricing and Cost Advice

"The price of Layer7 API Management is reasonable compared to Apigee."
"There are some costs for maintenance that we are charged, but that seems fair because we get the support."
"I do not have experience with the pricing or licensing of the product."
"Purchase 4.0 now and wait until they flush out the 4.1 problems."
"It has a reasonable pricing model by instance."
"Pricing is competitive. CA is ready to offer attractive discounts."
"This solution is a bit more expensive than competitors."
"If you do a TCO of more than five years, then you will see a big jump in costs for some vendors."
"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,707 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
7%
Marketing Services Firm
7%
Healthcare Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise13
Large Enterprise84
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: December 2025.
881,707 professionals have used our research since 2012.