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

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

Mindshare comparison

As of February 2026, in the API Management category, the mindshare of Apigee is 8.3%, down from 14.4% compared to the previous year. The mindshare of OpenLegacy is 0.9%, 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 (%)
Apigee8.3%
OpenLegacy0.9%
Other90.8%
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

"The solution is stable and reliable."
"Apigee is very easy to use, and you can code in any language."
"Apigee is stable, and we have had the system running on Apigee servers for more than four years without any stability issues."
"It's a good return on my investment."
"Apigee is a great product with good feedback and recommendations from clients."
"I have not encountered instability with the product."
"Apigee is a pioneer in the industry and has good features and functionalities. It is a good tool for API management and it has more advancements than all other tools in the market in certain areas."
"Apigee Analytics dashboard is useful to monitor transactions, error percentage, transaction latency, etc."
"Opens the door to connect modern web products to an old legacy system."
"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 mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"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."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
 

Cons

"The integration could be improved within the solution. There is a need to pay more attention to this."
"Compared to its competitors, such as Axway AMPLIFY API Management and Layer7 API Management, Apigee could benefit from having more policies to cater to various use cases. This would reduce the need for writing custom JavaScripts. If more features come straight out of the box, we can leverage them instead of writing custom code to achieve the same functionality."
"Could be more user friendly."
"There should be an integrated continuous integration and continuous deployment approach with Apigee. Currently, for development at a more integrated level, you have set it up yourself."
"Apigee on premise is quite complex and it is always moving faster."
"They need to work on the cost of the solution."
"Google isn't enthusiastic about supporting older versions. Google is now trying to move all of its clients to X within the cloud."
"Apigee could improve by integrating with more identity providers and offering a default authentication module."
"Debugging and logging for programmers could be better."
"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."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
 

Pricing and Cost Advice

"You do not necessarily pay for the license. The cloud solution is based more on transactions. So, you pay for it either way."
"The solution’s pricing could be more competitive."
"I would like to see the implementation of further options for billing because as it is now, the opportunities you have in terms of a package are limited."
"It is more expensive when you compare to open-source products or other vendors."
"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 price of Apigee could be less expensive. The solution can be purchased monthly or annually."
"The current version of Apigee is not too expensive, but we are currently in talks with Google to understand their roadmap for Apigee X. However, we anticipate that with the introduction of Apigee X, the pricing will likely increase."
"My clients pay for a license."
"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.
882,813 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
10%
Manufacturing Company
9%
Insurance Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise9
Large Enterprise65
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...
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: February 2026.
882,813 professionals have used our research since 2012.