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

3scale 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

3scale API Management
Ranking in API Management
19th
Average Rating
7.4
Reviews Sentiment
7.0
Number of Reviews
11
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 June 2025, in the API Management category, the mindshare of 3scale API Management is 2.4%, up from 2.3% compared to the previous year. The mindshare of OpenLegacy is 0.4%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Jose Luis Bonilla - PeerSpot reviewer
Provides cost savings while maintaining the same functionality and capabilities
There were two main reasons for consideration. One of them was the cost. It is true that the other solution had more capabilities, but we didn't have plans to use them. We didn't need them, but the cost was slightly higher. Also, we were already working with the Red Hat solution and integrating it with some other solutions we have in place. It was better and more convenient for us. Overall, I rate the solution an eight out of ten.
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 standard deployment is very simple."
"3scale API Management's best feature is API management."
"I like the API automation."
"The most valuable features are the gateway and security features."
"The gateway is the most valuable feature because it makes it possible for us to gather all traffic into one proxy, which is a good thing."
"The solution is quite lightweight, and the installation is very easy. It's like a two-click installation."
"The product is stable."
"To me, the most valuable feature of 3scale API Management is that it lets you add a backend to the product. I also like that you can integrate it well with OpenShift clusters, making 3scale API Management a useful solution."
"Opens the door to connect modern web products to an old legacy system."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"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."
"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."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"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."
 

Cons

"I believe the CMS part of it has room for improvement though. That is where you write a couple of things if you want to publish your API. It's based on liquid scripting, which doesn't seem like the obvious ones to script with."
"What was suggested by Red Hat was a crucial part of the configuration, but when we started to ask about the supportability of this configuration, Red Hat said only some parts of the configuration would be supported."
"What I'd like to improve in 3scale API Management is its route-limiting feature. Currently, I don't know how to do that effectively on the solution, but in Kong, I know how to do it, so I would love to see route-limiting being easily done on 3scale API Management. It would also be good if there was some authentication that you could do from 3scale API Management because Kong offers that functionality out of the box. What I'd love to see in the next release of 3scale API Management is the ability to integrate more plug-ins easily onto the platform, so you'll be able to extend it, and even do customs management. If Red Hat could offer that extension where it allows the internal organization where 3scale API Management is deployed on-premise to integrate its tools on top of 3scale API Management and provide an API for that, that will make the solution very powerful."
"We tried to use the portal, but we decided that it wasn't enough. The content management system (CMS) is not easy to use if you want to customize things, and it's hard to get someone who has the knowledge to work with the CMS."
"3scale API Management only supports restful APIs and doesn't support SOAP."
"The product is not that flexible for developers. It's less flexible and rigid. It's not easy to make changes or customize it."
"It would be helpful to improve the customization features so that the customer can do it based on their own needs."
"The user experience could be better. The developer portal is too complex and hard to configure."
"Debugging and logging for programmers could be better."
"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."
"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."
"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."
"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

"The cost was around $45,000 per year."
"3scale API Management has reasonable pricing, judging from its competitor, Kong. My organization pays yearly for the 3scale API Management license, though I'm unable to give the exact figure because every single day there are new clusters deployed. I'm in charge of three to four clusters in my team, but give or take, it costs a few thousand lakhs."
"I don't think that 3scale is very expensive."
"The pricing is affordable, it's cheap."
"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.
857,162 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
11%
Insurance Company
10%
Government
9%
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 3scale API Management?
I rate the product’s pricing as two out of ten, where one is cheap, and ten is expensive.
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

Victor Ops, Coca Cola, The Telegraph, Skava, Orange, Typeform
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 3scale API Management vs. OpenLegacy and other solutions. Updated: June 2025.
857,162 professionals have used our research since 2012.