"It is helpful to have a central API that is hosted and managed."
"We loved the portal part the most, which had monetization and showed how people were using the stuff. It is a good product as a whole and has a lot of microservices and granular features."
"The most valuable feature of Layer7 API Management is that their policy is really easy to develop and it is flexible."
"It impresses me as a product because it never goes down. It always does what it is supposed to do."
"The solution fills our two most important concerns in seeking an API solution by providing a reliable gateway and security options."
"The mobile access gateway (MAG) is tremendous."
"Tech support is fast and responsive."
"A big win for CA was the expertise of the local country support plus having support staff on site in a matter of hours, if required."
"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."
"The UI design could be improved in the next release."
"Some problems with response time."
"The delivery is bulky in terms of implementation. Its price could also be better. It is a very good product as compared to CA API, Google API, and WSO2 API, but its price is high. From the cloud-native perspective, some new features need to be added. It could also be made simpler to implement."
"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."
"The Portal lacks maturity. Since the move from Portal 3.x to 4.x, a lot of features were removed. It is slowly coming back. I can see a lot of changes are done in the "background" to decouple components and make it more flexible. Those changes are just not getting to the UI side quick enough."
"Some users say that the API lacks some features and is lagging behind the competition although that has not been my personal experience."
"The interface is Java which is difficult to make look very nice."
"They need a multifactor authentication solution for the API layer and the other layers, as well."
"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."
Layer7 API Management is ranked 6th in API Management with 10 reviews while OpenLegacy is ranked 16th in API Management with 2 reviews. Layer7 API Management is rated 8.6, while OpenLegacy is rated 7.6. The top reviewer of Layer7 API Management writes "Serves to standardise routing messaging services into a single API view with multiple channels". On the other hand, the top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". Layer7 API Management is most compared with Apigee, Amazon API Gateway, Mulesoft Anypoint API Manager, Microsoft Azure API Management and Kong Enterprise, whereas OpenLegacy is most compared with IBM API Connect, Mulesoft Anypoint API Manager, Apigee and Axway AMPLIFY API Management. See our Layer7 API Management vs. OpenLegacy report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
