No more typing reviews! Try our Samantha, our new voice AI agent.

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
17th
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
33rd
Average Rating
7.6
Reviews Sentiment
6.2
Number of Reviews
5
Ranking in other categories
AI Software Development (78th)
 

Mindshare comparison

As of August 2026, in the API Management category, the mindshare of Layer7 API Management is 1.9%, down from 2.7% compared to the previous year. The mindshare of OpenLegacy is 1.4%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Layer7 API Management1.9%
OpenLegacy1.4%
Other96.7%
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

"Thanks to this product, we have successfully secured SOAP and REST APIs and exposed them to international/domestic partners using the standard industry protocols."
"We have been using API Gateway for four years and we have huge class actions, like 600 parts per second, and we have not seen any issues as of now."
"Initial setup is straightforward. It is simple and easy to do."
"Has great drag-and-drop features and requires minimal coding."
"The most valuable feature is the security with its out-of-the-box policies."
"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 recommend this product because of how successful we've been with it."
"There are many security policies within this solution that help to prevent attacks. We are also able to implement TLS to allow us to look at the application from the backend. There are workflows inside of the gate that help us a lot to implement customers and improve user experience. Our customers are also able to move from a customized creative view to taking advantage of AI bot solutions."
"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 opens the door to connect modern web products to our old legacy system."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"The speed of development of production, especially in specific environments like IBM mainframes, has been valuable."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"Without OpenLegacy, it would take us several months to create the same services."
"The product has helped our business by allowing us to become more efficient in data handling."
 

Cons

"What I find other people saying is that the product portal for API development lacks some features; people who need that functionality are not impressed, they say it is lagging behind the competition."
"We'd like to see an updated migration tool. Right now, the migration process works but it is a little clunky because there's not a good tool for migrating it."
"If they had different levels of support available then it would be easier to justify the costs."
"Some problems with response time."
"As well as the SOA Gateway - that is, the API Gateway; we call it the SOA Gateway - we also are now deploying the developer portal component of the SOA Gateway. That has limitations."
"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."
"Improvement in developer portal customization."
"The Portal lacks maturity. Since the move from Portal 3.x to 4.x, a lot of features were removed."
"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'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."
"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 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."
 

Pricing and Cost Advice

"There is an annual license for the use of this solution. I think we are paying for some support maintenance fees, included in that license. I don't know how it works. They should provide more information."
"Keep in mind the non-product licensing, e.g., if you opt not to use the embedded SQL."
"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."
"Purchase 4.0 now and wait until they flush out the 4.1 problems."
"I think it's competitive. It's not that expensive when you compare CA with the Oracle product."
"Licenses are required to operate the product, but I don't know much about the validity periods attached to it."
"There are some costs for maintenance that we are charged, but that seems fair because we get the support."
"For what we are after, the pricing is okay. It is competitive."
"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.
908,834 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
13%
Financial Services Firm
12%
Marketing Services Firm
7%
Outsourcing Company
6%
Construction Company
26%
Financial Services Firm
14%
Comms Service Provider
12%
Manufacturing Company
10%
 

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...
What is your primary use case for Layer7 API Management?
I am not the client. I implement Layer7 API Management ( /products/layer7-api-management-reviews ) for the clients. I have worked on multiple projects as a developer, implementing for Hydro Tasmani...
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: August 2026.
908,834 professionals have used our research since 2012.