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.8
Number of Reviews
88
Ranking in other categories
API Testing Tools (8th)
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 July 2025, in the API Management category, the mindshare of Apigee is 12.8%, down from 15.4% 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

ShawkyFoda  - PeerSpot reviewer
Provides high visibility and control with good traffic monitoring
Analytics is one of the areas needing enhancement, specifically more visibility and control over traffic to improve capacity management and high availability. The replication process between Master and Slave for disaster recovery takes too long. Dependencies on analytics impact the performance of the user interface, which should be separate. The complex setup process on-premises, especially with multi-node installations, could also be improved. Additional control in product declarations, based on operations like POST and GET, is needed.
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 solution is stable and reliable."
"It has a very efficient logging system which is easy to maintain."
"Apigee is a very lightweight solution."
"It's a good return on my investment."
"API/proxy lifecycle workflow for API providers is quite good and one of Apigee's strongest features."
"I simply like how you can personalize your products and put them into product categories. That's what I like the most."
"Items around the mobilization of the API interface and the ability to automate validations for our APIs are the most valuable aspects."
"Apigee is the heart of the architectural design for building an integration layer in our digital transformation projects. Organizations need an integration layer to connect their legacy backend services with the external world, such as Fintechs. This layer must be secure, not just a simple pass-through or gateway."
"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."
"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."
"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."
"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 mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
 

Cons

"One feature they have to invest time into is the developer portal they use."
"Apigee is not a solution compatible with public clouds, making it one of its shortcomings where improvements are required."
"We are experiencing some performance issues."
"Since it is based on various open sourced projects, we might have to depend on the fixes provided by those components rather than Apigee directly fixing the issues."
"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 is demanding on the infrastructure so the setup cost is very high for an on-premises deployment."
"The number one area this solution could be improved is by implementing support. Support is not a part of this solution."
"The Apigee cloud admin UI could be more user-friendly by adding a few more features."
"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."
"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."
"Debugging and logging for programmers could be better."
 

Pricing and Cost Advice

"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."
"Pricing options need to be chosen on a case-by-case basis."
"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."
"Apigee is expensive and not cost-effective. On a scale of one to ten, I would rate it an eight for the high cost. The changes individuals need to make on their side are costly."
"The cost of the licensing is based on the number of API calls that are made."
"It is an expensive solution."
"Apigee is slightly expensive, but again, it can depend on the type of usage. All things considered, it is slightly expensive."
"The price of Apigee could be less expensive. The solution can be purchased monthly or annually."
"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.
861,490 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
11%
Manufacturing Company
8%
Insurance Company
7%
Financial Services Firm
28%
Insurance Company
16%
Computer Software Company
10%
Real Estate/Law Firm
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
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: July 2025.
861,490 professionals have used our research since 2012.