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

Apigee vs Apollo GraphOS comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

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 (11th)
Apollo GraphOS
Ranking in API Management
19th
Average Rating
7.6
Reviews Sentiment
4.4
Number of Reviews
7
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2026, in the API Management category, the mindshare of Apigee is 6.7%, down from 11.4% compared to the previous year. The mindshare of Apollo GraphOS is 0.8%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Apigee6.7%
Apollo GraphOS0.8%
Other92.5%
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.
MB
Business Development Manager at Digitaltrack
Unified schemas have streamlined team collaboration and have reduced API-related deployment issues
We had a positive experience with Apollo GraphOS, but there are a few areas where I think it could be improved. One area is the learning curve around GraphQL Federation and schema governance. Teams that are new to federated architectures often need to understand best practices. More guided onboarding, built-in recommendations, and practical examples would make adoption easier. I also think the observability and troubleshooting experience could be enhanced, particularly when diagnosing issues that span multiple subgraphs. While the platform provides useful insights, tracing complex requests across a federated environment can still require additional investigations. Another improvement would be more granular administrative controls and reporting, especially for larger organizations where different teams manage different parts of the GraphQL platform. Although the CI/CD integration is one of the product's strengths, having more out-of-the-box integrations and similar configurations for popular DevOps tools would reduce the initial setup effort. These suggestions would make the platform easier to adopt, operate, and scale, particularly for organizations that are beginning their GraphQL Federation journey. One thing I would like to see in future releases is deeper operational visibility for large-scale federated environments. As the number of subgraphs and development teams grows, it becomes more important to quickly identify where performance bottlenecks or schema-related issues are originating without having to correlate information from multiple tools. More built-in governance capabilities would be valuable, such as stronger policy enforcement, approval workflows for schema changes, and richer reporting for platform administrators. Another area that could be improved is the onboarding experience. While the documentation is comprehensive, having more guided setup wizards, architectures, and real-world implementation examples would help new teams become productive more quickly. I would also like to see even broader integrations with common enterprise monitoring, security, and development platforms so organizations can manage Apollo GraphOS as part of their existing operational ecosystem rather than relying on additional customization. These points would make day-to-day administration easier and improve the experience for organizations running GraphQL at a larger scale.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Apigee is very easy to use, and you can code in any language, like JavaScript, Java, or any other language."
"The most valuable features are scalability and technical support."
"Overall, I am satisfied with this product and it is aligned to all of my needs."
"Before using Apigee, we used to have file transfer integrations; with Apigee in place, we are directly integrating or exposing our APIs to our partners who can access our services directly in real time."
"We use it to build API proxies for securing targeted back-ends with an emphasis on Continuous Integration/Continuous Development (CI/CD)."
"Apigee is among the leaders in API platforms."
"Highly scalable from any initial topology to horizontal extension"
"It nice and easy for the clients and those using the product to access the product's help resources."
"Apollo GraphOS has had a positive impact by improving the way we manage and evolve our GraphQL APIs."
"Apollo GraphOS has positively impacted our organization by reducing unwanted code and helping us combine multiple services."
"Apollo GraphOS has had a positive impact on our organization by making our API development process more structured, predictable, and collaborative."
"Apollo GraphOS positively impacts my organization by providing a complete platform for API orchestration, schema governance, observability, and federation."
"Overall, Apollo GraphOS has been a valuable asset."
"Apollo GraphOS has significantly enhanced both the developer experience and product delivery timelines by offering a centralized approach to managing GraphQL schemas and services, helping reduce overhead and improve collaboration between frontend and backend teams."
"The most valuable features of Apollo GraphOS OS for me are its security and authentication processes."
 

Cons

"Technical support model for OPDK should be more exposed and mature in terms of providing support during installation, run, and debug of Apigee in production on OPDK mode."
"Pricing is an area that can be improved, as it is a little on the higher side."
"I would like to see a long-term direction for the overall architecture (similar to what WSO2 has done), in that all three areas — pub/sub, events, and APIs — are treated as part of a continuum, instead of treating each as separate topics."
"For Apigee, I think licensing is on a monthly basis. The cost increases as the usage increases; it's higher than many competitors."
"Google technical support is not that good nowadays, but it was better earlier."
"I would like to see the monitoring, dashboards, and reports improve."
"The solution could add even more functionalities."
"The ability to work across different management solutions in a plug and play fashion would make it easier for faster uptake."
"Apollo GraphOS OS is using a detailed project, and it can be time-consuming because it has a lot of data to manage. It sometimes takes longer than three seconds, which can affect loading times and lead to user dissatisfaction. I would like to see improved performance."
"I think Apollo GraphOS can be improved since teams new to GraphQL federation may find concepts such as subgraphs, schema composition, contracts, and router configuration take time to understand, making the platform seem more complex than necessary for smaller teams."
"The reason I held back from giving it a perfect score is that some enterprise scenarios still require additional effort."
"Apollo GraphOS could be improved with simpler pricing, more transparent usage and cost reporting, easier onboarding for new teams and learners, and more detailed documentation and troubleshooting guidance for complex GraphQL."
"There’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API."
"I rated it six out of ten because while it offers useful capabilities such as schema management, schema validation, and API observability, I feel there are several areas that need improvement."
 

Pricing and Cost Advice

"The cost of the licensing is based on the number of API calls that are made."
"Apigee is subject to licensing fees."
"Pricing options need to be chosen on a case-by-case basis."
"The price of Apigee could be less expensive. The solution can be purchased monthly or annually."
"Based on your usage of the APIs you can take a decision to go with either an on-cloud or OPDK version. Get in touch with the sales representatives of Apigee."
"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."
"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 not suited for small companies. It's expensive."
Information not available
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
913,683 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Manufacturing Company
10%
Computer Software Company
8%
Outsourcing Company
7%
Manufacturing Company
12%
University
10%
Program Development Consultancy
10%
Financial Services Firm
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise9
Large Enterprise67
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise3
 

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?
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...
What is your experience regarding pricing and costs for Apollo GraphOS?
I am not sensitive to nor very knowledgeable about the pricing and setup cost.
What needs improvement with Apollo GraphOS?
I think Apollo GraphOS can be improved since teams new to GraphQL federation may find concepts such as subgraphs, schema composition, contracts, and router configuration take time to understand, ma...
What is your primary use case for Apollo GraphOS?
My main use case for Apollo GraphOS is creating APIs with GraphQL. I create subgraphs and schema composition, contracts, schema registry, and change validation, which helps me prevent breaking chan...
 

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
Information Not Available
Find out what your peers are saying about Apigee vs. Apollo GraphOS and other solutions. Updated: September 2026.
913,683 professionals have used our research since 2012.