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
12th
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
37th
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (44th)
 

Mindshare comparison

As of January 2026, in the API Management category, the mindshare of Layer7 API Management is 2.3%, down from 3.0% compared to the previous year. The mindshare of OpenLegacy is 0.8%, 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.3%
OpenLegacy0.8%
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

"For developers to be able to come, sign up, or find APIs."
"The benefits are rapid development and deployment of APIs, which means that your information, your ability to handle information, to receive it and to send it, to visualize it, to report on it, to get intelligence out of it, happens fast and happens with accuracy."
"The most important features of Layer7 API Management are the basic security functionality and validation checks."
"This product, at first blush, looks something like it's one of those weekend warrior tools, but it's not. It's an enterprise-class tool with the kind of usability that you wouldn't expect. And with that usability - how do you have your cake and eat it too? Well, it's because of the product's extensibility. It's very well-integrated with your existing Java library of processes and procedures, as well as your ability to write new extensions to it. You get so much of the base functionality but you don't give up the ability customize."
"I work for an information security company. CA API Management is capable of using tokens for authorization to manage access control for the APIs."
"One of the features that the tool provides is the ability to simply onboard new APIs to an existing security platform. We build all the policies for security upfront, and then we can add those policies pretty simply and straightforwardly to any new API that gets developed in the enterprise."
"Almost all security features are available out-of-the-box and can be deployed rapidly."
"There are a couple aspects of performance. One is just speed and uptime, and it's stellar in that regard. The other is, how much effort is it to put it in place in the first place, and then how much effort is it to keep it operational. That's where its real strength is. I'm able to do things quickly and easily that I couldn't do before​."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"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 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 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."
"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."
"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."
 

Cons

"The Policy Manager tool that is used to manage the solution is very heavy to use because it is based in Java. Sometimes it takes a long time to load. There could be some improvements to it. If they could make Policy Manager on a web page that would be a good alternative."
"One of the features that the tool provides is the ability to simply onboard new APIs to an existing security platform. We build all the policies for security upfront, and then we can add those policies pretty simply and straightforwardly to any new API that gets developed in the enterprise."
"It is not possible for clients to migrate to a newer version."
"Layer7 API Management should give a clear roadmap of the product and where it is going, and they should not change the underlying layers."
"The development toolkit used for creating APIs should be more online and user-friendly. Deployment and tracking could also be improved. Tools like Apigee provide a complete online experience along with RESTful APIs, to manage all activities. It is a very nice and user-friendly solution compared to CA."
"The API Development tool can be made more user-friendly by providing folder properties."
"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."
"The product needs to keep up with newer trends even though customers might not be requesting it yet."
"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."
"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'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

"It depends on your use case of course, how much you want to go with that, because it can get pricey and depends on the size of your company."
"It's my manager who takes care of the pricing. But I keep on hearing that it's a little pricey, it's on the higher side. That is what he says."
"The price of Layer7 API Management is reasonable compared to Apigee."
"It is a pricey product, although not extremely overpriced compared to competitors in the market."
"It was very high at that time. We are a Broadcom CA partner, and we got it only for testing purposes. We didn't pay anything for it."
"The product is moderately priced."
"At the time we bought the product it was a perpetual users license and there has been no need for additional licensing fees."
"APIs can be developed to provide security. We can show them in one single pane of glass, such as the CA API Management API Developer Portal. It is there that we can provide the monetization for their APIs and what is happening on third-party applications, like Paytm or BookMyShow."
"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,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Manufacturing Company
8%
Healthcare Company
7%
Computer Software 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,082 professionals have used our research since 2012.