Apollo Studio

Overview

Apollo Studio is the management interface for Apollo GraphOS, aimed at teams building and operating GraphQL supergraphs. It is strongest when schema changes need coordinated review and production usage needs to be visible across services and clients. For an individual developer who only needs to run queries, its governance features may be more than necessary.

Key features

Studio Explorer lets developers create, run, and share GraphQL operations, with autocomplete and query linting. That makes it useful for exploring an API and refining operations, while its value to a team grows when those operations are connected to shared schema workflows.

GraphOS centralizes schemas and metadata, generates changelogs, and visualizes the graph. Teams can propose and review schema changes asynchronously, then validate them against past requests from registered clients to catch potential breakage. Composition, validation, and approvals can also be integrated into existing CI/CD pipelines. This is a substantial governance toolkit for teams shipping across services; it is less compelling if all you need is a lightweight query editor.

Graph variants provide separate permissions for discoverability, review, and publishing, and filtered variants can present a tailored view to a client or partner. That separation helps teams manage access without treating every consumer as an internal developer. Studio also exposes usage trends, request volume, rates, errors, and service traces at field, client, and operation levels. OpenTelemetry support lets platform teams route metrics to their chosen APM tool.

Rover CLI supports publishing subgraph schemas, running checks in CI, and testing a supergraph locally; the Platform API supports custom automation. GraphOS supports any GraphQL API, including Federation and Connectors. Apollo says graph operation result data does not reach an Apollo-managed service, though some tools have opt-in GraphOS reporting and certain tools collect anonymous usage data by default.

Pricing

The Free plan costs nothing, is forever free, and requires no credit card. It supports up to 3 developers, limits a self-hosted GraphOS Router to 60 requests per minute, and retains checks and insights data for one day. Community Support is included. That makes it a sensible starting point for students, hobbyists, and small experiments, but the low router cap and short retention make it a poor fit for sustained production workloads.

Developer costs $5 a month, billed monthly, starting at $5 per million requests. It supports up to 10 developers and keeps data for 7 days; Developer Support is 8×5 with no SLA. A $50 usage credit is included when you sign up, and a credit card is required. This is the step up for a small production API team that needs more room than Free, though the brief retention and lack of an SLA still constrain its appeal for teams with stronger operational requirements.

Standard has custom pricing and requires talking to sales. It supports up to 30 developers, offers 90 days of retention, and includes 8×5 Standard Support with an SLA. It is aimed at teams scaling across services that need longer history and a support commitment. Enterprise also has custom pricing through sales, with unlimited developers, 18 months of retention, and Business Support 24×7×365 with an SLA. Its terms target companies with large-scale GraphQL initiatives. The move up the tiers chiefly buys greater team capacity, longer retention, and stronger support coverage.

Platforms

Apollo Studio is available on web and supports API, Linux, macOS, Windows, and self-hosted environments. The hybrid deployment model, API explorer, operation testing, and client code generation suit teams combining a hosted interface with self-managed components. Server-language support spans TypeScript, JavaScript, Java, Kotlin, Python, C#, Go, Ruby, Rust, Elixir, PHP, and Scala.

Who it's for

Choose Apollo Studio when a GraphQL team needs a shared schema registry, change validation, CI/CD checks, role controls, and usage visibility in one GraphOS workflow. Free suits learners and hobbyists; Developer is the entry point for small production teams; Standard and Enterprise address larger teams that need more seats, retention, and support. It is less suited to someone seeking only a standalone API client or mock server.

Pros and cons

• Pros: Schema changes can be reviewed asynchronously and checked against registered-client traffic, helping teams catch breaking changes before they ship.
• Pros: CI/CD integration, granular variant permissions, and metrics by field, client, and operation connect governance with operational visibility.
• Pros: Free access has no credit-card requirement, and Developer starts at $5 per million requests for small production teams.
• Cons: Free's self-hosted router is capped at 60 requests per minute and data retention is only one day, limiting its usefulness for ongoing production.
• Cons: Developer requires a credit card, retains data for just 7 days, and has no support SLA; stronger support and longer retention require custom-priced plans.

Alternatives

For a broader API design and tooling comparison, browse API Design Tools or GraphQL Tools.

• Apidog is a freemium alternative with a time-unlimited free plan for 4 users and a listed Basic plan at $12 a month; consider it if those plan terms suit your team better.
• Microcks is a free, 100% open-source community-driven CNCF Incubating project; choose it if open-source distribution is the priority.
• Pact offers free open-source tooling; consider it if that is the approach you want.
• Postman has a free plan with an API client and core tools, specs and mock servers, Native Git, Collection Runner, and 50 AI credits; it is an alternative when those tools better match your needs.
• TypeSpec is a free, Microsoft-built, community-supported project with a CLI and online playground; choose it if that project format is a better fit.
• oasdiff has an open-source engine, CLI, and GitHub Action under the Apache 2.0 license; consider it if you want that open-source tooling.
• WireMock offers a free forever plan with 1,000 calls per month, one user, three mock APIs, and 10 requests per second; it may suit a narrowly scoped mocking need.
• MockServer is free and open source, self-hosted, and requires no SaaS account; consider it if that deployment model is the priority.

Verdict

Apollo Studio is a strong choice for GraphQL teams that need schema governance, change validation, and usage insight tied to their delivery workflow. Its main advantage is bringing those controls together; its main drawback is that Free's router and retention caps are tight, while the tiers built for larger production needs move to custom pricing. Choose it for a coordinated GraphOS workflow, and look elsewhere if you need only a simple query client or free production-scale capacity.