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
90
Ranking in other categories
API Testing Tools (12th)
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 (78th)
 

Mindshare comparison

As of August 2026, in the API Management category, the mindshare of Apigee is 6.8%, down from 12.2% compared to the previous year. The mindshare of OpenLegacy is 1.4%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Apigee6.8%
OpenLegacy1.4%
Other91.8%
API Management
 

Featured Reviews

Amandeep Pawar - PeerSpot reviewer
Senior Engineer at Airy Software Technologies Private Limited
Centralized API gateway has improved microservice security and provided deep traffic analytics
Apigee's API gateway could be improved. There are some limitations for high throughputs, which we can address. Overall, Apigee is a robust API management platform where we can configure centralized traffic management, but there are a few areas for improvement. The developer experience could be more intuitive, especially for configurations and complex API proxies and policies. Debugging production issues can sometimes be challenging, so more detailed diagnostic and easier-to-use troubleshooting tools would be valuable. The analytics dashboard could offer more customization and deeper insights without requiring additional configuration. Simplifying pricing and licensing would make Apigee more accessible for smaller organizations. I would like better support for cloud-native deployments, Kubernetes integrations, and AI-assisted policy recommendations. I would also like to see AI-assisted troubleshooting, more customizable analytics and developer portal, better enterprise documentation, easier policy configuration, and a simplified licensing model to enhance both the developer experience and day-to-day operations.
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 capabilities are very powerful."
"Apigee has proven to be one of the best of the breed."
"Items around the mobilization of the API interface and the ability to automate validations for our APIs are the most valuable aspects."
"I simply like how you can personalize your products and put them into product categories. That's what I like the most."
"The installation is straightforward. You just need to get a license for Apigee and then configure the reverse proxy."
"Anyone with basic knowledge can build an API."
"The most valuable feature of Apigee is its simplicity of deploying an API and restricting access, like rate limit, with the API."
"Apigee is very fast in transferring requests and responses between Northbound systems to Southbound systems."
"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."
"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 product has helped our business by allowing us to become more efficient in data handling."
"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 solve larger legacy API issues on an enterprise level with this product."
"The speed of development of production, especially in specific environments like IBM mainframes, has been valuable."
"OpenLegacy opens the door to connect modern web products to our old legacy system."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
 

Cons

"I would like them to add features, such as caching and mediation policies."
"The Apigee cloud admin UI could be more user-friendly by adding a few more features."
"We do not have control over the installation."
"iPaaS is something that we would like to see. For example, MuleSoft is kind of an integrated platform as a service (iPaaS), and it provides a lot of out-of-the-box connectors and other such things. This is where Apigee lacks. I'm not sure if that's the roadmap for Apigee, but any improvements on those lines would be helpful where things become easier to implement."
"It is an expensive solution."
"I would like to see the support improved. I think the time frame should be shorter for responses when it comes to technical support. This is not the ideal situation you want to be in when you need support."
"Better functionality for validating inputs and outputs would be helpful."
"Proxy versioning seems a bit confusing and buried in the publishing experience, especially for the URI-based versioning approach."
"Debugging and logging for programmers could be better."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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."
"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 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."
 

Pricing and Cost Advice

"The cost of the licensing is based on the number of API calls that are made."
"The cost increases as the usage increases."
"In Latin America, Apigee is expensive. It's not for small businesses; it's more for big businesses."
"The iicense is subscription-based."
"Apigee is slightly expensive, but again, it can depend on the type of usage. All things considered, it is slightly expensive."
"It is not suited for small companies. It's expensive."
"It is more expensive when you compare to open-source products or other vendors."
"Its price is reasonable for the features they provide and the maturity of the platform."
"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.
909,948 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise9
Large Enterprise67
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: August 2026.
909,948 professionals have used our research since 2012.