Product Owner at a manufacturing company with 10,001+ employees
Real User
Top 20
Aug 27, 2026
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. Organizations with a simple API landscape may not fully benefit from Apollo GraphOS, as the platform delivers the most value when multiple teams and services need centralized GraphQL management.
Overall, I've had a good experience, but if I had to choose one improvement, it would be improving the onboarding and troubleshooting experience for large GraphQL environments. A better diagnostic tool with more guided information and recommendations would help developers resolve issues more quickly. I would like to see more customizable dashboards and reporting so that different teams can focus on the metrics that matter most to them. 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. In larger or more complex environments, I've experienced performance limitations and a steep learning curve for some advanced features. I think the troubleshooting experience and documentation could be better.
Apollo GraphOS is a strong platform, but there are a few areas where it could improve. The onboarding experience could be simpler for teams that are new to GraphQL. There are many powerful capabilities available, but it can take some time for new users to understand how everything fits together. I would also appreciate even more customizable dashboards and reporting options. Different teams often care about different metrics, so having greater flexibility in how insights are presented would be useful. From a larger organization perspective, additional guidance around governance and best practices could help teams adopt the platform more consistently across multiple services.
Artificial Intelligence Consultant at Medallion Technologies
Consultant
Top 10
Apr 8, 2025
So far, I could say that Apollo GraphOS is quite comprehensive, there’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API. More granular access control and role-based visibility within the platform would help enterprise teams better manage who can change what. Enhanced support for real-time use cases (e.g., subscriptions at scale) could also take it to the next level and give a better developer experience These might also be beneficial to have a more in-depth analytics around client usage and field-level insights to drive better decisions around deprecation or optimization.
I would like to see better performance in larger projects. When dealing with large amounts of data, it can become slow, causing users to potentially abandon the application. Improving performance and ensuring the app runs smoothly would enhance user experience. Stability issues, where it sometimes breaks down, need to be addressed as well.
Apollo GraphOS is a comprehensive platform designed for managing and enhancing GraphQL development. It streamlines the process of creating, testing, and maintaining GraphQL APIs effectively, offering a robust environment for developers.Apollo GraphOS offers developers a powerful toolkit for streamlining GraphQL API lifecycle management. Its robust structure supports efficient schema design, observability, and collaboration, making it a valuable asset for development teams. These features...
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. Organizations with a simple API landscape may not fully benefit from Apollo GraphOS, as the platform delivers the most value when multiple teams and services need centralized GraphQL management.
Overall, I've had a good experience, but if I had to choose one improvement, it would be improving the onboarding and troubleshooting experience for large GraphQL environments. A better diagnostic tool with more guided information and recommendations would help developers resolve issues more quickly. I would like to see more customizable dashboards and reporting so that different teams can focus on the metrics that matter most to them. 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. In larger or more complex environments, I've experienced performance limitations and a steep learning curve for some advanced features. I think the troubleshooting experience and documentation could be better.
Apollo GraphOS is a strong platform, but there are a few areas where it could improve. The onboarding experience could be simpler for teams that are new to GraphQL. There are many powerful capabilities available, but it can take some time for new users to understand how everything fits together. I would also appreciate even more customizable dashboards and reporting options. Different teams often care about different metrics, so having greater flexibility in how insights are presented would be useful. From a larger organization perspective, additional guidance around governance and best practices could help teams adopt the platform more consistently across multiple services.
Apollo GraphOS is good. There are no issues with it.
So far, I could say that Apollo GraphOS is quite comprehensive, there’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API. More granular access control and role-based visibility within the platform would help enterprise teams better manage who can change what. Enhanced support for real-time use cases (e.g., subscriptions at scale) could also take it to the next level and give a better developer experience These might also be beneficial to have a more in-depth analytics around client usage and field-level insights to drive better decisions around deprecation or optimization.
I would like to see better performance in larger projects. When dealing with large amounts of data, it can become slow, causing users to potentially abandon the application. Improving performance and ensuring the app runs smoothly would enhance user experience. Stability issues, where it sometimes breaks down, need to be addressed as well.