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

Apigee 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

Apigee
Ranking in API Management
3rd
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
89
Ranking in other categories
API Testing Tools (10th)
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 (101st)
 

Mindshare comparison

As of May 2026, in the API Management category, the mindshare of Apigee is 7.1%, down from 13.6% compared to the previous year. The mindshare of OpenLegacy is 1.2%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Apigee7.1%
OpenLegacy1.2%
Other91.7%
API Management
 

Featured Reviews

IM
consultant at Allstate
Apigee empowers effective API management while needing improvements in technical support
There is room for improvement with Apigee as OPDK private cloud enhancements have stopped, focusing only on Apigee hybrid and Apigee X, with Google no longer adding new features to OPDK private cloud. I am not currently utilizing AI in the private cloud with Apigee, but I'm unsure about hybrid and Apigee X.
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

"It has all the features necessary to work in anything from a basic scenario to advanced applications."
"It's a good return on my investment."
"The most important feature is the security capabilities and the way it integrates very quickly with other security providers. We have integrated it with Azure and it integrates quite seamlessly."
"Apigee has better scalability than WSA."
"The API moderation, administration monitoring, product architecture, infrastructure, and overall quality is good."
"Technical support is available twenty-four hours a day, and when it is a critical issue, they come online, take real-time access to our system, and support us in solving the problem."
"Items around the mobilization of the API interface and the ability to automate validations for our APIs are the most valuable aspects."
"Apigee is a very lightweight solution."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"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."
"Opens the door to connect modern web products to an old legacy system."
"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, and we were able to build out the OpenLegacy parts very quickly, putting together a couple hundred APIs in six months."
 

Cons

"The developer portal's adoption of the OpenAPI standard needs to be improved. In the latest version of the developer portal, they have adopted the OpenAPI standard. This feature, however, can be improved by supporting more characteristics of the OpenAPI standard."
"I have heard there maybe be some security issues that need to be addressed. If this is the situation I would encourage taking a look at the security matters."
"It is a bit on the expensive side. Its licensing cost is a bit high, and that's where we've seen people going back on their decisions."
"The solution tends to hide the limitations to keep selling the product."
"The company needs to better support webhooks. It used to support webhooks and their policies and they have since stopped. They had some issues in the product and they abandoned the support for them. It's not come back since."
"The caching capabilities are somewhat limited."
"The initial setup for the on-prem solution is a little complex."
"The solution can be improved by simplifying the account creation process."
"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."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case."
"Debugging and logging for programmers could be better."
"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."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing."
"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

"If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution."
"Apigee is a pretty expensive solution."
"The solution is a bit expensive. It's not for organizations in the early stages of their lifecycle but is more suited for mid- to enterprise-level platforms. Pricing varies by deployment model, with SaaS being the cheapest, costing around $100,000 per year for a subscription. For hybrid and on-prem deployments, the price increases. The on-prem model includes a license and additional installation and configuration professional service costs, which can be at least $40,000 to $60,000 for the initial setup. While it's not cheap, it offers long-term value and can be worthwhile."
"The cost increases as the usage increases."
"The tool is extremely expensive."
"The iicense is subscription-based."
"They need to work on the cost of the solution."
"Since it was acquired by Google, we can get a license based on our requirements and the cost level will depend on cloud access and support."
"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.
895,151 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
10%
Manufacturing Company
9%
Insurance Company
6%
Construction Company
26%
Comms Service Provider
13%
Financial Services Firm
12%
Insurance Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise9
Large Enterprise66
No data available
 

Questions from the Community

How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Apigee or Amazon API Gateway?
Amazon API Gateway is a platform that supports the creation and publication of API for web applications. The platform can support thousands of simultaneous API calls, and it provides monitoring, ma...
What needs improvement with Apigee?
There is room for improvement with Apigee as OPDK private cloud enhancements have stopped, focusing only on Apigee hybrid and Apigee X, with Google no longer adding new features to OPDK private clo...
Ask a question
Earn 20 points
 

Comparisons

 

Overview

 

Sample Customers

Adobe, advance.net, Amadeus, AT&T, Bechtel, Belly, Burberry, Chegg, Citrix, Dell, eBay, Equifax, GameStop, First Data, Globe, HCSC, Intralinks, Kao, Meredith, Mitchell, Orange, Pearson
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 Apigee vs. OpenLegacy and other solutions. Updated: April 2026.
895,151 professionals have used our research since 2012.