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

Apollo GraphOS vs Perforce Acana comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 22, 2026

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

Apollo GraphOS
Ranking in API Management
18th
Average Rating
7.4
Reviews Sentiment
4.1
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Perforce Acana
Ranking in API Management
34th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the API Management category, the mindshare of Apollo GraphOS is 0.8%, up from 0.3% compared to the previous year. The mindshare of Perforce Acana is 1.0%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Mindshare Distribution
ProductMindshare (%)
Apollo GraphOS0.8%
Perforce Acana1.0%
Other98.2%
API Management
 

Featured Reviews

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.
Saurav Krishna - PeerSpot reviewer
Data Engineering and AI Intern at .3Lines Venture Capital
Authentication mechanism is easy to implement but improvement is needed in documentation
For API security purposes, we use the tool to host all our APIs. This allows us to take advantage of the security features provided by the platform. With the solution, we can implement rules such as rate limiting and restricting the number of API calls for each user. It acts as a secure gateway…

Quotes from Members

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

Pros

"Apollo GraphOS has positively impacted our organization by reducing unwanted code and helping us combine multiple services."
"Apollo GraphOS has had a positive impact by improving the way we manage and evolve our GraphQL APIs."
"Apollo GraphOS has had a positive impact on our organization by making our API development process more structured, predictable, and collaborative."
"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."
"Its completeness feature for the large enterprises, in my case for the government, is the most valuable feature of this product."
"The tool's authentication mechanism is easy to implement. We had to define a few parameters."
"Good interface, intuitive solution."
"The interface is good, and the policies that it uses as opposed to the features that it has in terms of security and the throughput management and those aspects are intuitive."
"It allowed us to publish and replace pre-essential transactions in one place, with a uniformity in terms of control and policies."
 

Cons

"There’s room for improvement in schema collaboration tools, especially in large teams where multiple developers are working on overlapping parts of the API."
"The reason I held back from giving it a perfect score is that some enterprise scenarios still require additional effort."
"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 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."
"Akana API Management needs to improve its documentation."
"Lacks an integrated billing feature."
"We actually did reach out to the technical support and it was all right, not great. We didn't get the answers we needed."
"The product has new features that we are going to implement in the next few months, such as API management and analytic reporting."
"The version that we have is very old."
 

Pricing and Cost Advice

Information not available
"For us, the pricing and licensing policies were for an on-premise installation with a fixed cost structure, that matched our budgeting policies."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
University
12%
Program Development Consultancy
12%
Manufacturing Company
10%
Manufacturing Company
16%
Financial Services Firm
13%
Computer Software Company
11%
Construction Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise3
Large Enterprise2
No data available
 

Questions from the Community

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?
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 ...
What is your primary use case for Apollo GraphOS?
My main use case for Apollo GraphOS is managing and monitoring GraphQL APIs across the development life cycle. I use it to manage our GraphQL schema, validate schema changes before deployment, and ...
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

Information Not Available
British American Tobacco, Credit Suisse, Daimler, eBay, FOX, Liberty Mutual, Marriott, Mayo Clinic, Skandia, Tata communications
Find out what your peers are saying about Apollo GraphOS vs. Perforce Acana and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.