Enhance customer experiences with Apollo GraphOS

Apollo Summit 2026 Product Highlights: The Governed Graph for Agents and Apps

Introducing GraphOS Agent Services


<p class="wp-block-paragraph"><a href="https://www.apollographql.com/graphos-router">GraphOS Router</a> runs your graph, bringing data from its services together into an API your apps can use. With <a href="https://www.apollographql.com/docs/graphos/routing/v3">GraphOS Router 3.0</a>, launching today in Preview, we’re putting more control in the hands of the teams that build and run that API. We’re expanding Graph Artifacts, improving query planning, and adding native circuit breaking. We’ve also rewritten the request pipeline and improved JSON handling, with changes to the core engine that serves your graph.</p>



<h2 class="wp-block-heading"><a href="#more-control-over-startup-and-deployment" aria-hidden="true" class="aal_anchor" id="more-control-over-startup-and-deployment"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>More control over startup and deployment</h2>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/graph-artifacts">Graph Artifacts</a> package your supergraph schema as a version you can choose, test, and deploy. In GraphOS Router 3.0, we’re adding persisted queries to that package and removing the need to reach Apollo’s management plane at startup when you’ve supplied the required artifacts. That means you can deliver what the router needs through your own infrastructure, using the process your team already follows for a release. You choose when a new version goes live and can return to a known version if you need to roll back. The schema and persisted queries become part of the deployment, giving you more control over how your router fleet starts.</p>



<h2 class="wp-block-heading"><a href="#improvements-through-the-request-path" aria-hidden="true" class="aal_anchor" id="improvements-through-the-request-path"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Improvements through the request path</h2>



<p class="wp-block-paragraph">Router 3.0 introduces an incremental query planner that builds a complete plan field by field, then improves it within a set search budget. When several services can resolve a field, it compares routes and favors plans with fewer fetches and shorter chains of dependent calls. The planner algorithm will backtrack and try other routes searching for better paths. This constrains the search for a better plan and reduces the memory spent exploring alternatives. For very large queries, the planner is up to <strong>300 times faster while using 97% less memory</strong>. To learn more, read the Incremental Query Planner <a href="https://www.apollographql.com/blog/apollos-next-generation-query-planner">deep dive blog</a>.</p>



<p class="wp-block-paragraph">We’ve also rewritten the request pipeline around reusable Tower services, the Rust components that process each stage of a request. These services can be cloned, removing internal buffers that were previously needed to share access to a service. Readiness checks let downstream stages signal when they cannot accept more work, allowing backpressure to flow through the pipeline. Removing those extra queues reduces the handoffs and coordination needed to move a request through the router.</p>



<p class="wp-block-paragraph">On the response side, the router avoids repeated work over JSON data while collecting usage metrics. When it processes GraphQL fragments, it tracks response objects by their memory address instead of hashing their contents each time. This avoids repeatedly walking large JSON subtrees just to check whether a fragment has already been processed for an object. The reported data stays the same, with less CPU work on large responses that contain many fragments.</p>



<h2 class="wp-block-heading"><a href="#circuit-breaking-built-into-the-graphos-router" aria-hidden="true" class="aal_anchor" id="circuit-breaking-built-into-the-graphos-router"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Circuit breaking built into the GraphOS Router</h2>



<p class="wp-block-paragraph">Also coming soon to Router 3.0, we are adding native circuit breaking for <a href="https://www.apollographql.com/docs/graphos/resources/glossary?docs%5Bquery%5D=subgraph">subgraphs</a> and <a href="https://www.apollographql.com/docs/graphos/connectors">Apollo Connectors</a>, so the router can stop sending work to a service that is reporting failures. When a set failure threshold is reached, the breaker pauses those requests and later sends a probe to check whether the service has recovered. This gives the service room to recover and helps prevent failures from spreading through the graph. Teams can set thresholds for individual services and use telemetry to see when a breaker opens, rejects requests, or checks for recovery.</p>



<p class="wp-block-paragraph">Every subgraph and Apollo Connector features its own circuit breaker, allowing traffic to flow normally while monitoring errors in a closed state. Should downstream failures cross your set threshold, the breaker trips to open, promptly returning errors to clients and shielding that service from further traffic. Following a brief pause, the router enters a half-open state and dispatches a single probe request while holding back other work. A successful probe closes the breaker to restore standard operation, whereas a failed attempt reopens it to give the underlying service more room to recover.</p>



<h2 class="wp-block-heading"><a href="#distributed-rate-limiting" aria-hidden="true" class="aal_anchor" id="distributed-rate-limiting"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Distributed rate limiting</h2>



<p class="wp-block-paragraph">Distributed rate limiting is coming to Router 3.0, with a shared traffic limit across GraphOS Router instances. We’re using Redis to track that limit for routers that share the same policy and store. Each router draws from the same budget when it checks whether to allow an operation. Which means a limit will be enforced across the entire router fleet whether you run two routers or twenty. You can add router capacity without raising the load your services need to handle.</p>



<p class="wp-block-paragraph">You’ll be able to set limits for each client, so you can choose which budget applies. Each tenant could have its own allowance, so one tenant’s traffic doesn’t use up another’s share. You’ll be able to limit incoming GraphQL operations as well as downstream calls to subgraphs and Apollo Connectors. That gives you control over traffic entering the graph and the work sent to your services.</p>



<p class="wp-block-paragraph">We’re working towards an observation mode that shows which requests a proposed policy would reject. It will check the limit and record that decision, while leaving enforcement off for that policy. You can see which callers would be affected, adjust the limit, and test it against real traffic before you enforce it.</p>



<h2 class="wp-block-heading"><a href="#updated-to-support-the-latest-graphql-specification" aria-hidden="true" class="aal_anchor" id="updated-to-support-the-latest-graphql-specification"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Updated to support the latest GraphQL Specification</h2>



<p class="wp-block-paragraph">We’re bringing Router 3.0 up-to-date with the <a href="https://spec.graphql.org/September2025/">latest GraphQL specification</a>. This includes support for the built-in <code class="" data-line="">@oneOf</code> directive for modeling mutually exclusive inputs. Marking an input object with <code class="" data-line="">@oneOf</code> will require clients to submit exactly one of the input fields, enforced by the Router during operation validation. Previously, this would require custom validations in your subgraphs. Now you can shift the errors left and have the Router reject invalid queries before sending any traffic downstream. The <code class="" data-line="">@oneOf</code> directive is supported in Composition v3, which you can try out by switching to the Federation Next build track in GraphOS.</p>



<p class="wp-block-paragraph">The latest GraphQL specification also includes new validations for the <code class="" data-line="">@deprecated</code> directive. The <code class="" data-line="">reason</code> argument is now non-nullable. Previously, nullifying the argument with <code class="" data-line="">@deprecated(reason: null)</code> was valid, introducing ambiguity in the meaning of the directive. Some libraries considered this to mean the field was not deprecated, while others meant it to mean the field was deprecated without a reason. The latest spec removes the ambiguity altogether. Additionally, if you have an object type which implements an interface and you deprecate one of the object’s fields, the corresponding interface field must also be deprecated. This prevents dropping implementer fields when clients continue to rely on the related interface. Both of these patterns will be patched in the LTS version of Federation and raised as hints in the build system so you can try out Router 3.0 with your existing supergraph. These validations will be enforced in Federation 3.</p>



<p class="wp-block-paragraph">Finally, GraphOS Router 3.0 supports the other quality of life improvements from the GraphQL specification. You can now add descriptions to operation definitions, allowing you to describe your queries and fragments. This is especially useful for AI agents to get more context about how an operation is used and when to call it. Comments and strings in GraphQL documents now also support Unicode characters above 0xFFFF 🚀. These updates should allow you to write more expressive schemas while safely evolving your schema without disrupting clients.</p>



<h2 class="wp-block-heading"><a href="#where-to-go-next" aria-hidden="true" class="aal_anchor" id="where-to-go-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Where to go next&nbsp;</h2>



<p class="wp-block-paragraph">GraphOS Router 3.0 gives teams more control over how they deploy and operate their graph, while strengthening the performance and resilience of the infrastructure underneath it.</p>



<p class="wp-block-paragraph">If you’re already running GraphOS Router 2.x, you can start trying Router 3.0 in Preview today. Read the GraphOS Router 3.0 <a href="https://www.apollographql.com/docs/graphos/routing/v3">documentation</a> to explore what’s new, and follow the <a href="https://www.apollographql.com/docs/graphos/routing/v3/upgrade/from-router-v2">upgrade guide</a> for everything you need to move from Router 2.x to Router 3.0.</p>


Introducing GraphOS Router 3.0


<p class="wp-block-paragraph">GraphOS Factory is an agent skill that turns an existing REST API into an Apollo Connectors subgraph. Point it at an OpenAPI or Swagger spec, or at the API&#8217;s public docs, and it inventories the API, then works with you through the design questions: which operations and fields belong in the graph, what each field means, how the data relates, and what stays out. It validates the result and exports a subgraph you can add to your supergraph and run in Router.</p>



<p class="wp-block-paragraph">Answering those questions is domain modeling, not wrapping. A REST API describes how one service happens to be exposed. A graph describes the things your business works with and how they relate, and that is what you are building each time you bring a service into it. One connector is one bite of a larger problem. You model a few endpoints at a time, on your own terms, and over many services those pieces add up to a domain model for your business. GraphOS Factory is built for that work: for engineers who make these decisions, record them, and keep the model current as the APIs behind it change.</p>



<p class="wp-block-paragraph">What makes that possible across many services are the artifacts that GraphOS Factory collects as you work. Every decision, every pinned source, and everything the agent learned along the way is written to disk in Git. That means the work can be resumed, refined, handed to a teammate, and maintained like any other code in your software development lifecycle, instead of being regenerated from scratch each time.</p>



<p class="wp-block-paragraph">GraphOS Factory is available today as a preview skill in the <a href="https://github.com/apollographql/skills">Apollo Skills repository</a>.</p>



<h2 class="wp-block-heading"><a href="#less-manual-work-to-bring-a-rest-api-into-your-graph" aria-hidden="true" class="aal_anchor" id="less-manual-work-to-bring-a-rest-api-into-your-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Less manual work to bring a REST API into your graph&nbsp;</h2>



<p class="wp-block-paragraph">Bringing an existing REST API into a graph with Connectors has taken more work than it should. You have to read the API, decide which operations and fields belong in the graph, name things the way the domain thinks about them, work out how pagination and batching map onto GraphQL, and decide what to keep out. For a large API, with hundreds of endpoints and thousands of fields, it is weeks of careful work before the first query runs.</p>



<p class="wp-block-paragraph">We have been simplifying that work directly in Connectors. The latest release adds request-less connectors, a cleaner mapping language, and native support for abstract types, so more of the mechanics are handled for you.</p>



<p class="wp-block-paragraph">Agents can speed this up too, but the way most people use them today creates a second problem. Generation is a one-shot event. You get a Connector, you fix it by hand, and the next time you regenerate you lose every decision you made and risk breaking what was working. The API adds endpoints, deprecates a field, or you want to add scope you left out the first time, and you are back to a blank prompt. With a large API it gets worse: the agents might lose the context partway through leading to modifications in the schema that you did not intend to change.</p>



<p class="wp-block-paragraph">GraphOS Factory treats Connector generation as something you iterate on. The decisions you make, the sources the agent pinned, and what it learned about your API all live in Git next to the output. When the API changes, when you find a bug, or when Connectors ships a feature you want to use, you pick up where you left off. Because the context is on disk and not in one person&#8217;s chat history, a teammate can continue the work too.</p>



<h2 class="wp-block-heading"><a href="#how-it-works" aria-hidden="true" class="aal_anchor" id="how-it-works"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How it works</h2>



<p class="wp-block-paragraph">You give the agent an OpenAPI or Swagger spec, or a link to the API&#8217;s documentation. From there the skill runs a guided process rather than a single generation step.</p>



<ol class="wp-block-list">
<li><strong>Workspace.</strong> The agent sets up a dedicated Git workspace for this API. Everything it produces from here on, including its working notes, lands in that workspace.</li>



<li><strong>Inventory.</strong> It pulls the sources, pins them, and builds an inventory of the API&#8217;s operations and types.</li>



<li><strong>Scope.</strong> You choose which operations and fields belong in the graph. You can model three endpoints or thirty. You do not have to take the whole API surface.</li>



<li><strong>Design decisions.</strong> The agent walks you through the choices that shape the subgraph: read-only or mutations too, how to handle PII, batching and pagination, what each field means in your domain, and what stays out. Each answer is recorded.</li>



<li><strong>Validation.</strong> Every change is checked with composition, Connector unit tests, and a mocked end-to-end run against the Router. If you provide a credential, it also runs live against the real API.</li>



<li><strong>Export.</strong> When you confirm, it exports a Connectors subgraph you can add to your supergraph.</li>
</ol>



<p class="wp-block-paragraph">The result is a subgraph that composes, passes tests, and reflects decisions you made on purpose, with a record of why.</p>



<h2 class="wp-block-heading"><a href="#iterative-by-design" aria-hidden="true" class="aal_anchor" id="iterative-by-design"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Iterative by design</h2>



<p class="wp-block-paragraph">The difference between GraphOS Factory and a one-shot generator is what gets written to disk. Alongside the subgraph, the workspace holds three kinds of state:</p>



<ul class="wp-block-list">
<li><strong>Decisions.</strong> Every scope and design choice you made, in a form the agent reads back before it changes anything.</li>



<li><strong>Pinned sources.</strong> The spec or docs the inventory was built from, so a later run can tell what the API changed rather than re-reading it from scratch.</li>



<li><strong>Agent discoveries.</strong> What the agent worked out about the API along the way: quirks in pagination, fields that turned out to be optional, endpoints that behaved differently than documented.</li>
</ul>



<p class="wp-block-paragraph">All of it is in Git, so it is reviewable, diffable, and travels with the code. That changes what a second session looks like. When the API adds or deprecates endpoints, the agent reconciles against the pinned inventory and your existing decisions instead of regenerating. When you want to widen scope, fix a bug, or adopt a newly released Connectors feature, you make that one change and the validation layers tell you whether anything else moved. And because none of this depends on a particular person&#8217;s chat history, a teammate can open the workspace and continue where someone else stopped.</p>



<p class="wp-block-paragraph">Over time, the skill itself gets better, which will lead to higher quality Connectors. Apollo has spent years maintaining Federation and working with teams on domain model design across many industries and scales. As we fold more of that into the skill&#8217;s references, users get the latest best practices without changing their workflow.</p>



<h2 class="wp-block-heading"><a href="#who-its-for" aria-hidden="true" class="aal_anchor" id="who-its-for"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Who it&#8217;s for</h2>



<p class="wp-block-paragraph">GraphOS Factory is for engineers who need to bring an existing REST API into a graph and keep it there as both the API and the graph evolve. In practice that means people doing domain modeling: deciding what a service exposes, what its fields mean, how the data relates, and what stays out of scope. The skill handles the mechanics of Connectors so that your time goes into those decisions.</p>



<p class="wp-block-paragraph">It also fits teams that do not all use the same agent. The workflow and its decision history live in the workspace, not in the harness, so someone working in Claude Code, someone in Codex, and someone in an IDE plugin can all pick up the same Connector.</p>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p class="wp-block-paragraph">GraphOS Factory is part of the Apollo Skills collection. Installation instructions are in the <a href="https://github.com/apollographql/skills">apollographql/skills</a> repository.</p>



<p class="wp-block-paragraph">Once installed, the skill activates when you ask your agent to build a Connector or subgraph from a REST API. In Claude Code you can also invoke it directly:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">/apollo-skills:graphos-factory</code></pre>



<p class="wp-block-paragraph">Give it the API&#8217;s OpenAPI or Swagger spec, or a link to its docs. The agent will set up the workspace, inventory the API, ask you to select operations and fields, and work through the design decisions with you. Each change is validated as you go. When you confirm, it exports a Connectors subgraph ready to add to your supergraph.</p>



<p class="wp-block-paragraph">A good first run is a few endpoints from an API you already know well. You will see how the decision prompts work, and you will have a workspace to come back to when you want to widen scope.</p>



<h2 class="wp-block-heading"><a href="#where-this-is-today" aria-hidden="true" class="aal_anchor" id="where-this-is-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Where this is today</h2>



<p class="wp-block-paragraph">GraphOS Factory is available in preview. We have validated it with evals on the AppWorld dataset and used it to onboard more than 40 internal services, but it is early and the shape of the skill will change as people use it. We are sharing it now because the iterative, Git-backed approach is the part we most want feedback on.</p>



<p class="wp-block-paragraph">Try it on an API you care about and tell us what worked and what did not. Issues are welcome in the <a href="https://github.com/apollographql/skills">skills repository</a>. If you’re joining us at Summit, you’ll hear more about it in the <a href="https://apollosummit.dev/session/apollo-keynote">Apollo Keynote</a>. And if you can’t be there in person, you can tune in to the keynote live from anywhere via the <a href="https://apollosummit.dev/livestream">Summit livestream</a>. We’d love to hear what you think.</p>



<p class="wp-block-paragraph"></p>


Introducing GraphOS Factory

Apollo Connectors v0.4 is Generally Available


<p class="wp-block-paragraph">Rover has been the command-line entry point to the Apollo ecosystem since the earliest days of Apollo Federation. It has been the tool to publish subgraphs, run schema checks, compose supergraphs, and generally act as the bridge between your terminal and GraphOS. Today we&#8217;re shipping <strong>Rover 1.0</strong>, the biggest set of changes to the CLI since it was first released.</p>



<p class="wp-block-paragraph">This isn&#8217;t a 1.0 in the &#8220;we finally feel confident enough to drop the 0.x&#8221; sense, though that&#8217;s part of it. It&#8217;s a 1.0 because auth, configuration, extensibility, and checks/publish were rebuilt around how teams are running Rover today. This includes local development and CI, across multiple graphs and environments, and through agentic tooling built on top of Rover.</p>



<p class="wp-block-paragraph">Here&#8217;s what&#8217;s new.</p>



<h2 class="wp-block-heading"><a href="#auth-identity-oauth-instead-of-static-api-keys" aria-hidden="true" class="aal_anchor" id="auth-identity-oauth-instead-of-static-api-keys"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Auth &amp; Identity: OAuth instead of static API keys</h2>



<p class="wp-block-paragraph">Static API keys are simple, but they&#8217;re also the thing security teams ask you to rotate, the thing that leaks into CI logs, and the thing nobody remembers the scope of six months later.</p>



<p class="wp-block-paragraph">Rover 1.0 introduces <strong>OAuth-based auth flows</strong> as an alternative to long-lived static API keys. Instead of minting a key in Studio and pasting it into an environment variable, you can now authenticate Rover interactively and let it handle token exchange and refresh for you:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">rover auth login</code></pre>



<p class="wp-block-paragraph">Alongside the new auth flow, Rover 1.0 adds first-class <strong>API key and grant management</strong> so you can manage credentials Rover is using without leaving the CLI:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">rover api-key create my-org client-credentials my-ci-job
rover api-key list my-org </code></pre>



<p class="wp-block-paragraph">Static API keys aren&#8217;t going away as they&#8217;re still the right fit for a lot of CI pipelines, but they&#8217;re no longer the only path, and they&#8217;re no longer the <em>easiest</em> path either.</p>



<h2 class="wp-block-heading"><a href="#config-lifecycle-profiles-instead-of-environment-variables" aria-hidden="true" class="aal_anchor" id="config-lifecycle-profiles-instead-of-environment-variables"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Config &amp; lifecycle: profiles instead of environment variables</h2>



<p class="wp-block-paragraph">Rover has long supported multiple named auth profiles, but a lot of day-to-day configuration, such as graph refs, endpoints, output preferences, has historically lived in a scattering of environment variables that were easy to lose track of across shells, machines, and CI jobs.</p>



<p class="wp-block-paragraph">Rover 1.0 consolidates that configuration into <strong>Rover profiles</strong>, giving you a single, inspectable place for the settings a given graph or environment needs:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">rover config list
rover config show --profile production</code></pre>



<p class="wp-block-paragraph">The same release also removes legacy <strong>Apollo Federation 1</strong> support from Rover. Federation 2 has been the default for new graphs for a long time now, and carrying Federation 1 composition logic in the CLI was adding complexity for a shrinking number of users. If you&#8217;re still on Federation 1, now&#8217;s a good time to plan your migration. Federation 2 is a superset of Federation 1&#8217;s capabilities, and Apollo&#8217;s <a href="https://www.apollographql.com/docs/graphos/schema-design/federated-schemas/reference/moving-to-federation-2">migration guide</a> walks through the upgrade path.</p>



<h2 class="wp-block-heading"><a href="#a-more-reliable-plugin-system" aria-hidden="true" class="aal_anchor" id="a-more-reliable-plugin-system"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A more reliable plugin system</h2>



<p class="wp-block-paragraph">Rover has always relied on a plugin mechanism, with the supergraph plugin as the clearest example, to keep specific pieces of functionality independently versioned. Rover 1.0 makes that mechanism more reliable, so the plugins backing a given Rover install behave the same way every time you run it.</p>



<p class="wp-block-paragraph">That means:</p>



<ul class="wp-block-list">
<li><strong>Pinned versions</strong>, so a given Rover install always resolves to the exact plugin version it expects, instead of a version that can drift out from under you</li>



<li><strong>Reproducible results</strong>, so <code class="" data-line="">check,</code> <code class="" data-line="">publish</code>, and composition behave identically run after run on your laptop and in CI</li>



<li><strong>Transparent install and download behavior</strong>, so that when Rover needs a plugin binary, it tells you what it&#8217;s fetching, from where, and why, instead of silently pulling something down</li>
</ul>



<p class="wp-block-paragraph">The result is a CLI you can trust to behave the same way today as it did yesterday, wherever it&#8217;s running.</p>



<h2 class="wp-block-heading"><a href="#checks-publish-contract-variants" aria-hidden="true" class="aal_anchor" id="checks-publish-contract-variants"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Checks &amp; Publish: contract variants</h2>



<p class="wp-block-paragraph">If you&#8217;re using <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/contracts/overview">contracts</a> to expose different views of your supergraph to different consumers, Rover 1.0 now understands them natively in the two commands you run most: <code class="" data-line="">check</code> and <code class="" data-line="">publish</code>.</p>



<p class="wp-block-paragraph"><code class="" data-line="">rover subgraph check</code> and <code class="" data-line="">rover subgraph publish</code> now surface <strong>contract variant</strong> results directly, so you can see how a proposed change affects each contract, not just the underlying source variant, before you ship it:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">rover subgraph check my-graph@my-variant \
  --schema ./products.graphql \
  --name products \
  --include-contract-checks</code></pre>



<p class="wp-block-paragraph">No more publishing a change, then separately checking Studio to see whether it broke a contract downstream. The information you need is in the output of the command you were already running.</p>



<h2 class="wp-block-heading"><a href="#checks-publish-client-operations" aria-hidden="true" class="aal_anchor" id="checks-publish-client-operations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Checks &amp; Publish: client operations</h2>



<p class="wp-block-paragraph">We’ve introduced client operation checks to Rover. These were previously located in the <a href="https://github.com/apollographql/apollo-tooling#apollo-cli">legacy Apollo CLI</a>. With this addition to Rover, the Apollo CLI is officially deprecated. This feature allows you to verify your client operations against your graph variants, ensuring that your code works with a target graph before you ship. You can see how this works in Rover by reading through the guide <a href="https://www.apollographql.com/docs/rover/commands/client">here</a>.</p>



<h2 class="wp-block-heading"><a href="#upgrading" aria-hidden="true" class="aal_anchor" id="upgrading"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Upgrading</h2>



<p class="wp-block-paragraph">Rover 1.0 is a major version bump, and while most of these changes are additive, the removal of Federation 1 support and the shift away from some environment-variable-based configuration mean it&#8217;s worth reading the <a href="https://www.apollographql.com/docs/rover">migration guide</a> before upgrading CI. To get the latest version:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">curl -sSL https://rover.apollo.dev/nix/latest | sh</code></pre>



<p class="wp-block-paragraph">or via npm:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">npm install -g @apollo/rover</code></pre>



<p class="wp-block-paragraph">Rover&#8217;s source is available on <a href="https://github.com/apollographql/rover">GitHub</a>, and that&#8217;s also the best place to reach us. If you hit something that doesn&#8217;t feel right in 1.0, or you&#8217;re building a plugin and want to talk through the interface, open an issue. We&#8217;d love to hear from you.</p>


Rover 1.0 Is Now Generally Available


<p class="wp-block-paragraph">Today we are launching a new query planning algorithm which is built to scale to the most complex graphs, as part of <a href="https://www.apollographql.com/blog/introducing-graphos-router-3-0">GraphOS Router 3.0</a>. The existing planning algorithm has brought us a long way, and two years ago we completed our project to reimplement it with the native performance of Rust. This brought a step change improvement in speed compared to our TypeScript implementation.</p>



<p class="wp-block-paragraph">Our customers with the most complex graphs and operations still saw long planning times and high memory usage. Some users aggressively cache query plans to do the work before taking live traffic, while others have considered splitting the compute-heavy planning process out of the router entirely. These treat the symptoms of the core problem: the query planner itself is not as efficient as it should be.</p>



<p class="wp-block-paragraph">For Router 3.0, we aimed to create a planner that was <em>fast</em>, even for those complex operations, with bounded and predictable memory usage. This required a ground-up reimplementation of the core search algorithm and the representation of candidate plans during that search, resulting in what we call the <a href="https://www.apollographql.com/docs/graphos/routing/query-planning/incremental-query-planner">I</a><a href="https://www.apollographql.com/docs/graphos/routing/v3/query-planning/incremental-query-planner">ncremental Query Planner</a>.</p>



<h2 class="wp-block-heading"><a href="#planning-operations-incrementally" aria-hidden="true" class="aal_anchor" id="planning-operations-incrementally"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Planning Operations, Incrementally</h2>



<p class="wp-block-paragraph">In our existing planner, the search algorithm is primarily a Breadth-First Search (BFS) over the possible options for each set of fields to plan. When the planner considers which paths to take, it considers all possible combinations of paths extending from the set of decisions made so far. This is fast when there are relatively few options, but the number of options explodes when uses of @key and @shareable create many options at multiple levels of the search. Within each plan candidate, the planner models the fetches it will make to the upstream subgraphs, optimizes the candidate plan, and compares it to the other candidates. The best candidate should parallelize as much work as possible, with the fewest number of fetches. There are three core observations about this process:</p>



<ol class="wp-block-list">
<li>Running a BFS over the search space means we must run the search to completion to get a plan</li>



<li>Creating a fresh model of each plan candidate will result in many allocations for large search spaces</li>



<li>Optimizing a candidate plan is wasted computation when that plan is not better than the best plan so far</li>
</ol>



<p class="wp-block-paragraph">The Incremental Planner takes a fundamentally different approach, starting with a Depth-First Search (DFS). This allows the planner to quickly find an initial draft of the plan, progressively optimizing the plan as it explores and finds better options in the search space. The planner mutates a single candidate plan in place, instead of creating a fresh copy for each combination of search options, and the cost heuristic used to evaluate those plans takes future graph reductions into account, allowing the planner to skip wasteful optimization steps when comparing candidates.</p>



<h2 class="wp-block-heading"><a href="#bounding-memory-during-search" aria-hidden="true" class="aal_anchor" id="bounding-memory-during-search"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Bounding Memory During Search</h2>



<p class="wp-block-paragraph">Since we want to make memory usage more predictable, we implemented an algorithm called BULB search (Beam search Using Limited discrepancy Backtracking) from Furcy and Koenig&#8217;s <a href="https://dl.acm.org/doi/10.5555/1642293.1642313"><em>Limited Discrepancy Beam Search</em></a>. Variants of Beam Search limit the set of possible choices in the search by only keeping a subset of options at each decision point. This subset is called a <em>beam</em>, and the maximum number of options is called the <em>beam width</em>. Traditional Beam Search may prune globally optimal options, which is why we selected BULB. The backtracking introduced in BULB allows the planner to revisit locally suboptimal options that plain beam search would have pruned permanently, so a bad early decision doesn&#8217;t lock in a bad plan.</p>



<p class="wp-block-paragraph">The second modification is the in-place mutation of the candidate plan, which we call the <em>Fetch Graph</em>. Modifications to the Fetch Graph are tracked as a stack of operations with corresponding undo actions. When the planner backtracks to a previously explored decision, we undo the actions performed since that particular decision, then continue exploring in the new direction. If the in-progress candidate has routed all fields in the operation, and the candidate is more optimal than the best plan found thus far, the planner takes a snapshot of the plan and records it as the best candidate so far. This is the only time the Incremental Planner creates a full copy of the candidate plan.</p>



<h2 class="wp-block-heading"><a href="#optimizing-the-candidate-plan" aria-hidden="true" class="aal_anchor" id="optimizing-the-candidate-plan"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Optimizing the Candidate Plan</h2>



<p class="wp-block-paragraph">The Incremental Planner will start by finding a draft of the query plan by making locally optimal routing decisions for each field, as defined by its internal heuristics. This means it will prefer a local selection in the current subgraph over jumping to another subgraph, which is typically more efficient but can lead to suboptimal plans. After creating a draft, the search process will revisit previous decisions, trying locally suboptimal decisions which could result in a globally optimal plan.</p>



<p class="wp-block-paragraph">Once the planner creates the initial draft, it starts considering a parameter we call <em>fuel</em>. Each time the planner encounters a field which could come from multiple sources, the decision of where to route that field deducts from fuel. If the globally optimal plan could not be found before the fuel was exhausted, the planner returns the best plan found thus far. This provides a deterministic way to limit the amount of computation in the planning process. Customers who need extremely fast plans can set fuel to zero, always returning the first draft of the plan. Other customers who want to find the optimal plan can use a much higher fuel budget, so the planner continues exploring well beyond the first draft.</p>



<p class="wp-block-paragraph">The fuel parameter dovetails with the other primary configuration option for the search algorithm, <em>beam width</em>. The beam width determines how many options are tracked in memory for each decision point. A smaller beam width will use less memory for planning but may require more backtracking to find the best plan. Note that the backtracking will be limited by the fuel budget, so these two parameters work in tandem to limit the amount of compute and memory used to find the plan.</p>



<h2 class="wp-block-heading"><a href="#the-results" aria-hidden="true" class="aal_anchor" id="the-results"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The Results</h2>



<p class="wp-block-paragraph">We validated the Incremental Planner head-to-head against the existing planner on a set of 200,000 operations on our most complex customer graphs, some of which took nearly a minute to plan. The Incremental Planner plans each of them in less than two seconds, with a staggering <strong>300x speedup on the slowest operations and using 97% less memory!</strong></p>



<p class="wp-block-paragraph">It is important to note that the Incremental Planner can generate plans which are different from the existing planner. In simple cases, it often finds the same plan, or a plan with the same number of fetches with slightly different fetch content. There are large operations for which the Incremental Planner is not yet optimized, and it may find a less optimal plan. In these cases, try increasing your fuel to give the planner more time to optimize. On the other hand, the Incremental Planner can find more efficient plans for cases where the existing planner hits its maximum evaluated plans cap.</p>



<h2 class="wp-block-heading"><a href="#try-it-out-today" aria-hidden="true" class="aal_anchor" id="try-it-out-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try it out today</h2>



<p class="wp-block-paragraph">The Incremental Planner is available as an opt-in configuration in <a href="https://github.com/apollographql/router/releases#release-v3.0.0-preview.0">GraphOS Router 3.0</a>. Simply enable it in your Router config:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">supergraph:
  query_planning:
    incremental_planner:
      enabled: true</code></pre>



<p class="wp-block-paragraph">That&#8217;s it! The defaults should work well for nearly all graphs, but fuel and beam width are both configurable if you want to trade planning effort against speed and memory. To help you tune against real traffic, the planner also ships two new histogram metrics: <code class="" data-line="">apollo.router.query_planning.plan.fuel_consumed</code> and <code class="" data-line="">apollo.router.query_planning.plan.fuel_remaining</code>.</p>



<p class="wp-block-paragraph">If remaining fuel stays above zero, the planner explored every option it wanted to within your budget. If it hits zero, a larger budget may find better plans. Check out our <a href="https://www.apollographql.com/docs/graphos/routing/v3/query-planning/incremental-query-planner">documentation</a> for details. </p>



<p class="wp-block-paragraph">Since the Incremental Planner is opt-in during this release, your feedback directly shapes when it becomes the default. If you run a complex graph, we&#8217;d especially like to hear how it performs for you. File issues on <a href="https://github.com/apollographql/router">GitHub</a> or share your results in the <a href="https://community.apollographql.com/">Apollo Community</a>.</p>


Introducing Apollo’s Next Generation Query Planner


<p class="wp-block-paragraph">Today we&#8217;re introducing the <a href="https://www.apollographql.com/docs/router-support-tool">GraphOS Router Support Tool</a>, a new way to package up a diagnostic snapshot of your GraphOS Router and its Kubernetes environment, including router version and config, logs, pod health, and metrics, into a single sanitized archive, on demand, without affecting your router.</p>



<p class="wp-block-paragraph">This first release covers on-demand collection from any Kubernetes-hosted router deployment, with automatic redaction and local or customer-owned object storage. </p>



<h2 class="wp-block-heading"><a href="#the-problem-it-solves" aria-hidden="true" class="aal_anchor" id="the-problem-it-solves"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>The problem it solves</strong></h2>



<p class="wp-block-paragraph">Getting the full picture when something goes wrong has historically meant a manual, back-and-forth process: <code class="" data-line="">kubectl describe</code>, hunting down <code class="" data-line="">router.yaml</code>, grepping logs, screenshotting a dashboard. The Router Support Tool gathers all of it in one pass, often enough to diagnose and fix the issue yourself, and if not, exactly what a support ticket needs. This includes:</p>



<ul class="wp-block-list">
<li>Router version and startup configuration</li>



<li>Current and previous-container logs (so a router that already restarted still has its history captured)</li>



<li>Pod status, restart counts, and resource limits</li>



<li>A point-in-time Prometheus metrics snapshot, if you expose one</li>



<li>Sanitized <code class="" data-line="">router.yaml</code></li>
</ul>



<p class="wp-block-paragraph">You generate and store the bundle entirely within infrastructure you control, locally on disk, or in a bucket you own. Apollo only sees it if and when you choose to share it during a support engagement.</p>



<h2 class="wp-block-heading"><a href="#how-did-we-build-this" aria-hidden="true" class="aal_anchor" id="how-did-we-build-this"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>How did we build this?</strong></h2>



<p class="wp-block-paragraph">The support tool is built on top of <a href="https://troubleshoot.sh/">troubleshoot.sh</a>, the open-source Kubernetes support-bundle framework, so collection and redaction are handled by their engine. What we&#8217;ve added is everything around it: what to collect, how the spec reaches your cluster, how you trigger a collection, and where the resulting bundle goes. We have also built custom redactors that ensure that sensitive information is stripped automatically, on top of troubleshoot.sh’s own built-in redaction.</p>



<p class="wp-block-paragraph">A few things we built in deliberately:</p>



<ul class="wp-block-list">
<li>Generic secrets are stripped automatically, on every file, with no configuration. Environment-variable-named secrets (password, token, *_SECRET_ACCESS_KEY, and similar), credentials embedded in URLs, and database connection strings are all redacted unconditionally, before the bundle is written.</li>



<li>Router-specific sensitive fields get their own redaction rules, because generic pattern-matching doesn&#8217;t know your <code class="" data-line="">router.yaml</code>&#8216;s shape. This covers JWT verification and subgraph auth configuration, literal header values in your headers config, GraphQL operation bodies that reach router logs, subgraph routing URLs, and Redis credentials, whether embedded in a cache connection string or set as separate username/password fields.</li>



<li>It&#8217;s safe to run against a router that&#8217;s already degraded. Every collector gathers its signal externally, from the Kubernetes API, kubelet metrics, or an HTTP endpoint, rather than executing inside your router&#8217;s container, so running the tool doesn&#8217;t compete with your router process for CPU or memory.</li>
</ul>



<h2 class="wp-block-heading"><a href="#how-to-set-it-up" aria-hidden="true" class="aal_anchor" id="how-to-set-it-up"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>How to set it up</strong></h2>



<p class="wp-block-paragraph">Generating a support bundle is done through a single Helm chart, <code class="" data-line="">router-diagnostics-chart</code>, with a <code class="" data-line="">mode</code> value controlling how collection actually runs. </p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td></td><td><strong>mode: local</strong></td><td><strong>mode: job</strong></td></tr><tr><td>Who runs collection</td><td>You, from your own machine, with your own kubectl access</td><td>A Kubernetes Job, in-cluster, using its own ServiceAccount</td></tr><tr><td>What gets installed</td><td>Spec ConfigMap</td><td>Spec ConfigMap + Job + ServiceAccount/RBAC (namespace-scoped and cluster-scoped)</td></tr><tr><td>Where the bundle lands</td><td>Your current directory</td><td>S3 (or an S3-compatible store), GCS, or a bare HTTP(S) endpoint you configure</td></tr><tr><td>Use when</td><td>You have kubectl access to production</td><td>Your kubectl access is restricted and a platform team runs it on your behalf</td></tr></tbody></table></figure>



<h3 class="wp-block-heading"><a href="#running-the-tool" aria-hidden="true" class="aal_anchor" id="running-the-tool"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Running the tool</strong></h3>



<p class="wp-block-paragraph">Install a small Helm chart and point it at your router, with out-of-the-box support for the official Apollo router Helm chart and a bit more configuration for raw manifests or custom deployments.&nbsp;</p>



<p class="wp-block-paragraph">From there, you choose how the support bundle is collected: locally, with a script, from your own machine with <code class="" data-line="">kubectl</code> access, producing a bundle on your filesystem, or as a Kubernetes Job, running in-cluster against your live router pods, for teams whose access to production is more restricted. Both paths collect the same information, only how and where it runs and where the bundle lands differ.</p>



<p class="wp-block-paragraph">Collection is on-demand, you (or your platform team) kick it off when you need it, whether that&#8217;s in response to an incident or just to capture a healthy baseline for comparison later.</p>



<p class="wp-block-paragraph">The tool produces a single artifact: <code class="" data-line="">support-bundle-2026-09-11T14_32_00.tar.gz</code>, for example, a bundle collected with <code class="" data-line="">mode: local</code> is shown below:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="681" height="177" src="https://wp.apollographql.com/wp-content/uploads/2026/10/image-13.png" alt="" class="wp-image-25862" srcset="https://wp.apollographql.com/wp-content/uploads/2026/10/image-13.png 681w, https://wp.apollographql.com/wp-content/uploads/2026/10/image-13-300x78.png 300w" sizes="auto, (max-width: 681px) 100vw, 681px" /><figcaption class="wp-element-caption">Figure: Bundle collected in local mode</figcaption></figure>



<p class="wp-block-paragraph">From there, it&#8217;s yours. Inspect it, keep it, or attach it to a support ticket.<br></p>



<h2 class="wp-block-heading"><a href="#faq" aria-hidden="true" class="aal_anchor" id="faq"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>FAQ</strong></h2>



<p class="wp-block-paragraph"><strong>Does this restart my router?</strong></p>



<p class="wp-block-paragraph">No. Collection never touches a running router process. Everything is gathered from outside the container.</p>



<p class="wp-block-paragraph"><strong>Does Apollo automatically receive my bundle?</strong></p>



<p class="wp-block-paragraph">No. When running the tool locally (<code class="" data-line="">mode: local</code>),&nbsp; the bundle is always written to your own machine. When run as a Job (<code class="" data-line="">mode: job</code>), you choose the destination yourself: S3 (or an S3-compatible store), GCS, or a bare HTTP(S) endpoint you control. Either way, the bundle lands entirely within infrastructure you control. Apollo only sees it if and when you choose to share it with us.</p>



<p class="wp-block-paragraph"><strong>What gets redacted?</strong></p>



<p class="wp-block-paragraph">Tokens, credentials, connection strings, and generic secrets are stripped automatically on every file, along with router-specific values like JWT/auth configuration, header literal values, operation bodies in logs, subgraph URLs, TLS private keys, and Redis credentials. No configuration is required — redaction runs by default on every collection.</p>



<p class="wp-block-paragraph"><strong>Does this work outside Kubernetes?</strong></p>



<p class="wp-block-paragraph">Not in this release. Other types of deployments such as ECS, Fargate, and standalone VM deployments are not supported.</p>



<p class="wp-block-paragraph"><strong>Can I run this with the Apollo GraphOS Operator?</strong></p>



<p class="wp-block-paragraph">Not in this release, but support for the Apollo GraphOS Operator is on the roadmap.</p>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Get started</strong></h2>



<p class="wp-block-paragraph">The Router Support Tool is available today. To try it out:</p>



<ul class="wp-block-list">
<li>Check out our <a href="https://www.apollographql.com/docs/router-support-tool">documentation</a> for a step by step guide.&nbsp;</li>



<li>Have questions or hit an edge case? Share your feedback in the <a href="https://community.apollographql.com/?_gl=1*14rooy7*_gcl_au*MzU3NjE4NzU0LjE3ODUxNzM4ODQ.">Apollo Community</a>.&nbsp;</li>
</ul>



<p class="wp-block-paragraph">We built this because &#8220;can you send us your router config and logs&#8221; shouldn&#8217;t be the first hour of every support conversation. Let us know what you&#8217;d like to see it collect next.</p>


Troubleshoot faster with the GraphOS Router Support Tool

How we know a router performance result is real

Introducing Apollo’s Runtime Testing Framework


<p class="wp-block-paragraph">Building or testing a GraphQL client usually means dealing with data you don&#8217;t control yet: a backend that isn&#8217;t finished, a staging environment that&#8217;s flaky or rate-limited, or a dataset that simply doesn&#8217;t have the edge cases you need for a given test.&nbsp;</p>



<p class="wp-block-paragraph">The usual workarounds — hand-written fixtures, faker calls wired up field by field, or a hardcoded JSON blob that quietly drifts out of sync with the schema — all work, but they all cost maintenance time that scales with the size of your schema.</p>



<p class="wp-block-paragraph"><a href="https://github.com/apollographql/apollo-mock">Apollo Mock</a> takes a more direct approach: point it at a GraphQL schema, and it uses an LLM to generate a full set of fake entities that match that schema, once, as plain JSON files on disk. From there, a small GraphQL server resolves any query against that data.&nbsp;</p>



<p class="wp-block-paragraph">The LLM only runs at generation time, not per-request, so once the data is generated, serving it is fast, deterministic, and doesn&#8217;t depend on an API key or a model being available.</p>



<h2 class="wp-block-heading"><a href="#quickstart" aria-hidden="true" class="aal_anchor" id="quickstart"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Quickstart</h2>



<h3 class="wp-block-heading"><a href="#1-apply-the-gradle-plugin" aria-hidden="true" class="aal_anchor" id="1-apply-the-gradle-plugin"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>1. Apply the Gradle plugin</h3>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin" data-line="">plugins {
  id(&quot;com.apollographql.mock&quot;) version &quot;&lt;version&gt;&quot;
}

apolloMock {
  service(&quot;shop&quot;) {
    // The place where your schema is
    srcDir(&quot;src/main/graphql&quot;)
  }
}</code></pre>



<p class="wp-block-paragraph">By default, generation runs against a local <a href="https://ollama.com/">Ollama</a> model — no API key needed. <a href="https://console.anthropic.com/">Anthropic&#8217;s API</a> is also supported, and is generally a better fit for larger or more nuanced schemas:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin" data-line="">apolloMock {
  service(&quot;shop&quot;) {
    srcDir(&quot;src/main/graphql&quot;)
    provider.set(&quot;anthropic&quot;)
    apiKey.set(System.getenv(&quot;ANTHROPIC_API_KEY&quot;))
  }
}</code></pre>



<h3 class="wp-block-heading"><a href="#2-generate-the-data" aria-hidden="true" class="aal_anchor" id="2-generate-the-data"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2. Generate the data</h3>



<p class="wp-block-paragraph">Assuming a schema like this, under src/main/graphql/schema.graphqls:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">type Query {
  products: [Product!]!
  product(id: ID!): Product
  categories: [Category!]!
}

type Product {
  id: ID!
  name: String!
  description: String
  price: Float!
  category: Category!
}

type Category {
  id: ID!
  name: String!
}</code></pre>



<p class="wp-block-paragraph"><code class="" data-line="">./gradlew generateShopMockData</code> generates one JSON file per fake entity under src/main/graphql/mock-data/entity, keyed by GraphQL type. </p>



<p class="wp-block-paragraph">For an example: </p>



<pre class="wp-block-prismatic-blocks"><code class="language-json" data-line="">{
    &quot;name&quot;: &quot;Wireless Noise-Canceling Headphones&quot;,
    &quot;description&quot;: &quot;Premium over-ear headphones with 30-hour battery life and adaptive noise cancellation.&quot;,
    &quot;price&quot;: 249.99,
    &quot;currency&quot;: &quot;USD&quot;,
    &quot;inStock&quot;: true,
    &quot;id&quot;: &quot;product-1&quot;,
    &quot;category&quot;: {
        &quot;__typename&quot;: &quot;Category&quot;,
        &quot;id&quot;: &quot;category-1&quot;
    },
    &quot;reviews&quot;: [
        {
            &quot;__typename&quot;: &quot;Review&quot;,
            &quot;id&quot;: &quot;review-2&quot;
        },
        {
            &quot;__typename&quot;: &quot;Review&quot;,
            &quot;id&quot;: &quot;review-3&quot;
        },
        {
            &quot;__typename&quot;: &quot;Review&quot;,
            &quot;id&quot;: &quot;review-4&quot;
        }
    ]
}</code></pre>



<p class="wp-block-paragraph">Re-running the task after a schema change keeps existing entities and their ids stable: removed fields are dropped, newly added fields are filled in, and everything else is left alone — which matters if tests elsewhere depend on those ids.</p>



<h3 class="wp-block-heading"><a href="#3-serve-it" aria-hidden="true" class="aal_anchor" id="3-serve-it"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>3. Serve it</h3>



<p class="wp-block-paragraph">Add the server module and call serve from a small main:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin" data-line="">dependencies {
  implementation(&quot;com.apollographql.mock:server:&lt;version&gt;&quot;)
}

import apollo.mock.server.serve

fun main() {
  serve(
      schemaPath = &quot;src/main/graphql/schema.graphqls&quot;,
      dataPath = &quot;src/main/graphql/mock-data&quot;,
  )
}</code></pre>



<p class="wp-block-paragraph">Running it starts a GraphQL endpoint at <code class="" data-line="">http://localhost:4000/</code>graphql, along with a sandbox at <code class="" data-line="">http://localhost:4000/</code> to explore the schema and try queries interactively:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">curl -s http://localhost:4000/graphql \
  -H &quot;Content-Type: application/json&quot; \
  -d &#039;{&quot;query&quot;: &quot;{ products { name price category { name } } }&quot;}&#039;</code></pre>



<p class="wp-block-paragraph">That&#8217;s the whole loop: a schema in, a Gradle task to generate data against it, and a couple of lines of Kotlin to serve it. From here, an ApolloClient (or any GraphQL client, generated code or not) can point at <code class="" data-line="">localhost:4000</code> the same way it would point at a real backend.</p>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What&#8217;s next</h2>



<p class="wp-block-paragraph">This is the first release of Apollo Mock, we&#8217;re excited to hear your feedback and what you&#8217;re building with it.</p>



<p class="wp-block-paragraph">If not using Kotlin, you can use the cli directly. Find all the documentation on the <a href="https://www.apollographql.com/docs/kotlin/testing/mocking-http-responses">docs website</a>.</p>



<p class="wp-block-paragraph">If you have any questions or feedback, please reach out to us on <a href="https://github.com/apollographql/apollo-mock">GitHub</a> or <a href="https://discord.gg/apollographql">Discord</a>.</p>


Apollo Mock: LLM-generated data for your Kotlin applications


<p class="wp-block-paragraph">A few months ago, we announced our<a href="https://www.apollographql.com/blog/apollos-new-api-ip-allowlist-policy"> API IP Allowlist Policy</a>, which included a planned change: adding a second IP address to each covered Apollo Uplink service.</p>



<p class="wp-block-paragraph">That change has now taken effect.</p>



<p class="wp-block-paragraph"><strong>If your organization restricts outbound network access by IP address</strong>, confirm the following IPs are both allowlisted for their corresponding domains:</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Domain</td><td>Current IP</td><td>Additional IP</td></tr><tr><td>uplink.api.apollographql.com</td><td>34.117.186.194</td><td>34.149.219.4</td></tr><tr><td>persisted-queries.api.apollographql.com</td><td>34.36.202.125</td><td>8.233.57.214</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">If the additional IP isn&#8217;t yet in your allowlist, add it now. Without it, your Router or Gateway may be unable to fetch configuration from Uplink – you&#8217;d typically see this as failed schema/config polling in your Router logs.</p>



<p class="wp-block-paragraph"><strong>If you restrict access by domain name, or don&#8217;t restrict outbound access at all</strong>, no action is required.</p>



<p class="wp-block-paragraph"><strong>Not sure how your network is configured?</strong> Check with your network or infrastructure team. If Router is fetching its schema successfully today, domain-based allowlisting is likely already in place and this change doesn&#8217;t affect you.</p>



<p class="wp-block-paragraph"><strong>Stay Informed</strong></p>



<p class="wp-block-paragraph">The<a href="https://www.apollographql.com/trust/api-ip-allowlist-policy"> API IP Allowlist Policy</a> page is the authoritative source for current and upcoming IP changes, including at least 60 days&#8217; notice before any future addition. All future changes will be announced on this blog under Announcements.</p>



<p class="wp-block-paragraph">Questions? Reach out to Apollo Technical Support or email support@apollographql.com.</p>



<p class="wp-block-paragraph"></p>


Apollo API IP Allowlist Update: Second IP Addresses Now Live

What’s New in Apollo Client 4.3


<p class="wp-block-paragraph">Apollo GraphOS and Apollo MCP Server were named winners in the <a href="https://apiworld.co/awards/">2026 API Awards</a>, presented at <a href="https://apiworld.co/">API World 2026</a> this week in Santa Clara, California.</p>



<p class="wp-block-paragraph">Now in its 11th year, the 2026 API Awards program recognizes the technologies, products, and teams advancing innovation across the API landscape. Winners are chosen by the independent DevNetwork API Advisory Board based on technical innovation, industry impact, community adoption, and contribution to advancing API practices. </p>



<p class="wp-block-paragraph">&#8220;APIs have evolved from integration tools into the core infrastructure powering AI-native applications, autonomous agents, and intelligent digital experiences,&#8221; said Jonathan Pasky, Executive Producer &amp; Co-Founder of DevNetwork, producer of API World and the API Awards. &#8220;The 2026 API Award winners are helping define what&#8217;s next for the API ecosystem, and the recognition of both Apollo GraphOS &amp; Apollo MCP Server reflect its meaningful contribution to the industry&#8217;s continued innovation and growth.&#8221;</p>



<h1 class="wp-block-heading"><a href="#apollo-graphos-best-innovation-in-api-orchestration" aria-hidden="true" class="aal_anchor" id="apollo-graphos-best-innovation-in-api-orchestration"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo GraphOS: Best Innovation in API Orchestration</h1>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/graphos">Apollo GraphOS</a>, our unified platform for federating and governing APIs across an organization, was named a winner in the <strong>Best Innovation in API Orchestration</strong> category. This marks GraphOS&#8217;s second consecutive win in the category. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="815" src="https://wp.apollographql.com/wp-content/uploads/2026/09/image-1024x815.png" alt="" class="wp-image-25692" srcset="https://wp.apollographql.com/wp-content/uploads/2026/09/image-1024x815.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/09/image-300x239.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/09/image-768x611.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/09/image.png 1059w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h1 class="wp-block-heading"><a href="#apollo-mcp-server-best-innovation-in-ai-api" aria-hidden="true" class="aal_anchor" id="apollo-mcp-server-best-innovation-in-ai-api"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo MCP Server: Best Innovation in AI API</h1>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/apollo-mcp-server">Apollo MCP Server</a> was named a winner in the same program&#8217;s <strong>Best Innovation in AI API </strong>category. The Apollo MCP Server lets teams expose their existing GraphQL APIs as tools that AI agents can call directly, using the Model Context Protocol – giving agentic systems a safe, governed path to real production data instead of one-off integrations.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="822" src="https://wp.apollographql.com/wp-content/uploads/2026/09/image-1-1024x822.png" alt="" class="wp-image-25694" srcset="https://wp.apollographql.com/wp-content/uploads/2026/09/image-1-1024x822.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/09/image-1-300x241.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/09/image-1-768x616.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/09/image-1.png 1058w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h1 class="wp-block-heading"><a href="#see-it-in-action-at-apollo-summit-2026" aria-hidden="true" class="aal_anchor" id="see-it-in-action-at-apollo-summit-2026"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>See It in Action at Apollo Summit 2026</h1>



<p class="wp-block-paragraph">If you&#8217;re building your API agentic strategy and wondering what’s next, join us at <a href="https://www.ApolloSummit.dev">Apollo Summit 2026</a>, October 6-8 in San Francisco. The full agenda is live now, featuring exciting keynotes, a fireside chat with Angie Jones of the Agentic AI Foundation on where agentic systems are headed, and sessions from leading enterprises like American Airlines, Expedia Group, and Yahoo! on how they&#8217;re shipping agentic AI with Apollo. </p>



<p class="wp-block-paragraph">Apollo Summit is part of SF Tech Week and we are excited to join the world&#8217;s largest decentralized tech gathering, bringing together 100,000+ unique attendees across 3,000+ community-led events in San Francisco.&nbsp; Register for Apollo Summit <a href="https://partiful.com/e/VXloS3Sit59spA76uBao" target="_blank" rel="noreferrer noopener">here</a> and check out a packed calendar of Tech Week events <a href="https://www.tech-week.com/calendar?utm_medium=email&amp;_hsenc=p2ANqtz-9aSHyPtgdgjm1XpAIRPsHIcGFFk1IgrCtvPdeyQ_0U0CYPs8WWOf65GzwGeftbzeavUnHZD0GCF3jXTppIUxMhJjZoo0YYEFgPXJ1CqlX4SKu1IWc&amp;_hsmi=36640310&amp;utm_content=36640310&amp;utm_source=hs_email" target="_blank" rel="noreferrer noopener">here</a> happening October 5-11.</p>


Apollo GraphOS and Apollo MCP Server Named 2026 API Award Winners

Where Apollo MCP Server Stands on the OWASP MCP Top 10


<p class="wp-block-paragraph">Apollo’s annual conference, and the world&#8217;s largest GraphQL event, returns to San Francisco in October. <a href="http://www.apollosummit.dev">Apollo Summit 2026</a> runs October 6 to 8, 2026, at <a href="https://themidwaysf.com/">The Midway</a>, with sessions and workshops on how a well-governed graph turns into the entry point for agents and applications alike.</p>



<figure class="wp-block-image size-large"><a href="https://apollosummit.dev/"><img loading="lazy" decoding="async" width="1024" height="538" src="https://wp.apollographql.com/wp-content/uploads/2026/07/Speaker-Ann-Social-1200x630-1-1024x538.jpg" alt="" class="wp-image-25647" srcset="https://wp.apollographql.com/wp-content/uploads/2026/07/Speaker-Ann-Social-1200x630-1-1024x538.jpg 1024w, https://wp.apollographql.com/wp-content/uploads/2026/07/Speaker-Ann-Social-1200x630-1-300x158.jpg 300w, https://wp.apollographql.com/wp-content/uploads/2026/07/Speaker-Ann-Social-1200x630-1-768x403.jpg 768w, https://wp.apollographql.com/wp-content/uploads/2026/07/Speaker-Ann-Social-1200x630-1.jpg 1200w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>



<p class="wp-block-paragraph">Apollo has always worked on the difficult middle layer between backend systems and the clients that need to access them, from the early Meteor days through GraphQL’s origins as a way to fetch data for web and mobile apps, and now as the layer that connects AI agents to the systems they need to access in order to do real work. If you own a GraphQL implementation, or you are weighing how your API strategy fits into your AI roadmap, this is where the practical patterns get worked out in public.</p>



<h2 class="wp-block-heading"><a href="#meet-the-speakers" aria-hidden="true" class="aal_anchor" id="meet-the-speakers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Meet the Speakers</strong></h2>



<p class="wp-block-paragraph">Your APIs were built for apps. What happens when agents want in? These five speakers have already shipped an answer, and they’ll show their work. Stay tuned for more speakers to be announced soon.</p>



<ul class="wp-block-list">
<li><a href="https://www.linkedin.com/in/jonathanwondrusch/">Jonathan Wondrusch</a>, Staff Software Engineer at Block, argues your company already has a graph, hiding in Confluence pages and a hundred half-documented REST endpoints. He shows how to build an API schema that ships product to customers and becomes the context layer your agents reason against. The surprise is that it makes the business legible to itself.</li>



<li><a href="https://www.linkedin.com/in/clarice-abreu/">Clarice Abreu</a>, Senior Software Engineer at Brex, opened GraphOS and found 35% of their federated graph was dead code. Rather than spend months cleaning 60+ subgraphs by hand, she built an agent that deletes, validates, and opens the PR. It has removed over 100,000 lines, and not one customer noticed.</li>



<li><a href="https://www.linkedin.com/in/gijs-martens/">Gijs Martens</a>, Platform Engineer, and <a href="https://www.linkedin.com/in/bartvanlakwijk/">Bart van Lakwijk</a>, Manager Web Platform at Coolblue, routed all production traffic through their graph in week one. The cutover was the easy part. Winning over a &#8220;just do it&#8221; business meant treating the graph as a utility, not a religion, and never blocking a team. No mandate. The graph sold itself.</li>



<li><a href="https://www.linkedin.com/in/sgorla/">Sharon Gorla</a>, Lead Engineer at Starbucks, has a rule for what survives a rewrite: business semantics and shared contracts, never implementation patterns. As coding agents rebuild whole systems, the gap people miss isn&#8217;t MCP or agent frameworks. It&#8217;s alignment. Clients come and go. Shared nouns and verbs are the durable layer.</li>
</ul>



<h2 class="wp-block-heading"><a href="#why-this-matters-now" aria-hidden="true" class="aal_anchor" id="why-this-matters-now"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Why this matters now</strong></h2>



<p class="wp-block-paragraph">Organizations are often pulled in opposing directions: deploying agents quickly vs. keeping control over what they can do. Teams that move fast often hand agents broad access and lose visibility. Teams that lock things down slow every project to a crawl. Summit 2026 is built around a different premise: speed and control are not a tradeoff when the graph sits between your agents and your systems.</p>



<p class="wp-block-paragraph">A self-describing graph gives agents declared, scoped access to exactly the tools they need and nothing more. It reduces token costs by handing agents the right context for each action, enforces field-level security, and improves success rates by making your existing APIs discoverable. The sessions show how teams are already doing this in production.</p>



<h2 class="wp-block-heading"><a href="#what-youll-learn" aria-hidden="true" class="aal_anchor" id="what-youll-learn"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What you&#8217;ll learn</strong></h2>



<p class="wp-block-paragraph">The agenda is organized around four themes that map to the decisions facing platform and AI teams right now.</p>



<ul class="wp-block-list">
<li><strong>Agent infrastructure.</strong> Design the governed entry point between agents and enterprise systems. Build a context layer that improves task success rates while keeping costs down.</li>



<li><strong>Governance and security.</strong> Manage agent identity, start from zero-rights defaults, enforce field-level access policies, and handle credentials in a single layer. Give both developers and non-developers a trusted platform to build on.</li>



<li><strong>Agentic API access.</strong> Connect REST APIs, SQL data sources, MCP servers, and third-party systems into your context layer, whether or not they already live in your graph.</li>



<li><strong>GraphQL and GraphOS.</strong> For teams running GraphQL in production today: the latest in Apollo Federation, Apollo Router optimization, schema governance, Apollo Connectors, and the Apollo MCP Server.</li>
</ul>



<h2 class="wp-block-heading"><a href="#who-youll-meet" aria-hidden="true" class="aal_anchor" id="who-youll-meet"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Who you&#8217;ll meet</strong></h2>



<p class="wp-block-paragraph">Summit draws platform engineers, AI infrastructure leads, developers, and technical leaders who are building API infrastructure for both applications and agents. It is also where the broader GraphQL community gathers, including the people who maintain the specifications and tools the industry runs on. You will leave with patterns you can apply and a set of peers solving the same problems.</p>



<h2 class="wp-block-heading"><a href="#what-to-expect" aria-hidden="true" class="aal_anchor" id="what-to-expect"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What to expect</strong></h2>



<p class="wp-block-paragraph">The format balances learning and doing. Expect keynotes, customer talks, hands-on technical workshops, and time to meet the experts and ask your questions. You can hear about how some of the fastest-moving companies are building agents, learn architectural patterns to apply in your own API strategy, and try it out in a workshop, all in just a few days.</p>



<p class="wp-block-paragraph">Here is the shape of the conference:</p>



<ul class="wp-block-list">
<li><strong>Tuesday, October 6.</strong> Arrivals, registration, and a welcome reception from 5 to 7pm.</li>



<li><strong>Wednesday, October 7.</strong> Sessions and an evening event, 9am to 9pm.</li>



<li><strong>Thursday, October 8.</strong> Sessions and departures, 9am to 3pm.</li>
</ul>



<h2 class="wp-block-heading"><a href="#pricing-and-registration" aria-hidden="true" class="aal_anchor" id="pricing-and-registration"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Pricing and registration</strong></h2>



<p class="wp-block-paragraph">Registration is now open. Get your Summit pass for $399, including breakfast, lunch, and unlimited coffee and snacks across the event. Dietary preferences selectable at sign-up.</p>



<p class="wp-block-paragraph">October 6 to 8, 2026 at The Midway, San Francisco.</p>



<p class="wp-block-paragraph"><a href="https://apollosummit.dev/">Register now.</a></p>


Apollo Summit 2026: Turn Your API Platform Into Your AI Platform


<p class="wp-block-paragraph">GraphQL is in Gartner’s Trough of Disillusionment in the <a href="https://www.apollographql.com/resources/gartner-hype-cycle-for-apis-2026">2026 Gartner® Hype Cycle™ for APIs</a>. Good.</p>



<p class="wp-block-paragraph">The trough is what happens when expectations set during the hype phase meet the reality of actual production requirements. People stop hyping and start asking the key questions: Does this thing work? Does it solve a problem we actually have? Can we operate it in production without making everyone miserable?</p>



<p class="wp-block-paragraph">Those are the right questions, and any proposed platform tech has to answer them.</p>



<h2 class="wp-block-heading"><a href="#graphql-adoption-vs-graphql-readiness" aria-hidden="true" class="aal_anchor" id="graphql-adoption-vs-graphql-readiness"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL adoption vs. GraphQL “readiness”</h2>



<p class="wp-block-paragraph">With GraphQL in the trough, Gartner notes this observation:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">“Despite the potential, GraphQL adoption for AI and agentic workflows have not translated to increased adoption due to its limited penetration in key agentic use cases.”</p>
</blockquote>



<p class="wp-block-paragraph">That strikes us as basically right. MCP and other agent-oriented protocols arrived with an obvious, legible connection to AI. GraphQL, like other mature technologies, is adapting. Most companies adopted it years earlier to solve the problems of the day: frontend development, service integration, data aggregation, and the general difficulty of getting a large organization’s systems to behave as if they belong to the same company.</p>



<p class="wp-block-paragraph">But we think the sequencing matters. Are agents causing companies to adopt GraphQL? There’s some early signal that they are. But a more immediately interesting question is whether companies that already adopted GraphQL are better prepared to put agents into production. The answer is an unequivocal “yes.” There is another interesting signal in the Gartner report. GraphQL is in the trough, but Gartner forecasts that it will reach the Plateau of Productivity in less than two years.  That’s sooner than MCP, gRPC, and AI Agent Communication Protocols. In our read, that tells us something about maturity. GraphQL is no longer new enough to receive credit for its potential. It has to earn credit for being useful. That is a healthier place for infrastructure technology to be.</p>



<p class="wp-block-paragraph">It helps that GraphQL is not a speculative protocol waiting for its first serious workload. It is a <a href="https://spec.graphql.org/">Linux Foundation-backed open standard</a> that has been used at enterprise scale for years. This matters when you are choosing infrastructure that could outlive several executive teams, architecture strategies, and AI hype cycles. Proprietary protocols can disappear when their owner’s priorities change. Open standards have a chance to compound.</p>



<p class="wp-block-paragraph">In our view, Gartner’s own description of GraphQL makes this case more plainly. The report describes its capacity to serve as:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">“A unified enterprise data model, decoupled from the underlying service implementations. This shared schema fosters a common understanding of business data across teams, streamlines integration efforts, and accelerates the delivery of new features and digital products. As GraphQL adoption grows, it also supports advanced use cases, such as enterprisewide orchestration and AI integration, further amplifying its business value.”</p>
</blockquote>



<p class="wp-block-paragraph">You could remove “AI integration” from that paragraph and it would still describe why many organizations adopted GraphQL in the first place. Put it back in, though, and the connection becomes pretty obvious. Agents need to find data, understand how it relates, retrieve what they are allowed to retrieve, and take actions across systems. A governed graph does not solve the entire agent problem—nothing does—but it gives agents a coherent surface over systems that were not designed with agents in mind.</p>



<h2 class="wp-block-heading"><a href="#what-built-the-graph-first-looks-like-in-production" aria-hidden="true" class="aal_anchor" id="what-built-the-graph-first-looks-like-in-production"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What &#8220;built the graph first&#8221; looks like in production</h2>



<p class="wp-block-paragraph">American Airlines is a useful example because its story does not begin with an LLM, but it ends with one.</p>



<p class="wp-block-paragraph">Its core system of record is SABRE, which dates to the 1960s. Years before every software roadmap acquired an “agentic” section, the company built a federated graph spanning customer, loyalty, reservations, and check-in experiences across web, mobile, and kiosks. When its CEO later asked the organization to put AI agents into production on a 90-day delivery cycle, the company did not also have to invent a context layer from scratch. It had already done the foundational architecture work.</p>



<p class="wp-block-paragraph">As Senior Principal Architect Pragadeesh Prakasam recently explained at the <a href="https://www.apollographql.com/events/the-api-layer-is-the-agent-layer-whats-standing-between-your-ai-agents-and-produc">2026 AI Agent Conference</a>, the team placed <a href="https://www.apollographql.com/apollo-mcp-server">Apollo’s MCP Server</a> on top of the graph it already operated. <a href="https://www.apollographql.com/docs/graphos/platform/security/persisted-queries">Persisted queries</a> became the agents’ tool surface. Existing field-level security scopes applied to agent interactions. Authentication, governance, and observability were not exciting new items on an AI infrastructure backlog; they were capabilities the company already had.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">“We could just focus on the experience,” Prakasam said. “Not on rebuilding the plumbing.”</p>
</blockquote>



<p class="wp-block-paragraph">This is the part we think gets lost when people compare adoption curves. GraphQL did not need to arrive wearing an AI costume to be useful for AI. American Airlines built a graph to solve one generation of software problems and discovered that the same investment helped with the next one. <a href="http://booking.com">Booking.com</a>, <a href="https://www.apollographql.com/customers/how-indeed-built-an-ai-hiring-assistant-in-9-months-with-apollo">Indeed</a>, and <a href="https://www.apollographql.com/newsroom/press-releases/apollo-expands-platform-to-power-the-agentic-future-at-graphql-summit-2025">Yahoo!</a> have followed a similar pattern: build a mature, governed graph, then give agents access to that foundation.</p>



<p class="wp-block-paragraph">So yes, Gartner is right that GraphQL has not spread through agent use cases with the speed or visibility of MCP. But that is a claim about adoption speed, not about value. GraphQL can still be valuable infrastructure for agents even if agents are not yet driving much new adoption of it. In practice, some of the companies best positioned to ship agents today are the ones that built the graph first. We do not think that is a coincidence.</p>



<h2 class="wp-block-heading"><a href="#where-ai-gateways-fit-and-where-they-fall-short" aria-hidden="true" class="aal_anchor" id="where-ai-gateways-fit-and-where-they-fall-short"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Where AI gateways fit and where they fall short</h2>



<p class="wp-block-paragraph">The report’s treatment of AI gateways makes the connection even more interesting. Gartner defines an AI gateway as:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">“A tool that acts as an intermediary between applications and various artificial intelligence services or models. Its purpose is to simplify and manage connectivity between AI applications, agents, LLMs and enterprise applications by providing a central point to enable security, governance and observability of AI workloads.”</p>
</blockquote>



<p class="wp-block-paragraph">Most AI gateways today focus on traffic management: model routing, rate limits, token controls, and defenses against attacks such as prompt injection. We at Apollo believe that all of that is necessary. It is also insufficient.</p>



<p class="wp-block-paragraph">A gateway can control where a request goes without understanding what the underlying data means. It can know that an agent is allowed to call an API without knowing whether the agent should see a particular customer field returned by that API. Without a semantic model underneath it, an AI gateway risks becoming a very sophisticated traffic cop. That’s useful, but lacking the semantics to answer many of the authorization and governance questions that make managing enterprise agents difficult.</p>



<p class="wp-block-paragraph">Our bet is that the category will move toward combining both layers: gateway controls for AI traffic and a governed model of enterprise data and capabilities. Agents need routing and rate limits, but they also need context. They need to know what systems contain, how concepts relate, what actions are available, and what a particular user or agent is authorized to see.</p>



<p class="wp-block-paragraph">In our view, Apollo GraphOS can play that role when it is implemented as a <a href="https://www.apollographql.com/context-graph">context layer</a> for agents. It provides a centralized way to control, observe, and govern what agents do across tools and APIs, using the same federated graph that companies such as American Airlines, Indeed, and Yahoo! already operate in production. The field-level access controls, authentication, and governance are not decorations added after the agent demo gets executive attention. They are part of the graph. The ceiling is much higher with these capabilities in hand.</p>



<p class="wp-block-paragraph">MCP and GraphQL solve different and complementary problems, and American Airlines’ architecture is interesting precisely because it uses both. The hard part of enterprise agents is providing the model useful context while preserving the security, governance, and observability the organization already requires. Companies with a mature graph have a head start because they have already spent years doing that work.</p>



<p class="wp-block-paragraph">Call it the trough if you want. We call it a head start.</p>



<p class="wp-block-paragraph">If you are sorting through what GraphQL, MCP, AI gateways, and the growing pile of agent protocols mean for your architecture, Apollo is offering a complimentary copy of the full <a href="https://www.apollographql.com/resources/gartner-hype-cycle-for-apis-2026">2026 Gartner Hype Cycle for APIs</a> research. If you want to talk through how GraphQL fits into your API strategy, <a href="https://www.apollographql.com/contact-sales">get in touch.</a></p>



<p class="wp-block-paragraph"><em>Gartner, Hype Cycle for APIs, 2026, By Shameen Pillai, Mark O&#8217;Neill, 22 May 2026.&nbsp;</em></p>



<p class="wp-block-paragraph"><em>Gartner and Hype Cycle are trademarks of Gartner, Inc. and/or its affiliates.&nbsp;</em></p>



<p class="wp-block-paragraph"><em>Gartner does not endorse any company, vendor, product or service depicted in its publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner publications consist of the opinions of Gartner’s business and technology insights organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this publication, including any warranties of merchantability or fitness for a particular purpose.</em></p>


What We Think the 2026 Gartner Hype Cycle Gets Right About GraphQL


<p class="wp-block-paragraph">When we <a href="https://www.apollographql.com/blog/introducing-graph-artifacts">launched Graph Artifacts</a>, we gave teams a way to pin their <a href="https://www.apollographql.com/graphos-router">GraphOS Router</a> to a specific, immutable supergraph schema version using SHA digests. Graph artifacts are stored using OCI-compliant registries, and tagging is a native concept at that layer. A tag is just a mutable pointer to an immutable digest. In principle, nothing stopped a team from tagging an artifact prod and having their router resolve it.</p>



<p class="wp-block-paragraph">In practice, almost no one could do that through the GraphOS tools they actually used day to day. <a href="https://www.apollographql.com/docs/rover">Rover</a> had no way to assign one, list one, or fetch an artifact by one. And <a href="https://www.apollographql.com/graphos/studio">Studio&#8217;s</a> Launches page didn&#8217;t show which artifact a tag pointed to, or that tags existed at all. To see that, you had to call the <a href="https://www.apollographql.com/docs/graphos/platform/platform-api">Platform API</a> directly, dropping out of Rover and Studio entirely. That forced teams to write custom scripts against the OCI API to get tag-like behavior back. Graph artifacts were meant to streamline promotion and rollback, but in practice the workflow still requires the same manual steps it did before artifacts existed.</p>



<p class="wp-block-paragraph">This release closes that gap. It spans three parts of the platform: </p>



<ul class="wp-block-list">
<li><strong>Managing tags from Rover.</strong> Native CLI commands to assign, list, fetch, and delete tags, so promotion and rollback become one-line operations instead of maintaining in-house scripts that manage deployment.</li>



<li><strong>Discovering tags in Studio.</strong> The Launches page now surfaces tags alongside artifact digests, so you can answer &#8220;what&#8217;s tagged prod right now?&#8221; without leaving the browser.</li>



<li><strong>Standing on OCI standards.</strong> Tags are backed by OCI-compliant registry APIs under the hood, so tools like oras and any other OCI-aware client work with them the way they&#8217;d expect from any container registry.</li>
</ul>



<h3 class="wp-block-heading"><a href="#how-tags-behave-in-graphos" aria-hidden="true" class="aal_anchor" id="how-tags-behave-in-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>How tags behave in GraphOS</strong></h3>



<p class="wp-block-paragraph">A couple of things are specific to how GraphOS and the GraphOS Router work with tags, worth knowing before you start using them:</p>



<ul class="wp-block-list">
<li><strong>Apollo-managed vs. user-managed.</strong> Apollo-managed tags (such as variant auto-tags) are system-generated to track the latest publish for a variant and are immutable. User-managed tags are yours to assign, move, or delete as your promotion workflow dictates.</li>



<li><strong>Hot-reload depends on your router version.</strong> On Router v2.11.0+, a tag reassignment hot-reloads automatically. On earlier versions, the router still needs a restart to pick up the change.</li>
</ul>



<h2 class="wp-block-heading"><a href="#managing-tags-in-rover" aria-hidden="true" class="aal_anchor" id="managing-tags-in-rover"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Managing tags in Rover</h2>



<p class="wp-block-paragraph">Rover 0.41 ships with a full set of <code class="" data-line="">rover graph-artifact tag</code> commands, so tags can be managed entirely from the CLI or from CI/CD.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">rover graph-artifact tag --graph-id my-graph --digest &#039;sha256:01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b&#039; prod</code></pre>



<p class="wp-block-paragraph"><strong>List tags</strong> for a variant at a glance:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">rover graph-artifact list-tags --graph-id my-graph

TAG         DIGEST                                       CREATED
prod        sha256:6c3c624b58cd32b4c53f041e94d...        2026-07-10T14:30:00Z
canary      sha256:a1b2c3d4e5f678901234567890ab...       2026-07-09T09:15:00Z
v1.2.3      sha256:6c3c624b58cd32b4c53f041e94d...        2026-07-08T11:00:00Z</code></pre>



<p class="wp-block-paragraph"><strong>Inspect a tag</strong> and the artifact it points to:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">rover graph-artifact fetch --graph-id my-graph --tag-name prod</code></pre>



<p class="wp-block-paragraph"><strong>Delete a tag</strong> when it&#8217;s no longer needed (the underlying artifact is unaffected):</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">rover graph-artifact untag --graph-id my-graph canary</code></pre>



<p class="wp-block-paragraph">These slot naturally into a promotion pipeline:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line=""># 1. After checks pass, tag the artifact as canary
- run: rover graph-artifact tag --graph-id my-graph --digest $ARTIFACT_DIGEST canary

# 2. After canary validation passes, promote to production
- run: rover graph-artifact tag --graph-id my-graph --digest $ARTIFACT_DIGEST prod

# 3. Clean up the canary tag
- run: rover graph-artifact untag --graph-id my-graph canary</code></pre>



<p class="wp-block-paragraph"><strong>Verify your change:</strong> Run <code class="" data-line="">rover graph-artifact fetch --graph-id my-graph --tag-name</code> prod to confirm the tag is pointing to the correct digest.</p>



<h2 class="wp-block-heading"><a href="#discovering-tags-in-studio" aria-hidden="true" class="aal_anchor" id="discovering-tags-in-studio"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Discovering tags in Studio</h2>



<p class="wp-block-paragraph">In Studio, the Launches page now surfaces tag information right alongside each artifact&#8217;s digest, so when you&#8217;re looking at a specific launch, you can see at a glance which tags point to that build. No terminal required.</p>



<p class="wp-block-paragraph">We&#8217;ve also made it easier to act on what you find: graph admins can generate the exact Rover command, complete with <code class="" data-line="">--graph-id</code> and <code class="" data-line="">--digest</code> , to tag or untag an artifact, ready to copy into your terminal and run. If you need more context, you can find a link to the Rover graph artifact docs as well. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="584" src="https://wp.apollographql.com/wp-content/uploads/2026/07/image-1024x584.png" alt="" class="wp-image-25611" srcset="https://wp.apollographql.com/wp-content/uploads/2026/07/image-1024x584.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-300x171.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-768x438.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1536x875.png 1536w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1200x684.png 1200w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1980x1128.png 1980w, https://wp.apollographql.com/wp-content/uploads/2026/07/image.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="607" src="https://wp.apollographql.com/wp-content/uploads/2026/07/image-1-1024x607.png" alt="" class="wp-image-25614" srcset="https://wp.apollographql.com/wp-content/uploads/2026/07/image-1-1024x607.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1-300x178.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1-768x455.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1-1536x910.png 1536w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1-1200x711.png 1200w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1-1980x1173.png 1980w, https://wp.apollographql.com/wp-content/uploads/2026/07/image-1.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#built-on-oci-standards" aria-hidden="true" class="aal_anchor" id="built-on-oci-standards"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Built on OCI standards</h2>



<p class="wp-block-paragraph">Under the hood, graph artifact tags are backed by OCI-compliant registry APIs. That means tools like <code class="" data-line="">oras</code> and other OCI-compatible clients can interact with tags through standard endpoints: listing tags, pulling by tag, and pushing with a tag all work the way you&#8217;d expect from any container registry.</p>



<p class="wp-block-paragraph">For Enterprise customers who mirror artifacts to a private OCI registry, tags are preserved during the copy, so the experience stays consistent across GraphOS and your own infrastructure.</p>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<ol class="wp-block-list">
<li><strong>Update Rover</strong> to version 0.41 or later.</li>



<li><strong>Assign your first tag.</strong> After your next subgraph publish, find the artifact digest on the Launches page in Studio or via <code class="" data-line="">rover graph-artifact list</code>, then run:</li>
</ol>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">rover graph-artifact tag --graph-id my-graph --digest &lt;sha&gt; prod</code></pre>



<p class="wp-block-paragraph"><strong>Update your router config</strong> to reference the tag instead of the digest: </p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">APOLLO_GRAPH_ARTIFACT_REFERENCE=&quot;artifacts.api.apollographql.com/my-graph:prod&quot;</code></pre>



<p class="wp-block-paragraph"><strong>Wire it into CI/CD.</strong> Use <code class="" data-line="">rover graph-artifact tag</code> in your pipeline to automate promotion.</p>



<h2 class="wp-block-heading"><a href="#what-this-adds-up-to" aria-hidden="true" class="aal_anchor" id="what-this-adds-up-to"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What this adds up to </h2>



<p class="wp-block-paragraph">Graph artifacts already gave teams a deterministic, tamper-proof way to deploy schema changes. Now Rover and Studio catch up. Rover has a CLI surface for tags that matches what the registry already supported underneath, so promotion and rollback don&#8217;t require a workaround anymore. And Studio&#8217;s Launches page finally shows which artifact a tag points to, so that information doesn&#8217;t require going around GraphOS to find.</p>



<p class="wp-block-paragraph">Graph artifact tags are available now for all GraphOS customers. Update to Rover 0.41 and start tagging.&nbsp;</p>



<p class="wp-block-paragraph">For the full reference, see the <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/graph-artifacts">Graph Artifacts documentation</a> and the <a href="https://www.apollographql.com/docs/rover/commands/graph-artifact">Rover artifact CLI (v0.41.0) docs</a>.</p>



<p class="wp-block-paragraph"><em>Note: Wendy Peralta and Ana De Magalhães also contributed to this blog post.</em></p>


What’s new in Graph Artifacts


<p class="wp-block-paragraph">Answering &#8220;is my graph healthy?&#8221; used to mean a tour across half a dozen <a href="https://www.apollographql.com/graphos/studio">Studio</a> pages: launch history, composition errors, lint reports, router status, operation latency, and error rates.</p>



<p class="wp-block-paragraph">Today we&#8217;re launching&nbsp;<strong>GraphOS MCP Server</strong>, Apollo&#8217;s hosted MCP server that connects your AI agent directly to GraphOS. Point it at your graph and your agent can read launches, schema checks, router configuration, and traffic metrics. Each tool answers one focused question, and an agent can combine them to answer bigger ones like:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">Is my graph healthy? Run the relevant checks and summarize findings as Attention Required, Review Recommended, or What&#8217;s Working Well.</p>
</blockquote>



<h2 class="wp-block-heading"><a href="#one-endpoint-zero-infrastructure" aria-hidden="true" class="aal_anchor" id="one-endpoint-zero-infrastructure"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>One endpoint, zero infrastructure</h2>



<p class="wp-block-paragraph">GraphOS MCP Server lives at https://mcp.apollographql.com. There is nothing to install, deploy, or upgrade. If your client speaks MCP over Streamable HTTP, you&#8217;re two minutes from a working setup.</p>



<p class="wp-block-paragraph">It&#8217;s a built-in connector in Claude and Claude Desktop. For Claude Code, it&#8217;s one command:</p>



<pre class="wp-block-code"><code class="" data-line="">claude mcp add graphos https://mcp.apollographql.com \
--transport http --header &#039;x-api-key: YOUR_GRAPH_API_KEY&#039;</code></pre>



<p class="wp-block-paragraph">Cursor, VS Code, Codex CLI, Gemini CLI, and GitHub Copilot are covered too. The <a href="https://www.apollographql.com/docs/graphos/platform/graphos-mcp-server/install">installation guide</a> has the exact configuration for each.</p>



<p class="wp-block-paragraph">If you&#8217;ve used this as GraphOS MCP Tools before for docs search or the Connectors spec, that&#8217;s the same endpoint under a new name, GraphOS MCP Server, now with graph-aware tools too. The documentation and Connectors tools still need no key. What&#8217;s new is the graph-aware tools below, which run once you bring a graph API key.</p>



<h2 class="wp-block-heading"><a href="#meet-the-graph-aware-tools" aria-hidden="true" class="aal_anchor" id="meet-the-graph-aware-tools"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Meet the graph-aware tools</h2>



<p class="wp-block-paragraph">With a graph API key in the <code class="" data-line="">x-api-key</code> header, your agent gets a set of tools that map to the questions you&#8217;d actually ask about a production graph:</p>



<p class="wp-block-paragraph"><strong>What is my graph?</strong> The<em> GetMyIdentity</em> tool resolves the caller&#8217;s identity from the API key, so the agent can discover your graph and its variants without you spelling out IDs.</p>



<p class="wp-block-paragraph"><strong>What is this variant running?</strong><em> The GetVariantDetails</em> tool returns the federation version, subgraph inventory, router status, and router configuration in one call.</p>



<p class="wp-block-paragraph"><strong>Are deployments stable?</strong> The <em>GetLatestLaunch</em>,<em> GetLaunch</em>, and <em>GetLaunchHistory</em> tools expose launch status, composition errors, and schema diff summaries, so the agent can spot repeated failures or a suspicious streak of superseded launches.</p>



<p class="wp-block-paragraph"><strong>Is traffic healthy?</strong> The <em>GetTopOperations</em>, <em>GetOperationMetrics</em>, and <em>GetSubgraphMetrics</em> tools surface request counts, p50/p99 latencies, and error counts as daily buckets, ranked by whichever metric matters: busiest, slowest, or most error-prone.</p>



<p class="wp-block-paragraph"><strong>Is quality slipping?</strong> The <em>GetLintResults</em> tool pulls schema lint violations from recent checks, and the <em>GetPersistedQueryListStatus</em> tool tells you whether a variant has a PQL configured. A production variant without one may be a security gap worth flagging.</p>



<p class="wp-block-paragraph">Each tool is useful on its own. The real payoff is chaining: the agent resolves your graph from the key, pulls the latest launch, checks lint results, cross-references top operations against their latency and error metrics, and assembles the picture a human would have built from six browser tabs.</p>



<h2 class="wp-block-heading"><a href="#mix-and-match" aria-hidden="true" class="aal_anchor" id="mix-and-match"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Mix and match</h2>



<p class="wp-block-paragraph">The tools are useful one at a time, and they&#8217;re more useful together. Because each returns focused, structured data, an agent can feed the result of one into the next and answer questions no single tool covers:</p>



<ul class="wp-block-list">
<li><strong>Cross-reference traffic with health.</strong>&nbsp;Pull the busiest operations, then their latency and error metrics, and flag any high-traffic operation that&#8217;s also slow or failing.</li>



<li><strong>Investigate a bad deploy.</strong>&nbsp;Start from the latest launch, spot a composition error, then walk the launch history to see whether it&#8217;s a one-off or a pattern.</li>



<li><strong>Run a full health check.</strong>&nbsp;Combine variant details, launches, lint, and metrics into one prioritized report, the &#8220;is my graph healthy?&#8221; prompt from the top of this post.</li>
</ul>



<p class="wp-block-paragraph">You stay in control of the depth. Ask a narrow question and the agent calls a single tool; ask a broad one and it composes as many as it needs.</p>



<h2 class="wp-block-heading"><a href="#built-for-agent-context-not-for-dashboards" aria-hidden="true" class="aal_anchor" id="built-for-agent-context-not-for-dashboards"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Built for agent context, not for dashboards</h2>



<p class="wp-block-paragraph">Raw platform data is designed for dashboards, not context windows. A month of per-operation timeseries data as JSON runs to hundreds of kilobytes. Feed that to an agent and you&#8217;ve burned the context budget before the analysis starts.</p>



<p class="wp-block-paragraph">So the metrics tools return compact, ranked CSV instead: top operations or subgraphs, ordered by the metric you care about, one row per day. The same month of data lands in about a kilobyte. The agent spends its context on reasoning about the numbers rather than parsing them.</p>



<p class="wp-block-paragraph">This is the same philosophy behind <a href="https://www.apollographql.com/blog/apollo-mcp-server/smart-schema-discovery-how-apollo-mcp-server-maximizes-ai-context-efficiency">smart schema discovery</a> in Apollo MCP Server: give the agent exactly what it needs in the smallest faithful form, and it gets more done with fewer tokens.</p>



<h2 class="wp-block-heading"><a href="#scoped-by-your-key-by-design" aria-hidden="true" class="aal_anchor" id="scoped-by-your-key-by-design"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Scoped by your key, by design</h2>



<p class="wp-block-paragraph">The security model is deliberately boring. Your API key travels with each request and is forwarded to the GraphOS Platform API, so every tool call is evaluated against what that key is allowed to see. The server adds no ambient permissions on top.</p>



<p class="wp-block-paragraph">The graph tools accept graph API keys, not personal keys, and we recommend a least-privilege key: an <strong>Observer</strong>-role key can run every health check above. Your agent gets read-only eyes on the graph and nothing else.</p>



<h2 class="wp-block-heading"><a href="#try-it-on-your-own-graph" aria-hidden="true" class="aal_anchor" id="try-it-on-your-own-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try it on your own graph</h2>



<p class="wp-block-paragraph">Connect with your client of choice, then start with something small:</p>



<ul class="wp-block-list">
<li>&#8220;Show the federation version, subgraphs, and router status for my production variant.&#8221;</li>
</ul>



<ul class="wp-block-list">
<li>&#8220;Have the recent launches on my graph been stable, or were there repeated failures?&#8221;</li>
</ul>



<ul class="wp-block-list">
<li>&#8220;Which of my subgraphs have the highest error rates this month?&#8221;</li>
</ul>



<p class="wp-block-paragraph">Then ask the big one:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">Scan my graph for issues across schema composition, lint, router version and config, and deployment stability, and prioritize what needs attention.</p>
</blockquote>



<figure class="wp-block-video"><video height="1080" style="aspect-ratio: 1920 / 1080;" width="1920" controls src="https://wp.apollographql.com/wp-content/uploads/2026/07/graphos-mcp-server-3-2.mp4"></video></figure>



<p class="wp-block-paragraph">GraphOS MCP Server is available now at <a href="https://mcp.apollographql.com">https://mcp.apollographql.com</a>. The&nbsp;<a href="https://www.apollographql.com/docs/graphos/platform/graphos-mcp-server/tools">tool reference</a>&nbsp;documents every tool your agent can call, with arguments and example prompts. If you have feedback, ideas, or a check you wish your agent could run, tell us in the&nbsp;<a href="https://community.apollographql.com/">Apollo Community Forum</a>. This launch is the first batch of graph-aware tools, and what we build next depends on what you ask your agents to do.</p>


Graph Health Checks, Now a Prompt Away


<p class="wp-block-paragraph">Rover is Apollo&#8217;s CLI for managing GraphQL schemas, running checks, and working with the GraphOS registry. It is the primary tool most teams use to integrate graph operations into their development workflows and CI/CD pipelines.</p>



<p class="wp-block-paragraph">This quarter we shipped a set of improvements that have been on the roadmap for a while. Some close long-standing gaps in Rover&#8217;s CI/CD story. One completes the feature parity work that has blocked teams from fully migrating off the deprecated Apollo CLI. And two new commands expand what Rover can do for teams building AI agents on their graphs.</p>



<p class="wp-block-paragraph">Here is what shipped.</p>



<h2 class="wp-block-heading"><a href="#official-docker-image" aria-hidden="true" class="aal_anchor" id="official-docker-image"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Official Docker image</strong></h2>



<p class="wp-block-paragraph">Starting with Rover v0.39.1, Apollo publishes an official Docker image with every release. If you are still installing Rover via curl script or maintaining your own container build in CI, we recommend switching to the official image. Each version tag is immutable, so you can pin to a specific version with a guarantee that the artifact will not change.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">docker pull ghcr.io/apollographql/rover:0.40.0
docker run ghcr.io/apollographql/rover:0.40.0 subgraph check my-graph@prod \
  --name products \
  --schema ./schema.graphql</code></pre>



<p class="wp-block-paragraph">The image is available on GitHub Container Registry (<code class="" data-line="">ghcr.io/apollographql/rover</code>). All CI platforms that support running steps inside a container image (CircleCI, Bitbucket Pipelines, GitLab CI/CD, Jenkins with a Docker agent) can reference it directly.</p>



<h2 class="wp-block-heading"><a href="#atomic-check-and-publish-with-check" aria-hidden="true" class="aal_anchor" id="atomic-check-and-publish-with-check"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Atomic check and publish with <code class="" data-line="">--check</code></strong></h2>



<p class="wp-block-paragraph">Rover has always supported running schema checks and publishing schemas as separate commands. Most teams who wanted a safety gate in their pipeline had to wire those steps together manually: run the check, inspect the exit code, conditionally run the publish, handle failures.</p>



<p class="wp-block-paragraph">A <code class="" data-line="">--check</code> flag on <code class="" data-line="">rover graph publish</code> collapses that into one step. Pass it and Rover runs all configured checks against the registry first. If checks pass, the publish proceeds. If checks fail, the publish is aborted and the command exits non-zero.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">rover graph publish my-graph@production \
  --schema schema.graphql \
  --check</code></pre>



<h2 class="wp-block-heading"><a href="#rover-client-extract-and-rover-client-check-native-client-operation-checks" aria-hidden="true" class="aal_anchor" id="rover-client-extract-and-rover-client-check-native-client-operation-checks"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong><code class="" data-line="">rover client extract</code> and <code class="" data-line="">rover client check</code>: native client operation checks</strong></h2>



<p class="wp-block-paragraph">This is the update that completes the Apollo CLI migration story.</p>



<p class="wp-block-paragraph">The Apollo CLI has been deprecated for some time, but one workflow kept teams on it: <code class="" data-line="">apollo client:check</code>. That command validates GraphQL operation files against the GraphOS registry to catch breaking changes before they reach production. Rover&#8217;s client commands now cover that workflow.</p>



<p class="wp-block-paragraph"><code class="" data-line="">rover client extract</code> scans your source files for embedded GraphQL documents (it detects <code class="" data-line="">gql</code> and <code class="" data-line="">graphql</code> tagged templates in TypeScript, and triple-quoted strings in Swift and Kotlin) and writes each one to a standalone <code class="" data-line="">.graphql</code> file. <code class="" data-line="">rover client check</code> then validates those files against your graph&#8217;s published schema in GraphOS.</p>



<p class="wp-block-paragraph">Run them in sequence:&nbsp;</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">rover client extract --out-dir graphql 
rover client check my-graph@staging --include &quot;graphql/**/*.graphql&quot;</code></pre>



<p class="wp-block-paragraph"><code class="" data-line="">client check</code> supports <code class="" data-line="">--include</code> and <code class="" data-line="">--exclude</code> patterns, so you can point it at exactly the extracted output you want validated, and it reports any operation that references a field that&#8217;s been removed or renamed before that change reaches production. If you have been holding onto the Apollo CLI for <code class="" data-line="">apollo client:check,</code> this is your migration path.</p>



<h2 class="wp-block-heading"><a href="#rover-schema-describe-and-rover-schema-search-schema-intelligence-for-agents" aria-hidden="true" class="aal_anchor" id="rover-schema-describe-and-rover-schema-search-schema-intelligence-for-agents"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong><code class="" data-line="">rover schema describe</code> and <code class="" data-line="">rover schema search</code>: schema intelligence for agents</strong></h2>



<p class="wp-block-paragraph">These two commands are different in character from the others. They are not about CI/CD. They are about making the schema queryable by agents and developers from the command line, with no additional infrastructure.</p>



<p class="wp-block-paragraph">As teams start building AI agents on top of their graphs, a practical problem has emerged. The schema is in the registry, but there was no CLI-native way to explore it. Agents working on graph-related tasks had to either parse raw SDL or depend on a running MCP server to access schema intelligence.</p>



<p class="wp-block-paragraph"><code class="" data-line="">rover schema describe</code> solves exploration. You give it a schema coordinate and get back everything you need to understand that part of the schema: the type or field definition, paths from query and mutation roots, and the context needed to write a query against it.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line=""># Schema overview
rover schema describe schema.graphql

# A specific type
rover schema describe schema.graphql:Order

# A specific field, with paths from query roots
rover schema describe schema.graphql:Order.status</code></pre>



<p class="wp-block-paragraph"><code class="" data-line="">rover schema search</code> solves discovery. You give it a keyword and it returns complete root-to-field paths for every match, including all the intermediate types needed to write a query.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line=""># Search a local schema file
rover schema search schema.graphql &quot;payment status&quot;

# Search against a registry graph by piping
rover graph fetch my-graph@current | rover schema search - &quot;payment status&quot;</code></pre>



<p class="wp-block-paragraph">The output of both commands is designed to pipe cleanly. When used in an automated workflow, the results give an agent enough context to go from a vague user request to an executable GraphQL query without human guidance and without a running MCP server. Fetch the schema, search for the concept, describe the field, write the query.</p>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What&#8217;s next</strong></h2>



<p class="wp-block-paragraph">These updates reflect where Rover is headed: more reliable in production pipelines and more useful beyond schema management for the agentic workflows teams are building.</p>



<p class="wp-block-paragraph">A few things to do now:</p>



<ul class="wp-block-list">
<li>Switch your CI/CD pipelines to the <a href="https://www.apollographql.com/docs/rover/getting-started">official Docker image</a> if you are still using a curl install or a custom container.</li>



<li>Add <code class="" data-line="">--check</code> to your <code class="" data-line="">rover graph publish</code> commands to get atomic check-and-publish in a single step.</li>



<li>If you are still running <code class="" data-line="">apollo client:check</code>, test <code class="" data-line="">rover client extract</code> and <code class="" data-line="">rover client check</code> against your operation files and start planning the migration.</li>



<li>If you are building agents on your graph, try <code class="" data-line="">rover schema describe</code> and <code class="" data-line="">rover schema search</code> and share feedback in the <a href="https://community.apollographql.com/">Apollo Community</a>.</li>
</ul>



<p class="wp-block-paragraph">The full changelog is available in the <a href="https://github.com/apollographql/rover/releases">Rover release notes</a>.</p>


What’s New in Rover: Docker Image, Schema Search, Client Checks, and More


<p class="wp-block-paragraph">If you run <a href="https://www.apollographql.com/graphos-router">GraphOS Router</a> or Apollo Gateway behind a corporate proxy or firewall, you may need to configure outbound network access to <a href="https://www.apollographql.com/trust/graphos-data-privacy-and-compliance">Apollo’s domain names</a> such as uplink.api.apollographql.com, which Router uses to fetch its schema and configuration from GraphOS. Apollo recommends configuring your network access rules based on domain name. However, some network environments require IP-based rules and, for those deployments, you need advance notice when IP addresses change.</p>



<h1 class="wp-block-heading"><a href="#introducing-the-apollo-api-ip-allowlist-policy" aria-hidden="true" class="aal_anchor" id="introducing-the-apollo-api-ip-allowlist-policy"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Introducing the Apollo API IP Allowlist Policy</h1>



<p class="wp-block-paragraph">Apollo has published an <a href="http://apollographql.com/trust/api-ip-allowlist-policy">API IP Allowlist Policy</a>, available now in our Trust Center. The policy documents:</p>



<ul class="wp-block-list">
<li><strong>Which services are covered,</strong> starting with the GCP endpoints for Apollo Uplink (uplink.api.apollographql.com and persisted-queries.api.apollographql.com).</li>



<li><strong>What IP addresses those services currently resolve to, </strong>so you have a single authoritative source of truth.</li>



<li><strong>How changes will be communicated,</strong> with at least 60 calendar days&#8217; advance notice before any new IP is added, announced here on the Apollo blog in the Announcements category. See the <a href="http://apollographql.com/trust/api-ip-allowlist-policy">policy</a> for full details.</li>
</ul>



<p class="wp-block-paragraph">This post is itself the first announcement under that policy.</p>



<h1 class="wp-block-heading"><a href="#whats-changing-a-second-ip-per-service-effective-no-earlier-than-september-16-2026" aria-hidden="true" class="aal_anchor" id="whats-changing-a-second-ip-per-service-effective-no-earlier-than-september-16-2026"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What&#8217;s changing: a second IP per service, effective no earlier than September 16, 2026</h1>



<p class="wp-block-paragraph">Along with the policy, we&#8217;re announcing our first planned change: we will be adding a second IP address to each covered service, effective no earlier than September 16, 2026.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Domain</td><td>Current IP</td><td>Additional IP</td></tr><tr><td>uplink.api.apollographql.com</td><td>34.117.186.194</td><td>34.149.219.4</td></tr><tr><td>persisted-queries.api.apollographql.com</td><td>34.36.202.125</td><td>8.233.57.214</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">If you already have configured your network policy to allow your GraphOS Router (or Apollo Gateway) to access the current IP addresses, you should add the second IP address as well before September 16th; otherwise, your installation may be unable to fetch its configuration from Apollo’s Uplink servers after that date.</p>



<p class="wp-block-paragraph">The reason for maintaining two IPs per service is operational: it gives Apollo the infrastructure flexibility to make future changes with minimal disruption, which means fewer situations requiring customer action down the road.</p>



<h1 class="wp-block-heading"><a href="#what-you-need-to-do" aria-hidden="true" class="aal_anchor" id="what-you-need-to-do"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What you need to do</h1>



<h2 class="wp-block-heading"><a href="#if-you-restrict-outbound-network-access-by-ip-address" aria-hidden="true" class="aal_anchor" id="if-you-restrict-outbound-network-access-by-ip-address"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>If you restrict outbound network access by IP address:</strong></h2>



<p class="wp-block-paragraph">Before September 16, 2026, add the additional IP addresses listed above to your allowlist for the corresponding domains. If you need help or have questions about your specific setup, contact Apollo Technical Support.</p>



<h2 class="wp-block-heading"><a href="#if-you-restrict-outbound-access-by-domain-name-or-dont-restrict-it-at-all" aria-hidden="true" class="aal_anchor" id="if-you-restrict-outbound-access-by-domain-name-or-dont-restrict-it-at-all"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>If you restrict outbound access by domain name, or don&#8217;t restrict it at all:</strong></h2>



<p class="wp-block-paragraph">No action required. This change does not affect you.</p>



<h2 class="wp-block-heading"><a href="#if-youre-not-sure-how-your-network-is-configured" aria-hidden="true" class="aal_anchor" id="if-youre-not-sure-how-your-network-is-configured"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>If you&#8217;re not sure how your network is configured:</strong></h2>



<p class="wp-block-paragraph">Check with your network or infrastructure team. If Router is fetching its schema successfully today, domain-based allowlisting is likely already in place.</p>



<h1 class="wp-block-heading"><a href="#stay-informed" aria-hidden="true" class="aal_anchor" id="stay-informed"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Stay informed</h1>



<p class="wp-block-paragraph">The policy page is the authoritative source for current and upcoming IP changes. All future changes will be announced on the Apollo blog in the Announcements category – <a href="https://www.apollographql.com/blog/rss-announcement.xml">subscribe</a> to our blog’s announcement RSS feed or bookmark the <a href="http://apollographql.com/trust/api-ip-allowlist-policy">policy page</a> if IP allowlisting is relevant to your deployment.</p>



<p class="wp-block-paragraph">Questions? Reach out to Apollo Technical Support or email <a href="mailto:support@apollographql.com">support@apollographql.com</a>.</p>


Apollo’s New API IP Allowlist Policy


<p class="wp-block-paragraph"><a href="https://www.apollographql.com/docs/graphos/platform/schema-management/proposals">Schema proposals</a> are how teams running Apollo GraphOS coordinate changes to their graph: a place to draft a schema change, talk about it, review it, and ship it with confidence. As more teams have moved their schema work into proposals, and into the developer workflows and automations they build around them, we&#8217;ve spent the last several months listening closely to how that work actually flows.</p>



<p class="wp-block-paragraph">This release is the result of that listening. It spans four parts of the product:</p>



<ul class="wp-block-list">
<li><strong>Working on a proposal. </strong>Improvements to authoring and reviewing in Studio: navigating long diffs, understanding what changed, commenting in context, resolving conflicts without leaving the editor, and flagging inaccurate diffs.</li>



<li><strong>Better webhook notifications.</strong> Richer payloads and two new event types give your integrations the full picture of what happened, who triggered it, and where to look.</li>



<li><strong>Building on a reliable API. </strong>Robust updates to our API that provide more precise coverage detection and reliable data for your automated pipelines.</li>



<li><strong>Strengthening our foundations. </strong>Deeper consistency improvements that remove UI ambiguity and make the proposal workflow more predictable and stable.</li>
</ul>



<h2 class="wp-block-heading"><a href="#working-on-a-proposal" aria-hidden="true" class="aal_anchor" id="working-on-a-proposal"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Working on a proposal </h2>



<p class="wp-block-paragraph">This is the part of schema proposals where the work actually happens, whether you&#8217;re drafting changes or reviewing them. What follows is about that motion itself: moving through a diff, understanding what changed, commenting, and handling conflicts.</p>



<p class="wp-block-paragraph">Most of what changed here came out of close conversations with the platform teams who use proposals most, about how authors and reviewers actually spend their time. </p>



<figure class="wp-block-image size-large"><img decoding="async" src="https://res.cloudinary.com/apollographql/image/upload/v1782343701/www/blog/proposals-jumptochanges.gif" alt=""/></figure>



<h3 class="wp-block-heading"><a href="#moving-through-a-diff" aria-hidden="true" class="aal_anchor" id="moving-through-a-diff"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Moving through a diff</h3>



<p class="wp-block-paragraph">Working through a long proposal should keep your attention on the schema changes, not on the mechanics of getting to them. Long proposals now have a change navigator: the up and down arrows, or J and K from the keyboard, step you through every change in the diff, with a counter showing where you are in the sequence. When you scroll past the top of the changes section, a compact sticky bar follows you with the navigator, plus an expand-all / collapse-all toggle for the detailed views.<br></p>



<figure class="wp-block-image size-large"><img decoding="async" src="https://res.cloudinary.com/apollographql/image/upload/v1782344465/www/blog/v06tbw2vnvhupvtwpi8m.png" alt=""/></figure>



<h3 class="wp-block-heading"><a href="#understanding-whats-actually-different" aria-hidden="true" class="aal_anchor" id="understanding-whats-actually-different"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Understanding what&#8217;s actually different</h3>



<p class="wp-block-paragraph">Pulling changes from a source variant and authoring your own are different kinds of work, and the experience now keeps them visibly separate at every step.<br><br>It starts in the proposal list, where each entry shows whether it&#8217;s still in sync with the latest source variant, so you know before opening it whether there&#8217;s anything new to pull. When you pull changes into a revision, they show up in a dedicated &#8220;Pulled from source&#8221; section in the editor, separated from the changes you authored. And when you save that revision, both show up together in a single activity feed card with clearly labeled sections, so the timeline tells the full story of a save without fragmenting it. That same language carries through to the Changes page sidebar, which now reflects where you are: browsing across all revisions (think GitHub&#8217;s &#8220;All commits&#8221; view), or scoped into one with its authored and pulled sections clearly labeled. </p>



<figure class="wp-block-image size-large"><img decoding="async" src="https://res.cloudinary.com/apollographql/image/upload/v1782344181/www/blog/proposals-commentergonomics.gif" alt=""/></figure>



<h3 class="wp-block-heading"><a href="#commenting-in-place" aria-hidden="true" class="aal_anchor" id="commenting-in-place"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Commenting in place</h3>



<p class="wp-block-paragraph">Comments shouldn&#8217;t feel cramped, especially for the longer reviews and discussions that often shape a schema change. The comment drawer can now adapt to the scale of what you&#8217;re writing: drag it wider for more horizontal room, and drag the text area taller for more vertical room. The Write and Preview tabs were also cleaned up, so longer comments are easier to format and review.</p>



<figure class="wp-block-image size-large"><img decoding="async" src="https://res.cloudinary.com/apollographql/image/upload/v1782344236/www/blog/proposals-conflictresolution.gif"/></figure>



<h3 class="wp-block-heading"><a href="#resolving-conflicts-in-the-editor" aria-hidden="true" class="aal_anchor" id="resolving-conflicts-in-the-editor"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Resolving conflicts in the editor</h3>



<p class="wp-block-paragraph">A conflict shouldn&#8217;t drop you out of the workflow you were in. The proposal editor can now show you when a conflict exists, help you make sense of it, and let you resolve it without leaving the place you were working.</p>



<p class="wp-block-paragraph">Resolving a conflict in a proposal used to be a heads-down, manual job: find the conflict markers in the SDL, read both sides, edit the file to keep what you wanted. There was no signal that conflicts existed unless you went looking for them, and no scaffolding for the work of resolving one once you did.</p>



<p class="wp-block-paragraph">Now, conflicts are visible from the moment they appear. A count badge in the editor toolbar tells you how many there are, and every conflict region is highlighted inline, with colored backgrounds that distinguish your changes from the incoming ones at a glance. Each conflict has its own set of clearly-named actions (&#8220;Accept incoming,&#8221; &#8220;Accept current,&#8221; &#8220;Accept both&#8221;) rendered right above it, so resolving one is a single click rather than a manual edit.</p>



<p class="wp-block-paragraph">A dedicated conflicts drawer gives you a list view of every conflict in the active subgraph, with navigation between them and the same resolution actions as the inline buttons. Keyboard users have a full parallel path, and the drawer opens from the toolbar or with a keyboard shortcut.</p>



<p class="wp-block-paragraph">The editor itself also gets quieter while you&#8217;re resolving. The diagnostic noise that conflict markers usually trigger is suppressed, so the only thing in your way is the actual work to do.</p>



<figure class="wp-block-image size-large"><img decoding="async" src="https://res.cloudinary.com/apollographql/image/upload/v1782344300/www/blog/proposals-diffreporting.gif" alt=""/></figure>



<h3 class="wp-block-heading"><a href="#flagging-inaccurate-diffs" aria-hidden="true" class="aal_anchor" id="flagging-inaccurate-diffs"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flagging inaccurate diffs</h3>



<p class="wp-block-paragraph">Occasionally, diffs may not perfectly capture your changes, such as when pulling upstream updates or encountering stale conflict badges. Previously, flagging these inaccuracies required filing a support ticket, which often left issues unreported and delayed fixes.</p>



<p class="wp-block-paragraph">We’ve introduced a new diff reporting option directly on the Changes page. If you spot a missing change, incorrect removal, or unusual conflict indicator, you can flag it in one click.</p>



<p class="wp-block-paragraph">This creates a structured feedback loop, allowing us to capture the necessary proposal context automatically. By surfacing these edge cases, you help us prioritize fixes and close the accuracy gap, ensuring the diffs you review are always reliable.</p>



<h2 class="wp-block-heading"><a href="#better-webhook-notifications" aria-hidden="true" class="aal_anchor" id="better-webhook-notifications"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Better webhook notifications</h2>



<p class="wp-block-paragraph">When teams wire proposals into their own automation, the events that fire from GraphOS have to carry enough context to be useful. Until now, a proposal webhook event told you that something happened, along with a handful of IDs, but not much about what actually changed, who triggered it, or what the proposal looked like. Getting that context meant a follow-up Platform API call, which added overhead and friction to any integration.</p>



<p class="wp-block-paragraph">We have closed this gap by enriching the existing webhook payloads and adding new event types. Proposal events now include the proposal title, the actor who triggered the event, a direct Studio URL, the affected subgraphs, and (where relevant) the current approval progress. Your integration gets the context it needs from the event itself.</p>



<p class="wp-block-paragraph">Two new event types have been added:</p>



<ul class="wp-block-list">
<li><strong>REVIEW_SUBMITTED</strong> fires when a reviewer submits a review on a proposal, with the reviewer&#8217;s details and the review outcome included. This is distinct from the existing approval event: Proposals can require input from multiple reviewers, and not every review is an approval. Teams tracking review activity now have a dedicated event for it.</li>



<li><strong>COMMENT_MENTION</strong> fires when a user is @mentioned in a proposal comment, with the mentioned user&#8217;s info and a link to the specific comment. For teams routing notifications through their own tooling, @mentions can now get the same urgency they&#8217;d have inside Studio.</li>
</ul>



<p class="wp-block-paragraph">Finally, for teams already using Slack for schema coordination: Proposals now supports Slack channels as a notification target alongside webhooks. You can subscribe a Slack channel to the same proposal lifecycle events, with messages formatted using Block Kit so each notification carries the proposal name, the event that triggered it, who caused it, and a link back to Studio. </p>



<h2 class="wp-block-heading"><a href="#building-on-a-reliable-api" aria-hidden="true" class="aal_anchor" id="building-on-a-reliable-api"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Building on a reliable API</h2>



<p class="wp-block-paragraph">Schema proposals are an essential part of modern CI/CD pipelines. To better support your automated workflows, we’ve strengthened the Proposals API, focusing on robustness and integration reliability. We’ve overhauled our core matching logic <strong>(</strong><strong>ProposalsCheckTask)</strong>, ensuring that schema coverage and check results are precise and dependable. We’ve also refined conflict detection to eliminate false positives caused by upstream changes, ensuring that your review process remains focused on the updates you actually authored. Finally, we’ve improved our platform’s observability by cleaning up logging noise, making it easier to diagnose issues quickly. These enhancements provide the consistent, reliable data you need to power your schema governance at scale.</p>



<h2 class="wp-block-heading"><a href="#strengthening-our-foundations" aria-hidden="true" class="aal_anchor" id="strengthening-our-foundations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Strengthening our foundations</h2>



<p class="wp-block-paragraph">A governance workflow is only as strong as the trust you place in it. When reliability is compromised by inconsistent status flags, phantom conflicts, or unexplained check failures, the entire review process suffers. We’ve dedicated significant effort to identifying and closing those trust gaps. We’ve overhauled the core matching logic to ensure that statuses and schema checks accurately reflect your supergraph, eliminating errors like incorrect &#8220;Implemented&#8221; transitions. We’ve also resolved UI inconsistencies, including false-positive conflict badges and race conditions that hindered diff loading. By removing ambiguity from the system, we’re ensuring that proposals are predictable and stable, giving you the confidence to manage even your most complex schema changes.</p>



<h2 class="wp-block-heading"><a href="#what-this-adds-up-to" aria-hidden="true" class="aal_anchor" id="what-this-adds-up-to"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What this adds up to</h2>



<p class="wp-block-paragraph">Schema proposals were already a meaningful part of how graph teams ship schema changes. The work shipping in this release is about making them feel like a natural part of how those teams already work: the proposal workflow flows the way the work actually flows, the API meets your schema changes where they live, and the foundations underneath both are reliable enough to build on with confidence.<br></p>



<p class="wp-block-paragraph">If you&#8217;re already using proposals, this release should feel like it caught up with the way your team has been using them all along. If you&#8217;ve been thinking about bringing schema proposals more deeply into your pipelines or your agent-driven workflows, this release makes that practical. If you’d like to dig into it further, <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/proposals">our schema proposals docs</a> have you covered.<br></p>



<p class="wp-block-paragraph">And we’re not finished. There&#8217;s more to do on diff intelligence, on conflict resolution, and on the developer experience of the Platform API. Even so, this release is a meaningful step toward schema proposals becoming more than just a place to coordinate schema changes, and into a piece of platform infrastructure your team can rely on.</p>



<p class="wp-block-paragraph"><em>Note: Alex Lange and Chris Lee also contributed to this blog post.</em></p>


What’s new in Schema Proposals


<p class="wp-block-paragraph">Today, we&#8217;re launching a new API keys page in <a href="https://www.apollographql.com/graphos/studio">GraphOS Studio</a>, a single place where you can view and manage your SCIM, subgraph, and operator API keys directly from the UI. With built-in tools to filter by key status, cleanly rotate expiring keys with configurable buffer periods, and revoke unused keys, it empowers platform teams to maintain strict security oversight over their graph infrastructure without disrupting active development workflows.<br></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="480" src="https://wp.apollographql.com/wp-content/uploads/2026/06/image-1024x480.png" alt="" class="wp-image-25470" srcset="https://wp.apollographql.com/wp-content/uploads/2026/06/image-1024x480.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-300x141.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-768x360.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-1200x563.png 1200w, https://wp.apollographql.com/wp-content/uploads/2026/06/image.png 1271w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Figure 1: <em>API keys page in GraphOS Studio</em></figcaption></figure>



<h2 class="wp-block-heading"><a href="#the-problem-it-solves" aria-hidden="true" class="aal_anchor" id="the-problem-it-solves"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The problem it solves</h2>



<p class="wp-block-paragraph">API keys are the backbone of securing access to your GraphQL infrastructure. But managing them has historically been fragmented. Subgraph keys, operator keys, and SCIM keys lived in different places, and were only available through <a href="https://www.apollographql.com/docs/rover">Rover CLI</a> and the <a href="https://www.apollographql.com/docs/graphos/platform/platform-api">Platform API</a>.</p>



<p class="wp-block-paragraph">If a key was compromised or a token needed to be rotated out, your options were binary: delete it and lose the audit trail, or leave it active and accept the risk. Now, you can rotate or revoke a key so that it cannot be used, but you can continue to view it in your list of API keys.</p>



<h2 class="wp-block-heading"><a href="#what-we-built" aria-hidden="true" class="aal_anchor" id="what-we-built"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What we built </h2>



<h3 class="wp-block-heading"><a href="#view-search-and-filter-api-keys-at-a-glance" aria-hidden="true" class="aal_anchor" id="view-search-and-filter-api-keys-at-a-glance"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>View, search, and filter API keys at a glance</h3>



<p class="wp-block-paragraph">SCIM, subgraph, and operator keys are now visible in Apollo Studio. Search by name, filter by type or status, and quickly find the key you&#8217;re looking for. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="562" src="https://wp.apollographql.com/wp-content/uploads/2026/06/image-1-1024x562.png" alt="" class="wp-image-25472" srcset="https://wp.apollographql.com/wp-content/uploads/2026/06/image-1-1024x562.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-1-300x165.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-1-768x421.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-1-1536x842.png 1536w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-1-1200x658.png 1200w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-1-1980x1086.png 1980w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-1.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Figure 2: <em>Filter API keys by type</em></figcaption></figure>



<h3 class="wp-block-heading"><a href="#create-rename-and-update-expiration" aria-hidden="true" class="aal_anchor" id="create-rename-and-update-expiration"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Create, rename, and update expiration</h3>



<p class="wp-block-paragraph">Need a new API key for an upcoming deployment? As long as you have the appropriate permissions you can now spin one up without leaving the browser. You can also rename existing keys and adjust their expiration dates directly from the UI, keeping your key inventory clean and descriptive as your organization grows.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="937" src="https://wp.apollographql.com/wp-content/uploads/2026/06/image-2-1024x937.png" alt="" class="wp-image-25474" srcset="https://wp.apollographql.com/wp-content/uploads/2026/06/image-2-1024x937.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-2-300x275.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-2-768x703.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-2-1200x1098.png 1200w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-2.png 1530w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"><em>Figure 3: Create a new API key</em></figcaption></figure>



<h3 class="wp-block-heading"><a href="#rotate-api-keys-without-downtime" aria-hidden="true" class="aal_anchor" id="rotate-api-keys-without-downtime"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Rotate API keys without downtime</h3>



<p class="wp-block-paragraph">The new rotate action lets you cycle out a key while keeping it accessible for investigation or a transition period, so you can maintain continuity without sacrificing oversight. No more choosing between security and uptime. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="680" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2026/06/image-3-680x1024.png" alt="" class="wp-image-25476" srcset="https://wp.apollographql.com/wp-content/uploads/2026/06/image-3-680x1024.png 680w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-3-199x300.png 199w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-3-768x1157.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-3.png 1002w" sizes="auto, (max-width: 680px) 100vw, 680px" /><figcaption class="wp-element-caption">Figure 4: <em>Rotate API key</em></figcaption></figure>



<h3 class="wp-block-heading"><a href="#revoke-vs-delete-api-key" aria-hidden="true" class="aal_anchor" id="revoke-vs-delete-api-key"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Revoke vs. delete API key</h3>



<p class="wp-block-paragraph">Sometimes you need to immediately cut off access to a key, but you&#8217;re not ready to erase it entirely. Revoking a key stops it from being used right away while preserving the record, useful for incident response, audits, or investigations where visibility matters. Deleting a key remains available when you&#8217;re ready to permanently remove it.<br></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="442" src="https://wp.apollographql.com/wp-content/uploads/2026/06/image-5-1024x442.png" alt="" class="wp-image-25480" srcset="https://wp.apollographql.com/wp-content/uploads/2026/06/image-5-1024x442.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-5-300x129.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-5-768x331.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-5.png 1038w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Figure 5: <em>Revoke API key</em></figcaption></figure>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p class="wp-block-paragraph">Access to the API keys page is based on your role in GraphOS Studio. Graph admins can manage subgraph keys for their associated graphs. Org Admins have full access to all key types across the organization. Want to learn more? Check out our <a href="https://apollographql.com/docs/graphos/platform/access-management/api-keys/manage-api-keys-studio">documentation</a> for detailed setup instructions.&nbsp;</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="444" src="https://wp.apollographql.com/wp-content/uploads/2026/06/image-6-1024x444.png" alt="" class="wp-image-25482" srcset="https://wp.apollographql.com/wp-content/uploads/2026/06/image-6-1024x444.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-6-300x130.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-6-768x333.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-6-1536x665.png 1536w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-6-1200x520.png 1200w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-6-1980x858.png 1980w, https://wp.apollographql.com/wp-content/uploads/2026/06/image-6.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">Rover CLI users, this doesn&#8217;t change your workflow. Rover CLI continues to support creating, listing, deleting, and renaming subgraph and operator API keys. The Studio UI is an additive surface, not a replacement.</p>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What&#8217;s next</h2>



<p class="wp-block-paragraph">The <a href="https://apollographql.com/docs/graphos/platform/access-management/api-keys/manage-api-keys-studio">API keys page</a> is the foundation for a broader vision: a unified view of every key in your Apollo organization. Currently, graph and user API keys are available on separate key management pages, but in the future they will be available on the API keys page. You&#8217;ll be able to see and manage personal, graph-level, and org-level keys side by side. We&#8217;re also working on getting all of these new capabilities into Rover CLI.</p>


API Key Management now in GraphOS Studio


<p class="wp-block-paragraph">We&#8217;re excited to announce the release of Apollo Client 4.2. This release brings two additional long-awaited features:</p>



<ul class="wp-block-list">
<li>Type-safe default options</li>



<li>Event-based refetching</li>
</ul>



<p class="wp-block-paragraph">Let&#8217;s dive in!</p>



<h2 class="wp-block-heading"><a href="#type-safe-default-options" aria-hidden="true" class="aal_anchor" id="type-safe-default-options"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Type-safe default options</h2>



<p class="wp-block-paragraph">Prior to version 4.2, you had to choose between convenience and type-safety when you wanted to propagate a default option throughout your application. For example, you might set your default <code class="" data-line="">errorPolicy</code> to <code class="" data-line="">&quot;all&quot;</code> in order to render partially successful queries in your components.</p>



<p class="wp-block-paragraph">This could introduce a mismatch between the runtime behavior and what TypeScript reports as the right value. Consider this <code class="" data-line="">useSuspenseQuery</code> example:</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">const { data } = useSuspenseQuery(QUERY);
//      ^? TData

const { data } = useSuspenseQuery(QUERY, { errorPolicy: &quot;all&quot; });
//      ^? TData | undefined</code></pre>



<p class="wp-block-paragraph">With no explicit <code class="" data-line="">errorPolicy</code>, <code class="" data-line="">useSuspenseQuery</code>&#8216;s throws by default when an error is returned, which means `data` can be typed as the query data type. Passing <code class="" data-line="">errorPolicy: &quot;all&quot;</code> changes the return type to include <code class="" data-line="">undefined</code> because the server might return an error with no data.</p>



<p class="wp-block-paragraph">Changing the default <code class="" data-line="">errorPolicy</code> in <code class="" data-line="">defaultOptions</code> was considered unsafe however because it modified the runtime behavior, but the types remained the same. This could cause crashes in your production environment that weren&#8217;t caught by TypeScript because you might access properties on <code class="" data-line="">undefined</code>.</p>



<p class="wp-block-paragraph">In 4.2, default options are now propagated through all React hooks and APIs to provide the correct type to match the runtime value. You opt in by declaring your default options using TypeScript module augmentation:</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">// apollo.d.ts
import &quot;@apollo/client&quot;;

declare module &quot;@apollo/client&quot; {
  namespace ApolloClient {
    namespace DeclareDefaultOptions {
      interface WatchQuery {
        errorPolicy: &quot;all&quot;;
      }
    }
  }
}</code></pre>



<p class="wp-block-paragraph">To make sure the runtime behavior matches the types, Apollo Client forces you to add a matching <code class="" data-line="">defaultOptions</code> option:</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">new ApolloClient({
  // without this option, TypeScript reports an error
  defaultOptions: {
    watchQuery: {
      errorPolicy: &quot;all&quot;
    }
  }
})</code></pre>



<p class="wp-block-paragraph">With that TypeScript declaration in place, the hook now reflects the runtime value:</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">const { data } = useSuspenseQuery(QUERY);
//      ^? TData | undefined</code></pre>



<p class="wp-block-paragraph">This behavior extends to all query and mutation hooks and core APIs.</p>



<p class="wp-block-paragraph">Learn more about declaring type-safe default options in the <a href="https://www.apollographql.com/docs/react/data/typescript#declaring-default-options-types">TypeScript guide</a>.</p>



<h3 class="wp-block-heading"><a href="#deprecation-of-generic-arguments" aria-hidden="true" class="aal_anchor" id="deprecation-of-generic-arguments"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deprecation of generic arguments</h3>



<p class="wp-block-paragraph">To achieve type-safe default options, Apollo Client requires the use of type inference. As a result, passing generic arguments to hooks and core APIs is now deprecated.</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">// Generic arguments are no deprecated
useQuery&lt;DataType, VariablesType&gt;(QUERY)</code></pre>



<p class="wp-block-paragraph">You can still use this signature, but you won&#8217;t be able to take advantage of the new type-safety. Migrate to <code class="" data-line="">TypedDocumentNode</code> instead:</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">const QUERY: TypedDocumentNode&lt;DataType, VariablesType&gt; = gql``</code></pre>



<p class="wp-block-paragraph">Learn more about migrating in the <a href="https://www.apollographql.com/docs/react/migrating/apollo-client-4-migration#type-safety-for-default-options">migration guide</a>.</p>



<h2 class="wp-block-heading"><a href="#event-based-refetching" aria-hidden="true" class="aal_anchor" id="event-based-refetching"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Event-based refetching</h2>



<p class="wp-block-paragraph">One of our most popular requests has been window focus refetching, a feature popularized by TanStack Query that triggers automatic refetches when the browser tab regains focus. Building your own system for handling automatic refetches resulted in a <a href="https://github.com/apollographql/apollo-feature-requests/issues/247#issuecomment-1650221163">complicated mess</a> of <code class="" data-line="">useEffect</code> or wrapper hooks to provide this sort of functionality yourself.</p>



<p class="wp-block-paragraph">4.2 introduces the new <code class="" data-line="">RefetchEventManager</code>, which handles refetches for you in response to events such as window focus or network reconnection. Pass a <code class="" data-line="">RefetchEventManager</code> instance to the <code class="" data-line="">refetchEventManager</code> option to opt-into automatic refetches:</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">import { RefetchEventManager, windowFocusSource } from &quot;@apollo/client&quot;;

const client = new ApolloClient({
  // ...
  refetchEventManager: new RefetchEventManager({
    sources: {
      windowFocus: windowFocusSource,
    },
  }),
});</code></pre>



<p class="wp-block-paragraph">Anytime a user focuses the browser tab, the client automatically refetches active queries.</p>



<p class="wp-block-paragraph">Queries can also opt-out of a specific event refetch with the new <code class="" data-line="">refetchOn</code> option:</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">useQuery(QUERY, { 
  // Don&#039;t refetch this query when the windowFocus event is triggered
  refetchOn: { windowFocus: false } 
});</code></pre>



<p class="wp-block-paragraph"><code class="" data-line="">RefetchEventManager</code> is designed for extensibility in mind. You can register your own custom events, provide customized handlers to determine which queries should be refetched, and more.</p>



<p class="wp-block-paragraph">See the <a href="https://www.apollographql.com/docs/react/data/event-based-refetching">event-based refetching docs</a> to learn more.</p>



<h2 class="wp-block-heading"><a href="#wrapping-up" aria-hidden="true" class="aal_anchor" id="wrapping-up"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Wrapping up</h2>



<p class="wp-block-paragraph">Ready to upgrade? Install Apollo Client 4.2 today:</p>



<pre data-line="" class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">npm install @apollo/client@latest</code></pre>



<p class="wp-block-paragraph">For the full list of changes, check out the <a href="https://github.com/apollographql/apollo-client/releases/tag/%40apollo%2Fclient%404.2.0">release notes</a>. Questions and feedback are always welcome in the<a href="https://community.apollographql.com/"> Apollo Community</a>.</p>



<p class="wp-block-paragraph">Happy querying!</p>


What’s New in Apollo Client 4.2


<p class="wp-block-paragraph">Today we&#8217;re releasing a preview of Rust-native composition for Apollo Federation. We are close to the finish line of a multi-year effort to replatform Apollo Federation, both the query planner and the composition engine, from JavaScript/TypeScript to Rust. You can try it now by enabling the <strong>Federation Next</strong> build track in <a href="https://studio.apollographql.com/">GraphOS Studio</a>. </p>



<h2 class="wp-block-heading"><a href="#why-rust" aria-hidden="true" class="aal_anchor" id="why-rust"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Why Rust</h2>



<p class="wp-block-paragraph">When we shipped the <a href="https://www.apollographql.com/docs/graphos/routing/query-planning/native-query-planner">Rust-native query planner</a> over a year ago, the performance and reliability improvements were immediate. <a href="https://www.apollographql.com/docs/graphos/schema-design/federated-schemas/composition">Composition</a> was the obvious next target, and the last major Federation component still running in JavaScript.</p>



<p class="wp-block-paragraph">The JS composition engine relied on an embedded Deno runtime and V8 to execute. That meant garbage collection pauses and high memory consumption for large graphs. Rust eliminates that entire class of overhead, and its predictable memory model handles graphs with hundreds of subgraphs comfortably.</p>



<p class="wp-block-paragraph">Beyond performance, this unifies our codebase. The query planner and composition engine now live in a single Rust monorepo. We no longer need to duplicate bug fixes across two languages, synchronize spec changes between JS and Rust implementations, or manage complex cross-language dependency chains. That simplification lets us iterate faster on Federation features going forward. </p>



<h2 class="wp-block-heading"><a href="#performance" aria-hidden="true" class="aal_anchor" id="performance"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Performance</h2>



<p class="wp-block-paragraph">We benchmarked the Rust implementation against the JS implementation across tens of thousands of real-world production graphs. The results are significant. At the median, Rust composition is roughly <strong>27x faster</strong>. At p95, it&#8217;s about <strong>8.5x faster</strong>. The gap narrows at higher percentiles because the largest graphs stress both implementations, but Rust still delivers a <strong>6x improvement </strong>at p99.</p>



<p class="wp-block-paragraph">These numbers are pre-GA and measure composition in isolation. Your experience in Studio may differ since composition is one step in a larger build pipeline. That said, these results are with minimal dedicated optimization work on the Rust side, so there&#8217;s room to go further.</p>



<h2 class="wp-block-heading"><a href="#how-we-built-it" aria-hidden="true" class="aal_anchor" id="how-we-built-it"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How We Built It</h2>



<p class="wp-block-paragraph">Composition is a multi-stage pipeline. Rewriting all of it at once would have been risky. A single bug in any stage could produce incorrect supergraph schemas. Instead, we built a hybrid pipeline that let each stage run independently in either JavaScript or Rust.</p>



<p class="wp-block-paragraph">This allowed us to develop and validate one stage at a time, comparing JS and Rust output at every boundary to catch regressions before they compounded. In production, we ran the Rust implementation in shadow alongside the existing JS pipeline, processing the same graphs in parallel so we could validate correctness and performance against real-world workloads without any risk.</p>



<h2 class="wp-block-heading"><a href="#how-we-validated-it" aria-hidden="true" class="aal_anchor" id="how-we-validated-it"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How We Validated It</h2>



<p class="wp-block-paragraph">Correctness was the bar we had to clear before anything else. A composition engine that produces fast but wrong supergraph schemas is worse than useless. It&#8217;s dangerous.</p>



<p class="wp-block-paragraph">We tested against tens of thousands of real-world production graphs from our corpus. For every graph, we ran composition through both the JS and Rust implementations and compared their outputs at each stage of the pipeline. This wasn&#8217;t just &#8220;does it produce a schema.&#8221; We compared the full output including the supergraph schema, composition hints, and error messages.</p>



<p class="wp-block-paragraph">To make these comparisons meaningful, we normalized for known cosmetic differences between the implementations. The JS and Rust compilers handle whitespace in schema descriptions differently, and JS relies on automatic type coercion for default values where Rust is explicit. We accounted for these so we could focus on semantic correctness rather than surface-level formatting noise.</p>



<p class="wp-block-paragraph">At the time of this preview release, the Rust implementation produces identical results to JS on <strong>the vast majority </strong>of the corpus with the majority of differences appearing in hints or error messages rather than in the composed schemas themselves. A meaningful number of schema differences are cases where the Rust implementation is actually more correct. Any remaining differences are actively categorized and will be resolved before the GA release.</p>



<h2 class="wp-block-heading"><a href="#try-it" aria-hidden="true" class="aal_anchor" id="try-it"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try It</h2>



<p class="wp-block-paragraph">You can test the Rust composition preview today by enabling the <strong>Federation Next</strong> build track in <a href="https://studio.apollographql.com/">GraphOS Studio</a>. This will run your graph&#8217;s compositions through the Rust pipeline.</p>



<p class="wp-block-paragraph">We want to hear from you. If you encounter any differences in composition behavior, please report them through your usual support channel or file an issue on the <a href="https://github.com/apollographql/router">Apollo Router GitHub repo</a>.</p>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What&#8217;s Next</h2>



<p class="wp-block-paragraph">We&#8217;re working toward general availability, which means resolving the remaining equivalence gaps, completing our production shadow validation, and ultimately removing the JS fallback path entirely.</p>



<p class="wp-block-paragraph">We&#8217;re also porting contracts, the last piece of Federation tooling still in JavaScript, to Rust. Once that&#8217;s complete, the entire Federation stack will run natively.</p>



<h2 class="wp-block-heading"><a href="#acknowledgments" aria-hidden="true" class="aal_anchor" id="acknowledgments"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Acknowledgments</h2>



<p class="wp-block-paragraph">This was a multi-year effort done right. Rewriting, validating and shipping a system that processes schemas for thousands of production graphs demands that kind of rigor.&nbsp;</p>



<p class="wp-block-paragraph">We&#8217;re grateful to everyone across the Apollo team who contributed, and to the community members whose large, complex real-world graphs continue to push us to make Federation better. Those graphs are both our hardest test cases and our strongest motivation.</p>



<p class="wp-block-paragraph"></p>


Apollo Federation Goes Full Rust


<p class="wp-block-paragraph">Today we&#8217;re honored to announce Apollo has been recognized in the <a href="https://www.gartner.com/reprints/?id=1-2N9TA4ZU&amp;ct=260429&amp;st=sb">2026 Gartner Peer Insights “Voice of the Customer” for API Management</a> for the first time. We scored 4.7 out of 5 stars from 55 verified enterprise reviewers, and 98% said they would recommend Apollo to a peer as of January 31, 2026.</p>



<figure class="wp-block-pullquote"><blockquote><p>“The overall experience with Apollo GraphOS has been amazing. It has provided us with good visibility on our subgraphs.”</p></blockquote></figure>



<p class="wp-block-paragraph">Every score in this report comes directly from customers: people who deployed the product, ran it in production, and took the time to write about the experience honestly. We also are named as a Strong Performer in the report’s quadrant view.</p>



<p class="wp-block-paragraph"><strong>Thank You</strong></p>



<p class="wp-block-paragraph">The above numbers show the aggregate view, but what our customers actually wrote is what I want to share.</p>



<ul class="wp-block-list">
<li>“Excellent at allowing our teams onboard quickly to the graph without them needing to setup everything from scratch.” – <a href="https://www.gartner.com/reviews/market/api-management/vendor/apollo-graphql/product/apollo-graphos/review/view/6427154">Software Developer in Media</a>, 5/5 rating</li>



<li>“The overall experience with Apollo GraphOS has been amazing. It has provided us with good visibility on our subgraphs.” – <a href="https://www.gartner.com/reviews/market/api-management/vendor/apollo-graphql/product/apollo-graphos/review/view/6427152">Engineer in Real Estate</a>, 5/5 rating</li>



<li>“The Apollo Connector is something I was interested in as we have a lot of REST services and we plan to leverage that for our company.” – <a href="https://www.gartner.com/reviews/market/api-management/vendor/apollo-graphql/product/apollo-graphos/review/view/6429056">Senior Staff Software Engineer in Banking</a>, 5/5 rating</li>



<li>“Ease of setting up applications from scratch and the latest products with Apollo Connectors for REST APIs making it a breeze.” – <a href="https://www.gartner.com/reviews/market/api-management/vendor/apollo-graphql/product/apollo-graphos/review/view/6427108">Software Developer in Media</a>, 5/5 rating</li>
</ul>



<p class="wp-block-paragraph">To every customer who took the time to share their experience: thank you. The feedback you leave shapes how we build, how we support, and how we show up for the next team working through the same problems you solved.</p>



<p class="wp-block-paragraph">If you’re an Apollo customer and haven’t yet left a review, we’d love to hear from you on <a href="https://www.gartner.com/reviews/market/api-management/vendor/apollo-graphql/product/apollo-graphos">Gartner Peer Insights</a>. Your perspective makes the product better for everyone.&nbsp;</p>



<p class="wp-block-paragraph"><em>Gartner® and Peer Insights™ are trademarks of Gartner, Inc. and/or its affiliates. All rights reserved. Gartner® Peer Insights™ content consists of the opinions of individual end users based on their own experiences, and should not be construed as statements of fact, nor do they represent the views of Gartner or its affiliates. Gartner does not endorse any vendor, product or service depicted in this content nor makes any warranties, expressed or implied, with respect to this content, about its accuracy or completeness, including any warranties of merchantability or fitness for a particular purpose.</em></p>



<p class="wp-block-paragraph"><em>Gartner, Voice of the Customer for API Management, by Peer Contributors, 31 March 2026.&nbsp;</em></p>


Apollo is Recognized in Gartner® Voice of the Customer 


<p class="wp-block-paragraph">Today, we’re releasing <a href="https://github.com/apollographql/apollo-kotlin-normalized-cache">the new cache library</a> for <a href="https://github.com/apollographql/apollo-kotlin">Apollo Kotlin</a>, the GraphQL client library for Android and Kotlin.</p>



<p class="wp-block-paragraph">Historically, caching has generated the most questions, tickets, and feedback, and we knew it was an area that deserved significant attention.</p>



<p class="wp-block-paragraph">To do that efficiently, we decided early on to create a <a href="https://github.com/apollographql/apollo-kotlin-normalized-cache">new repository</a> with its own independent name, artifacts, and versioning. This allowed us to iterate on this new version without disrupting the existing stable library.</p>



<p class="wp-block-paragraph">After more than a year of development and invaluable community feedback (thank you!), <a href="https://github.com/apollographql/apollo-kotlin-normalized-cache/releases">v1 is now available</a>, and we are excited to share it with you.</p>



<h2 class="wp-block-heading" id="What’s-new?"><a href="#whats-new" aria-hidden="true" class="aal_anchor" id="whats-new"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s new?</h2>



<p class="wp-block-paragraph">Compared to the previous iteration, this new normalized cache brings:</p>



<h3 class="wp-block-heading" id="Pagination-support"><a href="#pagination-support" aria-hidden="true" class="aal_anchor" id="pagination-support"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Pagination support</h3>



<p class="wp-block-paragraph">Caching paginated queries has always been a bit tricky, and required a lot of manual work to merge the results. With this new version, Relay-style pagination is supported out of the box, and the cache will take care of merging the results for you.</p>



<h3 class="wp-block-heading" id="Expiration-(a.k.a.-Time-to-live)"><a href="#expiration-a-k-a-time-to-live" aria-hidden="true" class="aal_anchor" id="expiration-a-k-a-time-to-live"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Expiration (a.k.a. Time to live)</h3>



<p class="wp-block-paragraph">The new cache allows you to specify a maximum age (TTL) for your types and fields, and will automatically expire them when they are too old. By default, expired fields are treated as a cache miss, which results in a network request to fetch the fresh data.</p>



<h3 class="wp-block-heading" id="Partial-results-from-the-cache"><a href="#partial-results-from-the-cache" aria-hidden="true" class="aal_anchor" id="partial-results-from-the-cache"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Partial results from the cache</h3>



<p class="wp-block-paragraph">Partial cache reads are now possible, similar to how GraphQL supports partial responses. This means that even if <em>some</em> fields from your query are missing from the cache, the available ones can still be returned and displayed.</p>



<h3 class="wp-block-heading" id="Garbage-collection-and-trimming"><a href="#garbage-collection-and-trimming" aria-hidden="true" class="aal_anchor" id="garbage-collection-and-trimming"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Garbage collection and trimming</h3>



<p class="wp-block-paragraph">A cache can grow indefinitely, and previously the only thing you could do is to clear it entirely. We now have APIs to:</p>



<ul class="wp-block-list">
<li>remove unused data from the cache to reduce its size,</li>



<li>trim the cache to a maximum size by removing the oldest records.</li>
</ul>



<h3 class="wp-block-heading" id="Key-scope-support"><a href="#key-scope-support" aria-hidden="true" class="aal_anchor" id="key-scope-support"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Key scope support</h3>



<p class="wp-block-paragraph">Specifying the cache keys for your types is vital for a normalized cache to work efficiently. The cache used to always prefix keys with the type name (e.g. <code class="" data-line="">User:42</code>). If your keys are unique across all types, this isn&#8217;t always necessary and adds overhead. This is now configurable.</p>



<h3 class="wp-block-heading" id="Improved-performance"><a href="#improved-performance" aria-hidden="true" class="aal_anchor" id="improved-performance"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Improved performance</h3>



<p class="wp-block-paragraph">The SQL cache now stores normalized records in a more efficient way, resulting in better performance, and a smaller on-disk footprint.</p>



<h3 class="wp-block-heading" id="And-more!"><a href="#and-more" aria-hidden="true" class="aal_anchor" id="and-more"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>And more!</h3>



<p class="wp-block-paragraph">There are also many smaller improvements along with API polish, and simplifications.</p>



<h2 class="wp-block-heading" id="Try-it-out!"><a href="#try-it-out" aria-hidden="true" class="aal_anchor" id="try-it-out"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try it out!</h2>



<p class="wp-block-paragraph">If you&#8217;re already using the normalized cache, follow the <a href="https://apollographql.github.io/apollo-kotlin-normalized-cache/migration-guide.html">migration guide</a>.</p>



<p class="wp-block-paragraph">Otherwise, hop over to the <a href="https://apollographql.github.io/apollo-kotlin-normalized-cache/welcome.html">documentation</a> to get started.</p>



<p class="wp-block-paragraph">Either way, let us know what you think &#8211; via <a href="https://github.com/apollographql/apollo-kotlin-normalized-cache/issues">GitHub issues</a>, the <a href="https://discord.gg/graphos">Apollo Community</a>, or the <a href="https://slack.kotl.in/">Kotlin Slack</a>!</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">If you’re thinking about caching, GraphOS also supports <a href="https://www.apollographql.com/docs/graphos/routing/performance/caching/response-caching/overview">response caching</a> at the router level.</p>
</blockquote>



<p class="wp-block-paragraph"></p>


The New Apollo Kotlin Normalized Cache


<p class="wp-block-paragraph">Back in December, I shared a preview of how to <a href="https://www.apollographql.com/blog/building-apps-for-chatgpt-with-apollo-mcp-server-and-apollo-client">build apps for ChatGPT using Apollo MCP Server and Apollo Client</a>. This post introduced the idea of building apps that live inside the conversation with an LLM. Users can ask follow up questions, trigger actions, and interact with rich UI components powered by your existing APIs.&nbsp;</p>



<p class="wp-block-paragraph">Since then, the ecosystem has matured quickly. The ChatGPT App Store is open, the MCP Apps specification has launched, and many platforms have added support for MCP Apps. ChatGPT has also introduced a bridge for MCP Apps support. This space is rapidly evolving and there is a lot to keep up with.</p>



<p class="wp-block-paragraph">Today, we are officially launching our framework for building MCP Apps using Apollo Client and Apollo MCP Server. This launch includes support for both OpenAI and any platform that supports the MCP Apps specification. With this framework, you can build using familiar Apollo Client patterns and serve your app through Apollo MCP Server, without standing up or maintaining dedicated MCP infrastructure.</p>



<p class="wp-block-paragraph">In this post, we’ll dive into what we’re launching, why it matters, and what it unlocks for Apollo Client teams.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">Join us on <strong>March 3 at 9:00 a.m. PT</strong> for a live walkthrough of building and deploying an MCP App with Apollo Client and Apollo MCP Server.</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/events/building-mcp-apps-with-apollo-client-and-apollo-mcp-server">Register now</a></p>
</blockquote>



<h1 class="wp-block-heading"><a href="#why-should-you-care-about-mcp-apps" aria-hidden="true" class="aal_anchor" id="why-should-you-care-about-mcp-apps"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Why Should You Care About MCP Apps?</h1>



<p class="wp-block-paragraph">AI chat interfaces like ChatGPT and Claude are quickly becoming the default way many users interact with the internet. Conversations in these platforms are now a primary way to discover products, evaluate options, and make purchases.</p>



<p class="wp-block-paragraph">For companies that rely heavily on traditional search traffic and web-based lead capture, this shift can feel threatening. If more user journeys begin inside AI interfaces, some existing business models will face pressure.&nbsp;</p>



<p class="wp-block-paragraph">This doesn’t mean SEO is dead. It means distribution is expanding.&nbsp;</p>



<p class="wp-block-paragraph">In-chat apps represent a new surface area, similar to how mobile apps emerged alongside the web in the early 2010s. Companies didn’t shut down their websites when mobile took off. They added another channel. The same pattern is emerging here.&nbsp;</p>



<p class="wp-block-paragraph">MCP Apps give you a way to:</p>



<ul class="wp-block-list">
<li>Reach users inside AI-driven interfaces</li>



<li>Offer structured, interactive experiences instead of plain text responses</li>



<li>Enable agentic workflows like booking, purchasing, or configuring directly within a conversation</li>
</ul>



<p class="wp-block-paragraph">This is not a replacement for your existing channels, it’s an additional channel where users are increasingly spending time. Having an MCP App is quickly becoming as strategically important as having a mobile app was a decade ago.&nbsp;</p>



<h1 class="wp-block-heading"><a href="#getting-started-out-of-the-box-template" aria-hidden="true" class="aal_anchor" id="getting-started-out-of-the-box-template"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting Started: Out-of-the-Box Template</h1>



<p class="wp-block-paragraph">You can quickly get started by using our <a href="https://github.com/apollographql/ai-apps-template">AI Apps Template</a>. This provides a demo React app that includes the scaffolding for the framework, along with the @apollo/client-ai-apps integration library which provides the foundation for developing MCP Apps with Apollo Client and Apollo MCP Server.</p>



<figure class="wp-block-embed is-type-video is-provider-wistia-inc wp-block-embed-wistia-inc"><div class="wp-block-embed__wrapper">
<script src="https://fast.wistia.com/player.js" async></script><script src="https://fast.wistia.com/embed/xqtnazhb06.js" async type="module"></script><style>wistia-player[media-id='xqtnazhb06']:not(:defined) { background: center / contain no-repeat url('https://fast.wistia.com/embed/medias/xqtnazhb06/swatch'); display: block; filter: blur(5px); padding-top:56.25%; }</style> <wistia-player media-id="xqtnazhb06" seo="false" dnt="1" aspect="1.7777777777777777"></wistia-player>
</div></figure>



<p class="wp-block-paragraph">The framework <strong>automatically generates</strong> a .application-manifest.json file. Apollo MCP Server utilizes this manifest at startup to automatically generate MCP Tools and Resources for your app.&nbsp;</p>



<p class="wp-block-paragraph">Serving your new app over MCP is as simple as deploying the build artifacts next to a running Apollo MCP Server. All of the MCP plumbing happens automagically for you behind the scenes.</p>



<h1 class="wp-block-heading"><a href="#benefits-self-service-and-velocity" aria-hidden="true" class="aal_anchor" id="benefits-self-service-and-velocity"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Benefits: Self Service and Velocity</h1>



<p class="wp-block-paragraph">This framework allows you to utilize what you already know about building apps with Apollo Client and layer on paradigm-specific knowledge for MCP. It prevents you from having to dive deep into the MCP Apps specification or build and maintain a new MCP Server that effectively serves as a BFF for your MCP App. This greatly increases your velocity, both when getting started and as you develop new features over time.</p>



<p class="wp-block-paragraph">For frontend teams, there’s no need to stand up an MCP Server or learn the inner workings of MCP. Your GraphQL queries become MCP server tools simply by adding an `@tool` directive. This provides a frictionless way to create new MCP server functionality without touching the server itself.</p>



<p class="wp-block-paragraph">For platform teams, Apollo MCP Server empowers your frontend teams to self-serve. A single MCP Server can serve multiple MCP Apps which helps avoid the &#8220;MCP Server Sprawl&#8221;. Maintenance remains minimal as your MCP app footprint grows.</p>



<p class="wp-block-paragraph">The end result is less infrastructure to maintain, fewer cross-team dependencies, and higher velocity by leveraging your existing knowledge and technology investments.</p>



<h1 class="wp-block-heading"><a href="#whats-new-in-this-launch" aria-hidden="true" class="aal_anchor" id="whats-new-in-this-launch"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s New in This Launch</h1>



<p class="wp-block-paragraph">A few things have changed since our original preview that are worth highlighting:</p>



<ul class="wp-block-list">
<li>Support for MCP Apps &#8211; Most of this is taken care of behind the scenes!</li>



<li>Easier config using <a href="https://github.com/cosmiconfig/cosmiconfig">cosmiconfig</a> &#8211; App configuration can now be loaded via a config file or an apollo-client-ai-apps property in your package.json&nbsp;</li>



<li>Platform-specific utilities and conventions &#8211; React-native style file conventions allow hot-swapping components for a given platform, which is especially useful for ChatGPT extensions.</li>



<li>Improved Typescript Configuration &#8211; The package now ships with extensible tsconfig to ensure you&#8217;re using the right tool for the right platform</li>



<li>Improved Tree Shaking &#8211; Extensive work to re-organize the library to minimize bundle size, shipping only the exact code required for your app for a given platform target</li>
</ul>



<p class="wp-block-paragraph">Overall, this is now the build once, deploy anywhere solution that we aimed to release with an exceptional developer experience.</p>



<h1 class="wp-block-heading"><a href="#summary" aria-hidden="true" class="aal_anchor" id="summary"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Summary</h1>



<p class="wp-block-paragraph">With our framework, it’s now easier than ever to build an MCP App using the knowledge and skills you already possess using React and Apollo Client. Instead of focusing on MCP internals, platform specific meta values, or building yet another BFF-like service, you can focus on what matters most: building great experiences for your customers.</p>



<p class="wp-block-paragraph"><br>Try building an MCP App today with Apollo Client and Apollo MCP Server by going to our <a href="https://github.com/apollographql/ai-apps-template">AI Apps Template</a> and following the README. We’d love to hear what you think. If you find any issues or bugs, you can open an issue on our <a href="https://github.com/apollographql/apollo-client-ai-apps">@apollo/client-ai-apps GitHub repo</a>.</p>


Building MCP Apps with Apollo Client and Apollo MCP Server


<p class="wp-block-paragraph">Apollo Client 4.1 is here with significant updates to incremental delivery, fragment watching capabilities, and cache improvements. This release introduces full <code class="" data-line="">@stream</code> directive support, compatibility with the latest GraphQL incremental delivery spec, and powerful new APIs for working with fragments.</p>



<h2 class="wp-block-heading"><a href="#stream-directive-support" aria-hidden="true" class="aal_anchor" id="stream-directive-support"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code class="" data-line="">@stream</code> directive support</h2>



<p class="wp-block-paragraph">Apollo Client 4.1 introduces support for the <code class="" data-line="">@stream</code> directive, allowing you to stream array items incrementally from your GraphQL server. <code class="" data-line="">@stream</code> works with both the <code class="" data-line="">Defer20220824Handler</code> and the newer <code class="" data-line="">GraphQL17Alpha9Handler</code>.</p>



<p class="wp-block-paragraph">The <code class="" data-line="">@stream</code> directive is useful when fetching large lists where you want to display items as they become available rather than waiting for the entire response. As each item arrives, Apollo Client updates the cache and notifies your components.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">const QUERY = gql`
  query FeedQuery {
    feed @stream(initialCount: 5) {
      id
      contents
    }
  }
`</code></pre>



<p class="wp-block-paragraph"><strong>Note:</strong> The implementations of <code class="" data-line="">@stream</code> differ between GraphQL spec versions in how incremental results are delivered. If you&#8217;re upgrading handlers, expect the timing of some incremental results to change.</p>



<h2 class="wp-block-heading"><a href="#graphql17alpha9handler" aria-hidden="true" class="aal_anchor" id="graphql17alpha9handler"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code class="" data-line="">GraphQL17Alpha9Handler</code></h2>



<p class="wp-block-paragraph">For servers that use the newer incremental delivery format implemented in <code class="" data-line="">graphql@17.0.0-alpha.9</code>, Apollo Client now provides a dedicated handler:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">import { GraphQL17Alpha9Handler } from &quot;@apollo/client/incremental&quot;;

const client = new ApolloClient({
  // ...
  incrementalHandler: new GraphQL17Alpha9Handler(),
});</code></pre>



<p class="wp-block-paragraph">This handler supports both <code class="" data-line="">@defer</code> and <code class="" data-line="">@stream</code> with the updated wire format. The handler automatically sets the appropriate <code class="" data-line="">accept</code> header (<code class="" data-line="">multipart/mixed;incrementalSpec=v0.2</code>) to request the newest format.</p>



<p class="wp-block-paragraph"><strong>Note:</strong> Your GraphQL server must implement the newer incremental delivery format for this handler to work correctly.</p>



<h2 class="wp-block-heading"><a href="#array-support-for-usefragment" aria-hidden="true" class="aal_anchor" id="array-support-for-usefragment"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Array support for <kbd>useFragment</kbd></h2>



<p class="wp-block-paragraph">You can now pass an array to the <code class="" data-line="">from</code> option in <code class="" data-line="">useFragment</code>, <code class="" data-line="">useSuspenseFragment</code>, and <code class="" data-line="">client.watchFragment</code> to watch multiple cache entities simultaneously:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">import type { FragmentType } from &quot;@apollo/client&quot;;

interface ItemListProps {
  items: Array&lt;FragmentType&lt;ItemFragment&gt;&gt;;
}

function ItemList({ items }: ItemListProps) {
  const result = useFragment({
    fragment: ITEM_FRAGMENT,
    from: items,
  });

  console.log(result);
  // { 
  //   data: [{...}, {...}, {...}, ...], 
  //   dataState: &quot;complete&quot;, 
  //   complete: true 
  // }
}</code></pre>



<p class="wp-block-paragraph">This eliminates the need to either hoist the item fragment into the parent fragment or create a child component with <code class="" data-line="">useFragment</code> for each array item.</p>



<h2 class="wp-block-heading"><a href="#other-notable-changes" aria-hidden="true" class="aal_anchor" id="other-notable-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Other notable changes</h2>



<h3 class="wp-block-heading"><a href="#bug-fixes" aria-hidden="true" class="aal_anchor" id="bug-fixes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Bug fixes</h3>



<ul class="wp-block-list">
<li>Fixed an issue where incremental payloads returning arrays with fewer items than cached items would incorrectly retain old items (<a href="https://github.com/apollographql/apollo-client/pull/12923">#12923</a>)</li>



<li><code class="" data-line="">fetchMore</code> now rerenders incremental results when using <code class="" data-line="">@defer</code> or <code class="" data-line="">@stream</code> (<a href="https://github.com/apollographql/apollo-client/pull/12925">#12925</a>) </li>



<li>Ensured <code class="" data-line="">PreloadedQueryRef</code> instances are unsubscribed when garbage collected (<a href="https://github.com/apollographql/apollo-client/pull/12884">#12884</a>)</li>
</ul>



<h3 class="wp-block-heading"><a href="#performance-improvements" aria-hidden="true" class="aal_anchor" id="performance-improvements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Performance improvements</h3>



<ul class="wp-block-list">
<li>Watches and observables created by <code class="" data-line="">useFragment</code>, <code class="" data-line="">client.watchFragment</code>, and <code class="" data-line="">cache.watchFragment</code> are now deduplicated for the same object, fragment, and variables. This should improve performance dramatically in cases where the same object is watched in the cache multiple times in the application. (<a href="https://github.com/apollographql/apollo-client/pull/12927">#12927</a>, <a href="https://github.com/apollographql/apollo-client/pull/13026">#13026</a>, <a href="https://github.com/apollographql/apollo-client/pull/13053">#13053</a>)</li>
</ul>



<h3 class="wp-block-heading"><a href="#other-improvements" aria-hidden="true" class="aal_anchor" id="other-improvements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Other improvements</h3>



<ul class="wp-block-list">
<li>The observable returned from <code class="" data-line="">client.watchFragment</code> now includes a <code class="" data-line="">getCurrentResult</code> function to get the current value of the fragment</li>



<li><code class="" data-line="">@client</code> fields with read functions now receive <code class="" data-line="">undefined</code> for the cache value instead of <code class="" data-line="">null</code> when a resolver is not defined (<a href="https://github.com/apollographql/apollo-client/pull/12927">#12927</a>)</li>



<li>Support for callback functions as the context option on mutate (<a href="https://github.com/apollographql/apollo-client/pull/12927">#12927</a>)</li>



<li>Support the <code class="" data-line="">headers</code> transport for enhanced client awareness (<a href="https://github.com/apollographql/apollo-client/pull/13043">#13043</a>)</li>



<li><code class="" data-line="">InMemoryCache</code> no longer filters out explicitly returned <code class="" data-line="">undefined</code> items from <code class="" data-line="">read</code> functions for array fields (<a href="https://github.com/apollographql/apollo-client/pull/13056">#13056</a>)</li>



<li><code class="" data-line="">prerenderStatic</code> now exposes the return value to enable the use of <a href="https://react.dev/reference/react-dom/static/resumeAndPrerender"><code class="" data-line="">resumeAndPrerender</code></a> with React 19.2 (<a href="https://github.com/apollographql/apollo-client/pull/13071">#13071</a>)</li>



<li>Add support for the <code class="" data-line="">from</code> option used with <code class="" data-line="">useFragment</code> to <code class="" data-line="">client.readFragment</code>, <code class="" data-line="">cache.readFragment</code>, <code class="" data-line="">client.writeFragment</code>, <code class="" data-line="">cache.writeFragment</code>, and <code class="" data-line="">cache.updateFragment</code>. (<a href="https://github.com/apollographql/apollo-client/pull/13038">#13038</a>)</li>



<li>Cache <code class="" data-line="">merge</code> functions now receive <code class="" data-line="">extensions</code> returned in the response (<a href="https://github.com/apollographql/apollo-client/pull/13058">#13058</a>)</li>
</ul>



<p class="wp-block-paragraph">For a full list of changes, please see the <a href="https://github.com/apollographql/apollo-client/releases/tag/%40apollo%2Fclient%404.1.0">4.1 release notes</a>.</p>



<p class="wp-block-paragraph">Happy querying!</p>


@stream all the things with Apollo Client 4.1

Introducing Response Caching: GraphQL‑aware performance for your graph 


<p class="wp-block-paragraph">Recent security research has reinforced important considerations around Federated subgraph exposure. This work is increasingly critical as AI-powered tools make it easier than ever to discover and exploit publicly accessible services that were never intended to be exposed.</p>



<p class="wp-block-paragraph"><strong>Apollo Federation subgraphs are intended to remain internal services, accessible only through the router.</strong> This architectural requirement for isolation is fundamental to Federation&#8217;s security model. It also reflects a broader API strategy principle: centralized governance and observability through a unified access layer are essential to avoid API sprawl. This is not a vulnerability in Federation itself, but a deployment and trust-boundary issue that arises when internal services are exposed outside their intended architecture.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="340" src="https://wp.apollographql.com/wp-content/uploads/2026/01/image-2-1024x340.png" alt="Origin services should be protected behind a router; this depicts a federated diagram" class="wp-image-25022" srcset="https://wp.apollographql.com/wp-content/uploads/2026/01/image-2-1024x340.png 1024w, https://wp.apollographql.com/wp-content/uploads/2026/01/image-2-300x100.png 300w, https://wp.apollographql.com/wp-content/uploads/2026/01/image-2-768x255.png 768w, https://wp.apollographql.com/wp-content/uploads/2026/01/image-2-1536x511.png 1536w, https://wp.apollographql.com/wp-content/uploads/2026/01/image-2-1200x399.png 1200w, https://wp.apollographql.com/wp-content/uploads/2026/01/image-2.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">The router is designed to be the centralized security enforcement point, providing critical protections like access control, demand control, and operation safelisting. When subgraphs are inadvertently made public, they can bypass these protections, exposing internal coordination mechanisms that are intended only for router-to-subgraph communication.</p>



<p class="wp-block-paragraph">We will continue to make these security patterns prominent in our documentation and welcome ongoing collaboration with security researchers to help the Federation community build more secure GraphQL architectures.</p>



<h2 class="wp-block-heading"><a href="#understanding-federation-architecture" aria-hidden="true" class="aal_anchor" id="understanding-federation-architecture"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Understanding Federation Architecture</strong></h2>



<p class="wp-block-paragraph">Apollo Federation uses internal coordination fields to enable distributed graph functionality, allowing the router to query schemas and fetch entities across subgraph boundaries. GraphQL libraries serving Federated subgraphs automatically expose these coordination fields to maintain Federation compatibility, even when standard introspection is disabled for clients. These mechanisms exist by design as internal protocols that require a critical trust boundary: <strong>only the router should communicate with subgraphs</strong>.&nbsp; For this reason, subgraphs should operate behind the router with protections like network isolation and authentication preventing direct subgraph access. This further centralizes governance and security into the router.</p>



<p class="wp-block-paragraph">When subgraphs are directly accessible, you bypass the router&#8217;s security enforcement entirely and internal coordination mechanisms become information disclosure vectors equivalent to leaving introspection enabled.</p>



<h2 class="wp-block-heading"><a href="#recommended-security-practices" aria-hidden="true" class="aal_anchor" id="recommended-security-practices"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Recommended Security Practices</strong></h2>



<p class="wp-block-paragraph">If you&#8217;re running Apollo Federation, follow these practices to ensure proper security:&nbsp;</p>



<p class="wp-block-paragraph"><strong>API Discoverability</strong></p>



<ul class="wp-block-list">
<li><strong>Keep subgraphs internal </strong>&#8211;<strong> </strong>Subgraphs should only be accessible from your router, never directly from the public internet, enabling you to leverage its centralized governance and security enforcement. </li>



<li><strong>Turn off introspection in production</strong> &#8211; <a href="https://www.apollographql.com/blog/why-you-should-disable-graphql-introspection-in-production#turning-off-introspection-in-production">GraphQL&#8217;s built-in introspection query</a> reveals your entire schema to bad actors, but note this does not replace the need to keep subgraphs internal.</li>



<li><strong>Obfuscate error details</strong> &#8211; <a href="https://www.apollographql.com/docs/apollo-server/data/errors#omitting-or-including-stacktrace">Remove verbose error information</a> like stack traces from your production server </li>
</ul>



<p class="wp-block-paragraph"><strong>Defend Against Malicious Operations</strong></p>



<ul class="wp-block-list">
<li><strong>Validate and sanitize data</strong> &#8211; Apply standard input validation; use enums, custom scalars, and directives to codify validation in your schema</li>



<li><strong>Paginate fields</strong> &#8211; Set maximum limits on how many items can be requested at once</li>



<li><strong>Implement authentication/authorization in the router</strong> &#8211; Enforce auth at the entry point to drop invalid requests before they reach downstream services</li>



<li><strong>Set operation limits</strong> &#8211; Configure max depth, max root fields, and other request limits to prevent resource exhaustion</li>



<li><strong>Use operation cost analysis</strong> &#8211; Calculate operation costs and configure demand control for rate limiting based on query complexity</li>



<li><strong>Safelist with persisted queries</strong> &#8211; <a href="https://www.apollographql.com/blog/secure-your-graphql-platform-by-safelisting-known-queries">Register trusted operations</a> in a <a href="https://www.apollographql.com/docs/kotlin/advanced/persisted-queries">persisted query list</a> (PQL); router rejects unregistered operations</li>



<li><strong>Control batched requests</strong> &#8211; Limit query breadth and use cost analysis to prevent enumeration attacks through batching</li>



<li><strong>Set timeouts</strong> &#8211; Apply timeouts at HTTP server, router-to-subgraph, and individual operation levels</li>
</ul>



<p class="wp-block-paragraph"><strong>Additional Best Practices</strong></p>



<ul class="wp-block-list">
<li><strong>Client identification</strong> &#8211; Require clients to identify themselves so you can monitor schema usage. These are <a href="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/enabling-telemetry/usage-guides/client-id-enforcement">configurable headers</a> in the Apollo Router. </li>



<li><strong>Monitor with observability</strong> &#8211; Use tracing, alerts, and OpenTelemetry integration to track performance and errors</li>



<li><strong>Restrict write access</strong> &#8211; Use graph API keys, personal API keys, SSO, member roles, and protected variants to control who can modify schemas</li>
</ul>



<p class="wp-block-paragraph">For comprehensive implementation guidance, see our<a href="https://www.apollographql.com/docs/graphos/platform/security/overview"> GraphOS Security documentation</a>, <a href="https://www.apollographql.com/blog/secure-your-graphql-microservices">microservices security best practices</a>, and the <a href="https://www.apollographql.com/docs/graphos/resources/saf/security">Security section of the Supergraph Architecture Framework</a>.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#conclusion" aria-hidden="true" class="aal_anchor" id="conclusion"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Conclusion</strong></h2>



<p class="wp-block-paragraph">Apollo Federation&#8217;s security model is built on a fundamental principle: subgraphs are internal services that must only be accessed through the router. This isn&#8217;t a limitation – it&#8217;s the foundation that enables the router to enforce access control, demand control, and operation safelisting across your entire graph. As AI-powered tools make automated discovery and exploitation easier, maintaining this architectural boundary and implementing centralized governance through Apollo GraphOS isn&#8217;t just a best practice – it&#8217;s essential to protecting your API infrastructure.</p>


Securing Apollo Federation Subgraphs: Context and Best Practices


<p class="wp-block-paragraph">Apollo introduced the Long-Term Support (LTS) policy for the Router to give users a predictable, stable release cycle and the confidence to operate the Router in long-running or regulated production environments. The policy ensures teams can take advantage of new capabilities at their own pace, while always having a supported and secure baseline to rely on.</p>



<p class="wp-block-paragraph">To better support upgrade planning and provide greater clarity around version lifecycles, we are refining our Router LTS policy and introducing updates to the current maintenance schedule for both Router and Federation.</p>



<h2 class="wp-block-heading"><a href="#new-lts-release-router-v2-10-and-federation-v2-12" aria-hidden="true" class="aal_anchor" id="new-lts-release-router-v2-10-and-federation-v2-12"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>New LTS Release: Router v2.10 and Federation v2.12</h2>



<p class="wp-block-paragraph">To support users migrating from v1.x and to provide a dependable maintenance baseline on the Router v2.x platform, Apollo has released <strong>Router v2.10 with Federation v2.12</strong> as the next LTS version as of December 12, 2025.</p>



<p class="wp-block-paragraph"><strong>Router v2.10 and Federation v2.12 </strong></p>



<ul class="wp-block-list">
<li>Will receive <strong>critical security patches and essential reliability updates</strong> throughout its maintenance window until September 2026</li>



<li>Offers a stable upgrade target for users <a href="https://www.apollographql.com/docs/graphos/routing/upgrade/from-router-v1">transitioning from older Router versions.</a></li>



<li>Router v2.x will continue active development with future feature releases and new minor versions, while the v2.10 line will receive fixes via the new LTS policy (see below)</li>
</ul>



<h2 class="wp-block-heading"><a href="#end-of-support-for-router-v1-x-and-federation-v2-9" aria-hidden="true" class="aal_anchor" id="end-of-support-for-router-v1-x-and-federation-v2-9"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>End of Support for Router v1.x and Federation v2.9</h2>



<p class="wp-block-paragraph">Router v1.x, including v1.61.x LTS, and Federation v2.9 will reach <strong>End of Support (EOS) on March 31st, 2026</strong>.</p>



<p class="wp-block-paragraph">After EOS, these versions will no longer receive updates, including security or critical reliability fixes. Users operating on Router v1.x should begin planning their upgrade to the Router v2.x and Federation v2.12 line to remain on a supported version. Upgrading your Federation version can be done by changing the graph variant settings in Studio, or changing the federation composition version in your build configuration locally.</p>



<h2 class="wp-block-heading"><a href="#new-support-policy" aria-hidden="true" class="aal_anchor" id="new-support-policy"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>New Support Policy</h2>



<p class="wp-block-paragraph">With the End of Support for the Router v1.x line, we have <a href="https://www.apollographql.com/docs/graphos/resources/router-release-lifecycle">updated our LTS policy</a> to provide consistent and scheduled releases as we look forward to 2026.&nbsp;</p>



<ul class="wp-block-list">
<li>New major Router versions yearly with<strong> 12 months of Active development</strong></li>



<li>Recurring LTS releases <strong>every 6 months </strong>to provide continued support</li>



<li>LTS releases <strong>supported for 9 months</strong>, with an additional <strong>3 months </strong>of support for our <strong>Premier Support </strong>customers</li>



<li>New policy will start in 2026</li>
</ul>



<h2 class="wp-block-heading"><a href="#required-actions" aria-hidden="true" class="aal_anchor" id="required-actions"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Required Actions</h2>



<ul class="wp-block-list">
<li>If you are currently running <strong>Router v1.x</strong>, please <a href="https://www.apollographql.com/docs/graphos/routing/upgrade/from-router-v1">begin planning your upgrade path</a> before March 2026.</li>



<li>Router v2.10 (released December 2025) will serve as a strong, stable LTS target for teams seeking minimal operational risk.</li>



<li>After updating to Router v2.x, review and update your Federation composition settings in Apollo Studio to ensure you&#8217;re using a supported version (LTS or latest). Note that <strong>no changes to your subgraphs are required </strong>if you are already using Federation v2<strong>.</strong><br></li>
</ul>



<h2 class="wp-block-heading"><a href="#our-commitment" aria-hidden="true" class="aal_anchor" id="our-commitment"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Our Commitment</h2>



<p class="wp-block-paragraph">Apollo values your partnership and trust as we continue to innovate. We are here to support you through this transition to keep your API infrastructure powerful and future-proof.</p>



<p class="wp-block-paragraph"><br>For additional support, please visit our<a href="https://community.apollographql.com/t/migrate-apollo-federation-1-0-supergraphs-to-apollo-federation-2-0/8125"> Apollo Community</a> or, for GraphOS users, contact our Technical Support team at <a href="http://support.apollographql.com">support.apollographql.com</a></p>


End of Support for Router v1.x; Long-Term Support (LTS) Policy Update

Building Apps for ChatGPT with Apollo MCP Server and Apollo Client


<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="768" src="https://wp.apollographql.com/wp-content/uploads/2025/12/IMG_3963-1024x768.jpeg" alt="" class="wp-image-24889" srcset="https://wp.apollographql.com/wp-content/uploads/2025/12/IMG_3963-1024x768.jpeg 1024w, https://wp.apollographql.com/wp-content/uploads/2025/12/IMG_3963-300x225.jpeg 300w, https://wp.apollographql.com/wp-content/uploads/2025/12/IMG_3963-768x576.jpeg 768w, https://wp.apollographql.com/wp-content/uploads/2025/12/IMG_3963-1536x1152.jpeg 1536w, https://wp.apollographql.com/wp-content/uploads/2025/12/IMG_3963-2048x1536.jpeg 2048w, https://wp.apollographql.com/wp-content/uploads/2025/12/IMG_3963-1200x900.jpeg 1200w, https://wp.apollographql.com/wp-content/uploads/2025/12/IMG_3963-1980x1485.jpeg 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<div class="wp-block-group is-nowrap is-layout-flex wp-container-core-group-is-layout-8f761849 wp-block-group-is-layout-flex">
<p class="wp-block-paragraph">Today, we’re excited to share that Apollo GraphQL is opening its new San Francisco headquarters at 201 California Street, between Embarcadero and Jackson Square.</p>
</div>



<p class="wp-block-paragraph">Apollo has always had a presence in San Francisco, but this move represents a deliberate strengthening of that footprint to support our mission of helping developers build the world. The new office expands our capacity and is designed to foster collaboration, customer meetings, and opportunities for our team to connect and build relationships. More importantly, this move reinforces our long-term investment in San Francisco as a center of innovation and talent – with the AI landscape evolving at an extraordinary pace, being present where the most important technical conversations are happening is critical.</p>



<p class="wp-block-paragraph">We’ll also continue to remain a distributed company; remote work is core to how we operate and we are <a href="https://www.apollographql.com/careers">actively hiring</a> across a number of roles. But there&#8217;s no substitute for what happens when great minds gather in one space during moments of technical inflection. Having a dedicated office in San Francisco allows us to accelerate thinking and decision-making while building at the forefront of a new agentic era.</p>



<p class="wp-block-paragraph">If you&#8217;re in the city, let us know. We&#8217;d love to see you.</p>


Apollo Strengthens Its San Francisco Presence for the Agentic Era


<p class="wp-block-paragraph">Today we&#8217;re announcing the general availability of Apollo MCP Server 1.0!</p>



<p class="wp-block-paragraph">If you&#8217;re building agentic applications, you know the challenge: LLMs need reliable, efficient access to your APIs. MCP provides the standard for this connection, and Apollo MCP Server provides a standard-based way to connect any GraphQL API to LLMs. As teams race from experiments to production in this emerging agentic world, the Apollo MCP Server is the powerful, supported, and reliable tool they need.</p>



<h2 class="wp-block-heading"><a href="#what-apollo-mcp-server-does" aria-hidden="true" class="aal_anchor" id="what-apollo-mcp-server-does"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What Apollo MCP Server Does</strong></h2>



<p class="wp-block-paragraph">At its core, Apollo MCP Server turns your GraphQL API into MCP tools. In turn, any MCP client, like Claude Desktop, Cursor, Goose, or your custom agent, can discover and use those tools.</p>



<h3 class="wp-block-heading"><a href="#core-functionality" aria-hidden="true" class="aal_anchor" id="core-functionality"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Core Functionality</strong></h3>



<p class="wp-block-paragraph"><strong>Your GraphQL operations become MCP tools.</strong> Save a query like GetCustomerOrders in your operations file or the GraphOS operation collection, and it&#8217;s instantly available as an MCP tool. No wrapper code, no manual tool definitions. The operation you test in the GraphOS Studio Explorer is exactly what your agent executes.</p>



<p class="wp-block-paragraph"><strong>Hot-reloading accelerates development.</strong> Change your GraphQL operations, and they&#8217;re immediately available to your agent. No restart, no rebuild. This tight feedback loop is essential when you&#8217;re iterating on agent behaviors and discovering what operations actually work.</p>



<p class="wp-block-paragraph"><strong>Agents can explore your schema intelligently.</strong> In addition to exposing GraphQL operations, the built-in introspection and execute tools let agents interact with your API dynamically, enabling a wide range of agentic workflows. This means your agent can not only execute predefined operations, but a user can also ask an agent questions like &#8220;what fields are available on the Customer type?&#8221; and receive structured answers. These tools can be disabled if an available agents&#8217; actions need to be more narrowly scoped.</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/blog/smart-schema-discovery-how-apollo-mcp-server-maximizes-ai-context-efficiency"><strong>Semantic search makes discovery efficient</strong></a><strong>.</strong> Instead of processing your entire schema (expensive in tokens), agents can search for relevant types and fields. Looking for inventory data? The search tool returns just the relevant parts: Product.inventory, Warehouse.stockLevels, Order.inventorySnapshot. This focused discovery keeps context windows lean.</p>



<p class="wp-block-paragraph"><strong>Efficient use of tokens.</strong> GraphQL, out-of-the-box, can be very precise with data, saving on token costs and reducing the risk of hallucination through context pollution. For agents using `introspect` or `search`, Apollo MCP Server also supports minification of their results to help optimize the context window usage. When you&#8217;re paying per token and working within context limits, these savings add up quickly across thousands of agent interactions.</p>



<p class="wp-block-paragraph"><strong>Persisted queries provide production safety.</strong> Instead of allowing any arbitrary queries, you can restrict them to a pre-approved set of persisted operations. Each query gets a unique ID, and agents can only execute operations from your manifest. This prevents malicious or expensive queries while maintaining the flexibility to update your operation set as needs evolve.</p>



<p class="wp-block-paragraph"><strong>Contracts shape what agents can see.</strong> Using <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/contracts/overview">Apollo Contracts</a>, you can create different views of your schema for different agents. Your customer support agent sees customer data and order information, but not internal pricing margins. Your analytics agent accesses aggregated data but not personally identifiable information. Same underlying GraphQL API, different bounded contexts.</p>



<h3 class="wp-block-heading"><a href="#operational-features" aria-hidden="true" class="aal_anchor" id="operational-features"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Operational Features</strong></h3>



<p class="wp-block-paragraph"><strong>OAuth keeps your MCP Server secure.</strong> We implemented the <a href="https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization">MCP Spec</a> so that your MCP Server can perform authorization with the same identity providers as the rest of your stack. JWT validation, audience restrictions, dynamic client registration, and scope enforcement all work as expected. Read more in our<a href="https://www.apollographql.com/blog/introducing-authorization-for-apollo-mcp-server"> authorization blog post</a>.</p>



<p class="wp-block-paragraph"><strong>Flexible transport options.</strong> Use stdio transport for local development with tools like MCP Inspector. Switch to streamable HTTP for remote production MCP Servers behind load balancers. The same configuration works across environments with environment variable overrides.</p>



<p class="wp-block-paragraph"><strong>YAML configuration with environment variables.</strong> Define your configuration in YAML, override with environment variables for different deployments. Standard DevOps practices, no surprises.</p>



<p class="wp-block-paragraph"><strong>Health monitoring enables reliable deployments.</strong> Liveness and readiness probes with configurable thresholds integrate with Kubernetes, load balancers, and monitoring systems. Know when your MCP server is healthy and ready to handle agent requests.</p>



<h3 class="wp-block-heading"><a href="#whats-new-in-1-0" aria-hidden="true" class="aal_anchor" id="whats-new-in-1-0"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What&#8217;s New in 1.0</strong></h3>



<p class="wp-block-paragraph"><strong>OpenTelemetry integration brings observability.</strong> AI agents create unpredictable usage patterns and complex request flows.The Apollo MCP Server&#8217;s OpenTelemetry integration provides the visibility you need to run a reliable service for AI agents. You can monitor agent behavior (which tools and operations are used most frequently), performance (response times and bottlenecks across tool executions), reliability (error rates and request success patterns), and distributed request flows (complete traces from agent request through your Apollo Router and subgraphs, with automatic trace context propagation). The server <a href="https://www.apollographql.com/docs/apollo-mcp-server/telemetry">exports metrics, traces</a>, and events to any OTLP-compatible collector, integrating seamlessly with your existing observability stack.</p>



<p class="wp-block-paragraph"><strong>CORS support enables browser-based agents.</strong> Web applications can now connect directly to Apollo MCP Server. Build agent interfaces that run entirely in the browser, or integrate AI capabilities into existing web apps. Configure allowed origins, handle credentials properly, maintain security.</p>



<p class="wp-block-paragraph"><strong>Production ready.</strong> Version 1.0 marks Apollo MCP Server as stable and production-ready. You can continue to engage with us on <a href="https://github.com/apollographql/apollo-mcp-server">GitHub</a>, the <a href="https://community.apollographql.com/c/mcp-server/41">Apollo Community</a>, and via the standard Apollo channels.</p>



<h2 class="wp-block-heading"><a href="#the-graphql-advantage-for-agents" aria-hidden="true" class="aal_anchor" id="the-graphql-advantage-for-agents"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>The GraphQL Advantage for Agents</strong></h2>



<p class="wp-block-paragraph">We&#8217;ve written before about<a href="https://www.apollographql.com/blog/the-future-of-mcp-is-graphql"> why GraphQL makes sense for AI agents</a> and<a href="https://www.apollographql.com/blog/building-efficient-ai-agents-with-graphql-and-apollo-mcp-server"> how GraphQL optimizes token usage</a>. Here&#8217;s the practical reality:</p>



<p class="wp-block-paragraph"><strong>Single request for related data.</strong> A REST-based agent might need five API calls to gather customer order details. With GraphQL, it&#8217;s one query that fetches exactly what&#8217;s needed. Lower latency, fewer tokens, simpler agent logic.</p>



<p class="wp-block-paragraph"><strong>Self-documenting schema.</strong> GraphQL schemas include descriptions, types, and relationships. Agents don&#8217;t just see that a customerId field exists &#8211; they understand it&#8217;s an ID type that references the Customer object. This semantic understanding helps agents make better decisions about which operations to use.</p>



<p class="wp-block-paragraph"><strong>Type safety prevents errors.</strong> Strong typing means agents know exactly what inputs each operation expects and what data they&#8217;ll receive back. No more runtime surprises when an API returns unexpected nulls or different data types.</p>



<p class="wp-block-paragraph"><strong>Declarative relationship handling.</strong> This is where GraphQL really shines for agents. Instead of writing code to orchestrate multiple API calls, you express relationships declaratively in your query. The agent says what it needs, and GraphQL figures out how to get it efficiently.</p>



<p class="wp-block-paragraph">Consider what happens without this orchestration layer. Either you write custom code for every possible API call sequence (brittle, time-consuming), or you let the LLM figure out how to chain REST APIs together (unpredictable, error-prone). GraphQL provides a principled middle ground &#8211; relationships are defined in the schema, traversal happens predictably.</p>



<p class="wp-block-paragraph">Yes, building a GraphQL schema requires upfront investment. We&#8217;re working on making this easier with tools like Apollo Connectors. But once you have that schema, it becomes the foundation for reliable agent interactions. No more writing orchestration code for each new use case. No more hoping the LLM correctly sequences API calls.</p>



<h2 class="wp-block-heading"><a href="#looking-ahead" aria-hidden="true" class="aal_anchor" id="looking-ahead"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Looking Ahead</h2>



<p class="wp-block-paragraph">Apollo MCP Server 1.0 serves GraphQL APIs today, but we see a broader opportunity. What if you could connect AI agents to any API or data source &#8211; REST, gRPC, databases &#8211; and Apollo handled the orchestration? This vision extends beyond just GraphQL to become the declarative orchestration platform for all AI-application interactions.</p>



<p class="wp-block-paragraph">We&#8217;re already exploring this with <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a>, which bring REST APIs into GraphQL without modification. The primitives are falling into place: schema federation, contract-based boundaries, and now MCP integration. Each piece moves us closer to a universal orchestration layer &#8211; not just for GraphQL, but for the entire stack that AI agents need to access.</p>



<h2 class="wp-block-heading"><a href="#get-started-today" aria-hidden="true" class="aal_anchor" id="get-started-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get Started Today</h2>



<p class="wp-block-paragraph">Ready to connect your AI agents to GraphQL APIs? <a href="https://www.apollographql.com/docs/apollo-mcp-server">Apollo MCP Server 1.0</a> is available today. Install it, connect your supergraph, and see how declarative orchestration transforms your AI applications.&nbsp;</p>



<p class="wp-block-paragraph">Have feedback or interesting use cases? File issues on <a href="https://github.com/apollographql/apollo-mcp-server">GitHub</a> or share your experiences in our <a href="https://community.apollographql.com/tag/mcp">community</a> &#8211; your input directly shapes our roadmap.</p>


Apollo MCP Server 1.0 is Generally Available


<p class="wp-block-paragraph">Today we’re launching <strong><a href="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/apm-guides/datadog/connecting-to-datadog">APM dashboard templates for Datadog</a></strong>, so platform and SRE teams can get <strong>best practices observability</strong> into GraphOS Router performance in just minutes. Previously teams would need to determine the important information to monitor, what telemetry is available, and then how to configure the dashboards. This could take hours or days of an engineers time to initially set up and refine over time.</p>



<p class="wp-block-paragraph">Whether you’re just turning on tracing or you’ve been running <a href="https://www.apollographql.com/graphos">Apollo GraphOS</a> at scale for years, these dashboards provide a clear, shared view of the <a href="https://www.apollographql.com/graphos-router">GraphOS Router</a>, <a href="https://www.apollographql.com/docs/graphos/resources/glossary?docs%5Bquery%5D=supergraph">supergraph</a>, and subgraph health in minutes, just import and go. </p>



<h2 class="wp-block-heading"><a href="#turn-key-observability-for-datadog" aria-hidden="true" class="aal_anchor" id="turn-key-observability-for-datadog"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Turn-key observability for Datadog</strong></h2>



<p class="wp-block-paragraph">Operating a supergraph is a team sport. When latency spikes or error rates climb, you need to answer:</p>



<ul class="wp-block-list">
<li>Is it the <strong>router</strong>, a <strong>specific subgraph</strong>, or <strong>client behavior</strong>?</li>



<li>Is the issue limited to a region, version, or deployment?</li>



<li>What changed right before the incident? </li>
</ul>



<p class="wp-block-paragraph">Our Datadog templates + GraphOS Router instrumentation answer those questions:</p>



<ul class="wp-block-list">
<li><strong>Clear, consistent operations:</strong> Spans and metrics are mapped into Datadog with <strong>stable operation and resource names</strong>, so charts and traces line up.</li>



<li><strong>First-class GraphQL error tracking:</strong> GraphQL errors are promoted into APM error views and correlated with latency.</li>



<li><strong>Supergraph ↔ subgraph drill-down:</strong> See end-to-end behavior, then pivot to the slow or noisy subgraph instantly. </li>
</ul>



<h2 class="wp-block-heading"><a href="#what-youll-see-in-datadog" aria-hidden="true" class="aal_anchor" id="what-youll-see-in-datadog"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What you’ll see in Datadog</strong></h2>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="495" src="https://wp.apollographql.com/wp-content/uploads/2025/10/datadog-dashboard-1024x495.png" alt="" class="wp-image-24767" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/datadog-dashboard-1024x495.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/10/datadog-dashboard-300x145.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/10/datadog-dashboard-768x371.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/10/datadog-dashboard-1536x742.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/10/datadog-dashboard-2048x989.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/10/datadog-dashboard-1200x580.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/10/datadog-dashboard-1980x956.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Figure: Apollo Router latency overview</figcaption></figure>



<ul class="wp-block-list">
<li><a href="https://sre.google/sre-book/monitoring-distributed-systems/#xref_monitoring_golden-signals"><strong>Golden signals</strong></a><strong> at the top:</strong> Requests, p95/p99, error rate, saturation.</li>



<li><strong>GraphQL errors:</strong> Surfaced as first-class errors with example traces.</li>



<li><strong>Subgraph focus views:</strong> Rank subgraphs by latency contribution and error impact.</li>



<li><strong>Operation insights:</strong> Identify the slowest or flakiest operations and track regressions by version.</li>



<li><strong>Deploy &amp; version overlays:</strong> Correlate performance shifts with version rollouts and activity.</li>
</ul>



<h2 class="wp-block-heading"><a href="#get-started-with-the-new-dashboard-templates" aria-hidden="true" class="aal_anchor" id="get-started-with-the-new-dashboard-templates"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Get started with the new dashboard templates</strong></h2>



<h3 class="wp-block-heading"><a href="#connect-apollo-router-to-datadog" aria-hidden="true" class="aal_anchor" id="connect-apollo-router-to-datadog"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Connect Apollo Router to Datadog</strong></h3>



<p class="wp-block-paragraph">Set up metric ingestion for <a href="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/apm-guides/datadog/connecting-to-datadog">Datadog</a> based on your preferred method:</p>



<ul class="wp-block-list">
<li><a href="https://docs.datadoghq.com/opentelemetry/setup/"><strong>Datadog OpenTelemetry Collector (DDOT)</strong></a> – straightforward if you’re already Datadog-centric.</li>



<li><a href="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/apm-guides/datadog/connecting-to-datadog/otel-collector"><strong>OpenTelemetry Collector</strong></a> – vendor-neutral with powerful processors/sampling.</li>



<li><a href="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/apm-guides/datadog/connecting-to-datadog/datadog-agent/datadog-agent-traces"><strong>Datadog Agent</strong></a> – direct OTLP ingestion alongside your existing Datadog infra agent.</li>



<li><a href="https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest/"><strong>Agentless</strong></a> – when you want no agents at all.</li>
</ul>



<h3 class="wp-block-heading"><a href="#configure-the-router-to-emit-the-needed-instrumentation" aria-hidden="true" class="aal_anchor" id="configure-the-router-to-emit-the-needed-instrumentation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Configure the </strong><strong>Router to emit the needed instrumentation</strong></h3>



<p class="wp-block-paragraph">Add the <a href="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/apm-guides/datadog/router-instrumentation" data-type="link" data-id="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/apm-guides/datadog/router-instrumentation">required opentelemetry settings</a> to the Router’s configuration file, tailoring resource.name and tags to your conventions (service, environment, version, region) if needed. Restart the router so that the new configuration can be applied.</p>



<h3 class="wp-block-heading"><a href="#install-the-dashboard-template" aria-hidden="true" class="aal_anchor" id="install-the-dashboard-template"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Install the dashboard template</strong></h3>



<p class="wp-block-paragraph">Inside the Datadog console, <a href="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/apm-guides/datadog/observing-and-monitoring/dashboard-template">import</a> the new dashboards: <strong>Dashboards → New Dashboard → Import JSON</strong> and then paste our <a href="https://github.com/apollographql/apm-templates/blob/main/datadog/graphos-template.json">template</a>.</p>



<p class="wp-block-paragraph">Set the template variables (service/env/version/region) to match your Datadog tags. You should see the dashboard graphs begin to populate within minutes.</p>



<p class="wp-block-paragraph">That’s it! Your supergraph’s APM story is live in Datadog</p>



<h2 class="wp-block-heading" id="Managing-your-observability-costs"><a href="#managing-your-observability-costs" aria-hidden="true" class="aal_anchor" id="managing-your-observability-costs"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Managing your observability costs</strong></h2>



<p class="wp-block-paragraph">In order to optimize observability costs, we recommend keeping <code class="" data-line="">resource.name</code> low cardinality by using stable values such as <code class="" data-line="">operation_kind</code> or <code class="" data-line="">subgraph.name</code>, and avoid embedding IDs or other highly variable strings.</p>



<p class="wp-block-paragraph">For high-throughput services, enable tail-based sampling in your OTLP collector to retain the most useful traces while controlling cost, and explicitly exempt error traces so failures always surface.</p>



<p class="wp-block-paragraph">Finally, apply Datadog’s Unified Service Tagging (service, env, version) consistently across traces and metrics so dashboard filters and version overlays behave reliably across teams.</p>



<h2 class="wp-block-heading"><a href="#questions-or-feedback" aria-hidden="true" class="aal_anchor" id="questions-or-feedback"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Questions or feedback?</h2>



<p class="wp-block-paragraph">Check out our <a href="https://www.apollographql.com/docs/graphos/routing/observability/router-telemetry-otel/apm-guides/datadog/connecting-to-datadog">documentation</a> to learn more about setting up and using these dashboards. We’d love to <a href="https://community.apollographql.com/t/announcing-apm-dashboard-templates-for-datadog">hear</a> how these dashboards are working for your team and what you want to see next.<br></p>


GraphOS Router APM Dashboard Templates for Datadog


<p class="wp-block-paragraph">Apollo iOS 2.0 is here, and it’s the biggest reimagining of our Swift client yet. Built from the ground up for Swift’s modern concurrency model, this release delivers snappier performance, stronger type guarantees, and a cleaner developer experience for teams shipping GraphQL-powered apps across Apple platforms.</p>



<h2 class="wp-block-heading"><a href="#improved-apis" aria-hidden="true" class="aal_anchor" id="improved-apis"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Improved APIs</h2>



<p class="wp-block-paragraph">Swift’s structured concurrency and the <code class="" data-line="">async</code>/<code class="" data-line="">await</code> syntax weren’t just sugar, they introduced an entirely new mental model for reasoning about work, isolation, and cancellation. With Swift 6 enforcing strict concurrency checks today, you need APIs that prove data is safe as it crosses actors and tasks. Apollo iOS 2.0 leans into that world: the client surface is <code class="" data-line="">Sendable</code>-aware, network requests naturally compose with tasks, and the compiler can flag data races before they ship. Instead of juggling completion handlers and manual thread hops, your GraphQL workflows read like straightforward, sequential Swift while still benefiting from the runtime’s scheduling and cancellation semantics.</p>



<p class="wp-block-paragraph">Current Apollo iOS users will notice the difference at the call site immediately. A familiar completion-handler fetch looks like this:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-swift" data-line="">apollo.fetch(query: HeroQuery()) { result in
  switch result {
  case .success(let graphQLResult):
    updateUI(with: graphQLResult.data)
  case .failure(let error):
    handle(error)
  }
}</code></pre>



<p class="wp-block-paragraph">In Apollo iOS 2.0, the same work becomes a single <code class="" data-line="">async</code> expression that fits naturally inside your task flow:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-swift" data-line="">let response = try await apollo.fetch(query: HeroQuery())
updateUI(with: response.data)</code></pre>



<p class="wp-block-paragraph">The benefits extend beyond ergonomics. <code class="" data-line="">ApolloClient</code>, <code class="" data-line="">ApolloStore</code>, request and response models, interceptors, and cache policies all conform to <code class="" data-line="">Sendable</code>, so they can pass safely across concurrency boundaries. The APIs themselves are streamlined, with clearer separation between transport, cache, and request layers. Once you’ve adjusted to the concurrency-first idioms, your codebase is better prepared for the evolution of Apple’s platforms and the reliability expectations that come with them.</p>



<h2 class="wp-block-heading"><a href="#modernizations-deprecations-and-websockets" aria-hidden="true" class="aal_anchor" id="modernizations-deprecations-and-websockets"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Modernizations, deprecations, and WebSockets</h2>



<p class="wp-block-paragraph">Before you upgrade, there are a few logistical checkpoints. Deployment targets move to iOS 15, macOS 12, tvOS 15, watchOS 8, and visionOS 1. CocoaPods support is retired, so Swift Package Manager and prebuilt XCFrameworks are the supported distribution paths. If you’re using GraphQL subscriptions, note that 2.0 supports HTTP-based subscriptions only for now, but an updated WebSocket implementation is our next priority and will be released in an upcoming minor version. If your app depends on subscriptions over web sockets, you will need to hold off on upgrading until then.</p>



<h2 class="wp-block-heading"><a href="#migration-path" aria-hidden="true" class="aal_anchor" id="migration-path"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Migration path</h2>



<p class="wp-block-paragraph">We’ve structured the migration to de-risk the journey. Start with the breaking pieces: custom interceptors, network transports, cache implementations, and request/response models all need to adopt the new structured APIs. Once that foundation is in place, you can modernize the rest of your client code gradually. The deprecated 1.x calls now conform to <code class="" data-line="">Sendable</code>, so your app continues to compile while you migrate queries, mutations, and subscriptions at whatever pace your release schedule allows.</p>



<h2 class="wp-block-heading"><a href="#upgrade-today" aria-hidden="true" class="aal_anchor" id="upgrade-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Upgrade today</h2>



<p class="wp-block-paragraph">Grab Apollo iOS 2.0 via SPM, update your codegen configuration, and start converting call sites to <code class="" data-line="">async</code>/<code class="" data-line="">await</code>. The migration guide at <a href="https://www.apollographql.com/docs/ios/v2/migrations/2.0">https://www.apollographql.com/docs/ios/v2/migrations/2.0</a> walks through every change in detail, with practical examples and notes to keep you unblocked. We can’t wait to see the apps you build on top of this new foundation! Let us know what you ship and how we can keep smoothing the path forward.</p>


Announcing Apollo iOS 2.0

GraphQL Summit 2025 Product Highlights: Building the future of AI and Apps


<p class="wp-block-paragraph">Today, we&#8217;re introducing <strong>Subgraph and Connector-level insights</strong> in <a href="https://www.apollographql.com/graphos/studio">GraphOS Studio</a>. This feature enables teams to quickly understand their services’ behavior in the context of a larger federated graph. Such insights help teams identify issues and proactively improve performance.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#the-problem-flying-blind-in-your-own-graph" aria-hidden="true" class="aal_anchor" id="the-problem-flying-blind-in-your-own-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>The Problem: Flying Blind in Your Own Graph</strong></h2>



<p class="wp-block-paragraph">In a federated GraphQL architecture, your subgraph or <a href="https://www.apollographql.com/graphos/apollo-connectors">connector</a> doesn&#8217;t exist in isolation. It&#8217;s part of a larger system where client queries span multiple services, and performance bottlenecks can cascade across the entire graph. Until now, engineers responsible for specific subgraphs or connectors could not see how their services were operating in GraphOS. They could only look at aggregate performance of the larger supergraph, or detailed performance of specific objects and fields. Those numbers don&#8217;t tell you:</p>



<ul class="wp-block-list">
<li>Which clients are hitting your subgraph the hardest</li>



<li>What operations are causing your service to slow down</li>



<li>How your performance compares to other subgraphs in the system</li>



<li>Whether that recent deployment had a positive impact</li>
</ul>



<p class="wp-block-paragraph">This lack of visibility made it difficult to proactively optimize performance or quickly triage incidents when they occurred.</p>



<h2 class="wp-block-heading"><a href="#what-we-built-your-subgraph-under-the-microscope" aria-hidden="true" class="aal_anchor" id="what-we-built-your-subgraph-under-the-microscope"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What We Built: Your Subgraph Under the Microscope</strong></h2>



<p class="wp-block-paragraph">Subgraph-level insights provide backend developers with unprecedented visibility into their specific APIs&#8217; performance. Think of it as a dedicated dashboard for your corner of the federated graph. Thanks to subgraph insights, you can now:</p>



<h3 class="wp-block-heading"><a href="#find-your-biggest-impact-opportunities" aria-hidden="true" class="aal_anchor" id="find-your-biggest-impact-opportunities"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Find your biggest impact opportunities</strong> </h3>



<p class="wp-block-paragraph">The Top Traffic Sources widgets show you exactly which clients or operations are generating the highest error rates and request volumes. No more guessing about where to focus your optimization efforts.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="433" src="https://wp.apollographql.com/wp-content/uploads/2025/10/image-5-1024x433.png" alt="" class="wp-image-24712" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/image-5-1024x433.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/10/image-5-300x127.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/10/image-5-768x325.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/10/image-5-1536x650.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/10/image-5-2048x867.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/10/image-5-1200x508.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/10/image-5-1980x838.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#discover-your-most-common-errors" aria-hidden="true" class="aal_anchor" id="discover-your-most-common-errors"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Discover your most common errors</strong></h3>



<p class="wp-block-paragraph"> The subgraphs Errors dashboard highlights error distribution patterns as well as providing details around which operations failed. No matter the granularity, you can always see where your service is struggling.&nbsp;&nbsp;&nbsp;&nbsp;</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="450" src="https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-errors-1024x450.png" alt="" class="wp-image-24714" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-errors-1024x450.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-errors-300x132.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-errors-768x337.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-errors-1536x674.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-errors-2048x899.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-errors-1200x527.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-errors-1980x869.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#spot-patterns-before-they-become-problems" aria-hidden="true" class="aal_anchor" id="spot-patterns-before-they-become-problems"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Spot patterns before they become problems</h3>



<p class="wp-block-paragraph"> The Latency Heatmap, Error Rate, and Request Rate charts reveal trends over different time horizons. Whether it&#8217;s a daily traffic pattern or a weekly spike in errors, you&#8217;ll be able to catch it using your subgraph insights page.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="494" src="https://wp.apollographql.com/wp-content/uploads/2025/10/SB-Insights-patterns-1024x494.png" alt="" class="wp-image-24716" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/SB-Insights-patterns-1024x494.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-Insights-patterns-300x145.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-Insights-patterns-768x371.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-Insights-patterns-1536x741.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-Insights-patterns-2048x988.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-Insights-patterns-1200x579.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-Insights-patterns-1980x955.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#sort-graphs-to-see-how-you-compare" aria-hidden="true" class="aal_anchor" id="sort-graphs-to-see-how-you-compare"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Sort graphs to see how you compare</h3>



<p class="wp-block-paragraph">Stack rank your subgraph&#8217;s request rate, latency, and error rates against other services using the “Sort subgraphs by” function. This&nbsp; context helps you understand when performance issues are localized to your subgraph or part of a broader system trend.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="497" src="https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insighs-sort-1024x497.png" alt="" class="wp-image-24718" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insighs-sort-1024x497.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insighs-sort-300x146.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insighs-sort-768x373.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insighs-sort-1536x745.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insighs-sort-2048x994.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insighs-sort-1200x582.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insighs-sort-1980x961.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#say-something-when-you-see-something" aria-hidden="true" class="aal_anchor" id="say-something-when-you-see-something"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Say something when you see something</h3>



<p class="wp-block-paragraph"> The subgraph owner info (which is derived from any&nbsp; @contact directive tags in your schema), gives you the information you need to reach out to the appropriate team if something is wrong.&nbsp;&nbsp;</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="475" src="https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-contact-owner-1024x475.png" alt="" class="wp-image-24720" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-contact-owner-1024x475.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-contact-owner-300x139.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-contact-owner-768x356.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-contact-owner-1536x712.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-contact-owner-2048x949.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-contact-owner-1200x556.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/10/SB-insights-contact-owner-1980x918.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#how-it-works-data-collection-for-service-owners" aria-hidden="true" class="aal_anchor" id="how-it-works-data-collection-for-service-owners"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How It Works: Data Collection for Service Owners&nbsp;</h2>



<p class="wp-block-paragraph">Apollo Router resolves a federated query by retrieving data from multiple services defined in the operation’s query plan. Each request the Router makes against a downstream service is called a fetch. Starting in Router 2.7.0, the Router measures the latency of every fetch made to a subgraph or connector.&nbsp; Apollo captures this data and uses it to present subgraph insights in our Studio UI.&nbsp;&nbsp;</p>



<p class="wp-block-paragraph">Router will still report subgraph fetch latency data through the <a href="https://www.apollographql.com/docs/graphos/routing/observability/telemetry/instrumentation/instruments#opentelemetry-standard-instruments">standard OTel instrument</a>, http.client.request.duration. Customers can export their subgraph fetch data to their teams’ APM tooling, as well as enrich the information with customized attributes.</p>



<h2 class="wp-block-heading"><a href="#getting-started-enable-insights-in-minutes" aria-hidden="true" class="aal_anchor" id="getting-started-enable-insights-in-minutes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Getting Started: Enable Insights in Minutes</strong></h2>



<p class="wp-block-paragraph">Subgraph insights is currently offered as a generally available, opt-in feature. If you&#8217;re already running a federated graph with Apollo Router 2.7.0+, enabling subgraph insights takes just a few lines of configuration: </p>



<p class="wp-block-paragraph">yaml</p>



<pre class="wp-block-code"><code class="" data-line="">telemetry:
  apollo:
    preview_subgraph_metrics: true # default: false</code></pre>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph"><strong>Note:</strong> In Apollo Router 2.8.0+ the configuration will be renamed to telemetry.apollo.subgraph_metrics.</p>
</blockquote>



<p class="wp-block-paragraph">You’re now ready to see your subgraph insights! Simply return to your GraphOS Studio insights page, filter by subgraphs, and start exploring your performance data.</p>



<h2 class="wp-block-heading"><a href="#no-surprises-pricing-and-availability" aria-hidden="true" class="aal_anchor" id="no-surprises-pricing-and-availability"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>No Surprises: Pricing and Availability</strong></h2>



<p class="wp-block-paragraph">Subgraph-level insights is part of our continued commitment to empower developers with the tools they need to build and maintain high-performance GraphQL APIs. It is available to all GraphOS Studio customers running Router 2.7.0+, regardless of <a href="https://www.apollographql.com/pricing">plan</a>. There are no additional costs, and metrics respect your existing data retention policies.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#looking-ahead-whats-next" aria-hidden="true" class="aal_anchor" id="looking-ahead-whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Looking Ahead: What’s Next</strong></h2>



<p class="wp-block-paragraph">Subgraph-level insights represent more than just new metrics. It&#8217;s about democratizing observability in federated architectures. When every backend developer can see how their service fits into the larger system, the entire graph gets better.&nbsp;</p>



<p class="wp-block-paragraph">Visibility can only go so far though if it isn’t easily accessible. To ensure every developer can benefit from our subgraph insights we’ll be working to turn subgraph insights on by default in future Router versions. We’ll also provide subgraph insights data in the platform API for further extensibility.&nbsp;&nbsp;</p>



<p class="wp-block-paragraph">Ready to get unprecedented visibility into your subgraph performance? Enable insights in your Router configuration and start exploring your data in GraphOS Studio today.&nbsp;</p>



<p class="wp-block-paragraph">Want to learn more? Check out our <a href="https://apollographql.com/docs/graphos/platform/insights/subgraphs">documentation</a> for detailed setup instructions and best practices. <a href="https://community.apollographql.com/t/subgraph-and-connector-insights/9484">Reach out and share your reactions</a> as you start working with subgraph insights. Your feedback will shape how these capabilities evolve.</p>



<p class="wp-block-paragraph"><em>Note: Ross Regitsky also contributed to this blog post. </em></p>


Subgraph and Connector Insights: Empowering Developers Through Endpoint Observability


<p class="wp-block-paragraph">We’re thrilled to announce the release of <a href="https://apollographql.com/docs/graphos/platform/access-management/api-keys#subgraph-api-keys">subgraph API keys</a>!</p>



<p class="wp-block-paragraph">Subgraph API keys are designed to scope permissions to a specific subgraph, or set of subgraphs, within your organization&#8217;s graph, and are ideal for CI/CD workflows.&nbsp; Until now, individual development teams have used Graph API keys in their deployment pipelines, giving them full access to a federated graph. In contrast, Subgraph keys provide more narrowly scoped permissions to only a select set of subgraphs, improving security and reducing risk.</p>



<h2 class="wp-block-heading"><a href="#what-customer-problems-do-subgraph-api-keys-solve" aria-hidden="true" class="aal_anchor" id="what-customer-problems-do-subgraph-api-keys-solve"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What customer problems do subgraph API keys solve?</h2>



<p class="wp-block-paragraph">API keys allow GraphOS to identify actors and the permissions those actors have in the system.&nbsp;</p>



<p class="wp-block-paragraph">Until now, Apollo customers have typically used a graph API key to interact with GraphOS in their build and deployment pipeline automation. However, graph API keys are scoped to an entire federated supergraph. This means that in the worst case, Team A could push a change to their pipeline and accidentally make changes to Team B’s subgraph. As the number of individual teams contributing to a federated graph grows, the risk of a team making changes outside its area of ownership grows as well. </p>



<p class="wp-block-paragraph">For many customers, graph API keys grant too many permissions at too high a level. This means they don’t follow the “principle of least permissions”, a security best practice for mature organizations. <br></p>



<h2 class="wp-block-heading"><a href="#what-are-subgraph-api-keys" aria-hidden="true" class="aal_anchor" id="what-are-subgraph-api-keys"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What are subgraph API keys?</h2>



<p class="wp-block-paragraph">Subgraph API keys are designed to scope permissions to a specific subgraph, or set of subgraphs, within your organization&#8217;s graph. When you create a subgraph key, you specify the desired subgraphs (and their variants) that you want to be able to change. Using a subgraph key therefore ensures that only the specified subgraphs can be modified when this key is used.</p>



<p class="wp-block-paragraph">Subgraph keys are ideal for use in CI/CD pipelines and deployment workflows, especially in cases where the ownership of multiple subgraphs is spread across multiple autonomous teams. These keys have the specific permissions needed for CI/CD workflow management, allowing you to run checks against your supergraph, and to publish subgraph schema changes.</p>



<p class="wp-block-paragraph">Subgraph API keys are available in <a href="https://www.apollographql.com/pricing">GraphOS Standard and Enterprise plans</a>. Users who have the Org Admin or Graph Admin role can create and manage subgraph keys.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="559" src="https://wp.apollographql.com/wp-content/uploads/2025/10/Subgraph-API-Keys_1-1024x559.png" alt="" class="wp-image-24668" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/Subgraph-API-Keys_1-1024x559.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/10/Subgraph-API-Keys_1-300x164.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/10/Subgraph-API-Keys_1-768x419.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/10/Subgraph-API-Keys_1-1536x839.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/10/Subgraph-API-Keys_1-2048x1118.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/10/Subgraph-API-Keys_1-1200x655.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/10/Subgraph-API-Keys_1-1980x1081.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Figure: Subgraph API keys grant permissions at the Subgraph level <br></figcaption></figure>



<h2 class="wp-block-heading"><a href="#how-do-i-use-a-subgraph-key" aria-hidden="true" class="aal_anchor" id="how-do-i-use-a-subgraph-key"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How do I use a subgraph key?</h2>



<ol class="wp-block-list">
<li>Create a subgraph key using Rover or the Platform API. (Stay tuned for key management in Studio in the near future!) Note that subgraph keys are immutable. You must list all subgraphs and variants you want the key to work against when you create the key.  </li>



<li>Store the key token in your secret manager.</li>



<li>Create a pipeline, or update your existing pipeline, to use your new key.</li>
</ol>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1006" height="1006" src="https://wp.apollographql.com/wp-content/uploads/2025/10/api-keys-fig2.png" alt="" class="wp-image-24671" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/api-keys-fig2.png 1006w, https://wp.apollographql.com/wp-content/uploads/2025/10/api-keys-fig2-300x300.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/10/api-keys-fig2-150x150.png 150w, https://wp.apollographql.com/wp-content/uploads/2025/10/api-keys-fig2-768x768.png 768w" sizes="auto, (max-width: 1006px) 100vw, 1006px" /><figcaption class="wp-element-caption">Figure 2: List subgraphs and variants for the API key</figcaption></figure>



<p class="wp-block-paragraph">You’re all set! You can now test your pipeline workflow with confidence, knowing that each deploy is scoped to only your specified services.</p>



<p class="wp-block-paragraph">Subgraph API keys are a meaningful improvement in letting teams right-size their permissions and the first stepping stone on our path towards fine-grained permissions! Get started today by <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/publishing">updating an existing pipeline</a> to use a subgraph key, or by <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/publishing/guide-github">creating your subgraph pipeline from scratch</a>.</p>



<p class="wp-block-paragraph"></p>


Subgraph API Keys and safer deployment pipelines


<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph"><em><strong>Every DevOps team knows the pain:</strong> a schema breaks production, and rolling back means republishing, recomposing, and crossing your fingers. Graph artifacts change that—giving you versioned, immutable schemas you can deploy, roll back, and audit with confidence.</em><br></p>
</blockquote>



<p class="wp-block-paragraph">DevOps best practices have given engineering teams confidence in how they ship software—except when it comes to supergraph schemas. The <a href="https://www.apollographql.com/docs/graphos/routing">Apollo Router</a> is often configured to auto-update to the &#8220;latest&#8221; schema, making it difficult to lock to a known version, roll back safely, or audit what was running in production at any given time. Teams managing production supergraphs need the same controls they have for application code: versioning, instant rollbacks, and clear audit trails.</p>



<p class="wp-block-paragraph"><strong>Graph artifacts, now in Public Preview</strong>, bring that control to schemas. Every publish automatically produces a versioned, immutable package you can pin, roll back, and audit. Your team gets the stability and traceability you expect from modern DevOps—no surprises, no drift, just the exact schema you intended. </p>



<h1 class="wp-block-heading"><a href="#why-graph-artifacts" aria-hidden="true" class="aal_anchor" id="why-graph-artifacts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Why graph artifacts?</h1>



<p class="wp-block-paragraph">Teams running production supergraphs—especially in enterprises and regulated industries—need more control and traceability over schema releases. When routers automatically update to the latest published schema, teams face three significant challenges:</p>



<ul class="wp-block-list">
<li><strong>No version pinning</strong>: You can&#8217;t lock a router to a specific schema version for testing or gradual rollouts</li>



<li><strong>Slow rollbacks</strong>: Fixing a bad release requires republishing schemas and waiting for recomposition</li>



<li><strong>Missing audit trail</strong>: There&#8217;s no way to confirm which exact schema was running at a specific point in time</li>
</ul>



<p class="wp-block-paragraph">Graph artifacts solve these problems. Each artifact is identified by a unique SHA-256 digest, creating an immutable reference you can deploy, roll back to, and audit with confidence.</p>



<h1 class="wp-block-heading"><a href="#how-they-work" aria-hidden="true" class="aal_anchor" id="how-they-work"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How they work</h1>



<p class="wp-block-paragraph">Graph artifacts require <a href="https://github.com/apollographql/router/releases">Apollo Router v2.7</a> or later. The publishing flow remains the same—you publish your subgraphs to GraphOS—but now every publish automatically generates an <a href="https://opencontainers.org/">OCI</a>-compliant artifact stored in the GraphOS registry with a unique SHA-256 digest. Your router configuration pins to that digest, ensuring it runs only that specific schema version.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="594" src="https://wp.apollographql.com/wp-content/uploads/2025/10/image-6.png" alt="" class="wp-image-24725" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/image-6.png 1600w, https://wp.apollographql.com/wp-content/uploads/2025/10/image-6-300x111.png 300w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /><figcaption class="wp-element-caption">Figure 1: Graph artifact lifecycle</figcaption></figure>



<h2 class="wp-block-heading"><a href="#manually-configure-your-router" aria-hidden="true" class="aal_anchor" id="manually-configure-your-router"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Manually configure your router</h2>



<p class="wp-block-paragraph">Graph artifacts and their SHA digests appear on the <strong>Launches</strong> page in Apollo Studio. Click the copy button to copy an artifact&#8217;s reference URI, then configure your router to run that specific schema version. </p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1042" height="1552" src="https://wp.apollographql.com/wp-content/uploads/2025/10/launct-graph-artifact02.png" alt="" class="wp-image-24738" srcset="https://wp.apollographql.com/wp-content/uploads/2025/10/launct-graph-artifact02.png 1042w, https://wp.apollographql.com/wp-content/uploads/2025/10/launct-graph-artifact02-201x300.png 201w" sizes="auto, (max-width: 1042px) 100vw, 1042px" /><figcaption class="wp-element-caption">Figure 2: Graph artifact build</figcaption></figure>



<p class="wp-block-paragraph">Once you have a graph artifact’s reference URI, point your router to it by setting this environment variable:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">APOLLO_GRAPH_ARTIFACT_REFERENCE=&quot;artifact.api.apollographql.com/my-graph-id@sha256:6c3c62...&quot;</code></pre>



<p class="wp-block-paragraph">This ensures your router only runs that specific schema version until you change the configuration to a new artifact reference.</p>



<h2 class="wp-block-heading"><a href="#integrate-graph-artifacts-with-ci-cd" aria-hidden="true" class="aal_anchor" id="integrate-graph-artifacts-with-ci-cd"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Integrate graph artifacts with CI/CD</h2>



<p class="wp-block-paragraph">Integrate graph artifacts into your CI/CD pipeline by programmatically fetching the latest artifact reference URI using the <a href="https://www.apollographql.com/docs/graphos/platform/platform-api">GraphOS Platform API</a>: </p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">query GetGraphArtifactHistory($graphId: ID!, $variantName: String!) {
  graph(id: $graphId) {
    variant(name: $variantName) {
      launchHistory {
        graphArtifact {
          completedAt
          status
          location {
            uri
          }
        }
      }
    }
  }
}</code></pre>



<p class="wp-block-paragraph">The artifact reference is returned in the <code class="" data-line="">location.uri</code> field of the graph artifact with the latest <code class="" data-line="">completedAt</code> value and a <code class="" data-line="">status</code> value of GRAPH_ARTIFACT_COMPLETED. Write this URI to your router&#8217;s configuration during deployment to ensure it runs that specific schema version.</p>



<h2 class="wp-block-heading"><a href="#deploy-with-the-apollo-graphos-operator-for-kubernetes" aria-hidden="true" class="aal_anchor" id="deploy-with-the-apollo-graphos-operator-for-kubernetes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deploy with the Apollo GraphOS Operator for Kubernetes</h2>



<p class="wp-block-paragraph">The <a href="https://www.apollographql.com/graphos/apollo-graphos-operator">Apollo GraphOS Operator</a>—now generally available—supports graph artifacts, enabling schema versioning in Kubernetes-native deployments. The Operator automatically releases new artifacts and handles orchestration through Kubernetes. Learn more in the <a href="https://www.apollographql.com/docs/apollo-operator">Operator documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#open-standards-flexible-tooling" aria-hidden="true" class="aal_anchor" id="open-standards-flexible-tooling"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Open standards, flexible tooling</h2>



<p class="wp-block-paragraph">Graph artifacts leverage the <a href="https://opencontainers.org/">Open Container Initiative (OCI)</a> image format and the GraphOS registry is OCI-compliant. This means you can use industry-standard tools like <a href="https://oras.land/docs/">ORAS</a> to pull and inspect graph artifacts directly from the registry—giving you flexibility in how you integrate artifacts into your workflows. Learn more in the <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/graph-artifacts">graph artifacts documentation</a>.</p>



<h1 class="wp-block-heading"><a href="#what-this-means-in-practice" aria-hidden="true" class="aal_anchor" id="what-this-means-in-practice"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What this means in practice</h1>



<p class="wp-block-paragraph">Graph artifacts transform how teams manage schema deployments across four critical workflows:</p>



<p class="wp-block-paragraph"><strong>Promote from staging to production with zero drift</strong></p>



<p class="wp-block-paragraph">Publish a schema change and GraphOS creates artifact <code class="" data-line="">sha256:abc123</code>. Pin your staging router to that artifact, run your full integration test suite, and validate performance. When you&#8217;re ready, pin production to that exact same <code class="" data-line="">sha256:abc123</code> reference—the identical schema that passed all your tests. No recomposition between environments, no timing windows, no surprises.</p>



<p class="wp-block-paragraph"><strong>Instantly rollback without republishing</strong></p>



<p class="wp-block-paragraph">At 3pm, you deploy artifact <code class="" data-line="">sha256:def456</code> to production. By 3:15pm, error rates spike. Instead of emergency schema changes and waiting for recomposition, you copy the previous artifact reference (<code class="" data-line="">sha256:abc123</code>) from the Launches page, update your router configuration, and redeploy. You&#8217;re back to stability in under 2 minutes—versus the several minutes a traditional republish-and-wait approach requires.</p>



<p class="wp-block-paragraph"><strong>Fleet-wide consistency across distributed deployments</strong></p>



<p class="wp-block-paragraph">Lock all your production routers—whether you&#8217;re running 3 or 300—onto a single artifact SHA. Every router in every region runs the identical schema version until you explicitly update them. No race conditions, no partial rollouts, no &#8220;works in <em>us-east</em> but not <em>eu-west</em>&#8221; troubles.</p>



<p class="wp-block-paragraph"><strong>Audit trails for compliance and debugging</strong></p>



<p class="wp-block-paragraph">When a customer reports an API issue from last Tuesday at 2pm, check the Launches page to see exactly which artifact was running at that time. Each artifact is immutable and tied to a specific launch, giving you a complete timeline of which schema version was active when. Perfect for post-mortems, compliance requirements, and reproducing production issues.</p>



<h1 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next</h1>



<p class="wp-block-paragraph">The Public Preview is just the start. Upcoming improvements include:</p>



<ul class="wp-block-list">
<li><strong>Enhanced support</strong> for CI/CD integration</li>



<li><a href="https://www.apollographql.com/docs/rover"><strong>Rover CLI</strong></a><strong> support</strong> for artifact history and details</li>



<li><strong>Custom tags</strong> to assign human-friendly identifiers to artifacts</li>



<li><strong>Hot-reloading</strong> of graph artifacts in the router by automatically following modifications to a specific tag</li>
</ul>



<h1 class="wp-block-heading"><a href="#start-using-graph-artifacts-today" aria-hidden="true" class="aal_anchor" id="start-using-graph-artifacts-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Start using graph artifacts today</h1>



<p class="wp-block-paragraph">The graph artifacts Public Preview is available now in GraphOS for all supergraph users running <a href="https://github.com/apollographql/router/releases">Apollo Router v2.7</a> or later. Get started today:</p>



<ul class="wp-block-list">
<li>Open the <strong>Launches</strong> page in Studio—your recent publishes already have graph artifacts</li>



<li>Copy an artifact reference and configure your router</li>



<li>Share your feedback in the <a href="https://community.apollographql.com/t/graph-artifacts-public-preview/9449">Apollo Community</a></li>
</ul>



<p class="wp-block-paragraph">Read the <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/graph-artifacts">full documentation</a> to learn more about CI/CD integration, rollback strategies, and OCI tooling support.<br></p>


Introducing Graph Artifacts: Versioned, Immutable Schemas for Confident Deployments


<p class="wp-block-paragraph">We&#8217;re thrilled to announce Apollo Client 4.0, a milestone release that delivers significant improvements in bundle size, TypeScript support, and developer experience. After extensive community feedback and months of iteration through release candidates, version 4.0 represents our most refined and performant Apollo Client yet.</p>



<p class="wp-block-paragraph">The JavaScript ecosystem has evolved dramatically since Apollo Client 3.0&#8217;s release. Modern build tools offer sophisticated tree-shaking, the state of the art of TypeScript has significantly improved, and applications demand smaller bundles to meet Core Web Vitals targets. Apollo Client 4.0 embraces these changes while maintaining the developer experience you love.</p>



<figure class="wp-block-embed aligncenter is-type-video is-provider-wistia-inc wp-block-embed-wistia-inc"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="What&#039;s new in Apollo Client 4.0 Video" src="https://fast.wistia.net/embed/iframe/agn6t05661?dnt=1" allow="autoplay; fullscreen" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" msallowfullscreen width="580" height="326"></iframe><script src="https://fast.wistia.net/assets/external/E-v1.js" async></script>
</div></figure>



<h2 class="wp-block-heading"><a href="#dramatically-smaller-bundles" aria-hidden="true" class="aal_anchor" id="dramatically-smaller-bundles"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Dramatically smaller bundles</h2>



<p class="wp-block-paragraph">Bundle size has been a top concern in community feedback, and we&#8217;ve taken it seriously. Apollo Client 4.0 introduces opt-in architecture for features that not everyone needs. The most impactful change is making local state management opt-in. If you&#8217;re not using <code class="" data-line="">@client</code> directives for local state, you no longer carry that code in your bundle. This same principle extends to other commonly unused features like <code class="" data-line="">HttpLink</code>, which is no longer bundled by default when you&#8217;re using custom terminating links. When you do need these features, importing them explicitly gives you the same powerful functionality, but only when you actually use it.</p>



<p class="wp-block-paragraph">We&#8217;ve also modernized our build targets. Apollo Client 4.0 ships JavaScript transpiled for browsers from 2023 and Node.js 20+, taking advantage of native language features instead of polyfills. Combined with proper ESM support and improved tree-shaking, most applications will see a <strong>20-30%</strong> reduction in Apollo Client&#8217;s bundle size contribution. For teams fighting to stay under performance budgets, this improvement alone makes upgrading worthwhile.</p>



<h2 class="wp-block-heading"><a href="#typescript-that-helps" aria-hidden="true" class="aal_anchor" id="typescript-that-helps"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>TypeScript that helps</h2>



<p class="wp-block-paragraph">We&#8217;ve completely reimagined our TypeScript architecture based on a simple principle: types should be discoverable where you use them. Instead of hunting through documentation for type names, types now live alongside their APIs through namespaces. When you import <code class="" data-line="">useQuery</code>, you get <code class="" data-line="">useQuery.Options</code> and <code class="" data-line="">useQuery.Result</code> right there. It&#8217;s a small change that makes a big difference in day-to-day development.</p>



<p class="wp-block-paragraph">But the improvements go deeper. Apollo Client 4.0 now enforces required variables at the type level — if your query has required variables, TypeScript won&#8217;t let you forget them. The fragile <code class="" data-line="">TContext</code> generic has been replaced with module augmentation for defining custom context types across your link chain. And with the new <code class="" data-line="">TypeOverrides</code> interface, you can customize how Apollo Client handles partial data, streaming responses, and more, all while maintaining type safety.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">import { useQuery } from &quot;@apollo/client/react&quot;;

// Variables are now required when the query needs them
function UserProfile({ userId }: { userId: string }) {
  // TypeScript error if variables are missing when required!
  const { data, dataState } = useQuery(USER_QUERY, {
    variables: { id: userId } // Required by TypeScript
  });
  
  if (dataState === &#039;complete&#039;) {
    // TypeScript knows data is fully populated
    return &lt;Profile user={data.user} /&gt;;
  }
  // ...
}

// Define context types once for your entire app
declare module &quot;@apollo/client&quot; {
  interface DefaultContext {
    authToken?: string;
    requestId?: number;
  }
}</code></pre>



<p class="wp-block-paragraph">Speaking of <code class="" data-line="">dataState</code>, this new property solves one of the most common TypeScript frustrations with Apollo Client. Previously, determining whether <code class="" data-line="">data</code> was partial, complete, or missing required checking multiple flags. Now, <code class="" data-line="">dataState</code> gives you a single source of truth with four clear states: <code class="" data-line="">empty</code>, <code class="" data-line="">partial</code>, <code class="" data-line="">streaming</code>, and <code class="" data-line="">complete</code>. TypeScript can narrow types based on these states, eliminating runtime errors from accessing undefined data.</p>



<h2 class="wp-block-heading"><a href="#more-intuitive-error-handling" aria-hidden="true" class="aal_anchor" id="more-intuitive-error-handling"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>More intuitive error handling</h2>



<p class="wp-block-paragraph">Error handling in Apollo Client 3 often required developers to dig through nested properties to understand what went wrong. Apollo Client 4.0 replaces the monolithic <code class="" data-line="">ApolloError</code> with specific error classes that tell you exactly what happened. GraphQL errors from your server are now clearly distinguished from network failures or parsing errors. Each error type has static methods for type checking, making error handling both more intuitive and more type-safe.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">import { CombinedGraphQLErrors } from &quot;@apollo/client&quot;;

// Clear, specific error handling
if (CombinedGraphQLErrors.is(error)) {
  error.errors.forEach(e =&gt; console.log(e.message));
} else if (error) {
  console.error(&quot;Network error:&quot;, error.message);
}</code></pre>



<p class="wp-block-paragraph">This clarity extends throughout the API. Hooks like <code class="" data-line="">useLazyQuery</code> now have clearer boundaries about what options go where — initial options on the hook, execution options on the execute function. The <code class="" data-line="">loading</code> state actually means loading now, with <code class="" data-line="">notifyOnNetworkStatusChange</code> defaulting to <code class="" data-line="">true</code> so refetches are properly reflected in your UI.</p>



<h2 class="wp-block-heading"><a href="#built-for-modern-javascript" aria-hidden="true" class="aal_anchor" id="built-for-modern-javascript"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Built for modern JavaScript<a href="https://github.com/apollographql/apollo-client/blob/7045de5f1ff856fd0d0a33542c3e23610fcd1cbc/apollo-client-4-blog-post.md#built-for-modern-javascript"></a></h2>



<p class="wp-block-paragraph">Apollo Client 4.0 fully embraces modern JavaScript standards. We&#8217;ve migrated from <code class="" data-line="">zen-observable</code> to RxJS, giving you access to a massive ecosystem of operators and debugging tools. RxJS is now a peer dependency, so you control the version and can share a single instance across your entire application.</p>



<p class="wp-block-paragraph">The move to ESM-first packaging isn&#8217;t just about following trends, it delivers real benefits. Your bundler can now analyze and optimize Apollo Client code just like your own application code. Dead code elimination works properly, dynamic imports are supported, and you get better debugging with proper source maps. For teams using Vite, Webpack 5, or other modern bundlers, the improvement in build times and bundle optimization is immediately noticeable.</p>



<p class="wp-block-paragraph">React has never been required to use Apollo Client, but in prior versions our exported modules could sometimes muddy the waters in a way that confused non-React users. Apollo Client 4.0 addresses this friction point by making all top-level exported members completely free of React dependencies. React remains a first-class citizen with all the hooks and patterns you&#8217;re familiar with, they just live in <code class="" data-line="">@apollo/client/react</code> now.</p>



<h2 class="wp-block-heading"><a href="#a-smooth-migration-path" aria-hidden="true" class="aal_anchor" id="a-smooth-migration-path"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A smooth migration path</h2>



<p class="wp-block-paragraph">We know that major version upgrades can be daunting, especially for large codebases. That&#8217;s why we&#8217;ve invested heavily in migration tooling. Our comprehensive codemod handles the mechanical changes automatically: updating imports, converting link creator functions to classes, and migrating deprecated APIs. For most applications, you can run the codemod and be 90% done with your migration in minutes.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">npx @apollo/client-codemod-migrate-3-to-4 src</code></pre>



<p class="wp-block-paragraph">The remaining changes are typically intentional breaking changes that require human judgment, like updating error handling or choosing whether to adopt new features like the <code class="" data-line="">LocalState</code> class. Our migration guide walks through each change with clear examples and explanations.</p>



<h2 class="wp-block-heading"><a href="#looking-forward" aria-hidden="true" class="aal_anchor" id="looking-forward"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Looking forward</h2>



<p class="wp-block-paragraph">Apollo Client 4.0 is more than a bundle size reduction or API cleanup, it&#8217;s a foundation for the next generation of UI development with GraphQL. We&#8217;re already seeing significant performance improvements from teams using the React Compiler-optimized hooks. The framework-agnostic core opens possibilities for deeper framework integrations. And the cleaner TypeScript architecture makes it easier for us to add new features without breaking existing code.</p>



<p class="wp-block-paragraph">This release wouldn&#8217;t have been possible without extensive community feedback and contributions. Thank you to everyone who tested release candidates, reported issues, and helped shape Apollo Client 4.0 into what it is today.</p>



<p class="wp-block-paragraph">Ready to upgrade? Install Apollo Client 4.0 today:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">npm install @apollo/client@latest graphql rxjs</code></pre>



<p class="wp-block-paragraph">For detailed upgrade instructions, check out our <a href="https://www.apollographql.com/docs/react/migrating/apollo-client-4-migration">migration guide</a>. For the complete list of changes, see the <a href="https://github.com/apollographql/apollo-client/releases/tag/%40apollo%2Fclient%404.0.0">changelog</a>.</p>



<p class="wp-block-paragraph">Happy querying!</p>


Apollo Client 4.0: A Leaner and Cleaner GraphQL Client with No Compromises


<p class="wp-block-paragraph">When we <a href="https://www.apollographql.com/blog/the-future-of-mcp-is-graphql">launched Apollo MCP Server</a>, teams started connecting their GraphQL APIs to AI agents immediately. The feedback has been enthusiastic and consistent. &#8220;This is exactly what we need. We can finally give LLMs the right context, and do it declaratively!&#8221; Quickly followed by: &#8220;But we can&#8217;t deploy this to production without appropriate auth.&#8221;</p>



<p class="wp-block-paragraph">They were right. Without knowing who they are and what they are allowed to do, every MCP server user shares the same anonymous access. Your intern and your CTO see the same data. There&#8217;s no audit trail. No way to separate development from production access. For teams serious about AI in production, this was a dealbreaker.</p>



<p class="wp-block-paragraph">Today, we&#8217;re shipping authorization support in Apollo MCP Server. It&#8217;s a complete OAuth 2.1 implementation following the newly ratified <a href="https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization">MCP Authorization specification</a> (as of June 18, 2025).</p>



<p class="wp-block-paragraph"><strong><strong>This makes Apollo MCP Server production-ready</strong></strong>.</p>



<h2 class="wp-block-heading"><a href="#why-authorization-matters-for-ai-agents" aria-hidden="true" class="aal_anchor" id="why-authorization-matters-for-ai-agents"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Why Authorization Matters for AI Agents</strong></h2>



<p class="wp-block-paragraph">The security research community has been raising legitimate concerns about MCP implementations. <a href="https://simonwillison.net/2025/Apr/9/mcp-prompt-injection/">For example, Simon Willison recently pointed out</a> that &#8220;Model Context Protocol has prompt injection security problems&#8221; – malicious actors could potentially manipulate AI behavior through carefully crafted responses.</p>



<p class="wp-block-paragraph">While authorization doesn&#8217;t solve prompt injection directly, it&#8217;s a critical first line of defense. Without authorization:</p>



<ul class="wp-block-list">
<li>Any user can access your MCP server</li>



<li>There&#8217;s no audit trail of who requested what</li>



<li>A single compromised session affects everyone (no way to revoke individual access)</li>



<li>You can&#8217;t implement rate limiting or access controls</li>
</ul>



<p class="wp-block-paragraph">But there&#8217;s a more fundamental issue at hand: you simply can&#8217;t deploy to production without knowing who&#8217;s making requests. Enterprise security requirements aren&#8217;t optional. Teams have been stuck running MCP servers mostly in local development, unable to unlock the real value of AI agents with access to production data.&nbsp; And this is where GraphQL&#8217;s declarative approach also really shines. Just as we&#8217;ve extended GraphQL&#8217;s schema-driven development to MCP tools, authorization policies can be defined declaratively alongside your graph. Instead of writing custom authorization code for each API endpoint, you define access rules that work across your entire GraphQL schema. This means consistent security policies whether you&#8217;re accessing data through traditional GraphQL queries or AI agent interactions through MCP tools.</p>



<h2 class="wp-block-heading"><a href="#what-we-built" aria-hidden="true" class="aal_anchor" id="what-we-built"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What We Built</strong></h2>



<p class="wp-block-paragraph">Apollo MCP Server now implements OAuth 2.1 with full PKCE support, following the <a href="https://datatracker.ietf.org/doc/html/rfc9728">Protected Resource Metadata specification (RFC 9728)</a>. It works with modern identity providers that support OAuth 2.1 or OAuth 2.0 with PKCE, including:</p>



<ul class="wp-block-list">
<li>Okta</li>



<li>Auth0</li>



<li>Google</li>



<li>Microsoft Entra ID (Azure AD)</li>



<li>And other standards-compliant providers</li>
</ul>



<h3 class="wp-block-heading"><a href="#security-first-features" aria-hidden="true" class="aal_anchor" id="security-first-features"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Security-First Features</strong></h3>



<p class="wp-block-paragraph">We designed this implementation with a security-first mindset. That means focusing not just on compatibility and standards, but on eliminating common attack vectors and enforcing safe defaults.&nbsp;</p>



<p class="wp-block-paragraph">Here are the core features of Apollo MCP Server’s OAuth implementation and what they protect against:</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td class="has-text-align-left" data-align="left"><strong>Feature</strong></td><td class="has-text-align-left" data-align="left"><strong>What It Prevents</strong></td></tr><tr><td class="has-text-align-left" data-align="left">PKCE required</td><td class="has-text-align-left" data-align="left">Authorization code interception attacks</td></tr><tr><td class="has-text-align-left" data-align="left">Token validation</td><td class="has-text-align-left" data-align="left">Confused deputy vulnerabilities</td></tr><tr><td class="has-text-align-left" data-align="left">No token passthrough</td><td class="has-text-align-left" data-align="left">Token leakage to downstream services</td></tr><tr><td class="has-text-align-left" data-align="left">Proper token scoping</td><td class="has-text-align-left" data-align="left">Over-privileged access</td></tr></tbody></table></figure>



<h3 class="wp-block-heading"><a href="#from-localhost-to-production" aria-hidden="true" class="aal_anchor" id="from-localhost-to-production"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>&nbsp;From Localhost to Production</strong></h3>



<h4 class="wp-block-heading"><a href="#at-the-mcp-server-level" aria-hidden="true" class="aal_anchor" id="at-the-mcp-server-level"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>At the MCP Server Level</strong></h4>



<p class="wp-block-paragraph">Authorization introduces critical capabilities for identity enforcement and session isolation:&nbsp;</p>



<ul class="wp-block-list">
<li><strong>User identity validated</strong>: OAuth tokens are verified and user identity extracted</li>



<li><strong>Secure token handling</strong>: Each user&#8217;s session is isolated</li>



<li><strong>SSO integration</strong>: Works with your existing identity provider</li>



<li><strong>Remote-ready</strong>: Deploy MCP Server beyond localhost with confidence</li>
</ul>



<h4 class="wp-block-heading"><a href="#combined-with-apollo-routers-built-in-authorization" aria-hidden="true" class="aal_anchor" id="combined-with-apollo-routers-built-in-authorization"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Combined with Apollo Router&#8217;s Built-in Authorization</strong></h4>



<p class="wp-block-paragraph">When combined with Apollo Router, you get out-of-the-box field-level access control, declaratively defined within your schema</p>



<ul class="wp-block-list">
<li><strong>Field-level access control</strong>: Use @authenticated, @requiresScopes, and @policy <a href="https://www.apollographql.com/docs/graphos/routing/security/authorization">directives in your schema</a></li>



<li><strong>Authorization at the edge</strong>: Access checks happen before requests reach your subgraphs</li>



<li><strong>No custom code needed</strong>: Authorization rules live declaratively in your GraphQL schema</li>



<li><strong>Automatic filtering</strong>: Router removes unauthorized fields from responses</li>
</ul>



<p class="wp-block-paragraph">Here’s a basic example:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">type Query {
  publicData: String
  userData: String @authenticated
  adminData: String @requiresScopes(scopes: [&quot;admin&quot;])
}</code></pre>



<h2 class="wp-block-heading"><a href="#simplifying-configuration-config-files-replace-cli-arguments" aria-hidden="true" class="aal_anchor" id="simplifying-configuration-config-files-replace-cli-arguments"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Simplifying Configuration: Config Files Replace CLI Arguments</strong></h2>



<p class="wp-block-paragraph">Together, these enhancements give your MCP Server the security and governance controls needed for safe, reliable AI integration in production environments.&nbsp;</p>



<p class="wp-block-paragraph">Here&#8217;s the thing about adding authorization, it requires more configuration. And our command-line arguments were already getting unwieldy. So we&#8217;re making a breaking change: moving to YAML configuration files.</p>



<h3 class="wp-block-heading"><a href="#why-this-is-actually-good-news" aria-hidden="true" class="aal_anchor" id="why-this-is-actually-good-news"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Why This Is Actually Good News:</strong></h3>



<ul class="wp-block-list">
<li>Secrets live in environment variables, not command lines</li>



<li>Version controlled and shareable with your team</li>



<li>Sensible defaults let you start without a config file</li>
</ul>



<p class="wp-block-paragraph">If you&#8217;re already using Apollo MCP Server, the move is straightforward, mostly copying your CLI args into a YAML file. </p>



<p class="wp-block-paragraph">Check our <a href="https://www.apollographql.com/docs/apollo-mcp-server/command-reference#config-options">documentation</a> for config file examples.</p>



<h2 class="wp-block-heading"><a href="#join-the-conversation" aria-hidden="true" class="aal_anchor" id="join-the-conversation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Join the Conversation</strong></h2>



<p class="wp-block-paragraph">The MCP Authorization specification was just ratified on June 18, 2025. This space is moving fast, and real-world usage will shape how these standards evolve. Unfortunately, this also means not all of the tooling in this space is as rock solid as we hope. For example, you may find some MCP clients are not yet working as expected when used in combination with Apollo MCP Server. Either way, we&#8217;re committed to staying close to the community and adapting our implementation based on what works in production.</p>



<p class="wp-block-paragraph">If you&#8217;re implementing MCP authorization, we want to hear about it:</p>



<ul class="wp-block-list">
<li>What worked?</li>



<li>What didn&#8217;t?</li>



<li>What patterns are you discovering?</li>
</ul>



<p class="wp-block-paragraph">Share your experiences in our <a href="https://community.apollographql.com/t/apollo-mcp-server-now-implements-the-mcp-auth-spec/9370">community forum</a> or open an issue on <a href="https://github.com/apollographql/apollo-mcp-server">GitHub</a>.</p>



<h2 class="wp-block-heading"><a href="#additional-resources" aria-hidden="true" class="aal_anchor" id="additional-resources"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Additional Resources</strong></h2>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/docs/apollo-mcp-server/guides/auth">Apollo MCP Server Authorization Docs</a></li>



<li><a href="https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization">MCP Authorization Specification</a></li>



<li><a href="https://community.apollographql.com/t/apollo-mcp-server-now-implements-the-mcp-auth-spec/9370">Community Forum</a></li>



<li><a href="https://github.com/apollographql/apollo-mcp-server">GitHub Repository</a></li>
</ul>



<h2 class="wp-block-heading"><a href="#tldr" aria-hidden="true" class="aal_anchor" id="tldr"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>TL;DR</strong></h2>



<ul class="wp-block-list">
<li>Apollo MCP Server now supports OAuth 2.1 with PKCE</li>



<li>Makes production deployment possible with user-level access control</li>



<li>New config file system (breaking change, but worth it)</li>



<li>Security-first implementation prevents common vulnerabilities</li>
</ul>



<p class="wp-block-paragraph"><strong>Ready to bring your AI agents to production? </strong><a href="https://www.apollographql.com/apollo-mcp-server"><strong>Get started</strong></a></p>



<p class="wp-block-paragraph"></p>


Introducing Authorization for Apollo MCP Server: Secure AI Access to Your GraphQL APIs


<h3 class="wp-block-heading"><a href="#simplifying-graphql-api-management-on-kubernetes" aria-hidden="true" class="aal_anchor" id="simplifying-graphql-api-management-on-kubernetes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><em>Simplifying GraphQL API Management on Kubernetes</em></h3>



<p class="wp-block-paragraph">As <a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery">GraphQL adoption accelerates</a> within organizations, so too does the need for a scalable, reliable API platform that empowers your developers and accelerates innovation. Today, we’re excited to introduce in public preview the <a href="https://apollographql.com/docs/apollo-operator"><strong>Apollo GraphOS Operator</strong></a>: the best way to manage GraphQL deployments within Kubernetes.</p>



<h2 class="wp-block-heading"><a href="#why-we-built-the-apollo-graphos-operator" aria-hidden="true" class="aal_anchor" id="why-we-built-the-apollo-graphos-operator"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Why we built the Apollo GraphOS Operator</h2>



<p class="wp-block-paragraph">Setting up a best-practices GraphQL development workflow often requires a significant upfront investment to create custom automation for coordinating the deployment process to production, setting up ephemeral development environments, implementing progressive deployments, rollbacks, and more.</p>



<p class="wp-block-paragraph">The Apollo GraphOS Operator is designed to dramatically reduce the initial and on-going effort by delivering out-of-the-box best-practice GraphQL management for Kubernetes. Over time, it will allow platform and infrastructure teams to:</p>



<ul class="wp-block-list">
<li><strong>Increase development velocity by empowering developers to easily deploy new GraphQL environments.</strong> Using the operator, individual development teams can easily deploy new environments aligned with the company and platform team requirements.&nbsp; Ephemeral development environments can be utilized to validate changes early in the development cycle. New graphs can be easily deployed and managed, supporting new workloads without federation.</li>



<li><strong>Safely deploy to production with progressive rollouts and quick rollbacks.</strong> Validate supergraph changes on a portion of the overall GraphOS Runtime fleet, affecting only a small percentage of traffic at first. In the event any issues are discovered, quickly rollback to the prior schema without having to recompose or waiting for checks to run.</li>



<li><strong>Monitor status and health using Kubernetes events and resource statuses</strong>, which integrates directly with many observability solutions and deployment management tools like Datadog, Argo CD, and more.</li>



<li><strong>Manage GraphQL environments declaratively or via Studio</strong>. Aligns with development team preferences by supporting both declarative as well as UI-based management. Teams who prefer a declarative approach can use Kubernetes resources to manage their GraphQL deployments, aligning with common Kubernetes and GitOps practices. Teams who prefer a UI-based approach can continue to use <a href="https://www.apollographql.com/graphos/studio">GraphOS Studio</a> like they do today.</li>
</ul>



<h2 class="wp-block-heading"><a href="#what-you-can-do-with-the-public-preview" aria-hidden="true" class="aal_anchor" id="what-you-can-do-with-the-public-preview"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What you can do with the Public Preview</h2>



<p class="wp-block-paragraph">With the public preview of the Apollo GraphOS Operator, teams can now:</p>



<ul class="wp-block-list">
<li>Declaratively manage fleets with Kubernetes resources, enabling teams to manage their GraphQL supergraphs with the same declarative, GitOps-friendly approach they use for the rest of their Kubernetes workloads. Additional details on declarative management are available in our <a href="https://apollographql.com/docs/apollo-operator/resources/supergraph">documentation</a> and our <a href="https://www.apollographql.com/blog/getting-started-with-apollo-graphos-operator/" data-type="link" data-id="https://www.apollographql.com/blog/getting-started-with-apollo-graphos-operator/">technical blog post</a>.</li>



<li>Continue to support GraphOS Studio managed router fleets, while providing the foundation for upcoming features like canary deployments.</li>



<li>Begin testing the operator so that they can more easily and quickly adopt upcoming features once they are available.</li>
</ul>



<h2 class="wp-block-heading"><a href="#who-should-consider-trying-the-operator" aria-hidden="true" class="aal_anchor" id="who-should-consider-trying-the-operator"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Who should consider trying the operator</h2>



<p class="wp-block-paragraph">Customers who are familiar with Kubernetes and are either actively or interested in deploying their graph infrastructure on it, should consider evaluating the operator. Cloud and on-premise Kubernetes deployments are supported, including common implementations like GKE and EKS. The minimum required Kubernetes version is 1.30.</p>



<p class="wp-block-paragraph">Customers who are interested in utilizing some of the upcoming features may also be interested in starting testing now, so that your feedback can be incorporated and upcoming features can be utilized more rapidly.&nbsp; </p>



<h2 class="wp-block-heading"><a href="#the-road-ahead-a-simpler-future-for-graphql-operations" aria-hidden="true" class="aal_anchor" id="the-road-ahead-a-simpler-future-for-graphql-operations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The road ahead: A simpler future for GraphQL operations</h2>



<p class="wp-block-paragraph">Our long-term vision for the Apollo GraphOS Operator is to make it the easiest, most robust way to run GraphQL in Kubernetes environments. Future releases after GA will further streamline the experience, adding capabilities that previously required extensive custom development:</p>



<ul class="wp-block-list">
<li><strong>Canary deployments</strong> for safe supergraph schema changes</li>



<li><strong>Fast rollbacks</strong> when issues arise</li>



<li><strong>Ephemeral environments</strong> for development and testing</li>



<li><strong>Progressive router upgrades</strong> with minimal downtime</li>



<li><strong>Self-healing router instances</strong> to improve resiliency</li>



<li><strong>Support for managing the Apollo MCP</strong> <strong>Server</strong> to seamlessly connect AI agents to the runtime environments powering your graph</li>
</ul>



<p class="wp-block-paragraph">These enhancements will empower teams to focus on building exceptional GraphQL experiences while letting the operator handle the deployment complexity.</p>



<h2 class="wp-block-heading"><a href="#how-to-get-started" aria-hidden="true" class="aal_anchor" id="how-to-get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How to get started&nbsp;</h2>



<p class="wp-block-paragraph">The Apollo GraphOS Operator is available now as a public preview. If you’re building GraphQL services on Kubernetes, this is the fastest path to scalable, best-practices supergraph infrastructure.&nbsp;</p>



<ul class="wp-block-list">
<li>Check out our <a href="https://apollographql.com/docs/apollo-operator">documentation</a> and <a href="https://www.apollographql.com/blog/getting-started-with-apollo-graphos-operator/">technical blog post</a> for detailed information&nbsp;</li>



<li>Join our <a href="https://community.apollographql.com/t/announcing-the-apollo-graphos-operator-in-public-preview/9339">community forum</a> to share your experiences</li>



<li>Let us know what features you need next via <a href="https://support.apollographql.com/">Apollo Support</a></li>
</ul>


Announcing the Apollo GraphOS Operator in Public Preview


<p class="wp-block-paragraph">The Kubernetes ecosystem has evolved to provide powerful declarative resource management for applications, services, and infrastructure. Today, we&#8217;re excited to announce the public preview of the <a href="https://apollographql.com/docs/apollo-operator">Apollo GraphOS Operator</a>, bringing the best way to manage your subgraphs and supergraphs in Kubernetes environments.</p>



<p class="wp-block-paragraph">With the operator, you can define your subgraphs, compose them into supergraphs, and deploy them using native Kubernetes resources and workflows. This solves key challenges like keeping subgraph implementations and schemas in sync, providing end-to-end declarative control over both subgraphs and supergraphs, and enabling controlled deployments supergraphs, all within a GitOps-friendly, Kubernetes-native environment.</p>



<p class="wp-block-paragraph">Let&#8217;s explore how the Apollo GraphOS Operator brings Kubernetes-native resource management to your GraphQL supergraphs. </p>



<h2 class="wp-block-heading"><a href="#what-is-the-apollo-graphos-operator" aria-hidden="true" class="aal_anchor" id="what-is-the-apollo-graphos-operator"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is the Apollo GraphOS Operator?</h2>



<p class="wp-block-paragraph">The Apollo GraphOS Operator introduces three new Kubernetes Custom Resource Definitions (CRDs) that work together to manage your supergraphs declaratively. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="512" src="https://wp.apollographql.com/wp-content/uploads/2025/08/tech-blog-diag1-1024x512.png" alt="" class="wp-image-24528" srcset="https://wp.apollographql.com/wp-content/uploads/2025/08/tech-blog-diag1-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/08/tech-blog-diag1-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/08/tech-blog-diag1-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/08/tech-blog-diag1-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/08/tech-blog-diag1-1200x600.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/08/tech-blog-diag1.png 1800w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">The <strong>Subgraph</strong> resource defines your subgraphs with their schemas and endpoints. You can specify your schema inline, load it from a container image, or reference it as an OCI artifact. The operator automatically discovers these subgraphs and makes them available for composition.</p>



<p class="wp-block-paragraph">The <strong>SupergraphSchema</strong> resource defines supergraph schemas from your Subgraph resources. It uses Kubernetes label selectors to dynamically find relevant subgraphs, then automatically publishes them to Apollo GraphOS Studio for composition. This gives you flexible, declarative control over which subgraphs participate in each supergraph.</p>



<p class="wp-block-paragraph">The <strong>Supergraph</strong> resource deploys GraphOS Routers. It automatically provisions all the necessary Kubernetes resources for your supergraphs: Deployments, Services, ConfigMaps, and Secrets. Because it creates standard Kubernetes deployments, you get all the native Kubernetes capabilities like rolling updates, automatic rollbacks, and integration with your existing monitoring and scaling tools.</p>



<h2 class="wp-block-heading" id="Declare-your-first-Subgraph"><a href="#declare-your-first-subgraph" aria-hidden="true" class="aal_anchor" id="declare-your-first-subgraph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Declare your first Subgraph</h2>



<p class="wp-block-paragraph">Once you have <a href="https://apollographql.com/docs/apollo-operator/get-started/install-operator">installed</a> the operator in your cluster, you can use the Subgraph resource to define your subgraphs declaratively. This ensures that your subgraph schemas and implementations are always in sync and stay versioned together.</p>



<p class="wp-block-paragraph">While you can specify your schema inline, we recommend storing your schema in the same container image as your subgraph implementation. Here&#8217;s an example of a Subgraph resource that loads its schema from a container image:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">apiVersion: apollographql.com/v1alpha1
kind: Subgraph
metadata:
  name: users-subgraph
  namespace: users
  labels:
    domain: retail
    service: users
spec:
  name: users
  endpoint: http://users-service.users.svc.cluster.local/graphql
  schema:
    ociImage:
      # Reference to your container image
      reference: my-registry/users-service:v1.0.0
      # Subgraph schema file in your image
      path: /schema.graphql</code></pre>



<p class="wp-block-paragraph">You can also use the Subgraph resource with Apollo Connectors to create GraphQL APIs from your existing REST services. As you might not have an implementation server, you can also define your subgraph schema directly in the Subgraph specification:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">apiVersion: apollographql.com/v1alpha1
kind: Subgraph
metadata:
  name: products-subgraph
  namespace: products
  labels:
    domain: retail
    service: products
spec:
  name: products
  schema:
    sdl: |
      extend schema
        @link(
          url: &quot;https://specs.apollo.dev/federation/v2.10&quot;
          import: [&quot;@key&quot;]
        )
        @link(
          url: &quot;https://specs.apollo.dev/connect/v0.2&quot;
          import: [&quot;@connect&quot;, &quot;@source&quot;]
        )
        @source(
          name: &quot;ecomm&quot;
          http: { baseURL: &quot;http://products-service.products.svc.cluster.local/&quot; }
        )

      type Product {
        id: ID!
        name: String
        description: String
      }

      type Query {
        products: [Product]
          @connect(
            source: &quot;ecomm&quot;
            http: { GET: &quot;/products&quot; }
            selection: &quot;&quot;&quot;
            $.products {
              id
              name
              description
            }
            &quot;&quot;&quot;
          )
      }</code></pre>



<p class="wp-block-paragraph">The operator will automatically discover these subgraphs and make them available for composition. You can check the status with:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">kubectl get subgraph users -o yaml
kubectl get subgraph products -o yaml</code></pre>



<h2 class="wp-block-heading"><a href="#automatically-compose-a-supergraphschema" aria-hidden="true" class="aal_anchor" id="automatically-compose-a-supergraphschema"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Automatically compose a SupergraphSchema</h2>



<p class="wp-block-paragraph">Now that you have your subgraphs defined, you can compose them into a supergraph schema using the SupergraphSchema resource. It automatically keeps track of the matching Subgraph resources, triggering launches when it detects changes to your subgraph schemas. It also performs automatic change debouncing and batching on your behalf.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">apiVersion: apollographql.com/v1alpha1
kind: SupergraphSchema
metadata:
  name: retail
  namespace: apollo-schemas
spec:
  selectors:
    - matchLabels:
        domain: retail
  graphRef: retail@current</code></pre>



<p class="wp-block-paragraph">This SupergraphSchema will automatically find all subgraphs with the <code class="" data-line="">domain: retail</code> label across namespaces and compose them into a supergraph. The operator discovers subgraphs using the label selector, publishes schemas to the Apollo GraphOS Platform for composition, and continuously monitors the composition status to keep your resource status updated.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph"><strong>Note:</strong> While the operator reconciles resources across namespaces, it can be finely tuned to monitor specific namespaces for each resource type. For example, you could allow service owners to manage Subgraphs in their own namespaces, while managing SupergraphSchemas in a dedicated namespace.</p>
</blockquote>



<p class="wp-block-paragraph">You can monitor the composition process with:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">kubectl get supergraphschema retail -o yaml</code></pre>



<p class="wp-block-paragraph">Once the composition is successful, you&#8217;ll see an <strong>Available</strong> condition indicating that your supergraph schema is ready for deployment.</p>



<h2 class="wp-block-heading"><a href="#deploy-your-supergraph" aria-hidden="true" class="aal_anchor" id="deploy-your-supergraph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deploy your Supergraph</h2>



<p class="wp-block-paragraph">Now that you have a composed supergraph schema, you can deploy it using a Supergraph resource:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">apiVersion: apollographql.com/v1alpha1
kind: Supergraph
metadata:
  name: retail
  namespace: apollo-supergraphs
spec:
  replicas: 2
  schema:
    resource:
      name: retail
      namespace: apollo-schemas
  podTemplate:
    routerVersion: 2.4.0
  routerConfig:
    sandbox:
      enabled: true
    supergraph:
      introspection: true</code></pre>



<p class="wp-block-paragraph">The operator takes care of all the complexity behind the scenes. It securely manages graph API key as Kubernetes secrets, sets up ConfigMaps with your router configuration, fetches the latest schema and deploys it to the router. Furthermore, it applies schema changes by triggering a standard rolling update, ensuring a progressive deployment that can be rolled back in case of problems.</p>



<p class="wp-block-paragraph"><strong>Remark</strong>: If you are not using SupergraphSchema resources, for example because your subgraphs are not all living in Kubernetes, or you deploy subgraphs across mutliple clusters, you can also use a graph variant reference directly. Check out the <a href="https://apollographql.com/docs/apollo-operator/workflows">operator workflow documentation</a> to learn more about advanced workflows.</p>



<p class="wp-block-paragraph">Once you have created your Supergraph, you can check its status with the following command:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">kubectl get supergraph retail -o yaml</code></pre>



<p class="wp-block-paragraph">Once the deployment is ready, you&#8217;ll see a <strong>Ready</strong> condition and your supergraph will be available through the automatically created Kubernetes service.</p>



<h2 class="wp-block-heading"><a href="#whats-next-for-the-operator" aria-hidden="true" class="aal_anchor" id="whats-next-for-the-operator"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next for the operator?</h2>



<p class="wp-block-paragraph">We’re only getting started bringing Kubernetes-native subgraphs and supergraphs management with the Apollo GraphOS Operator. In addition to our current capabilities, we will be working on new features that will enhance the developer experience even further.</p>



<p class="wp-block-paragraph">This includes the introduction of ephemeral supergraphs, allowing you to replace specific subgraphs while developping new features. Furthermore, we are focusing on implementing safe deployment strategies for your supergraphs, such as canary releases.</p>



<h2 class="wp-block-heading" id="Get-started-today"><a href="#get-started-today" aria-hidden="true" class="aal_anchor" id="get-started-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started today</h2>



<p class="wp-block-paragraph">The Apollo GraphOS Operator brings the power of Kubernetes-native resource management to your GraphQL supergraphs. With declarative subgraph definitions, automatic composition, and seamless deployment, you can manage your supergraphs using the same Kubernetes workflows and tooling you already know.</p>



<p class="wp-block-paragraph">Ready to simplify your supergraph management? <a href="https://apollographql.com/docs/apollo-operator/get-started/install-operator">Install</a> the Apollo GraphOS Operator and start defining your subgraphs, composing supergraphs, and deploying routers using the Kubernetes-native approach we&#8217;ve explored in this post.</p>



<p class="wp-block-paragraph">For advanced deployment patterns and workflow options, visit our operator <a href="https://apollographql.com/docs/apollo-operator">documentation</a>.</p>


Manage your subgraphs and supergraphs as Kubernetes-native resources


<p class="wp-block-paragraph"><em>The world&#8217;s largest and longest-running GraphQL event returns to San Francisco with 30+ sessions on building agents, MCP services, and modern API platforms</em></p>



<p class="wp-block-paragraph">Whether you’re building mobile apps, web experiences, or preparing for an agentic future, the challenge is the same: orchestrating your organization’s APIs is far more complex than it appears. And that&#8217;s why leading organizations are turning to GraphQL as their API orchestration layer.</p>



<p class="wp-block-paragraph">At Indeed, they&#8217;re reimagining talent discovery with GraphQL as the central interface between agents to enable a seamless, intelligent hiring experience. Intuit is building smart tools to eliminate bottlenecks, enabling developers to ship their supergraph with speed and confidence. And at Booking.com, they’re continuously modernizing their architecture to stay ahead of their scale, reduce operational overhead and improve performance.</p>



<p class="wp-block-paragraph">And we&#8217;re excited to welcome these industry leaders to the stage to share more at our next <a href="http://www.graphqlsummit.com">GraphQL Summit by Apollo 2025</a>, our flagship event and the 8th annual edition of the conference that started it all, taking place October 6-8, 2025 at the Hyatt Regency San Francisco.</p>



<h1 class="wp-block-heading"><a href="#a-declarative-approach-to-building-connected-applications" aria-hidden="true" class="aal_anchor" id="a-declarative-approach-to-building-connected-applications"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>A Declarative Approach to Building Connected Applications</strong></h1>



<p class="wp-block-paragraph">This year marks a special milestone – it’s been 10 years since the GraphQL specification was first made available to the world. A decade of innovation, adoption, and transformation in how we think about APIs and connected systems.</p>



<p class="wp-block-paragraph">And with GraphQL emerging as the API orchestration layer that makes today and tomorrow’s applications possible, this year&#8217;s Summit addresses the questions that matter most: How do you build systems that can truly connect everything while maintaining security and performance? How do you architect APIs that enable teams to build anything, from traditional applications to AI-powered experiences?</p>



<p class="wp-block-paragraph">GraphQL has evolved far beyond a query language. What started by reimagining web and mobile development is now expanding into new frontiers. Engineering teams are exploring how Apollo serves as the API orchestration layer for emerging use cases like AI agents, Model Context Protocol (MCP) services, and interconnected systems.</p>



<h1 class="wp-block-heading"><a href="#industry-leaders-share-real-world-breakthroughs" aria-hidden="true" class="aal_anchor" id="industry-leaders-share-real-world-breakthroughs"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Industry Leaders Share Real-World Breakthroughs</strong></h1>



<p class="wp-block-paragraph">The early speaker lineup demonstrates the breadth and depth of Graph-based API Orchestration innovation happening across industries:</p>



<ul class="wp-block-list">
<li><a href="https://www.linkedin.com/in/christian-ernst11/"><strong>Christian Ernst</strong></a>, Senior Software Engineer at Booking.com, details<strong> &#8220;Inside Booking.com&#8217;s Router Rollout: Powering Product and Platform at Massive Scale,&#8221;</strong> offering insights from one of the world&#8217;s largest travel platforms.</li>



<li><a href="https://www.linkedin.com/in/jeffrey-russom-0a520436/"><strong>Jeffrey Russum</strong></a>, Principal Software Engineer at Indeed, delivers <strong>&#8220;Powering Indeed&#8217;s Agentic Talent Scout with Federated Subscriptions,&#8221;</strong> revealing how the world&#8217;s largest job platform is building AI-powered experiences with GraphQL federation.</li>



<li><strong>Oleks Bidiuk</strong>, Software Engineer, at Intuit, presents <strong>“Stop Reviewing Schemas: How Intuit’s AI Schema Co-Pilot Made Developers Faster by Automating Governance,”</strong> demonstrating how one of the world&#8217;s largest financial platforms eliminates governance bottlenecks at scale.</li>



<li><a href="https://www.linkedin.com/in/wibodha/?originalSubdomain=uk"><strong>Dhanik Alkegama</strong></a>, Engineering Manager &#8211; Platform Services at N-able, shares<strong> &#8220;Certified to Scale: How N-able Hit 1300% GraphQL Growth in 12 Months,&#8221;</strong> providing proven strategies for explosive GraphQL adoption.</li>



<li><a href="https://www.linkedin.com/in/rohitgupta4/"><strong>Rohit Gupta</strong></a>, Platform Product Manager, and <a href="https://www.linkedin.com/in/bhavanapallempati/"><strong>Bhavana Sree Pallempati</strong></a>, Software Engineer, Wayfair, presents <strong>“AI Meets PlatformOps: Auto-Mocking and Documenting Schemas at Wayfair with GenAI,”</strong> showing how GraphQL enables rapid innovation in e-commerce.</li>



<li><a href="https://www.linkedin.com/in/henp/?originalSubdomain=il"><strong>Hen Perez</strong></a>, Field CTO for API Infrastructure at Wiz, presents <strong>&#8220;How Wiz Is Reimagining Partner Integrations with Apollo MCP,&#8221;</strong> demonstrating cutting-edge approaches to partner connectivity in the cybersecurity space.</li>
</ul>



<h1 class="wp-block-heading"><a href="#what-youll-experience" aria-hidden="true" class="aal_anchor" id="what-youll-experience"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What You’ll Experience</strong></h1>



<p class="wp-block-paragraph">GraphQL Summit 2025 delivers unparalleled learning and networking opportunities:</p>



<ul class="wp-block-list">
<li><strong>Keynotes</strong> featuring industry leaders sharing transformative insights on the future of GraphQL and connected systems.</li>



<li><strong>Breakout Sessions </strong>covering real-world implementations, best practices, and cutting-edge use cases from companies successfully deploying GraphQL at scale.</li>



<li><strong>Meet the Apollo Experts </strong>sessions providing direct access to the team behind Federation and Apollo&#8217;s latest innovations.</li>



<li><strong>Connectors Hackathon </strong>where you can get hands-on experience building with Apollo&#8217;s newest tools and technologies.</li>



<li><strong>AI + Connectors Certification </strong>to validate your expertise in building AI-powered applications with GraphQL.</li>
</ul>



<p class="wp-block-paragraph">Beyond technical content, GraphQL Summit creates opportunities to connect with the broader GraphQL ecosystem. The conference includes a welcome reception, evening event celebration, and plenty of space for networking, connection, and demos throughout the event.</p>



<p class="wp-block-paragraph">Partnership opportunities are available – reach out to <a href="mailto:events@apollographql.com">events@apollographql.com</a> if interested in partnering.</p>



<p class="wp-block-paragraph"><strong>Ready to Connect Everything and Build Anything?</strong></p>



<p class="wp-block-paragraph">Join us in San Francisco at the Hyatt Regency on October 6-8, 2025, to learn from the best, connect with innovators, and discover how GraphQL can unlock new possibilities for your organization.</p>



<p class="wp-block-paragraph"><strong>Early bird registration is now open at $599</strong> with special rates available for Apollo customers and community contributors. Early bird pricing ends August 1, 2025.</p>



<p class="wp-block-paragraph">Register now at <a href="http://www.graphqlsummit.com">www.graphqlsummit.com</a>.</p>



<p class="wp-block-paragraph">Thank you to our community and partners for the privilege of working together and delivering more and more impact with GraphQL, every day.</p>



<p class="wp-block-paragraph">Here&#8217;s to GraphQL Summit 2025!</p>



<figure class="wp-block-embed is-type-video is-provider-wistia-inc wp-block-embed-wistia-inc"><div class="wp-block-embed__wrapper">
<script src="https://fast.wistia.com/player.js" async></script><script src="https://fast.wistia.com/embed/f1u17mz9bs.js" async type="module"></script><style>wistia-player[media-id='f1u17mz9bs']:not(:defined) { background: center / contain no-repeat url('https://fast.wistia.com/embed/medias/f1u17mz9bs/swatch'); display: block; filter: blur(5px); padding-top:56.25%; }</style> <wistia-player media-id="f1u17mz9bs" seo="false" dnt="1" aspect="1.7777777777777777"></wistia-player>
</div></figure>


Announcing GraphQL Summit by Apollo 2025: Connect Everything. Build Anything.

What’s New in GraphOS: Apollo Summer ’25 Release – AI-Ready API Orchestration with Enhanced MCP Server, Pricing Plans, and Performance Upgrades


<p class="wp-block-paragraph">Today we&#8217;re introducing <a href="https://github.com/apollographql/apollo-mcp-server">Apollo MCP Server,</a> enabling AI systems like Claude and GPT to interact with your organization&#8217;s APIs through GraphQL. While you can learn more about how to get started here, I wanted to share why we think GraphQL enabled by Model Context Protocol (MCP) will be an essential part of a modern AI stack.</p>



<h1 class="wp-block-heading"><a href="#connecting-ais-to-apis" aria-hidden="true" class="aal_anchor" id="connecting-ais-to-apis"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Connecting AIs to APIs</h1>



<p class="wp-block-paragraph">MCP – a new protocol that standardizes how LLMs interface with external systems – opens the door wide open to agentic applications. APIs are the entry point to capabilities: adding items to carts, checking order status, scheduling appointments, updating inventory. When AI can reliably interact with these systems, we unlock an entirely more capable kind of software where natural language becomes the interface to complex business operations. MCP makes this possible by providing the connective tissue between AI&#8217;s language understanding and your API infrastructure.</p>



<p class="wp-block-paragraph">One approach to MCP is to build an MCP server for each API you want AI to access. Your payment API gets its own MCP server, your inventory system gets another, customer data gets a third. It&#8217;s a straightforward way to get started. Most teams can build an initial MCP for a service reasonably quickly and LLMs support multiple MCP tools. It makes for a compelling experience.</p>



<p class="wp-block-paragraph">As we’ve worked with teams pushing from prototype to product, we&#8217;re discovering that complex AI systems need more than what is possible by directly connecting individual APIs through MCP. We&#8217;ve found four particular requirements that show up consistently:</p>



<p class="wp-block-paragraph"><strong>Deterministic execution</strong>: An AI will often have to call multiple APIs in sequence and filter the results to just the appropriate fields for the user. This execution pattern needs to work exactly the same way every time for consistent, correct user experiences. Consider an AI returning purchase history – you can&#8217;t have one customer seeing five past orders while another sees three, or some results including shipping details while others don&#8217;t. We&#8217;ve also found that the more focused you keep the AI&#8217;s context, the better results you get. When APIs return large objects with hundreds of fields, the extra data can lead AI down unintended paths. Limiting data to exactly what&#8217;s needed keeps the AI on track and improves overall response quality.</p>



<p class="wp-block-paragraph"><strong>Policy enforcement</strong>: Giving AI direct access to individual APIs makes it difficult to enforce appropriate limits and access controls. A rule like “only loyalty members have access to the detailed shipping tracking information for their outstanding orders” can’t easily be written in the API layer, as it relates to a specific combination of data spread across multiple systems.</p>



<p class="wp-block-paragraph"><strong>Efficiency</strong>: Even simple customer queries can generate thousands of tokens when APIs return complete objects. Processing all of this and directly orchestrating multiple tool invocations from the AI becomes costly, both in terms of tokens and milliseconds.&nbsp;</p>



<p class="wp-block-paragraph"><strong>Agility</strong>: The pace of AI is unprecedented. The technology and techniques are progressing furiously. Just as interesting to me is that the freeform nature of AI makes it possible to deliver new functionality faster than ever before: most users wouldn’t tolerate a mobile app that changed every day, but continuous improvement of an AI agent is nothing but good news. So an AI stack needs to accommodate and facilitate a tempo we’ve never seen before in software development. This requirement rules out strategies that aren’t aligned to the modern platform engineering discipline of self-service tools and workflows.</p>



<h1 class="wp-block-heading"><a href="#graphql-solves-these-needs-well" aria-hidden="true" class="aal_anchor" id="graphql-solves-these-needs-well"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL solves these needs well</h1>



<p class="wp-block-paragraph">What these requirements point to is the need for an abstraction layer between the AI and APIs. This <a href="https://www.apollographql.com/guides/api-orchestration">orchestration layer</a> exposes a set of MCP tools, where each tool provides a specific capability backed by some number of orchestrated API calls. The AI&#8217;s job is to reason about which MCP tools to invoke; the orchestration layer’s job is deterministic, efficient execution and policy enforcement.</p>



<p class="wp-block-paragraph">GraphQL is an ideal foundation of this orchestration layer.</p>



<ul class="wp-block-list">
<li>It’s declarative: MCP tools are defined in terms of schema and queries, rather than code.</li>



<li>It’s performant: one GraphQL query can traverse your entire graph, gathering exactly what&#8217;s needed (and nothing that’s not) in an optimized way.</li>



<li>It’s self-documenting: LLMs can reason about the meaning of the graph and its objects.</li>



<li>It&#8217;s standards-based: a mature ecosystem with proven scalability.</li>



<li>It’s self-service: on a GraphQL-based platform like Apollo, everyone with access to the graph can wire up MCP tools with the appropriate level of governance.</li>
</ul>



<p class="wp-block-paragraph">The characteristics of GraphQL align perfectly with what AI needs to access APIs: a clean, understandable interface to AI while handling the messy reality of existing systems and services. </p>



<p class="wp-block-paragraph">Consider the earlier example of retrieving purchase history with shipping updates. A GraphQL query defines an MCP tool that the AI system can use. Under the hood, that query orchestrates multiple API calls into the order, shipping and loyalty systems and enforces the necessary policy check. That query can be authored and deployed by anyone on the platform, with the support of design and governance tools provided by the graph platform.</p>



<p class="wp-block-paragraph">The challenges an abstraction layer solves may seem like tomorrow’s problems when just getting started with MCP. It’s always worth planning for success, but a good declarative architecture also saves time and effort in the earliest stages of development. A GraphQL-based approach avoids having to build, debug and deploy custom MCP servers. Apollo Connectors let you bring REST APIs to GraphQL (and now MCP) without any modification. And the benefits of having a semantic API layer are truly remarkable – watching an LLM traverse a large GraphQL schema as it builds a new query is an exciting, eye-opening moment.</p>



<h1 class="wp-block-heading"><a href="#introducing-apollo-mcp-server" aria-hidden="true" class="aal_anchor" id="introducing-apollo-mcp-server"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Introducing Apollo MCP Server</h1>



<p class="wp-block-paragraph">The Apollo MCP Server represents our continued investment in making GraphQL the best way to build modern API infrastructure. We&#8217;ve spent years developing tools that help teams build, manage, and scale GraphQL – from <a href="https://www.apollographql.com/docs/react">Apollo Client</a> to <a href="https://www.apollographql.com/federation">Apollo Federation</a> to our most recent innovation, <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a>. Now we&#8217;re extending that toolkit to address AI integration.</p>



<p class="wp-block-paragraph">By implementing MCP for GraphQL, we&#8217;re making it simple to connect AI to your existing graph. If you&#8217;re already using Apollo, this fits naturally into your stack. If you&#8217;re new to GraphQL, the MCP server provides a compelling entry point that solves immediate AI challenges while setting you up for future growth, all on top of the APIs you already have.</p>



<p class="wp-block-paragraph">We believe the architectural patterns emerging around AI – the need for precision, policy, efficiency, and agility – align perfectly with what GraphQL was designed to do. This MCP server is our way of helping teams realize those benefits.</p>



<p class="wp-block-paragraph">As you explore connecting AI to your services, consider not just immediate integration but your longer-term strategy. The architectural decisions you make today will determine how quickly and safely you can evolve AI capabilities tomorrow.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Ready to get started? Connect your REST and GraphQL APIs to the <a href="https://github.com/apollographql/apollo-mcp-server">Apollo MCP server </a>today, explore our Odyssey training course, or join us at our upcoming <a href="https://www.apollographql.com/events/get-started-with-mcp-tools-for-your-graphql-api-today">event</a> to learn more.&nbsp;<br><br>The future of APIs is here – powered by <a href="https://www.apollographql.com/guides/api-orchestration">graph-based API orchestration</a> that makes it easier than ever to build applications.</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">​​</p>


The Future of MCP is GraphQL

Getting Started with Apollo MCP Server for any GraphQL API


<p class="wp-block-paragraph">Apollo’s GraphOS API orchestration platform now offers a forever-free plan.&nbsp; Whether you’re already using GraphQL or are just getting started, this free plan is designed for anyone learning, exploring, or prototyping with Apollo GraphQL. You can begin immediately without needing a credit card. In this article, you’ll learn:</p>



<ul class="wp-block-list">
<li>What the GraphOS API orchestration platform is<br></li>



<li>What is included in the free plan (and its limitations)<br></li>



<li>How to get started with your first GraphQL query using the free plan</li>
</ul>



<h2 class="wp-block-heading"><a href="#what-is-the-graphos-api-orchestration-platform" aria-hidden="true" class="aal_anchor" id="what-is-the-graphos-api-orchestration-platform"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is the GraphOS API orchestration platform?</h2>



<p class="wp-block-paragraph">The GraphOS API orchestration platform from Apollo GraphQL is a collection of services and tools that help you build, manage, and orchestrate APIs at any scale. Apollo Studio is the UI for the control plane and includes:</p>



<ul class="wp-block-list">
<li><strong>GraphOS Explorer IDE</strong> for interactive query development<br></li>



<li><strong>GraphOS Registry</strong> for schema management and versioning<br></li>



<li><strong>GraphOS Insights</strong> for performance monitoring and analytics&nbsp;</li>
</ul>



<figure class="wp-block-image"><img loading="lazy" decoding="async" width="1440" height="570" src="https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXdETHv3MQt_PCbPvKtBYu-lPseiJQyOba2QU1EYGvXAm3fDM0tPosyj-k7OigfvlandjZ4WXsA3W_zJYRpsLI9wHhS3oVaYR4qO_ss6QSE8ILKJc7jrM-GnX8kT6pafbeg76j6VyQ.png" alt="" class="wp-image-24256" srcset="https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXdETHv3MQt_PCbPvKtBYu-lPseiJQyOba2QU1EYGvXAm3fDM0tPosyj-k7OigfvlandjZ4WXsA3W_zJYRpsLI9wHhS3oVaYR4qO_ss6QSE8ILKJc7jrM-GnX8kT6pafbeg76j6VyQ.png 1440w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXdETHv3MQt_PCbPvKtBYu-lPseiJQyOba2QU1EYGvXAm3fDM0tPosyj-k7OigfvlandjZ4WXsA3W_zJYRpsLI9wHhS3oVaYR4qO_ss6QSE8ILKJc7jrM-GnX8kT6pafbeg76j6VyQ-300x119.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXdETHv3MQt_PCbPvKtBYu-lPseiJQyOba2QU1EYGvXAm3fDM0tPosyj-k7OigfvlandjZ4WXsA3W_zJYRpsLI9wHhS3oVaYR4qO_ss6QSE8ILKJc7jrM-GnX8kT6pafbeg76j6VyQ-1024x405.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXdETHv3MQt_PCbPvKtBYu-lPseiJQyOba2QU1EYGvXAm3fDM0tPosyj-k7OigfvlandjZ4WXsA3W_zJYRpsLI9wHhS3oVaYR4qO_ss6QSE8ILKJc7jrM-GnX8kT6pafbeg76j6VyQ-768x304.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXdETHv3MQt_PCbPvKtBYu-lPseiJQyOba2QU1EYGvXAm3fDM0tPosyj-k7OigfvlandjZ4WXsA3W_zJYRpsLI9wHhS3oVaYR4qO_ss6QSE8ILKJc7jrM-GnX8kT6pafbeg76j6VyQ-1200x475.png 1200w" sizes="auto, (max-width: 1440px) 100vw, 1440px" /><figcaption class="wp-element-caption">&nbsp;Figure 1: GraphOS control and runtime planes</figcaption></figure>



<p class="wp-block-paragraph">The runtime plane contains the GraphOS Router (Router) and Apollo Server.&nbsp; These components fulfill GraphQL query requests for both single-server graphs and federated supergraph deployments.&nbsp; For example, in a federated use case, clients send queries to the Router, which intelligently determines which back-end subgraphs contain the necessary data, orchestrates the data exchange, and returns precisely what the client requested.</p>



<p class="wp-block-paragraph">GraphOS is a complete API orchestration solution that enables you to:&nbsp;</p>



<ul class="wp-block-list">
<li>Filter and transform data&nbsp;<br></li>



<li>Execute operations synchronously and in parallel<br></li>



<li>Manage authentication and authorization<br></li>



<li>Integrate diverse data sources seamlessly</li>
</ul>



<h2 class="wp-block-heading"><a href="#what-is-the-apollo-graphos-free-plan" aria-hidden="true" class="aal_anchor" id="what-is-the-apollo-graphos-free-plan"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is the Apollo GraphOS free plan?</h2>



<p class="wp-block-paragraph">The free plan replaced the enterprise trial plan that was limited to 90 days. This free plan has no time restrictions, making it easy to get started with GraphQL and prototype your next project.&nbsp;</p>



<p class="wp-block-paragraph">It also offers access to Apollo Connectors, which integrates REST API data into a graph without writing complex procedural code. The free plan includes the same functionalities as the enterprise plan, with the following limitations:</p>



<ul class="wp-block-list">
<li>Self-hosted routers are rate-limited to 60 requests per minute<br></li>



<li>Organizations are limited to 3 team members<br></li>



<li>Insights, checks, and traces for graphs of all types (not just those using GraphOS Router), with data retention limited to one day</li>
</ul>



<p class="wp-block-paragraph">Support is available through the <a href="https://community.apollographql.com/">Apollo Community</a>.</p>



<p class="wp-block-paragraph">The free plan is ideal for personal projects and exploring GraphOS, providing all the essentials to learn, experiment, and create at no cost. When your API orchestration needs expand, Apollo’s paid plans immediately remove the free plan&#8217;s rate limits, allowing you to scale your workload to any level of request volume.&nbsp; Depending on your paid plan, you may also use features such as:</p>



<ul class="wp-block-list">
<li><strong>Single Sign-On (SSO)</strong> support<br></li>



<li><strong>GraphOS Router extensibility</strong>, such as external coprocessors<br></li>



<li><strong>Advanced collaboration tools</strong>, such as schema proposals or configurable linting<br></li>



<li>Comprehensive <strong>Audit History</strong></li>
</ul>



<h2 class="wp-block-heading"><a href="#get-started-with-your-free-plan" aria-hidden="true" class="aal_anchor" id="get-started-with-your-free-plan"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started with your free plan</h2>



<p class="wp-block-paragraph">Anyone can create an organization on the free plan by:</p>



<ol class="wp-block-list">
<li>Signing up for <a href="https://studio.apollographql.com/signup?utm_campaign=Unlock%20the%20Power%20of%20API%20Orchestration&amp;utm_medium=blog&amp;utm_source=website">GraphOS</a>, or</li>



<li>Logging into Apollo Studio with your existing account and creating a new organization.</li>
</ol>



<figure class="wp-block-image"><img loading="lazy" decoding="async" width="1600" height="949" src="https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXeTzXGT4_GJJY58eM78S03CiVrcXwlLRntcNPBTYEgTjX_oDHZ9oo8MhYJuLjYlFW2S7tbr2ztEq2pzD9y087BO9hVcxJWX9xE0LpWyVA23A0lGwKSj1-Xs86wfzMhqjw-t4oXigw.png" alt="" class="wp-image-24258" srcset="https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXeTzXGT4_GJJY58eM78S03CiVrcXwlLRntcNPBTYEgTjX_oDHZ9oo8MhYJuLjYlFW2S7tbr2ztEq2pzD9y087BO9hVcxJWX9xE0LpWyVA23A0lGwKSj1-Xs86wfzMhqjw-t4oXigw.png 1600w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXeTzXGT4_GJJY58eM78S03CiVrcXwlLRntcNPBTYEgTjX_oDHZ9oo8MhYJuLjYlFW2S7tbr2ztEq2pzD9y087BO9hVcxJWX9xE0LpWyVA23A0lGwKSj1-Xs86wfzMhqjw-t4oXigw-300x178.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXeTzXGT4_GJJY58eM78S03CiVrcXwlLRntcNPBTYEgTjX_oDHZ9oo8MhYJuLjYlFW2S7tbr2ztEq2pzD9y087BO9hVcxJWX9xE0LpWyVA23A0lGwKSj1-Xs86wfzMhqjw-t4oXigw-1024x607.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXeTzXGT4_GJJY58eM78S03CiVrcXwlLRntcNPBTYEgTjX_oDHZ9oo8MhYJuLjYlFW2S7tbr2ztEq2pzD9y087BO9hVcxJWX9xE0LpWyVA23A0lGwKSj1-Xs86wfzMhqjw-t4oXigw-768x456.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXeTzXGT4_GJJY58eM78S03CiVrcXwlLRntcNPBTYEgTjX_oDHZ9oo8MhYJuLjYlFW2S7tbr2ztEq2pzD9y087BO9hVcxJWX9xE0LpWyVA23A0lGwKSj1-Xs86wfzMhqjw-t4oXigw-1536x911.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/04/AD_4nXeTzXGT4_GJJY58eM78S03CiVrcXwlLRntcNPBTYEgTjX_oDHZ9oo8MhYJuLjYlFW2S7tbr2ztEq2pzD9y087BO9hVcxJWX9xE0LpWyVA23A0lGwKSj1-Xs86wfzMhqjw-t4oXigw-1200x712.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /><figcaption class="wp-element-caption">Figure 2: Apollo Studio showing free plan organization&nbsp;</figcaption></figure>



<p class="wp-block-paragraph">Self-hosted routers can be hosted on the cloud provider of your choice.&nbsp; The Free plan limits requests to 60 per minute. Exceeding this limit will return an HTTP 503 (Service Unavailable) error, and you’ll receive upgrade instructions via email if this occurs.</p>



<p class="wp-block-paragraph"><strong>Important Note</strong>: If you have an existing enterprise trial, you’ll need to create a new organization to migrate to the free plan, then <a href="https://www.apollographql.com/docs/graphos/platform/graph-management/transfers">transfer</a> your existing GraphQL APIs and schemas to that new organization.&nbsp;</p>



<p class="wp-block-paragraph">For more information, check out the <a href="https://www.apollographql.com/pricing">https://www.apollographql.com/pricing</a> page and <a href="https://support.apollographql.com/space/ETKB/1297809476/Free+plan+FAQs">Apollo GraphOS Free plan FAQs</a>.</p>



<p class="wp-block-paragraph"></p>


Apollo GraphOS Free Plan: Unlock the Power of API Orchestration


<p class="wp-block-paragraph">Did you know mobile application performance was the use case that drove the initial development of GraphQL? GraphQL has grown by leaps and bounds and is now used to power entire API platforms, but it remains an essential part of the mobile application developer’s toolkit.  To that end, we are excited to launch new, free courses for <a href="https://www.apollographql.com/tutorials/apollo-ios-swift-part1">iOS</a> and <a href="https://www.apollographql.com/tutorials/apollo-kotlin-android-part1">Android</a> developers in the Apollo Odyssey learning platform!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="666" src="https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1024x666.png" alt="The image is a screenshot of a webpage from the Apollo GraphQL Odyssey tutorial series titled “Apollo iOS and Swift: Pagination, Mutations, and Subscriptions”. The tutorial section displayed is “Complete the details view”. The page includes a heading titled “Test the DetailView”, followed by instructions guiding users to build and run their application, verifying that clicking on a launch item navigates to a corresponding DetailView.

There are two prominent visuals on the page:
	1.	A screenshot of an Xcode editor showing SwiftUI code for handling the DetailView.
	2.	An iPhone simulator displaying a detailed launch view with a mission patch, launch details, and a “Book Now!” button.

The left sidebar contains a navigation menu with sections:
	•	Introduction
	•	Complete the details view (highlighted)
	•	Write your first mutation
	•	Authenticate your operations
	•	Define additional mutations
	•	Paginate results
	•	Write your first subscription

Below the main content, there is a paragraph mentioning that the “Book Now!” button has been added but isn’t functional yet, leading into the next section about making changes with GraphQL mutations, including authentication." class="wp-image-24074" srcset="https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1024x666.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-300x195.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-768x499.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1536x999.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-2048x1332.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1200x780.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1980x1287.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#apollo-ios-and-apollo-kotlin" aria-hidden="true" class="aal_anchor" id="apollo-ios-and-apollo-kotlin"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo iOS and Apollo Kotlin</h2>



<p class="wp-block-paragraph">Apollo is proud to maintain the most widely-used free and open source GraphQL clients for web and mobile platforms.  <a href="https://www.apollographql.com/docs/ios">Apollo iOS</a> and <a href="https://www.apollographql.com/docs/kotlin">Apollo Kotlin</a> are trusted by thousands of iOS and Android teams to power their production applications written in Swift and Kotlin.  In order to fully leverage these industry-standard tools, a grasp of the fundamentals is essential.</p>



<p class="wp-block-paragraph">App development teams getting started with GraphQL now have access to new two-part courses:</p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/tutorials/apollo-ios-swift-part1">Apollo iOS and Swift</a></li>



<li><a href="https://www.apollographql.com/tutorials/apollo-kotlin-android-part1">Android Development with Apollo Kotlin</a></li>
</ul>



<p class="wp-block-paragraph">All of these courses are part of our expansive and free Apollo Odyssey platform.  There’s plenty more where that came from, too: check out our extensive library of courses for UI developers, backend developers, and platform engineers.</p>



<p class="wp-block-paragraph">If you have any ideas for new courses, please post your feedback in this <a href="https://community.apollographql.com/t/new-odyssey-courses-for-apollo-kotlin-and-apollo-ios-post-your-feedback-here/8678" data-type="link" data-id="https://community.apollographql.com/t/new-odyssey-courses-for-apollo-kotlin-and-apollo-ios-post-your-feedback-here/8678">Apollo Community thread</a>!  We’re always eager to hear what people want to learn about next.</p>


New GraphQL courses for iOS and Android development

What’s New in GraphOS: Apollo Winter ’25 Release – Apollo Connectors, Native Query Planner, Improved Tools, and More!


<p class="wp-block-paragraph">Today we are releasing <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a>, a major update that brings our declarative, graph-based orchestration technology to teams using REST APIs.</p>



<p class="wp-block-paragraph">Modern applications integrate dozens or even hundreds of different APIs. The task is significant. These APIs must be called in a precise manner and sequence. API calls need to be chained together, feeding the output of one into the next. In some cases, it’s desirable to parallelize them for better performance. Synchronous services can be made async, and vice versa. Almost universally, it is necessary to filter, transform, and reformat the responses, as they are rarely an exact match for the needs of an application. Teams must properly handle errors and timeouts, not to mention authentication and authorization.</p>



<p class="wp-block-paragraph">We can give a name to these tasks: API orchestration.</p>



<p class="wp-block-paragraph">API orchestration accounts for a significant fraction of the total cost of implementing software. It shows up everywhere: application teams shipping roadmap items, companies migrating off of legacy software systems or onto modern microservice architectures, anyone acquiring products and integrating them together, and in every agentic AI project – the last of these especially top of mind now for many. And because orchestration requirements tend to be unique to each individual application or use case, teams end up accumulating a mountain of code dedicated to orchestration.</p>



<p class="wp-block-paragraph">In the vast majority of cases, API orchestration is implemented procedurally, as code. This is the world of backends-for-frontends, integration APIs, and SDKs autogenerated from service catalogs. Sometimes the code is implemented as a separate tier, as in the BFF pattern. Other times, it lurks inside applications or services. No matter where it lives, this code is expensive to write and annoying to maintain. It holds API-rich companies back from shipping great products and getting the most value from their API investments.</p>



<h3 class="wp-block-heading"><a href="#graphql-is-graph-based-api-orchestration" aria-hidden="true" class="aal_anchor" id="graphql-is-graph-based-api-orchestration"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL is graph-based API orchestration</h3>



<p class="wp-block-paragraph">What we’ve known all along is that GraphQL is really a technology for API orchestration. GraphQL federation, which we developed in collaboration with many of the teams using GraphQL at large scales, allows developers to write GraphQL queries that get executed as an automatically planned sequence of individual API calls. The heart of what makes this possible is an advanced runtime, the <a href="https://www.apollographql.com/graphos-router">Apollo Router</a>, that provides connection management, rate limits, error handling, API call chaining and more, all made available through GraphQL schemas and operations.</p>



<p class="wp-block-paragraph">Most of the API orchestration tasks I listed above? They’re built right into the Apollo Router with our implementation of <a href="https://www.apollographql.com/federation">GraphQL federation</a>. Apollo developers don’t write procedural code to cache API responses, enforce authentication policies, filter results, or join across APIs. To give one example of how much power comes with this, you can mark part of a query as “deferrable” which instructs the query planner to break the query into a synchronous portion and an async portion to be delivered later – typically data coming from slow APIs that you can’t allow to delay app interactivity or a screen render. Six characters and a couple of braces replace what would have been a significant amount of procedural code to write, test, and maintain.</p>



<p class="wp-block-paragraph">GraphQL federation has been a huge success. It now powers many of the largest online retailers, media properties, traditional banks, and fintech startups. It’s probably inside your television and will almost certainly be in your next car. Companies that adopt this architecture are able to ship new products in a fraction of the time it used to take and with far less development risk.</p>



<h3 class="wp-block-heading"><a href="#bringing-graphql-to-everyone" aria-hidden="true" class="aal_anchor" id="bringing-graphql-to-everyone"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Bringing GraphQL to everyone</h3>



<p class="wp-block-paragraph">There’s one hitch, though. To use graph-based API orchestration, you needed GraphQL APIs – either by adding GraphQL to existing services or by creating new GraphQL-specific services (what GraphQL federation developers call “subgraph servers”). This requirement was a significant up-front price of admission to the benefits of graph-based orchestration. And hearing customer after customer tell us about the REST APIs they wanted to bring to the graph led us to a key insight, which is that the responses from these APIs are awfully close to the entity objects that make up a federated GraphQL schema. All that’s really necessary is a language for describing the relationship between them.</p>



<p class="wp-block-paragraph">And that leads us to today’s news: we’re making <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a> for REST APIs generally available, which lets you define a GraphQL schema in terms of the REST APIs you have and orchestrate calls to those APIs with just a few lines of configuration. </p>



<p class="wp-block-paragraph">Connectors are meant to work with real-world APIs: they include functions you can use to restructure and transform API responses as needed and support the usual patterns for headers, auth credentials, and so on. And it’s just federated GraphQL under the hood, so you can use all the usual federation features and mix and match any combination of REST and GraphQL together. You can read much more technical detail about how Apollo Connectors work in our <a href="https://www.apollographql.com/blog/our-journey-to-apollo-connectors">engineering blog</a>, the <a href="https://www.apollographql.com/docs/graphos/schema-design/connectors">documentation</a>, or just give it a try with your own APIs. Everything you need is included in our free tier of GraphOS and you can be orchestrating APIs in well under an hour.<br>Since we <a href="https://www.apollographql.com/events/exploring-apollo-s-new-products-a-deep-dive">previewed Apollo Connectors</a> at GraphQL Summit in October we’ve worked with many of you to improve every aspect of their tooling and functionality. Early results are promising: you can read about how the team at <a href="https://www.apollographql.com/customers/cox-automotive">Cox Automotive </a>used Apollo Connectors to add a particularly important API to their graph in just days, saving nearly a year of otherwise planned development work. We’re looking forward to hearing about your experience.</p>



<h3 class="wp-block-heading"><a href="#the-future-is-declarative" aria-hidden="true" class="aal_anchor" id="the-future-is-declarative"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The future is declarative</h3>



<p class="wp-block-paragraph">Declarative architectures define the modern, cloud-native stack. Containerization for packaging software. React for packaging UI components. It should be no different for APIs.  Apollo Connectors allows developers to describe the data model they want, and let Apollo&#8217;s graph-based API orchestration infrastructure figure out how to do it.</p>



<p class="wp-block-paragraph">We believe declarative, graph-based orchestration is going to replace procedural orchestration code. We’re excited to see GraphQL become the standard that all developers can reach for and we’re committed to working with everyone interested to make that happen. And we can’t wait to see what you build with it.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Ready to get started? Try Connectors today with <a href="https://studio.apollographql.com/signup?referrer=blog">our new free tier</a>, explore our <a href="https://www.apollographql.com/docs/">documentation</a> and<a href="https://www.apollographql.com/tutorials/"> Odyssey training courses</a>, or join us at upcoming <a href="https://www.apollographql.com/events">Connectors Live events</a> to learn more. The future of APIs is here – powered by GraphQL-based API orchestration that makes it easier than ever to build applications.</td></tr></tbody></table></figure>


REST API Orchestration With GraphQL

Our Journey to Apollo Connectors


<p class="wp-block-paragraph">We&#8217;re announcing an important update: starting with the 1.60 release of <a href="https://www.apollographql.com/graphos-router">Apollo GraphOS Router</a> and Apollo Router Core coming in the next few weeks, <a href="https://www.apollographql.com/federation">Apollo Federation</a> 1.0 supergraphs will no longer be supported. This update accompanies the introduction of a <a href="https://www.apollographql.com/docs/graphos/routing/query-planning/native-query-planner">new native query planner</a> in these Apollo Router versions, marking a significant advancement in our technology. <a href="https://www.apollographql.com/docs/graphos/reference/migration/to-federation-version-2">Upgrading to Apollo Federation 2.0</a> is essential to leverage these improvements fully, and as Federation and Apollo Router are mission-critical infrastructure for your API workloads, we are here to guide you through every step of this transition to confidently operating your GraphQL platform.</p>



<p class="wp-block-paragraph"><strong>Understanding the importance of upgrading</strong></p>



<p class="wp-block-paragraph">The next Apollo Router versions, 1.60 and beyond, include a new native query planner with significant performance enhancements. Our extensive testing of over 620 million operations showed a median 10x improvement in query planning time, a 2.9x reduction in CPU utilization, and a 2.2x reduction in memory consumption. Designed specifically for Federation 2.0 supergraphs, this new query planner simplifies maintenance and enhances security by eliminating dependencies, including the need for a JavaScript execution engine within the Apollo Router process.</p>



<p class="wp-block-paragraph"><strong>Timeline and planning</strong></p>



<p class="wp-block-paragraph">Federation 1.0 supergraphs have been marked as deprecated in our <a href="https://www.apollographql.com/graphos/studio">GraphOS Studio</a> UI and users have not been able to create them since Q3 2023. With the upcoming new Apollo Router versions, support for Federation 1.0 supergraphs will end across all Apollo products, including Apollo Gateway. We strongly recommend you upgrade to Apollo Router and Federation 2.0 to ensure continued compatibility with our latest innovations.</p>



<p class="wp-block-paragraph">If you are still operating your GraphQL deployment without having yet migrated to Federation 2.0, upgrading to the new query planner in Apollo Router 1.60 and beyond will introduce a breaking change.&nbsp;</p>



<p class="wp-block-paragraph">Migration to Federation 2.0 is simple and focuses on the composition layer, without requiring changes to existing subgraphs in most cases. You only need to compose a supergraph with Federation 2.0 and typically your subgraphs can continue using Federation 1.0 until they need 2.0 features. Our<a href="https://www.apollographql.com/docs/graphos/reference/migration/to-federation-version-2"> migration guide</a> details how you can update just your Federation composition step to compile a compatible supergraph.</p>



<p class="wp-block-paragraph"><strong>Available resources and ongoing support</strong></p>



<p class="wp-block-paragraph">We recognize that transitioning from Federation 1.0 to Federation 2.0 is a significant step for some of our users. This decision reflects our commitment to eliminating the complexities of outdated technology and ensuring our offerings meet the evolving needs of modern API infrastructures. We are dedicated to transparent communication and improving our deprecation processes to help maintain the robustness, efficiency, and security of your systems.&nbsp;</p>



<p class="wp-block-paragraph">Apollo values your partnership and trust as we continue to innovate. We are here to support you through this transition to keep your API infrastructure powerful and future-proof. For additional support, please visit our <a href="https://community.apollographql.com/t/migrate-apollo-federation-1-0-supergraphs-to-apollo-federation-2-0/8125">Apollo Community</a> or, for GraphOS users, contact our Technical Support team at <a href="mailto:support@apollographql.com">support@apollographql.com</a>. </p>



<p class="wp-block-paragraph"></p>


Migrate Apollo Federation 1.0 Supergraphs to Apollo Federation 2.0


<p class="wp-block-paragraph">Writing resolvers for REST APIs has been a rite of passage for developers working with GraphQL, but what if there were an easier way? Meet Apollo Connectors.&nbsp;&nbsp;</p>



<p class="wp-block-paragraph">As shown in Figure 1, Apollo Connectors mitigate the need to write code that connects to and returns data from REST APIs, reducing code surface area and time so you can focus on the business problem you&#8217;re trying to solve.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdJZU6oZN7MiGs9r1tQQXZkwJJpcuPFikCrKor3lk6x3MroNldHwChst6pbHyV0h2d8fx0bdhmW7xxntWRZCNWhxOe3ZrMe-lt0P1_MZQ16jxNuOmPkQdayuZT_XW9cF_69YpmiEA?key=Tfq51hg4_0CBkUiIKxkXplEo" alt=""/></figure>



<p class="wp-block-paragraph"><em>Figure 1: Data flow showing Apollo Connector for REST APIs</em></p>



<p class="wp-block-paragraph">In this article, we will walk through a React client web application that leverages the Apollo GraphQL client to call a public <a href="https://currencyapi.com/">CurrencyAPI</a> web service using the REST API Apollo Connector for REST APIs.&nbsp; A screenshot of the UI is seen in the following figure:&nbsp;&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdmYwlhbO07vkGGfTIugVC2usLpczle-KJMiJoGsGgE53FYx4zzzo3TFsFiMJ5InCSTzJ7HA7cSxtF9HRXJLQ7j6zhZ1jatfDn1WGDFQ2sY-ixRi7Fmpz-HNH2TQPQiOOmat7an?key=Tfq51hg4_0CBkUiIKxkXplEo" alt=""/></figure>



<p class="wp-block-paragraph"><em>Figure 2: Screenshot of the Currency Converter</em></p>



<p class="wp-block-paragraph">Under the covers, the React app uses the GraphQL Client as usual and issues the query statement.&nbsp; There are no changes there.&nbsp; On the backend, you simply define the GraphQL schema file and that’s it. There is no need to create resolvers to fetch the data from the REST API.&nbsp; In the following sections, you will learn how to set up and configure the Apollo Connector for REST APIs.</p>



<h1 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting Started</h1>



<p class="wp-block-paragraph">In this article we will use a third party service called CurrencyAPI to fetch real-time currency exchange rates.&nbsp; At the time of this writing (Nov 2024), CurrencyAPI offers a free API key.&nbsp; If you wish to follow along, create an API key from <a href="https://currencyapi.com/">https://currencyapi.com/</a> and copy it down, as you will need it later.</p>



<p class="wp-block-paragraph">You will also need an Apollo account and the latest version of Apollo Rover CLI.&nbsp; See sections 1 and 2 of the following Apollo Connector tutorial for installation instructions:</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/tutorials/connectors-intro-rest/02-setup">https://www.apollographql.com/tutorials/connectors-intro-rest/02-setup</a></p>



<p class="wp-block-paragraph">Next, clone the repository.</p>



<p class="wp-block-paragraph"><code class="" data-line="">git clone https://github.com/RWaltersMA/CurrencyConverter.git</code></p>



<h2 class="wp-block-heading"><a href="#obtain-api-keys-and-configure-demo" aria-hidden="true" class="aal_anchor" id="obtain-api-keys-and-configure-demo"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Obtain API keys and configure demo</h2>



<p class="wp-block-paragraph">At the time of this writing, Apollo Connectors is in preview with an anticipated general availability in early 2025.&nbsp; This blog will be updated as this feature evolves.</p>



<p class="wp-block-paragraph">Now, we are ready to configure Apollo Studio and obtain our API Key.&nbsp; Navigate to <a href="http://studio.apollographql.com/?_gl=1*tm0r8z*_gcl_aw*R0NMLjE3MzE3MDM4ODQuQ2owS0NRaUFfOXU1QmhDVUFSSXNBQmJNU1BzRm5OM1NIXzRWQWN2VHJGRFBrQkctcVltVk9ncU1iLUJjczh4YkpBOVlUZzFGQ3MyWngwZ2FBaHBfRUFMd193Y0I.*_gcl_au*MTM2NzI4NDM4Ny4xNzMwMjIwNjQ0">Apollo Studio</a> and click “Create a new Graph.”&nbsp; In the “Publish your schema using Federation” dialog, you will see toward the bottom the API Key to be used with Rover.</p>



<p class="wp-block-paragraph">Below is a sample:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">APOLLO_KEY=service:Currency-02wxjh:xxxxxxxxxxxxxxx \
  rover subgraph publish Currency-02wxjh@current \
  --schema ./products-schema.graphql \
  --name your-subgraph-name \
  --routing-url http://products.prod.svc.cluster.local:4001/graphql</code></pre>



<p class="wp-block-paragraph">Copy the value for <code class="" data-line="">APOLLO_KEY</code>.&nbsp; Open the <code class="" data-line="">rover-dev.md file</code> and update the section with your personalized <code class="" data-line="">APOLLO_KEY</code>.&nbsp; Copy the service name to <code class="" data-line="">APOLLO_GRAPH_REF</code> and save the file.</p>



<p class="wp-block-paragraph">Next, update the <code class="" data-line="">router-config.yaml</code> file and replace the placeholders “&lt;&lt;REPLACE&gt;&gt;” with the API Key you obtained from currencyAPI and save this file.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml" data-line="">preview_connectors:
  subgraphs:
    currency:
      $config:
        # Replace this value with your currencyAPI key
        apikey: &lt;&lt;REPLACE&gt;&gt;</code></pre>



<p class="wp-block-paragraph">Now, we are ready to start a local Apollo instance.&nbsp; Copy and paste into a terminal the <code class="" data-line="">rover dev</code> statement that is within your <code class="" data-line="">rover-dev.md </code>file.&nbsp; For example, the command for <code class="" data-line="">sh</code> looks like the following:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session" data-line="">APOLLO_KEY=&quot;service:Currency-02wxjh:xxxxxxxxxx&quot; \
APOLLO_GRAPH_REF=&quot;Currency-02wxjh@current&quot; \
APOLLO_ROVER_DEV_ROUTER_VERSION=2.0.0-preview.1 \
rover dev --supergraph-config supergraph.yaml --router-config router-config.yaml</code></pre>



<p class="wp-block-paragraph">If successful, the console will display the following:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">supergraph config loaded successfully
warning: Do not run this command in production! It is intended for local development only.
==&gt; Watching /Users/robwalters/Code/CurrencyConverter/currency.graphql for changes
WARN: Connector debugging is enabled, this may expose sensitive information.
==&gt; your supergraph is running! head to http://localhost:4000 to query your supergraph
successfully composed with version =2.10.0-preview.0
successfully composed with version =2.10.0-preview.0 after updating the &#039;currency&#039; subgraph</code></pre>



<div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained">
<p class="wp-block-paragraph">A note about <code class="" data-line="">router-config.yaml</code>:&nbsp; In this example, we are launching a react client on the same machine as Rover.&nbsp; Since these are operating on different ports, the client on localhost:4000 and Rover on localhost:3000, the server needs to address CORS (Cross origin resource sharing).&nbsp; To do this, we added the following configuration to the <code class="" data-line="">router-config.yaml </code>file:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml" data-line="">cors:
  allow_any_origin: true</code></pre>
</div></div>



<p class="wp-block-paragraph">Note that setting CORS to allow any origin option is not recommended for production use unless necessary.&nbsp; For more information on configuration parameters in the router, check out the <a href="https://www.apollographql.com/docs/graphos/reference/router/configuration#yaml-config-file">online documentation</a>.</p>



<h1 class="wp-block-heading"><a href="#starting-the-client" aria-hidden="true" class="aal_anchor" id="starting-the-client"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Starting the client</h1>



<p class="wp-block-paragraph">Navigate to the <strong>client</strong> folder and issue:</p>



<p class="wp-block-paragraph"><code class="" data-line="">npm install</code></p>



<p class="wp-block-paragraph">Then</p>



<p class="wp-block-paragraph"><code class="" data-line="">npm start</code></p>



<p class="wp-block-paragraph">Once launched, a web browser will open to localhost:3000 and display the UI shown in Figure 2.</p>



<p class="wp-block-paragraph">Enter any value into the amount and select your favorite base and desired currency.&nbsp; Press Convert to see the most current amount in your desired currency.</p>



<p class="wp-block-paragraph">Let’s take a look at what is happening under the covers.&nbsp; First let’s look at the client code, specifically the <code class="" data-line="">convert.js</code> file within the <strong>src/components </strong>folder.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-typescript" data-line="">// GraphQL query to fetch currencyList and listExchangeRate
const GET_currencyList = gql`
  query Query {
    currencyList {
      symbol
      name
    }
    listExchangeRate {
      symbol
      rate
    }
  }
`;</code></pre>



<p class="wp-block-paragraph">Our simple example has two queries <code class="" data-line="">currencyList</code><strong>,</strong> which returns the complete list of symbols and names for the currency, and <code class="" data-line="">listExchangeRate</code><strong>,</strong> which returns the current rate for each symbol.&nbsp; These data are used to populate the drop-downs in the UI.&nbsp; When using Apollo Connectors, the client does not need to make any changes.&nbsp; It is business as usual for your front-end folks.&nbsp; The real magic is in the back end.</p>



<h1 class="wp-block-heading"><a href="#taking-a-closer-look-at-the-apollo-connector" aria-hidden="true" class="aal_anchor" id="taking-a-closer-look-at-the-apollo-connector"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Taking a closer look at the Apollo Connector</h1>



<p class="wp-block-paragraph">Open the <code class="" data-line="">currency.graphql</code> file.&nbsp; This file contains the configuration for the REST Apollo Connector.&nbsp;&nbsp;</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">extend schema
  @link(
    url: &quot;https://specs.apollo.dev/federation/v2.10&quot;
    import: [&quot;@key&quot;]
  )
  @link(
    url: &quot;https://specs.apollo.dev/connect/v0.1&quot;
    import: [&quot;@source&quot;, &quot;@connect&quot;]
  )
  @source(
    name: &quot;v1&quot;
    http: {
      baseURL: &quot;https://api.currencyapi.com/v3/&quot;
      headers: [{ name: &quot;apikey&quot;, value: &quot;{$config.apikey}&quot; }]
    }
  )

type Query {
  &quot;A list of currencies&quot;
  currencyList: [Currency]
    @connect(
      source: &quot;v1&quot;
      http: { GET: &quot;/currencies&quot; }
      selection: &quot;&quot;&quot;
        data-&gt;entries {
          symbol: key
          name: value.name
        }
      &quot;&quot;&quot;
    )

  &quot;List exchange rates&quot;
  listExchangeRate: [ExchangeRate]
    @connect(
      source: &quot;v1&quot;
      http: { GET: &quot;/latest&quot; }
      selection: &quot;&quot;&quot;
        data-&gt;entries {
          symbol: key
          rate: value.value
        }
      &quot;&quot;&quot;
    )
}

type Currency {
   symbol: String
   name: String
}

type ExchangeRate {
   symbol: String
   rate: Float
}</code></pre>



<p class="wp-block-paragraph">This is all that is needed for your Apollo Server to connect to a REST API, no extra resolver code!&nbsp; Looking at the GraphQL query, you’ll see an <code class="" data-line="">@link</code> statement referencing Apollo Connector.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">@link(
  url: &quot;https://specs.apollo.dev/connect/v0.1&quot;
  import: [&quot;@source&quot;, &quot;@connect&quot;]
)</code></pre>



<p class="wp-block-paragraph">Here, we are importing the <code class="" data-line="">@source</code> and <code class="" data-line="">@connect</code> directives.&nbsp; The <code class="" data-line="">@connect</code> requires additional configuration parameters such as the details about the HTTP request, any headers, and a parameter called “selection” which filters the data from the REST API results.&nbsp; Here is the <code class="" data-line="">currencyList</code> field in our example:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">  &quot;A list of currencies&quot;
  currencyList: [Currency]
    @connect(
      source: &quot;v1&quot;
      http: { GET: &quot;/currencies&quot; }
      selection: &quot;&quot;&quot;
        data-&gt;entries {
          symbol: key
          name: value.name
        }
      &quot;&quot;&quot;
    )</code></pre>



<p class="wp-block-paragraph">In this query, the Apollo Connector will use the base url defined in the <code class="" data-line="">@link</code> and append the string defined as part of the HTTP request type in this case is GET.&nbsp; Since our currencyAPI endpoint requires an authentication header, we add the <strong>headers</strong> field and add a key-value pair referencing the API Key and value we defined earlier in the <code class="" data-line="">router-config.yaml </code>file.&nbsp; Next, we need to tell the connector what data to extract from the API results.&nbsp; We define this in the <strong>selection</strong> parameter.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-perl" data-line="">data-&gt;entries {
  symbol: key
  name: value.name
}</code></pre>



<p class="wp-block-paragraph">For reference, the data that returns from the CurrencyAPI is similar to the following:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-json" data-line="">{
  &quot;data&quot;: {
    &quot;AED&quot;: {
      &quot;symbol&quot;: &quot;AED&quot;,
      &quot;name&quot;: &quot;United Arab Emirates Dirham&quot;,
      &quot;symbol_native&quot;: &quot;د.إ&quot;,
      &quot;decimal_digits&quot;: 2,
      &quot;rounding&quot;: 0,
      &quot;code&quot;: &quot;AED&quot;,
      &quot;name_plural&quot;: &quot;UAE dirhams&quot;,
      &quot;type&quot;: &quot;fiat&quot;,
      &quot;countries&quot;: [
        &quot;AE&quot;
      ]
    },
    ...
  }
}</code></pre>



<p class="wp-block-paragraph">For our client we want to return just the symbol and name of each of the currencies.&nbsp; Since our return result has all our data under the “data” field, we start with data and iterate through each subdocument using the <strong>entities</strong> keyword.&nbsp; For each of these <strong>entities,</strong> we return the key, which in this example result is “AED” and add that value to a “symbol” field.&nbsp; We give the field “name” the value of the name field in the result. For a complete discussion and more examples of selection parameters, see the <a href="https://www.apollographql.com/docs/graphos/schema-design/connectors/selection">online documentation</a>.</p>



<h1 class="wp-block-heading"><a href="#summary" aria-hidden="true" class="aal_anchor" id="summary"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Summary</h1>



<p class="wp-block-paragraph">Building resolvers for REST APIs can be a complex yet essential task for developers working with GraphQL. However, Apollo Connectors now provide a simpler, more efficient way to integrate REST APIs into your GraphQL schema, eliminating the need for custom resolver code. In this article, you learned how to setup and configure an Apollo Connector for REST APIs that query data from the CurencyAPI public API endpoint.&nbsp; Apollo Connectors is currently in preview, for more information, check out the <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a> website.</p>



<h1 class="wp-block-heading"><a href="#call-to-action" aria-hidden="true" class="aal_anchor" id="call-to-action"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Call to action</h1>



<p class="wp-block-paragraph">Curious how Apollo Connectors can streamline your GraphQL workflows? Sign up for a <a href="https://www.apollographql.com/connectors-demo">demo</a> or join our upcoming webinar on December 12th, 2024: <a href="https://www.apollographql.com/events/api-orchestration-in-30-minutes-a-stripe-checkout-workflow-with-apollo-connectors">API Orchestration in 30 Minutes: A Stripe Checkout Workflow with Apollo Connectors</a>.&nbsp; After attending this webinar, you will have a solid understanding of orchestrating API calls with Apollo Connectors in the context of real-world use cases.&nbsp; If you are reading this after the event date, the webinar will be available on-demand.</p>


Effortless Data Fetching: Introducing Apollo Connectors for REST APIs


<p class="wp-block-paragraph">Apollo Connectors make it easier than ever to create a GraphQL API leveraging non-GraphQL services. Developers can use a declarative syntax, right in their schema files, to connect GraphQL fields to HTTP APIs. GraphOS Router uses that information to talk <em>directly</em> to the API, no subgraph needed.</p>



<h2 class="wp-block-heading"><a href="#reducing-complexity" aria-hidden="true" class="aal_anchor" id="reducing-complexity"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Reducing complexity</h2>



<p class="wp-block-paragraph">Before today, when developers wanted to add a REST service to their federated GraphQL API, they had to take several steps:</p>



<ol class="wp-block-list">
<li>Identify a programming language and a Federation-compatible GraphQL framework</li>



<li>Deploy a new subgraph service, including monitoring, auto-scaling, and load-balancing, which will sit in between the router and the REST API</li>



<li>For each change to the REST API:
<ol class="wp-block-list">
<li>Design the subgraph schema for the underlying REST data</li>



<li>Write bindings to the REST API in the chosen programming language</li>



<li>Write resolvers that leverage those bindings</li>



<li>Deploy the subgraph service</li>



<li>Compose and publish the schema to update the router</li>
</ol>
</li>
</ol>



<p class="wp-block-paragraph">Apollo Connectors eliminate the need for the intermediate service, saving developer time and infrastructure cost. With connectors, each iteration is reduced to:</p>



<ol class="wp-block-list">
<li>Design the subgraph schema for the underlying REST data</li>



<li>Compose and publish the schema to update the router</li>
</ol>



<p class="wp-block-paragraph">The router then speaks directly to the REST APIs:</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd9Ttaekoj3X97LvhKoxcsHefPNT2jOCAh5GViBlTzPwsiGwXwmCMFahiAhQ81UNfPP6h4y_f4rnW4V8Fyh-wRlyjvRMXvT6FcTY4m8CGpQk_V3L1hgX5YZQhLl8AhEa7EjYdZJ0hROdshuIyUgDSXVsio?key=X-2ujg-cWaXZiwKXT52_aQ" alt=""/></figure>



<h2 class="wp-block-heading"><a href="#delighting-developers" aria-hidden="true" class="aal_anchor" id="delighting-developers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Delighting developers</h2>



<p class="wp-block-paragraph">Apollo Connectors are designed with a singular goal in mind: make it as easy as possible for developers to build high-quality GraphQL APIs. Every aspect was built from the ground up to achieve this goal, starting with the declarative syntax:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">type Query {
 post(id: ID!): Post
   @connect(
     source: &quot;rest_api_v1&quot;
     http: { GET: &quot;/posts/{$args.id}&quot; }
     selection: &quot;&quot;&quot;
       id
title
body
author: { id: userId }
     &quot;&quot;&quot;
   )
}</code></pre>



<p class="wp-block-paragraph">Data sources are connected right in your schema, so there&#8217;s no need to hop back and forth between multiple files. The selection format, for transforming the data, is designed to feel like the GraphQL query language to reduce context switching. It&#8217;s also designed to provide as much feedback as possible early in the development lifecycle, especially when combined with our <a href="http://go.apollo.dev/connectors/guides#visual-studio-code">Visual Studio Code extension</a>. No more catching typos after deploy:</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfTnKYrGuW1QQgne9IzJQFlLYxcC_tYJD8KOGK4MV2o1jlSiV-tmWWYyR-Mr42H0bQoz0TyKM1nTW8Rd3xymb7s2JRS3JB881hhNPmuSLhho9IfACWABG7xI917Pk6cskl45msWuHK9AdjwR8_lanBEat0?key=X-2ujg-cWaXZiwKXT52_aQ" alt=""/><figcaption class="wp-element-caption">Apollo&#8217;s Visual Studio Code extension underlines errors in your Connectors definition</figcaption></figure>



<p class="wp-block-paragraph">Our focus on developers extends through the testing phase, with powerful new debugging tools built into <a href="https://www.apollographql.com/docs/graphos/explorer/sandbox/">Apollo Sandbox</a>:</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcuYoRXVO2LnwxaISPX-Cn_aGE_-Hz5J9W_rmxODLNyECou0Q3MLijxEYKRiMxnvCiQnqLSRqTvTaMPByLdVx-A2xLCoZpHlW8YirW0gZA8m0fRnUmmziCfeJoSbwLuCOjfM93XRz6yhXKpl4U69ydOs1O1?key=X-2ujg-cWaXZiwKXT52_aQ" alt=""/></figure>



<p class="wp-block-paragraph">And, of course, you get the production-ready features you&#8217;ve come to expect from GraphOS Router, like in-depth observability, built on the OpenTelemetry standard:</p>



<figure class="wp-block-image is-resized"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfZi8mBk3kSsuD3CUdbPZpxzdtXdVfpdaZawe42ny1vaohq8hUwWffKVwOF-7bmBsZeaTfx0SMHa830H9A4xFZNiYzKNyut-_g5Op_0LdyyfVZ6k31axT-fWlrnjKU28F_M3p4EBvbQGe24KrFxpDJOItpu?key=X-2ujg-cWaXZiwKXT52_aQ" alt="" style="width:610px;height:auto"/><figcaption class="wp-element-caption">Apollo Studio&#8217;s insights page</figcaption></figure>



<h2 class="wp-block-heading"><a href="#get-connected" aria-hidden="true" class="aal_anchor" id="get-connected"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get connected</h2>



<p class="wp-block-paragraph">Apollo is on a journey to make developing, operating, and consuming APIs as delightful as possible. GraphQL is a developer-friendly abstraction over all the moving pieces of modern applications. Apollo Connectors make the process of tying those pieces together into a cohesive, well-crafted schema, better than ever. You can <a href="https://go.apollo.dev/connectors">try out connectors today</a> with your existing Enterprise plan or by getting <a href="https://studio.apollographql.com/signup?referrer=blog">started with GraphOS</a> for free. Send us your feedback and ask questions in our <a href="https://community.apollographql.com/tag/connectors">forums</a> or <a href="https://discord.gg/graphos">Discord server</a>. We can&#8217;t wait to see what you create!</p>


Apollo Connectors: Blazing-Fast Integration with REST APIs

What’s new in Apollo GraphOS 


<p class="wp-block-paragraph">Apollo Kotlin 4 is the new major version of Apollo Kotlin. It builds on top of Apollo Kotlin 3 and brings a number of tooling and API improvements:</p>



<ul class="wp-block-list">
<li>A brand new IDE plugin for all your refactoring needs.</li>



<li>Improvement to the error handling APIs, making it easier to handle errors in a single place.</li>



<li>WasmJs support.</li>



<li>A multiplatform GraphQL parser.</li>



<li>A preview of semantic nullability.</li>



<li>Network monitoring API, new WebSocket APIs and more …</li>
</ul>



<p class="wp-block-paragraph">For a comprehensive list of all changes, please review the <a href="https://github.com/apollographql/apollo-kotlin/releases/tag/v4.0.0">full changelog</a>.</p>



<p class="wp-block-paragraph">If you&#8217;re currently using Apollo Kotlin 3, refer to the <a href="https://www.apollographql.com/docs/kotlin/v4/migration/4.0/#moved-artifacts">migration guide</a> for step-by-step migration instructions.</p>



<p class="wp-block-paragraph">Or read on for a brief summary of the key updates and a preview of what&#8217;s on the horizon.</p>



<h2 class="wp-block-heading"><a href="#android-studio-intellij-plugin" aria-hidden="true" class="aal_anchor" id="android-studio-intellij-plugin"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Android Studio/IntelliJ plugin</h2>



<p class="wp-block-paragraph">If you’re using Android Studio or IntelliJ, <a href="https://www.apollographql.com/docs/kotlin/v4/testing/android-studio-plugin/">you can now download the Apollo IntelliJ plugin in the IntelliJ marketplace</a> and get even more help from your IDE.</p>



<p class="wp-block-paragraph">Apollo IDE plugin core features include:</p>



<ul class="wp-block-list">
<li>On the fly code generation</li>



<li>GraphQL &lt;-> Kotlin navigation</li>



<li>Unused field inspection</li>



<li>High Field latency inspection</li>



<li>Normalized cache viewer</li>



<li>Schema download </li>



<li>Automatic migration</li>
</ul>



<p class="wp-block-paragraph">That last point means you can now use the plugin to automate most of your v3 -&gt; v4 migration.</p>



<p class="wp-block-paragraph"><img loading="lazy" decoding="async" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXdaWp_FZSNQWfiwe6FNOOsEcoK1pc4K1wAsu7BX6Am-8yP7Rdjs0ZPGbgppgMND00Yvs4iBQbOlY9IBVwwYhjUNrHUq8_vIeAGxaxKNvL7S_aG00mq18dCdD8PYBtBbQO5-_8XWu5e1wL2MtRvZykK-86SW?key=12X6ltZW9oZBbxKegGgpWw" width="668" height="463"></p>



<h2 class="wp-block-heading"><a href="#api-consolidation" aria-hidden="true" class="aal_anchor" id="api-consolidation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>API consolidation</h2>



<p class="wp-block-paragraph">With the release of Apollo Kotlin 4, we&#8217;ve achieved a significant milestone where our core APIs—including code generation, parsers, and interceptors—are now stable. This stability means we don’t anticipate any major overhauls like the transition from version 2 to 3, though the landscape of Kotlin and GraphQL continues to evolve rapidly. Developments such as <a href="https://youtrack.jetbrains.com/issue/KT-68296">union types for errors</a> or <a href="https://github.com/graphql/nullability-wg/discussions/58">semantic nullability schemas</a> may necessitate breaking changes in the future.</p>



<p class="wp-block-paragraph">Looking ahead, our goal is to roll out smaller, more frequent updates, including major versions. This approach will keep the core APIs consistent, enabling us to introduce new features and adapt more swiftly to changes in the environment. To facilitate this, we’ve updated the package name from <code class="" data-line="">com.apollographql.apollo3</code> to <code class="" data-line="">com.apollographql.apollo</code>.<br><br>With Apollo Kotlin 4, we are also introducing an evolution policy. This policy will steer the development of future versions and ensure that we provide clear deprecation notices, helping you to transition smoothly and confidently.</p>



<h2 class="wp-block-heading"><a href="#multiplatform-graphql-parser" aria-hidden="true" class="aal_anchor" id="multiplatform-graphql-parser"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Multiplatform GraphQL parser</h2>



<p class="wp-block-paragraph">Previously, Apollo Kotlin relied on<a href="https://github.com/graphql/graphql-js" data-type="link" data-id="https://github.com/graphql/graphql-js"> <code class="" data-line="">graphql-js</code></a> for parsing GraphQL documents. In version 2, we transitioned to using <a href="https://www.antlr.org/">Antlr</a> to generate parsers from <code class="" data-line="">.g4</code> grammars.</p>



<p class="wp-block-paragraph">With Apollo Kotlin 4, we’ve taken a significant leap forward by developing our <a href="https://github.com/apollographql/apollo-kotlin/pull/5047">own recursive descent</a> parser.</p>



<p class="wp-block-paragraph">The new parser not only performs up to <a href="https://github.com/apollographql/apollo-kotlin/pull/5047#issue-1780385717">twice </a>as fast as the previous Antlr-based parser in certain scenarios, but it’s also entirely written in Kotlin, ensuring full multiplatform support. This means you can seamlessly integrate it into your Kotlin multiplatform projects just like any other KMP dependency.</p>



<p class="wp-block-paragraph">Here’s how you can add the new parser to your project:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin" data-line="">kotlin {
  sourceSets {
    getByName(&quot;commonMain&quot;) {
      dependencies {
        implementation(&quot;com.apollographql.apollo:apollo-ast&quot;)
      }
    }
  }
}</code></pre>



<p class="wp-block-paragraph">And here’s how to utilize it at runtime:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin" data-line="">  // Parse a document
  val document = &quot;query { hello }&quot;.toGQLDocument()

  // transform/inspect it
  // And serialize it again
  println(document.toUtf8())</code></pre>



<h2 class="wp-block-heading"><a href="#introducing-wasmjs-support" aria-hidden="true" class="aal_anchor" id="introducing-wasmjs-support"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Introducing WasmJs support</h2>



<p class="wp-block-paragraph">Apollo Kotlin 4 now includes support for the WasmJs target, expanding your capabilities to use the generated models and <code class="" data-line="">apollo-runtime</code> in a Wasm application. Experience this new feature firsthand by trying out the Confetti wasm demo at <a href="https://wasm.confetti-app.dev/">https://wasm.confetti-app.dev/</a> (<a href="https://github.com/joreilly/Confetti">GitHub</a>).</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="874" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-874x1024.png" alt="" class="wp-image-23864" srcset="https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-874x1024.png 874w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-256x300.png 256w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-768x900.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-1311x1536.png 1311w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-1748x2048.png 1748w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-1200x1406.png 1200w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47.png 1886w" sizes="auto, (max-width: 874px) 100vw, 874px" /></figure>



<h2 class="wp-block-heading"><a href="#enhancing-nullability-handling" aria-hidden="true" class="aal_anchor" id="enhancing-nullability-handling"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Enhancing nullability handling</h2>



<p class="wp-block-paragraph">In GraphQL, <a href="https://graphql.org/learn/best-practices/#nullability">fields are traditionally nullable by default</a>. However, the standards set in 2015 don’t always align with the needs of 2024, especially as <a href="https://github.com/graphql/nullability-wg/">the GraphQL community seeks to enhance </a>type safety for languages like TypeScript, Swift, and Kotlin.</p>



<p class="wp-block-paragraph">Apollo Kotlin 4 introduces two experimental directives, <code class="" data-line="">@semanticNonNull</code> and <code class="" data-line="">@catch</code>, designed to simplify interactions with nullable fields.</p>



<p class="wp-block-paragraph">The <code class="" data-line="">@semanticNonNull</code> directive is a server-side directive, indicating that a field is guaranteed to be non-null unless an error happens. This directive can be incorporated into your <code class="" data-line="">.graphqls</code> schema extensions, enhancing the clarity and reliability of your data models:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin" data-line=""># name is never null unless an error happens
extend type User @semanticNonNullField(name: &quot;name&quot;)</code></pre>



<p class="wp-block-paragraph">On the code generation front, Apollo Kotlin recognizes <code class="" data-line="">@semanticNonNullField</code> and accordingly generates non-null Kotlin properties, ensuring that your application code remains type-safe and concise.</p>



<p class="wp-block-paragraph">Additionally, the <code class="" data-line="">@catch</code> directive is a client-side directive for opting into specific error handling strategies during operations. By using <code class="" data-line="">@catch</code> in your <code class="" data-line="">.graphql</code> operations, you can manage how errors are handled directly within the data context—whether by mapping errors to <code class="" data-line="">null</code>, re-throwing them, or using another method:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin" data-line="">query GetUser {
  user {
    # map name to FieldResult&lt;String?&gt; instead of stopping parsing
    name @catch(to: RESULT)
  }
}</code></pre>



<p class="wp-block-paragraph">For a deeper understanding of these enhancements and their implications on your projects, please refer to our detailed <a href="https://www.apollographql.com/docs/kotlin/v4/advanced/nullability#handle-errors-and-receive-partial-data-with-catch">nullability documentation page</a>.</p>



<h2 class="wp-block-heading"><a href="#looking-ahead" aria-hidden="true" class="aal_anchor" id="looking-ahead"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Looking ahead</h2>



<p class="wp-block-paragraph">Beyond the updates already discussed, Apollo Kotlin 4 introduces several exciting features including support for<a href="https://github.com/graphql/graphql-spec/pull/825"> <code class="" data-line="">@oneOf</code></a>, new WebSockets APIs, new low-level Apollo compiler plugin APIs, and new Gradle APIs. For a detailed list of all the enhancements, make sure to read the full changelog.</p>



<p class="wp-block-paragraph">One significant area poised for further development is the normalized cache, which continues to present challenges. While Apollo Kotlin 3 introduced <a href="https://www.apollographql.com/docs/kotlin/caching/declarative-ids/">&nbsp;<code class="" data-line="">@typePolicy</code> and <code class="" data-line="">@fieldPolicy</code> for declarative ids</a>, certain scenarios still demand the use of complex programmatic APIs.</p>



<p class="wp-block-paragraph">Additionally, issues such as garbage collection and invalidation remain unresolved. We aim to address these in version 5.</p>



<p class="wp-block-paragraph">With the modularization of Apollo Kotlin development has shifted to <a href="https://github.com/apollographql/apollo-kotlin-normalized-cache-incubating/">a separate repository</a>, enabling more agile iteration and improvement.<br>For the latest updates and future plans, please refer to <a href="https://github.com/apollographql/apollo-kotlin/blob/main/ROADMAP.md">the ROADMAP</a> document on what is being worked on.</p>



<h2 class="wp-block-heading"><a href="#join-the-community" aria-hidden="true" class="aal_anchor" id="join-the-community"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Join the community</h2>



<p class="wp-block-paragraph">Have a question or wish to discuss GraphQL, Kotlin, or the<a href="https://github.com/apollographql/apollo-kotlin/blob/main/ROADMAP.md"> ROADMAP</a>? We encourage you to connect with us and join the conversation:</p>



<ul class="wp-block-list">
<li><a href="https://github.com/apollographql/apollo-android/issues">Github</a></li>



<li><a href="http://community.apollographql.com/new-topic?category=Help&amp;tags=mobile,client">Community forums</a></li>



<li>Join the <a href="https://app.slack.com/client/T09229ZC6/C01A6KM1SBZ">Apollo KotlinLang slack channel</a> (click <a href="https://slack.kotl.in/">here</a> for an invite).</li>
</ul>



<p class="wp-block-paragraph">We&#8217;re here to support you and look forward to your insights and contributions!</p>


Apollo Kotlin 4 is now available


<p class="wp-block-paragraph">On, June 12, 2024, we hosted our <a href="https://www.apollographql.com/events/apollo-graphos-summer-update-operational-excellence-for-graphql-federation">GraphOS summer launch event</a>, where we announced new features designed to improve the performance and operational excellence of GraphQL platforms. These new capabilities improve how API platform teams implement and optimize GraphQL federation, providing faster baseline performance and greater control over API request execution in a supergraph.</p>



<h2 class="wp-block-heading"><a href="#graphql-federation-usage-on-the-rise" aria-hidden="true" class="aal_anchor" id="graphql-federation-usage-on-the-rise"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL Federation: Usage on the rise</h2>



<p class="wp-block-paragraph">GraphQL adoption in the enterprise is at an inflection point, driven by the proliferation of federated GraphQL architectures – a pattern originally introduced by Apollo GraphQL in 2019 with the launch of Apollo Federation and <a href="https://www.apollographql.com/graphos">GraphOS</a>. In a <a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery">recent report</a>, Gartner® predicts that 30% of enterprises using GraphQL will utilize GraphQL federation by 2027, up from less than 5% in 2024. Apollo believes this trend suggests the number of enterprises using GraphQL federation as their API access layer will increase by 12x.</p>



<p class="wp-block-paragraph">Apollo Federation is a specification for modularly and declaratively mapping existing application services into a unified GraphQL API access layer, known as a supergraph. This architecture empowers platform engineering teams to provide client applications with self-serve access to services through a single GraphQL endpoint, facilitating the rapid evolution of complex end-user experiences. By decoupling backend development from frontend complexity, teams can independently manage and contribute services to the supergraph via subgraphs, representing core business entities such as Product, User, or Cart.</p>



<p class="wp-block-paragraph">In our summer launch, we focused on the Operational Excellence pillar of the <a href="https://saf.apollographql.com/">Supergraph Architecture Framework</a>. The <a href="https://www.apollographql.com/docs/graphos/enterprise/supergraph-architecture-framework/operational-excellence">Operational Excellence pillar</a> focuses on empowering subgraph and stewardship teams. A well-architected graph isn&#8217;t only technically excellent—it&#8217;s also operationally excellent. Processes and tools should be in place to ensure that the supergraph is easy to use, understand, and maintain. These principles help ensure that the graph is a successful tool for building new experiences quickly.</p>



<h2 class="wp-block-heading"><a href="#key-announcements" aria-hidden="true" class="aal_anchor" id="key-announcements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Key Announcements</h2>



<h3 class="wp-block-heading"><a href="#query-batching-ga" aria-hidden="true" class="aal_anchor" id="query-batching-ga"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Query Batching: GA</h3>



<p class="wp-block-paragraph">GraphOS now supports end-to-end (client-to-subgraph) <a href="https://www.apollographql.com/docs/router/executing-operations/query-batching">query batching</a>, which is essential for ensuring consistency in component-based architecture where individual micro-frontends (MFE) make requests separately to fetch data relevant to them. By handling several queries in one request, this feature has the additional performance benefit of reduced network traffic and server load.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcMs0LzYIGqdyyR5_ULkftZoSb34V-0mHkjOc6wSHysBXe3PSoZ0uABtVJXFzeKO4_HN820CVzHBq1uom6ZOktomLhPU7wju0j8BcbT7ph8h9WRJT8UVZTFP8gk7LD_ukgKayrPxU0YhaHKcf8Ihqt7aQrY?key=PFk4g9hPuyvLkr-tso1A2A" alt=""/></figure>



<h3 class="wp-block-heading"><a href="#enhanced-telemetry-and-insights-ga" aria-hidden="true" class="aal_anchor" id="enhanced-telemetry-and-insights-ga"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Enhanced Telemetry and Insights: GA</h3>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="Improve GraphQL observability with Telemetry in GraphOS Router" width="580" height="326" src="https://www.youtube.com/embed/bdHWjn9lVvM?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<p class="wp-block-paragraph">The enhancements to <a href="https://www.apollographql.com/docs/router/configuration/telemetry/overview">custom telemetry</a> in GraphOS Router provide platform teams with deeper visibility into the performance of their supergraphs. New support for custom <a href="https://www.apollographql.com/docs/router/configuration/telemetry/instrumentation/events">events</a> gives you full customization over signalling when something of note happens in the Apollo Router&#8217;s request lifecycle. <img loading="lazy" decoding="async" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcH37HOKu_mbsFQs_VA9UWf-DCOBgYfvxCycR3HOeOM0i7u_zEIm8jgOySM8mVfUy7QhL48QdMNmlPu8t_E6AJRcV3ayaB2Ntl2AaaYUTkrv6ynGSyuFE3JmdVO2snCghn6_FqMja19MKeY53qk3L7YczXZ?key=PFk4g9hPuyvLkr-tso1A2A" width="1638" height="670"></p>



<p class="wp-block-paragraph">New custom <a href="https://www.apollographql.com/docs/router/configuration/telemetry/instrumentation/instruments">instruments</a> collects custom data and reports measurements to a metric backend.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcYaXIRpEMeymT44OAbW73Y54rXd_cTX44WnjrUkPUdHJ8ZOk2bjnRuZHdjePwPR6PRDKGYQQU-cicr0cUMDWonOh7MYzhcpI_csuy02t4bE2oWRR9Ts4Jh2Iz8W6t33Po4vkRwkpg9tvi6iClO8b--J9Y?key=PFk4g9hPuyvLkr-tso1A2A" alt=""/></figure>



<p class="wp-block-paragraph">Combined, enhanced telemetry allows client teams to investigate runtime errors and performance issues autonomously, reducing the debugging burden on core platform teams.&nbsp;</p>



<p class="wp-block-paragraph">Additionally, GraphOS Studio now offers more <a href="https://www.apollographql.com/blog/new-graphql-observability-and-insights-in-graphos-studio">comprehensive checks and insights</a>, giving teams greater control over supergraph operation validation to mitigate production errors.</p>



<h3 class="wp-block-heading"><a href="#entity-caching-with-per-subgraph-ttl-public-preview" aria-hidden="true" class="aal_anchor" id="entity-caching-with-per-subgraph-ttl-public-preview"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Entity Caching with Per-Subgraph TTL: Public Preview</h3>



<p class="wp-block-paragraph">Configuring response caching in a supergraph can be challenging due to the varied refresh rates of different fields. <a href="https://www.apollographql.com/docs/router/configuration/entity-caching">Subgraph entity caching</a> addresses this by allowing platform teams to cache entities centrally while setting granular TTLs for each subgraph. For example, a Product entity can have a long TTL for its Name field and a short TTL for its Inventory field, so long as they are resolved by different subgraphs.</p>



<h3 class="wp-block-heading"><a href="#demand-control-public-preview" aria-hidden="true" class="aal_anchor" id="demand-control-public-preview"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Demand Control: Public Preview</h3>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="Manage costly GraphQL operations with Demand Control in GraphOS Router" width="580" height="326" src="https://www.youtube.com/embed/ms8yCYFuVUo?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<p class="wp-block-paragraph">Platform teams often need to protect their graphs against highly complex queries that can cause service disruption if left unchecked. Our new native cost calculation and limiting features make it easier for teams to observe the average cost of operations in their graph and implement cost controls centrally to avoid misuse of their GraphQL endpoints.</p>



<h2 class="wp-block-heading"><a href="#transforming-api-platform-operations" aria-hidden="true" class="aal_anchor" id="transforming-api-platform-operations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Transforming API Platform Operations</h2>



<p class="wp-block-paragraph">These new features mark a significant step forward in how organizations can improve the operational excellence with which they manage federated GraphQL architectures. By providing advanced tools for caching, cost control, and query batching, Apollo GraphOS empowers platform teams to build, operate, and evolve supergraphs efficiently.</p>



<p class="wp-block-paragraph">To learn more about these features and more, including schema visualization, context directives, and checks and insights, watch the <a href="https://www.apollographql.com/events/apollo-graphos-summer-update-operational-excellence-for-graphql-federation?utm_campaign=2024-06-05_apollo-graphos-summer-update-operational-excellence-for-graphql-federation&amp;utm_medium=blog">Summer Launch webinar</a> hosted by VP Product, Rob Brazier.&nbsp;</p>


GraphOS Summer 2024 Launch Recap


<p class="wp-block-paragraph">We are experiencing a transformative period in application development, driven by the rise of AI across industries. This shift has made the API layer crucial for delivering innovative and personalized applications. At Apollo GraphQL, we aim to equip API platform teams with the tools they need to leverage GraphQL and GraphQL federation, helping them stay ahead in this AI-driven world.</p>



<p class="wp-block-paragraph">Our customers and partners frequently highlight the need to maximize their APIs&#8217; value in a way that is easy to use, scalable, and drives bottom-line growth. They want to increase productivity, improve the developer experience, and enhance software quality, all while delivering fast and tailored digital experiences. Organizations like Expedia, The New York Times, and Wayfair choose our GraphOS platform to achieve these goals.</p>



<p class="wp-block-paragraph">In light of these trends, <a href="http://www.apollographql.com/blog/apollo-graphql-announces-major-graphos-update-enhancing-observability-and-performance-for-enterprise-scale-graphql-federation">our latest GraphOS release</a> is a significant step forward. It improves observability and performance for enterprise-scale GraphQL federation and simplifies running a GraphQL platform with <a href="https://www.apollographql.com/docs/graphos/enterprise/supergraph-architecture-framework/operational-excellence/">operational excellence</a>. Gartner predicts that by 2026, over 30% of the increase in API demand will come from artificial intelligence and tools using large language models.<sup data-fn="3ded1729-df22-4efb-b57d-4a37b20c9290" class="fn"><a href="#3ded1729-df22-4efb-b57d-4a37b20c9290" id="3ded1729-df22-4efb-b57d-4a37b20c9290-link">1</a></sup> From building a chatbot, to AI-enabled personalization or transactions, or what’s to come in the future with autonomous agents, organizations require a resilient platform like GraphOS to connect their APIs and deliver a self-service graph that can power any number of applications.&nbsp;</p>



<p class="wp-block-paragraph">We are excited to also welcome to our team <a href="https://www.linkedin.com/in/jenniferhewlette/" data-type="link" data-id="https://www.linkedin.com/in/jenniferhewlette/">Jennifer Hewlette</a> as Chief Marketing Officer. Jennifer brings over twenty years of experience in building enterprise marketing strategies from pre-revenue to public high-tech companies such as DataRobot and Cisco. At DataRobot, known for its generative and predictive AI platform, she led marketing, go-to-market enablement, and education, focusing on delivering exceptional value to customers and partners. Joining us at a time of our rapid global growth and extensive cross-industry market adoption, her expertise in category expansion and deep understanding of AI’s business impact will be instrumental in advancing our mission to bring the benefits of our supergraph technology to help developers help the world.&nbsp;</p>



<p class="wp-block-paragraph">In Jennifer’s words:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">“I have spent the majority of my career forging the new – new markets, new technologies, and new ecosystems. Apollo GraphQL is already a leader beloved by developers with more than 25M downloads each month, and trusted by hundreds of enterprise customers like Netflix, Indeed, Intuit, and Wayfair. The technology can help any brand that strives to deliver personalized, performant digital customer and AI experiences. I look forward to working with our customers, prospects, and ecosystem partners to accelerate business value and create new experiences.”</p>
</blockquote>



<p class="wp-block-paragraph">We have welcomed seasoned veterans to our <a href="https://www.apollographql.com/leadership">leadership team</a> over the last year, with a rich pedigree in building world-class developer and enterprise companies from Atlassian, Twilio, Stripe, and Grammarly. These leaders have a remarkable track record of crafting customer-focused strategies that drive growth and innovation. Their expertise will be crucial as we help our users maximize the value of their API strategies and expand our market presence.</p>



<p class="wp-block-paragraph">We&#8217;re excited to share these developments with our community and deepen our engagement with our users, customers, and partners. I’m delighted to invite you to join us in New York City this fall for <a href="http://www.graphqlsummit.com">GraphQL Summit 2024</a>. At this event, we’ll unveil our latest innovations and explore the future of GraphQL. It’s a unique opportunity to connect, learn, and collaborate as we push the boundaries of what&#8217;s possible in application development.</p>



<p class="wp-block-paragraph">Join us in welcoming Jennifer Hewlette as our new Chief Marketing Officer as we embark on this exciting new chapter!</p>


<ol class="wp-block-footnotes"><li id="3ded1729-df22-4efb-b57d-4a37b20c9290"><a href="https://www.gartner.com/en/newsroom/press-releases/2024-03-20-gartner-predicts-more-than-30-percent-of-the-increase-in-demand-for-apis-will-come-from-ai-and-tools-using-llms-by-2026">https://www.gartner.com/en/newsroom/press-releases/2024-03-20-gartner-predicts-more-than-30-percent-of-the-increase-in-demand-for-apis-will-come-from-ai-and-tools-using-llms-by-2026</a> <a href="#3ded1729-df22-4efb-b57d-4a37b20c9290-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>

Embracing The Future And Welcoming Our New CMO


<p class="wp-block-paragraph"><em>Caching, Native Cost Calculation and Limiting, and Telemetry Capabilities Revolutionize API Management and Streamline Building Cross-Platform Digital Application Experiences</em></p>



<p class="wp-block-paragraph">Today at PlatformCon, <a href="https://apollographql.com">Apollo GraphQL</a>, the creator of GraphQL federation, announced new features in <a href="https://www.apollographql.com/graphos/">Apollo GraphOS</a> are now generally available to better leverage GraphQL’s developer productivity and performance benefits at any scale. This release provides API platform teams with visibility, usability, and performance benefits for GraphQL federation, enabling the engineering teams they serve to maximize the value of their APIs across their business.</p>



<p class="wp-block-paragraph">As the leading GraphQL federation platform, GraphOS provides an abstraction layer for API complexity, enabling product engineering teams to rapidly build and iterate features based on customer demand. <a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery">Gartner® predicts that </a>30% of enterprises using GraphQL will utilize GraphQL federation by 2027, up from less than 5% in 2024.<sup>1 </sup>Apollo believes this trend suggests the number of enterprises using GraphQL federation as their API access layer will increase by 12x. GraphOS provides everything enterprise teams need to deliver GraphQL federation at any scale.&nbsp;</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">“GraphQL federation removes the friction between the frontend and backend that we see in distributed architectures,” said Matt DeBergalis, Chief Technology Officer and co-founder at Apollo GraphQL. “This latest GraphOS release enables API platform teams to operationalize GraphQL federation’s benefits faster, so they can focus less on building custom tooling and more on their customers’ needs.”</p>
</blockquote>



<p class="wp-block-paragraph">This latest GraphOS release includes significant improvements around observability, usability, and performance, enabling API platform teams to operate GraphQL federation more easily than ever before.&nbsp; “At enterprise-scale, every millisecond of latency in your consumer’s digital experiences impacts the bottom line,” said Rob Brazier, VP of Product at Apollo GraphQL. “With this release of Apollo GraphOS, we’ve made it even easier for API platform teams to observe and optimize the performance of federated graphs.”&nbsp;</p>



<p class="wp-block-paragraph"><strong>Apollo’s latest release provides operational excellence for GraphQL federation</strong></p>



<p class="wp-block-paragraph">GraphQL federation is becoming a de facto architecture for platform engineering teams to simplify API governance across distributed architectures. Client teams can fetch all the data they need from a single endpoint, and this paradigm enables API platform teams to enforce better governance, provide better visibility into service usage, as well as use standardized tools for performance. GraphOS provides a complete solution for delivering GraphQL federation at any scale:</p>



<div class="wp-block-group is-vertical is-layout-flex wp-container-core-group-is-layout-4fc3f8e1 wp-block-group-is-layout-flex">
<ul class="wp-block-list">
<li><strong>Better application performance</strong> – Apollo introduces an improved and simplified form of API caching built for GraphQL federation. GraphOS’s caching layer spans any number of APIs and now, in public preview, supports entity caching. Entities are object types that are composed from multiple GraphQL APIs and are the business objects or “nouns of every business.” API platform teams can store entities such as their inventory, products, or user records in a Redis data store. API platform teams can set how long these entities are cached in the data store, enabling API platform teams to significantly improve performance across an entire fleet of applications. &#8220;We&#8217;ve rolled out entity caching in production and are observing a decrease in median response time,&#8221; said Nimit Barochia, Senior Principal Software Engineer at Dow Jones. &#8220;The major improvement is how much less traffic we send to our subgraphs. Like a 8-10x decrease in some cases.&#8221;</li>
</ul>



<ul class="wp-block-list">
<li><strong>Cost control </strong>– API platform teams need a means to ensure that costly GraphQL operations don’t slow performance or create a denial of service. Platform teams need a means to limit cost of GraphQL operations processed by the GraphOS Router. Apollo is adding in public preview native cost calculation and limiting to GraphOS to make it easy for platform teams to centrally implement this, rather than relying on underlying services.</li>



<li><strong>Stronger support and improved performance</strong> – Micro-frontends provide a frontend architecture that refines performance and composability across mobile and web applications. To improve performance, micro-frontend UIs typically batch multiple client operations, issued close together, into a single API request. GraphOS is adding better support for these use cases, enabling GraphOS to handle batched requests from clients to a supergraph. It also further augments performance by ensuring that batches are kept intact when processed and passed on to the required subgraphs.</li>



<li><strong>Enhanced telemetry</strong> – API platform teams need both standardized and custom metrics to better optimize federated graphs for performance and business objectives. GraphOS now provides unparalleled visibility to debug and optimize federated graphs, enabling these teams to import these metrics into their Application Performance Monitoring tool of choice for better decision-making.&nbsp;</li>



<li><strong>Significant improvements to the GraphOS management plane</strong> – In Apollo Studio, schema checks and insights enable API teams to build, test, and ship changes to their federated graph with confidence. This release features significant UX improvements and better insights, enabling API teams to ship changes faster without introducing breaking changes to downstream clients.</li>
</ul>
</div>



<p class="wp-block-paragraph"><strong>Apollo customers to focus on innovation instead of API aggregation or orchestration</strong></p>



<p class="wp-block-paragraph">AI is driving rapid innovation across industries, making the API layer critical for delivering competitive, personalized applications. Apollo aims to help API platform teams leverage GraphQL federation’s benefits across engineering organizations, empowering their teams to lead their organizations into the AI era.&nbsp;</p>



<p class="wp-block-paragraph"><strong>Learn more with Apollo&nbsp;</strong></p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/events/apollo-graphos-summer-update-operational-excellence-for-graphql-federation?utm_campaign=2024-06-12_Webinar_Apollo-GraphOS-Summer-Update-Operational-Excellence&amp;utm_medium=email&amp;utm_source=sales">Attend a webinar</a> on June 12 to learn more about what’s new in GraphOS and see new features demoed.&nbsp;</li>



<li>Join Apollo <a href="https://lu.ma/platformcon-watch-party-apollo">live on June 13 </a>in NYC as it celebrates the largest conference for platform engineering, PlatformCon, and hear from customers COX Automotive, The New York Times, and Wayfair on how they’re finding success with Apollo’s federated GraphQL technology.</li>



<li>And the largest gathering of GraphQL enthusiasts and API platform teams is coming. Join Apollo at <a href="https://summit.graphql.com/">GraphQL Summit</a>, October 8-10, where engineering teams can learn from industry leaders spearheading successful GraphQL deployments at scale.</li>
</ul>



<p class="wp-block-paragraph"><sup>1</sup>Gartner, When to Use GraphQL to Accelerate API Delivery, By Shameen Pillai, et al, March 7, 2024. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved.</p>



<h1 class="wp-block-heading"><a href="#about-apollo-graphql" aria-hidden="true" class="aal_anchor" id="about-apollo-graphql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>About Apollo GraphQL</h1>



<p class="wp-block-paragraph"><a href="https://apollographql.com">Apollo GraphQL </a>helps developers help the world by providing a better API platform across teams. Apollo’s open-source software is downloaded 25M times per month and its commercial GraphQL technologies power the most innovative brands today. Teams at Netflix, Snap, and the New York Times ship personalized, omnichannel experiences faster with a supergraph – a self-service GraphQL platform that spans any number of backend services. Serving over 5T requests in 2023, the Apollo GraphOS<sup>TM</sup> platform simplifies API development with workflows and infrastructure to build, test, and ship supergraphs at any scale. Based in San Francisco, Apollo is backed by Insight Partners, Andreessen Horowitz, Matrix Partners, and Trinity Ventures. Learn more at: <a href="https://www.apollographql.com">https://www.apollographql.com</a>.</p>


Apollo GraphQL Announces Major GraphOS Update, Enhancing Observability and Performance for Enterprise-Scale GraphQL Federation


<p class="wp-block-paragraph">Apollo Client 3.10 has just been released, and we want to provide you with an overview of what&#8217;s new:</p>



<ul class="wp-block-list">
<li>Introducing new experimental schema-based testing utilities</li>



<li>New API: <code class="" data-line="">client.watchFragment</code></li>



<li><code class="" data-line="">createQueryPreloader</code> reaches &#8220;stable&#8221; status</li>
</ul>



<p class="wp-block-paragraph">Let&#8217;s take a look:</p>



<h2 class="wp-block-heading"><a href="#introducing-new-experimental-schema-based-testing-utilities" aria-hidden="true" class="aal_anchor" id="introducing-new-experimental-schema-based-testing-utilities"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Introducing new experimental schema-based testing utilities</h2>



<p class="wp-block-paragraph">In Apollo Client 3.10, we are introducing new schema-based testing utilities under the <code class="" data-line="">@apollo/client/testing/experimental</code> import.</p>



<p class="wp-block-paragraph">This adds two new tools:</p>



<p class="wp-block-paragraph"><strong><code class="" data-line="">createTestSchema</code></strong> allows you to enhance a <code class="" data-line="">GraphQLSchema</code> class with mock scalars and mock resolvers. </p>



<p class="wp-block-paragraph">You can modify the resolvers inside your tests to simulate changing results.</p>



<p class="wp-block-paragraph">This approach is an alternative to the current testing approach with <code class="" data-line="">MockProvider</code>, allowing you to write tests similar to how you would implement your backend &#8211; applying skills you already have and can use in other situations.</p>



<p class="wp-block-paragraph">You can then use this schema with <a href="https://mswjs.io/" data-type="link" data-id="https://mswjs.io/">Mock Service Worker</a> to simulate a GraphQL server, or you can use our new <strong><code class="" data-line="">createSchemaFetch</code></strong> function to create a <code class="" data-line="">fetch</code> function to be used inside of your tests.</p>



<p class="wp-block-paragraph">Both of these approaches allow you to use your real link chain instead of a mocked one.</p>



<p class="wp-block-paragraph">You can read more on this testing approach in <a href="https://github.com/apollographql/apollo-client/issues/11705" data-type="link" data-id="https://github.com/apollographql/apollo-client/issues/11705">the schema-driven testing RFC</a> and <a href="https://www.apollographql.com/docs/react/development-testing/schema-driven-testing" data-type="link" data-id="https://www.apollographql.com/docs/react/development-testing/schema-driven-testing">the documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#new-api-client-watchfragment" aria-hidden="true" class="aal_anchor" id="new-api-client-watchfragment"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>New API: <code class="" data-line="">client.watchFragment</code></h2>



<p class="wp-block-paragraph">We also add a new function to the <code class="" data-line="">ApolloClient</code> class: <code class="" data-line="">watchFragment</code>.</p>



<p class="wp-block-paragraph">This function enables the functionality of the <code class="" data-line="">useFragment</code> hook to be used in Vanilla JavaScript or other frameworks. </p>



<p class="wp-block-paragraph">A PR to add a <code class="" data-line="">watchFragment</code> functionality to <code class="" data-line="">apollo-angular</code> has already been opened, and more will follow soon!</p>



<h2 class="wp-block-heading"><a href="#createquerypreloader-reaches-stable-status" aria-hidden="true" class="aal_anchor" id="createquerypreloader-reaches-stable-status"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code class="" data-line="">createQueryPreloader</code> reaches &#8220;stable&#8221; status</h2>



<p class="wp-block-paragraph">In Apollo Client 3.9, we introduced the <code class="" data-line="">createQueryPreloader</code> API as &#8220;alpha&#8221;, and since we&#8217;ve heard your positive feedback, with 3.10, we&#8217;re releasing it as &#8220;stable.&#8221;</p>



<p class="wp-block-paragraph"><code class="" data-line="">createQueryPreloader</code> is used to start a query outside of React (e.g. in a Router action) and then later attach to the generated <code class="" data-line="">queryRef</code> with the <code class="" data-line="">useReadQuery</code> hook.</p>



<p class="wp-block-paragraph">You can read more about it in the <a href="https://www.apollographql.com/docs/react/data/suspense/#initiating-queries-outside-react" data-type="link" data-id="https://www.apollographql.com/docs/react/data/suspense/#initiating-queries-outside-react">documentation</a>.</p>


What’s new in Apollo Client 3.10


<p class="wp-block-paragraph">In the realm of software development, evolution is not just desirable; it&#8217;s inevitable. Technologies advance, methodologies shift, and systems need to adapt to meet changing demands. In this ever-evolving landscape, Apollo Federation 2.7 introduces a groundbreaking feature: progressive <code class="" data-line="">@override</code> ✨</p>



<p class="wp-block-paragraph">Rolling out any change to a production subgraph, including field migration, risks degrading the performance of your graph. Progressive <code class="" data-line="">@override</code> enables you to migrate any part of your graph to a new service and customize how traffic is gradually rolled over to the new service.</p>



<h2 class="wp-block-heading" id="Understanding-@override:-A-Primer"><a href="#understanding-override-a-primer" aria-hidden="true" class="aal_anchor" id="understanding-override-a-primer"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Understanding <code class="" data-line="">@override</code>: A Primer</h2>



<p class="wp-block-paragraph">Before delving into the nuances of progressive <code class="" data-line="">@override</code>, let&#8217;s take a moment to revisit the concept of <code class="" data-line="">@override</code>. <code class="" data-line="">@override</code> provide a mechanism for migrating fields from one subgraph to another. By applying an <code class="" data-line="">@override</code> directive to a specific field, traffic for that field is rerouted to the designated service, facilitating the breakdown of monolithic architectures or the migration of fields between subgraphs.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line=""># Inventory subgraph
type Product @key(fields: &quot;id&quot;) {
  id: ID!
  inStock: Boolean! @override(from: &quot;Products&quot;)
}</code></pre>



<p class="wp-block-paragraph">In the example above, we’re migrating the <code class="" data-line="">Product.inStock</code> field from the <code class="" data-line="">Products</code> subgraph to the <code class="" data-line="">Inventory</code> subgraph. Rerouting all traffic from one subgraph to another all at once could overload the overriding subgraph.</p>



<h2 class="wp-block-heading" id="Override-only-a-portion-of-traffic"><a href="#override-only-a-portion-of-traffic" aria-hidden="true" class="aal_anchor" id="override-only-a-portion-of-traffic"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Override only a portion of traffic</h2>



<p class="wp-block-paragraph">Anything that ships to production, ideally, has a gradual rollout with a certain percentage of traffic. This gives us the ability to roll back any bad deployments with a smaller impact in case everything is just broken (we’ve all been there 😅).</p>



<p class="wp-block-paragraph">Progressive <code class="" data-line="">@override</code> makes this simple for our Apollo Router to handle. Simply label your <code class="" data-line="">@override</code> directive with the supported <code class="" data-line="">percent(x)</code> syntax.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line=""># Inventory subgraph
type Product @key(fields: &quot;id&quot;) {
  id: ID!
  inStock: Boolean! @override(from: &quot;Products&quot;, label: &quot;percent(1)&quot;)
}</code></pre>



<p class="wp-block-paragraph">Now our router will begin routing approximately 1% of all traffic to our new Inventory subgraph for the <code class="" data-line="">Product.inStock</code> field. When we want to ramp that up, we can simply update our schema and once we reach 100%, we can remove the <code class="" data-line="">inStock</code> field from the original <code class="" data-line="">Product</code> subgraph 🎉</p>



<h2 class="wp-block-heading" id="Customize-progressive-@override-with-a-feature-flag-service"><a href="#customize-progressive-override-with-a-feature-flag-service" aria-hidden="true" class="aal_anchor" id="customize-progressive-override-with-a-feature-flag-service"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Customize progressive <code class="" data-line="">@override</code> with a feature flag service</h2>



<p class="wp-block-paragraph">It’s great that we can define a given percentage of traffic, but maybe we want to enable some items to bypass this percentage. You may want your beta application to always route to the new faster service 🏃</p>



<p class="wp-block-paragraph">The router provides an interface for coprocessors and rhai scripts to resolve arbitrary labels. This means you can provide anything as the label and have the router interact with your external coprocessor to resolve the label. For an example implementation of a coprocessor that resolves labels using LaunchDarkly, see <a href="https://github.com/apollographql/router/tree/main/examples/coprocessor-override-launchdarkly/README.md">the example</a> in the router repo.</p>



<h2 class="wp-block-heading" id="Championing-the-Monolith-Breakup"><a href="#championing-the-monolith-breakup" aria-hidden="true" class="aal_anchor" id="championing-the-monolith-breakup"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Championing the Monolith Breakup</h2>



<p class="wp-block-paragraph">A common use case we see with progressive <code class="" data-line="">@override</code> is breaking down a GraphQL monolith. Everyone starts their GraphQL adoption journey with a monolith and although that can take you far, there are challenges as the usage of the graph increases. Eventually there is a desire to break a service off of the monolith, whether it’s to address a performance issue or maybe to utilize a new 3rd party service.</p>



<p class="wp-block-paragraph">The easiest way to evaluate breaking up the monolith is to start with a known view that has some meaningful value in the overall application. You’ll want to keep the shape of the operation the same for the client so that you can just use a new URL for that single view&#8217;s GraphQL query. Let’s take this screen as an example:</p>


<div class="wp-block-image">
<figure class="aligncenter size-full"><img loading="lazy" decoding="async" width="444" height="673" src="https://wp.apollographql.com/wp-content/uploads/2024/04/Screenshot-2024-04-08-at-10.08.19-AM-1.png" alt="" class="wp-image-23637" srcset="https://wp.apollographql.com/wp-content/uploads/2024/04/Screenshot-2024-04-08-at-10.08.19-AM-1.png 444w, https://wp.apollographql.com/wp-content/uploads/2024/04/Screenshot-2024-04-08-at-10.08.19-AM-1-198x300.png 198w" sizes="auto, (max-width: 444px) 100vw, 444px" /></figure>
</div>


<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">query ProductDetails {
  product(id: &quot;space-boots&quot;) {
      sku
      name
      details
      rating
      price # The field we want to migrate
    }
}</code></pre>



<p class="wp-block-paragraph">We want to migrate the <code class="" data-line="">Product.price</code> field from our existing monolith to a new microservice. Ideally, this would require no changes to our client or monolith codebase. This is possible with progressive override and the architecture federation provides. Most commonly, teams will begin sending the traffic of the single client view to the hosted Apollo Router instance.</p>



<p class="wp-block-paragraph">The Apollo Router can handle bridging traffic between your monolith and the new GraphQL service. Some teams will even opt to switch all of a single clients traffic to the router as a step of their progressive rollout (ie. switching the URL in <code class="" data-line="">@apollo/client</code> to use the newly hosted router). Even though the router acts as a proxy for the rest of the clients traffic, it paves a golden path for adding new services that further break down the monolith.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="652" height="760" src="https://wp.apollographql.com/wp-content/uploads/2024/04/Group-1-1-1.png" alt="" class="wp-image-23626" srcset="https://wp.apollographql.com/wp-content/uploads/2024/04/Group-1-1-1.png 652w, https://wp.apollographql.com/wp-content/uploads/2024/04/Group-1-1-1-257x300.png 257w" sizes="auto, (max-width: 652px) 100vw, 652px" /></figure>



<p class="wp-block-paragraph">For our example, we need to create a new subgraph that resolves the <code class="" data-line="">Product.price</code> field. This will require us defining <code class="" data-line="">Product</code> as an <a href="https://www.apollographql.com/docs/federation/entities">entity</a> using the <code class="" data-line="">@key</code> directive and adding the <code class="" data-line="">@override</code> directive to <code class="" data-line="">Product.price</code>. This requires no changes to our existing monolith or it’s schema:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line=""># Existing Monolith
type Product { 
	sku: ID!
	name: String
	details: String
	rating: Float
	price: Float
}
type Query {
	products: [Product]
	product(id: ID!): Product
}</code></pre>



<p class="wp-block-paragraph"><em>There are a lot of </em><a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs"><em>supported servers</em></a><em> you can use to build your GraphQL subgraph in your language of choice like Java, C#, Python and more.</em></p>



<p class="wp-block-paragraph">Once our router re-configures with the composed schema, it will have the metadata of the <code class="" data-line="">label</code> we added (<code class="" data-line="">percent(25)</code>). The Apollo Router will then use this information to change the generated query plan based on the percentage label 🎉</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="980" height="650" src="https://wp.apollographql.com/wp-content/uploads/2024/04/Apr-08-2024-14-36-00-1.gif" alt="" class="wp-image-23628"/></figure>



<p class="wp-block-paragraph">Now the <code class="" data-line="">Product.price</code> field of our graph can resolve from a new microservice in our infrastructure and we can progressively rollout this change with simple updates to the schema. Once we’ve moved to 100%, we can eventually <em><strong>delete</strong></em> that code from our monolith 🔥</p>



<h2 class="wp-block-heading" id="Wrapping-up"><a href="#wrapping-up" aria-hidden="true" class="aal_anchor" id="wrapping-up"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Wrapping up</h2>



<p class="wp-block-paragraph">Progressive override brings a powerful new tool for better flexibility and control in service migration. Embracing incremental adoption in our migrations helps developers navigate the complexities of the organization&#8217;s constantly evolving stack. This also enables platform engineering efforts to tackle self-service migrations for APIs to production 🤯. What would you migrate if you could?</p>



<p class="wp-block-paragraph">Progressive <code class="" data-line="">@override</code> is an <a href="https://www.apollographql.com/docs/router/enterprise-features">Enterprise feature</a> of the Apollo Router and requires an organization with a <a href="https://www.apollographql.com/pricing/?referrer=docs-content">GraphOS Enterprise plan</a>. If your organization doesn&#8217;t have an Enterprise plan, you can test it out by signing up for a free <a href="https://www.apollographql.com/docs/graphos/org/plans/#enterprise-trials">Enterprise trial</a>.</p>



<p class="wp-block-paragraph"></p>


Safer migrations of fields using progressive rollouts


<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="573" src="https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers-1024x573.png" alt="" class="wp-image-23618" srcset="https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers-1024x573.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers-300x168.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers-768x430.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers.png 1186w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">API Days NY is a must-attend for those looking to network with API leaders and learn how top enterprises are leveraging federated GraphQL in their API platforms. As you can see from the agenda highlights below, it will be an exciting two day event.&nbsp;</p>



<ul class="wp-block-list">
<li>Our founder and CTO, Matt DeBergalis, will share his keynote &#8220;The Year Ahead for GraphQL Federation: Uniting APIs for the AI Era”</li>



<li>API leaders from Netflix, Wayfair and Apollo will present sessions on optimizing performance, creating effective api schemas and building an internal community for effective API governance</li>



<li>Apollo is offering a free workshop to guide you through building your first GraphQL query and beyond</li>



<li><a href="https://bit.ly/43IhuX4">Register to join us for a meetup &amp; happy hour</a> to meet with peer API leaders and GraphQL experts</li>
</ul>



<p class="wp-block-paragraph">Swing by the Apollo booth to connect, and read on for more details.</p>



<h3 class="wp-block-heading"><a href="#keynote-the-year-ahead-for-graphql-federation-combining-apis-for-the-ai-era" aria-hidden="true" class="aal_anchor" id="keynote-the-year-ahead-for-graphql-federation-combining-apis-for-the-ai-era"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Keynote: The Year Ahead for GraphQL Federation: Combining APIs for the AI Era</strong></h3>



<p class="wp-block-paragraph"><em>Matt DeBergalis, Founder and CTO, Apollo GraphQL</em></p>



<p class="wp-block-paragraph">Forget what you’ve heard about GraphQL – it’s not a REST alternative, graph database, or just for front-end developers. GraphQL is about combining the APIs you already have.</p>



<p class="wp-block-paragraph">In this talk, you’ll learn how a federated GraphQL architecture brings a platform approach to API composition, where it fits into the API stack, and what is coming next to help teams build tomorrow’s AI products and experiences on today’s APIs.</p>



<h3 class="wp-block-heading"><a href="#session-the-graphql-overhead-myth-or-reality" aria-hidden="true" class="aal_anchor" id="session-the-graphql-overhead-myth-or-reality"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Session: The GraphQL Overhead: Myth or Reality?</strong></h3>



<p class="wp-block-paragraph"><em>Marc-André Grioux, Senior Software Engineer &amp; Author, Netflix</em></p>



<p class="wp-block-paragraph">GraphQL is a powerful tool to enable declarative data fetching on the client and dynamic data representation on the server. This power must have an overhead. In this talk, investigate what this overhead is made of, how impactful it can be to scaling an API platform and services, and how to mitigate it as much as possible while retaining the benefits of GraphQL.</p>



<h3 class="wp-block-heading"><a href="#session-the-secrets-to-graph-success-from-inception-to-general-availability" aria-hidden="true" class="aal_anchor" id="session-the-secrets-to-graph-success-from-inception-to-general-availability"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Session: The Secrets to Graph Success, from Inception to General Availability</strong></h3>



<p class="wp-block-paragraph"><em>Leah Hurwich-Adler, Senior Product Leader</em></p>



<p class="wp-block-paragraph">Building an API platform for a Fortune 100 retailer, capable of handling over 600 million requests per day, requires a highly distributed ecosystem and Federated GraphQL. Drawing from firsthand experience, Leah will share insights on building an internal API community, setting up governance models, and igniting leaders&#8217; enthusiasm for your platform vision. Join this talk to uncover the keys to launching a successful GraphQL platform, through lessons that merge technology with strategic and leadership insights.</p>



<h3 class="wp-block-heading"><a href="#session-benefits-of-idiomatic-code-first-graphql-development" aria-hidden="true" class="aal_anchor" id="session-benefits-of-idiomatic-code-first-graphql-development"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Session: Benefits of Idiomatic Code First GraphQL Development</strong></h3>



<p class="wp-block-paragraph"><em>Derek Kuc, Principal Engineer, Apollo GraphQL</em></p>



<p class="wp-block-paragraph">When building a GraphQL server, two main approaches exist: starting with an SDL and matching resolver logic, or generating the schema directly from code. In this talk, explore the benefits of idiomatic code-first GraphQL development, focusing on GraphQL Kotlin examples. Discover how this approach enhances developer experience and API consistency.</p>



<h3 class="wp-block-heading"><a href="#workshop-build-an-api-composition-layer-with-apollo-graphql" aria-hidden="true" class="aal_anchor" id="workshop-build-an-api-composition-layer-with-apollo-graphql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Workshop: Build an API Composition Layer with Apollo GraphQL</strong></h3>



<p class="wp-block-paragraph"><em>Michael Berger, Solutions Engineer, Apollo GraphQL</em></p>



<p class="wp-block-paragraph">Use GraphQL to accelerate developer velocity by creating a composition layer for your microservices. Orchestrate data by creating a query that spans your REST APIs and delivers exactly the data your application requires. Learn how to build your first GraphQL query and why GraphQL is valuable to your microservice architecture.</p>



<h3 class="wp-block-heading"><a href="#nyc-meetup-and-happy-hour" aria-hidden="true" class="aal_anchor" id="nyc-meetup-and-happy-hour"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>NYC Meetup and Happy Hour</strong></h3>



<p class="wp-block-paragraph"><a href="https://bit.ly/43IhuX4">Register to join the Apollo team, Graph Champions, and apidays attendees</a> on April 30 at 6 PM following the conference for bites and beverages at nearby restaurant The Reading Room (16 E 46th St, New York, NY 10017 &#8211; located in the Gotham Hotel)</p>



<h3 class="wp-block-heading"><a href="#still-deciding-get-your-free-pass-now-before-they-run-out" aria-hidden="true" class="aal_anchor" id="still-deciding-get-your-free-pass-now-before-they-run-out"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Still deciding? Get your free pass now before they run out!&nbsp;&nbsp;</strong></h3>



<p class="wp-block-paragraph">The full conference ticket includes access to the Keynotes, Track Sessions, Workshops and Networking Breakfasts and Lunches on April 30 &amp; May 1. Email <a href="mailto:champions@apollographql.com">champions@apollographql.com</a> to learn more and request a pass.</p>


Join Us at API Days in New York City, April 30 & May 1, 2024


<h2 class="wp-block-heading"><a href="#industry-leaders-to-showcase-tangible-business-impact-of-graphql-federation" aria-hidden="true" class="aal_anchor" id="industry-leaders-to-showcase-tangible-business-impact-of-graphql-federation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><em>Industry Leaders to Showcase Tangible Business Impact of GraphQL Federation</em></h2>



<p class="wp-block-paragraph">In the wake of a recent report by Gartner<sup>®</sup>, <a href="https://apollographql.com">Apollo GraphQL</a>, the creator of GraphQL federation, is announcing the 7th annual GraphQL Summit, scheduled for October 8–10, 2024, in New York City. This premier three-day event gathers the largest assembly of GraphQL enthusiasts and API platform teams. Engineering teams can learn from industry leaders spearheading successful GraphQL deployments at scale and hear from Apollo GraphQL on its product roadmap and vision for the future of GraphQL and GraphQL federation.</p>



<p class="wp-block-paragraph">According to the Gartner report, GraphQL&#8217;s adoption is on the rise, since “By 2027, more than 60% of enterprises will use GraphQL in production, up from less than 30% in 2024.” The report also predicts that “By 2027, 30% of enterprises using GraphQL will utilize GraphQL federation, up from less than 5% in 2024.”1<sup data-fn="5626a7a6-afc4-465e-84b4-2219decdae0e" class="fn"><a href="#5626a7a6-afc4-465e-84b4-2219decdae0e" id="5626a7a6-afc4-465e-84b4-2219decdae0e-link">1</a></sup> As GraphQL federation marks its<a href="https://www.apollographql.com/blog/celebrating-five-years-of-apollo-federation"> 5th anniversary,</a> Apollo GraphQL remains at the forefront of this transformative technology.</p>



<p class="wp-block-paragraph">Previous GraphQL Summits have featured internet giants like Netflix, Intuit, and Wayfair, sharing invaluable insights into deploying GraphQL at scale to support distributed architectures. Rather than a sprawl of backends-for-frontends or experience APIs, these teams implemented GraphQL federation, an architecture that combines APIs and enables any number of client teams to query them from a single endpoint. Engineering leaders and API platform teams can learn how to use this architecture to drive developer velocity, enhance the customer experience across any number of applications, or handle the technical side of mergers and acquisitions, where IT is saddled with many disparate siloed systems that were never designed to talk to each other.</p>



<p class="wp-block-paragraph">This year’s GraphQL Summit aims to support this burgeoning adoption with sessions led by industry luminaries across various sectors, including retail, automotive, and banking.&nbsp; Featured speakers include Stephanie Saunders, Engineering Manager at Coinbase; Mike Cohen, Technical Fellow at Indeed; and Marc-Andre Giroux, Senior Software Developer at Netflix, as well as the co-founders of Apollo GraphQL, Geoff Schmidt and Matt DeBergalis, who will share their insights and expertise on the future of GraphQL and GraphQL federation. Attendees can expect tracks and workshops covering best practices on security, governance, and API platform engineering; real-world use cases and the latest advancements in GraphQL technology; along with a new focus on leveraging GraphQL federation to support artificial intelligence.&nbsp;</p>



<figure class="wp-block-pullquote"><blockquote><p>Geoff Schmidt, CEO and co-founder of Apollo GraphQL, remarks: “As enterprise technology evolves, the rise of GraphQL represents a pivotal shift towards more efficient, scalable, and interconnected systems. The latest insights from Gartner reaffirm what we at Apollo GraphQL have long believed: GraphQL federation is not just a trend, but a fundamental technology shaping the future of digital experiences. Apollo GraphQL is committed to fostering an environment where developers and enterprises can learn, grow, and succeed with GraphQL. The upcoming GraphQL Summit is a reflection of this commitment, featuring talks from industry leaders like Coinbase and Netflix, and promises to be an invaluable opportunity for API platform engineers and leaders to discover how GraphQL federation revolutionizes API architectures for seamless, innovative systems that are driving the future of digital experiences.”</p></blockquote></figure>



<p class="wp-block-paragraph">All GraphQL enthusiasts are invited to join the conversation by submitting to speak at the Summit. Whether an industry veteran or a newcomer, this is a chance to share insights, experiences, and innovations with the GraphQL community.</p>



<p class="wp-block-paragraph">For more information about the GraphQL Summit or to submit your proposal to speak, please visit our website: <a href="http://www.graphqlsummit.com">www.graphqlsummit.com</a>.</p>



<h2 class="wp-block-heading"><a href="#resources" aria-hidden="true" class="aal_anchor" id="resources"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Resources</h2>



<ul class="wp-block-list">
<li>Read the<a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery"> latest Gartner report</a>, When to Use GraphQL to Accelerate API Delivery</li>



<li>Learn more about <a href="https://www.apollographql.com/blog/celebrating-five-years-of-apollo-federation">Apollo Federation</a>, Apollo’s implementation of GraphQL Federation&nbsp;</li>



<li>Stay up to date on the <a href="http://www.graphqlsummit.com">GraphQL Summit </a>agenda and learn more about it <a href="https://www.apollographql.com/blog/announcing-graphql-summit-2024-in-new-york-city">here</a></li>



<li><a href="https://www.apollographql.com/graphos/">Build </a>a GraphQL API platform today</li>



<li><a href="https://www.apollographql.com/tutorials/certifications/apollo-graph-professional/learning-path/">Become certified </a>as an Apollo GraphQL developer</li>



<li><a href="https://discord.com/invite/yFZJH2QYrK">Join</a> the Apollo GraphQL Community on Discord</li>
</ul>



<h2 class="wp-block-heading"><a href="#about-apollo-graphql" aria-hidden="true" class="aal_anchor" id="about-apollo-graphql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>About Apollo GraphQL</h2>



<p class="wp-block-paragraph"><a href="https://apollographql.com">Apollo GraphQL </a>helps developers help the world by providing a better API platform across teams. Apollo’s open-source software is downloaded 25M times per month and its commercial GraphQL technologies power the most innovative brands today. Teams at Netflix, Snap, and the New York Times ship personalized, omnichannel experiences faster with a supergraph – a self-service GraphQL platform that spans any number of backend services. Serving over 5T requests in 2023, the Apollo GraphOS<sup>TM</sup> platform simplifies API development with workflows and infrastructure to build, test, and ship supergraphs at any scale. Based in San Francisco, Apollo is backed by Insight Partners, Andreessen Horowitz, Matrix Partners, and Trinity Ventures. Learn more at: <a href="https://www.apollographql.com">https://www.apollographql.com</a>.</p>


<ol class="wp-block-footnotes"><li id="5626a7a6-afc4-465e-84b4-2219decdae0e">Gartner, When to Use GraphQL to Accelerate API Delivery, By Shameen Pillai, et al, March 7, 2024. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved. <a href="#5626a7a6-afc4-465e-84b4-2219decdae0e-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>

Image portays GraphQL Summit by Apollo logo and includes text that reads the conference for API platform engineering builders and leaders. October 8-10, 2024. Convene 225 Liberty New York City.

Apollo GraphQL Announces the Next GraphQL Summit Amid Rapid GraphQL Enterprise Adoption 


<p class="wp-block-paragraph">GraphQL federation has emerged as the industry consensus for composing APIs at scale. Organizations such as Netflix, Expedia, and Wayfair quickly adopted this architecture to abstract API complexity and further adoption is on the rise.<a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery"> Gartner predicts</a> that “By 2027, 30% of enterprises using GraphQL will use GraphQL federation, up from less than 5% in 2024.”<sup data-fn="29ebcf61-2dba-471e-a128-d8d3f07a6d34" class="fn"><a href="#29ebcf61-2dba-471e-a128-d8d3f07a6d34" id="29ebcf61-2dba-471e-a128-d8d3f07a6d34-link">1</a></sup> This pattern didn’t emerge by accident; it was created and refined here at Apollo GraphQL. The first lines of <a href="https://www.apollographql.com/docs/federation/">Federation</a> code were published five years ago, so it’s the right moment to take a step back and examine the past, present, and future of this transformative technology.</p>



<h1 class="wp-block-heading"><a href="#graphql-federation-enables-a-platform-strategy" aria-hidden="true" class="aal_anchor" id="graphql-federation-enables-a-platform-strategy"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL federation enables a platform strategy</h1>



<p class="wp-block-paragraph">Data storage and retrieval needs exploded decades ago, so SQL emerged. Container usage exploded years ago, so Kubernetes emerged. API development is exploding, so GraphQL federation has arrived. It’s declarative, composable, and self-service. Federation isn’t just an idea anymore: it’s a solution that has been proven, at scale, time and again. And according to Gartner, “Federation enables centralized governance, team autonomy (teams can own their own subgraphs), composability, and adaptability to evolving requirements at different speeds.”<sup>1</sup>&nbsp;&nbsp;</p>



<p class="wp-block-paragraph">We at Apollo GraphQL believe GraphQL federation is now synonymous with GraphQL at enterprise scale. Companies such as Zillow, Square, Priceline.com, and Booking.com rely on Apollo Federation to power their API platforms. Read more about <a href="https://www.apollographql.com/blog/mlbs-api-strategy-hitting-a-home-run-transformation-with-graphql-midfield">how Federation powers Major League Baseball’s API strategy</a> and <a href="https://www.apollographql.com/blog/how-intuit-handled-their-busiest-time-of-year-with-apollo-router">how Intuit handled their busiest time of year with Apollo Router</a>.</p>



<p class="wp-block-paragraph">These brands chose GraphQL to serve their product and platform goals, allowing them to ship better user experiences faster and without the overhead that legacy API architectures incentivize. Federation is:</p>



<ul class="wp-block-list">
<li><strong>Unified.</strong> Federation preserves the GraphQL experience client teams love by making this data accessible via a single endpoint.</li>



<li><strong>Modular.</strong> Federation makes it easier to break up a monolithic architecture. This enables teams to contribute to the graph independently at scale.</li>



<li><strong>Iterative.</strong> Teams can evolve their graph with confidence, surfacing backwards compatibility concerns early in the process thanks to robust composition rules.</li>
</ul>



<p class="wp-block-paragraph">Whether you have one service or one thousand, they can all be composed into a single entry point without compromising their existing service boundaries. GraphQL is declarative, flexible, and supported by an open specification. Even if you have a small number of services (as few as one!), Federation can enrich your systems with new features out of the box. This piece isn’t a primer on how to use Apollo Federation, though &#8211; we highly recommend our <a href="https://www.apollographql.com/tutorials/">course catalog in Odyssey</a> for that.</p>



<h2 class="wp-block-heading"><a href="#" aria-hidden="true" class="aal_anchor" id=""><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><img decoding="async" src="https://lh7-us.googleusercontent.com/pagAz5iafYg9GqprnGVOzqsuCB4zbY83Bqh88ohnNXtv_iqW0o4xpAk9-8K1H5LRaybG7AbFjLTq41heJwJeuxob7qNlAQSdTx5frbfy-vkQ-U9o3YOjm-Y6lbWseBPLMMGBp6j3HXPxTMlvhJwUtLU" alt="Image portrays three visuals. The first visual is on GraphQL architecture and includes text that reads build a unified but modular graph of your data and services. The second visual showcases GraphQL infrastructure and includes text that reads Secure, scale, and govern the graph across any number of applications. The third visual showcases GraphQL workflows and includes text that reads enable teams to contribute to and consume the graph in a self-service way." width="&quot;624&quot;&quot;" height="253"></h2>



<h1 class="wp-block-heading"><a href="#how-we-got-here" aria-hidden="true" class="aal_anchor" id="how-we-got-here"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How we got here</h1>



<p class="wp-block-paragraph">Federation wasn’t built overnight. Here’s a timeline of milestones we reached along the way:</p>



<h2 class="wp-block-heading"><a href="#2019" aria-hidden="true" class="aal_anchor" id="2019"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2019</h2>



<p class="wp-block-paragraph"><strong>Initial Apollo Federation commits published</strong>. After years of design and months of implementation and building on the vision Martijn Walraven <a href="https://www.youtube.com/watch?v=OFT9bSv3aYAa">spoke about</a> at GraphQL Summit 2018, our first lines of Federation <a href="https://github.com/apollographql/apollo-server/pull/2742">code</a> became complete enough to publish. Shortly afterwards we <a href="https://www.apollographql.com/blog/apollo-federation-f260cf525d21">released</a> Apollo Federation and Apollo Gateway, creating the GraphQL federation category. At GraphQL Summit 2019, <a href="https://www.youtube.com/watch?v=LKQKn1oFXJU">Jeff Hampton</a> and <a href="https://www.youtube.com/watch?v=EDqw-sGVq3k&amp;t=1047s">Matt DeBergalis</a> dove deep into the use case for GraphQL federation, how it works, and what solutions it offers</p>



<h2 class="wp-block-heading"><a href="#2020" aria-hidden="true" class="aal_anchor" id="2020"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2020</h2>



<p class="wp-block-paragraph"><strong>More expressive graphs</strong>. As developers embraced Federation and our tooling matured, we converged on a more elegant and complete set of <a href="https://www.apollographql.com/docs/federation/federated-types/federated-directives">directives</a> for creating federated graphs. Concepts like entities, owners, and required input data were fully fleshed out with feedback from our enterprise design partners and refined over time.</p>



<h2 class="wp-block-heading"><a href="#2021" aria-hidden="true" class="aal_anchor" id="2021"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2021</h2>



<p class="wp-block-paragraph"><strong>Apollo Federation 2.0 </strong><a href="https://www.apollographql.com/blog/announcing-federation-2"><strong>released</strong></a>. This version of Federation was created in close collaboration with the excellent engineers at Netflix. Apollo Federation 2 helps organizations operate even better across teams, leveraging shared types and the ability to migrate parts of a federated schema from one owner to another.</p>



<h2 class="wp-block-heading"><a href="#2022" aria-hidden="true" class="aal_anchor" id="2022"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2022</h2>



<p class="wp-block-paragraph"><strong>Apollo Router became </strong><a href="https://www.apollographql.com/blog/apollo-router-is-now-generally-available"><strong>generally available</strong></a>. Apollo Router has since become the standard-bearer for enterprise GraphQL at scale and is an indispensable part of the stack for a growing number of organizations.</p>



<h2 class="wp-block-heading"><a href="#2023" aria-hidden="true" class="aal_anchor" id="2023"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2023</h2>



<p class="wp-block-paragraph"><strong>Federated subscriptions </strong><a href="https://www.apollographql.com/blog/federated-subscriptions-in-graphos-real-time-data-at-scale"><strong>shipped</strong></a>. This enabled realtime data from anywhere in your infrastructure to all your clients, all made possible by protocol innovations and made available with a polished full-stack developer experience.</p>



<h1 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next</h1>



<p class="wp-block-paragraph">Apollo is proud to be a founding member of the <a href="https://graphql.org/foundation/">GraphQL Foundation</a> and to be represented on the GraphQL Specification’s Technical Steering Committee and GraphQL Working Group. Since the composition and execution behaviors in Apollo Federation are becoming increasingly adopted by a wide array of users and toolmakers, there is a clear benefit for developing a common standard focused specifically on this domain.</p>



<p class="wp-block-paragraph">Contributors from Apollo are working with others in the community to <a href="https://github.com/graphql/composite-schemas-spec">collaborate on a proposal</a> for a common specification within the GraphQL Working Group. We are beyond excited at the innovation that this effort will unlock, and thrilled that the community is moving towards a common understanding of the importance of this technology category.</p>



<h1 class="wp-block-heading"><a href="#a-universe-of-possibilities" aria-hidden="true" class="aal_anchor" id="a-universe-of-possibilities"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A universe of possibilities</h1>



<p class="wp-block-paragraph">Apollo is the leading GraphQL platform in the industry, serving the highest-volume, most demanding production workloads of today while developing the software that will power tomorrow’s use cases. In a rapidly changing world, enterprise organizations can count on the creators of Apollo Federation to continue to invest in solutions that meet and exceed the needs of the world’s largest platforms, all while empowering a robust and open GraphQL community.</p>


<ol class="wp-block-footnotes"><li id="29ebcf61-2dba-471e-a128-d8d3f07a6d34">Gartner, When to Use GraphQL to Accelerate API Delivery, By Shameen Pillai, et al, March 7, 2024. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved. <a href="#29ebcf61-2dba-471e-a128-d8d3f07a6d34-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>

Five Years of Apollo Federation: the Standard for Enterprise API Platforms


<p class="wp-block-paragraph">At last year’s GraphQL Summit, we learned why <a href="https://www.apollographql.com/blog/redefining-api-strategy-why-netflix-platform-engineering-chose-federated-graphql">Netflix placed a “big bet” on GraphQL federation</a>. We heard about <a href="https://www.apollographql.com/blog/how-intuit-handled-their-busiest-time-of-year-with-apollo-router">Intuit’s measured rollout of Apollo Router</a>. And we learned how <a href="https://www.youtube.com/watch?v=-4R6rLMZ9mc">federated subscriptions</a> enable client teams to deliver real-time updates to their apps – no matter where that data is stored. This year’s <a href="http://www.graphqlsummit.com">GraphQL Summit</a> is in New York City, and we expect an even better event this year.</p>



<p class="wp-block-paragraph">After just five years, GraphQL federation is becoming a de facto skill to manage API complexity in distributed architectures. In fact, Gartner predicts that <a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery">30% of enterprises will incorporate GraphQL federation</a> into their stacks within three years. This architecture didn’t just take off at digital-native companies like Netflix, PayPal, and Expedia. It’s now a critical part of the API programs across industries like retail, healthcare, CPG, automotive, and many others. Organizations like Major League Baseball and Volvo Cars chose GraphQL federation to help them deliver immersive, omni-channel, and feature-rich digital experiences at any scale.</p>



<p class="wp-block-paragraph">So what do the next five years look like for federated graphs? How can larger organizations leverage this architecture to roll out the next generation of personalized, AI-driven applications? That’s the theme of this year’s GraphQL Summit on October 8-10.</p>



<h2 class="wp-block-heading"><a href="#graphql-summit-the-ultimate-conference-for-api-platform-teams-and-decision-makers" aria-hidden="true" class="aal_anchor" id="graphql-summit-the-ultimate-conference-for-api-platform-teams-and-decision-makers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL Summit: The ultimate conference for API platform teams and decision-makers</h2>



<p class="wp-block-paragraph">If you’re interested in learning how some of the most innovative companies in the world tackle these problems with GraphQL federation, don’t miss this year’s <a href="http://www.graphqlsummit.com">GraphQL Summit</a>. This event provides an insider’s look behind the API platforms and strategies that power some of the biggest digital brands on the internet today. Join a community of your peers to learn how they’re thinking about GraphQL in the AI era.</p>



<h3 class="wp-block-heading"><a href="#learn-connect-impact" aria-hidden="true" class="aal_anchor" id="learn-connect-impact"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Learn, connect, impact</h3>



<p class="wp-block-paragraph">This year’s GraphQL Summit will be power-packed with useful talks, workshops, and networking opportunities. Whether you’ve been using GraphQL federation for years or are just evaluating it, you’ll benefit from real-world anecdotes and practical advice for managing a supergraph at any scale. This year’s Summit features talk tracks and hands-on workshops that cover architecture, platform management, human factors, and client development. There is also a new AI track, highlighting how to use GraphQL federation to power the next generation of applications.&nbsp;</p>



<p class="wp-block-paragraph">GraphQL Summit isn’t just about technical know-how though. GraphQL federation is becoming a de facto component of a modern API platform. By attending this conference, you will learn how to modernize your API strategy to better reduce technical debt, improve developer velocity, drive a better user experience across applications, and help your organization better adapt to the ever-changing digital landscape.</p>



<h3 class="wp-block-heading"><a href="#and-drumrollhere-are-our-confirmed-speakers" aria-hidden="true" class="aal_anchor" id="and-drumrollhere-are-our-confirmed-speakers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>And *drumroll*…here are our confirmed speakers:</h3>



<ul class="wp-block-list">
<li>Marc-André Giroux, Senior Software Developer from Netflix and author of <em>Production-Ready GraphQL</em>&nbsp;</li>



<li>Stephanie Saunders, Engineering Manager at Coinbase</li>



<li>Mike Cohen, Senior Technical Fellow from Indeed</li>
</ul>



<p class="wp-block-paragraph">Be sure to pay attention to Apollo on <a href="https://x.com/apollographql">X</a> and/or <a href="https://www.linkedin.com/company/apollo-graphql">LinkedIn</a> to find out our next batch of confirmed speakers. If you would like to share your GraphQL federation knowledge to the world, submit a talk at <a href="http://www.graphqlsummit.com">www.graphqlsummit.com</a>.&nbsp;</p>



<p class="wp-block-paragraph"><a href="https://summit.graphql.com/">Early bird tickets </a>are available until May 20th. We look forward to seeing you in New York City!</p>


Announcing GraphQL Summit 2024 in New York City


<p class="wp-block-paragraph">GraphQL’s secret sauce is its ability to act as an abstraction layer for service-oriented backends, translating a sea of microservices into a more human-friendly representation of an organization’s data and capabilities. However, as a graph inevitably expands across more and more of the backend, it becomes increasingly difficult for the platform and backend teams that own it to fully understand its structure.&nbsp;</p>



<p class="wp-block-paragraph">This pain is particularly acute at organizations deploying a federated GraphQL API (also known as a supergraph) at a massive scale with <a href="https://apollographql.com/docs/federation">GraphQL Federation</a>. The distributed nature of developing supergraphs makes it possible to scale them across many independent backend teams and domains, but it also significantly increases the complexity of the relationships in the schema and makes it difficult to find value in existing schema visualization tools which are designed for traditional monolithic graphs.&nbsp;</p>



<p class="wp-block-paragraph">As the creators of Federation, we want to give API developers a better way to visually explore their supergraph. Today, we’re excited to release native schema visualization in Apollo GraphOS Studio, <strong>free</strong> ( 🎉) for all users. API architects and developers can now use <a href="https://www.apollographql.com/graphos">Apollo GraphOS</a> to visually explore the types, fields, and connections in their graph without running their graph locally, enabling introspection, or spinning up a separate visualization tool.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1493" height="814" src="https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis.png" alt="" class="wp-image-23493" srcset="https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis.png 1493w, https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis-300x164.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis-1024x558.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis-768x419.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis-1200x654.png 1200w" sizes="auto, (max-width: 1493px) 100vw, 1493px" /></figure>



<h2 class="wp-block-heading"><a href="#centrally-explore-your-federated-graph" aria-hidden="true" class="aal_anchor" id="centrally-explore-your-federated-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Centrally explore your federated graph</h2>



<p class="wp-block-paragraph">Historically, generating a schema visualization for a federated graph required jumping through some hoops. You either had to run the graph with introspection enabled (<a href="https://www.apollographql.com/blog/why-you-should-disable-graphql-introspection-in-production">generally not recommended</a> for production graphs) or copy-paste the supergraph SDL into a hosted visualization tool. For extra points, you could spin up your own visualization service and integrate it with your graph’s deployment pipeline, but even then you would probably experience limited returns as most out-of-the-box graph visualization libraries aren’t equipped to handle the scale and complexity of a supergraph.</p>



<p class="wp-block-paragraph">With GraphOS Studio, you and your team can explore an always-up-to-date visualization of your graph with integrated capabilities like subgraph filtering and entity highlighting that simplify navigation for supergraphs. You can also copy and share a direct link to any view within the visualization to help other developers, product managers, and non-technical contributors understand the structure of the graph.</p>



<figure class="wp-block-video"><video height="1490" style="aspect-ratio: 2880 / 1490;" width="2880" autoplay controls loop muted src="https://wp.apollographql.com/wp-content/uploads/2024/03/vis-highlight-entities-1.mp4" playsinline></video></figure>



<h2 class="wp-block-heading"><a href="#visualize-graph-performance" aria-hidden="true" class="aal_anchor" id="visualize-graph-performance"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Visualize graph performance</h2>



<p class="wp-block-paragraph">In addition to making large graphs more intelligible, the schema visualizer in GraphOS Studio also helps you uncover more actionable information by integrating metrics for your graph. From the Highlight drop-down in the UI, you can choose to highlight fields by error rate, request rate, and P95 latency, helping you understand which parts of the graph may need to be debugged or optimized.</p>



<figure class="wp-block-video"><video height="1490" style="aspect-ratio: 2880 / 1490;" width="2880" autoplay controls loop muted src="https://wp.apollographql.com/wp-content/uploads/2024/03/vis-highlight-usage-1.mp4" playsinline></video></figure>



<p class="wp-block-paragraph">To dig further into errors and performance, you can navigate to the insights page for any field directly from the schema visualization UI.</p>



<figure class="wp-block-video"><video height="1490" style="aspect-ratio: 2880 / 1490;" width="2880" autoplay controls loop muted src="https://wp.apollographql.com/wp-content/uploads/2024/03/vis-to-insights.mp4" playsinline></video></figure>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p class="wp-block-paragraph">Schema visualization is available today for all GraphOS users! To get started, log in or create a graph in <a href="https://studio.apollographql.com">GraphOS Studio</a>, and navigate to Schema &gt; Visualization. As always, we would love to hear your feedback so we can improve our visualization tools in future iterations. Don’t hesitate to drop us a question or comment in our community <a href="https://discord.gg/graphos">Discord</a>.</p>



<p class="wp-block-paragraph">Happy visualizing!</p>


Visualizing federated GraphQL APIs with GraphOS Studio


<p class="wp-block-paragraph"><a href="https://apollographql.com">Apollo GraphQL</a>, the creator of GraphQL Federation, today announced its membership with the Cloud Native Computing Foundation (CNCF) as a Silver member. This strategic alliance reinforces Apollo GraphQL’s commitment to fostering innovation, enhancing API efficiency, and promoting the importance of GraphQL in platform engineering.&nbsp;</p>



<p class="wp-block-paragraph">Platform engineering has emerged as one of the top strategic trends for 2024, for which the CNCF recently issued a<a href="https://tag-app-delivery.cncf.io/whitepapers/platforms/"> set of recommendations</a> and a <a href="https://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/">maturity model </a>defining it. Apollo GraphQL helps API platform teams apply these recommendations to the API layer with Apollo GraphOS, its flagship product. Rather than delivering APIs as a barrage of new endpoints to manage, the Apollo GraphOS platform empowers teams to use GraphQL to build an API composition layer called a &#8216;supergraph&#8217;. This supergraph enables backend teams to connect APIs, and then makes them available to client teams via a single endpoint. Apollo GraphQL now offers a vision to significantly increase developer velocity using a supergraph in its new white paper, <a href="https://www.apollographql.com/resources/platform-engineering-for-apis">“Platform Engineering for APIs: Using GraphQL to Drive Developer Efficiency.”</a>&nbsp;</p>



<p class="wp-block-paragraph">This approach introduces a self-service, self-documenting system, departing from traditional methods of building experience APIs or backends-for-frontends. It enables client teams to use a declarative query language to fetch the required data for their apps, reducing the cognitive load on product engineering teams. A supergraph also provides a scalable composition layer for backend teams, providing an architecture that can support any number of client applications. Using Apollo GraphOS, platform teams gain the tools to secure, scale, and operationalize a supergraph across any number of teams and applications.</p>



<p class="wp-block-paragraph">Apollo GraphQL also recently launched a better workflow for backend teams to contribute to the graph with <a href="https://www.apollographql.com/blog/graphos-schema-proposals-a-principled-development-workflow-for-graphql-api-platforms?utm_campaign=2024-02-12_blog_graphos-schema-proposals&amp;utm_medium=social&amp;utm_source=linkedin">schema proposals</a> &#8211; a new centralized change management workflow that streamlines the process of proposing, reviewing, and approving schema changes to a supergraph.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">“Platforms are transforming every layer of the stack and the supergraph provides the next chapter of the story — it&#8217;s the architecture of choice for combining services and APIs into coherent, integrated application experiences using GraphQL,” said Matt DeBergalis, CTO and co-founder at Apollo GraphQL. “Joining the Cloud Native Computing Foundation (CNCF) is an important milestone forward for Apollo GraphQL to bring GraphQL into an ecosystem focused on building and shaping the future of cloud-native composable platforms.”</p>
</blockquote>



<h2 class="wp-block-heading"><a href="#see-what-customers-are-talking-about" aria-hidden="true" class="aal_anchor" id="see-what-customers-are-talking-about"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>See what customers are talking about</h2>



<p class="wp-block-paragraph">Apollo GraphQL will be a sponsor and exhibit at the eminent <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">KubeCon + CloudNativeCon Europe 2024</a>, the Cloud Native Computing Foundation&#8217;s flagship conference that gathers adopters and technologists from leading open source and cloud native communities. Visitors to Apollo GraphQL’s booth will see the platform that enables API platform teams, such as <a href="https://www.apollographql.com/blog/mlbs-api-strategy-hitting-a-home-run-transformation-with-graphql-midfield">MLB</a> and <a href="https://www.apollographql.com/blog/how-intuit-handled-their-busiest-time-of-year-with-apollo-router">Intuit</a>, connect their APIs and deliver a self-service graph that can power any number of applications. Visitors will be able to have one-on-one conversations with the Apollo GraphQL team and will also be eligible to win great prizes.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#resources" aria-hidden="true" class="aal_anchor" id="resources"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Resources</h2>



<ul class="wp-block-list">
<li>Download the white paper, <a href="https://www.apollographql.com/resources/platform-engineering-for-apis">Platform Engineering for APIs</a></li>



<li>Learn more and engage with the Apollo GraphQL team at booth #G33 at <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">KubeCon + CloudNativeCon Europe 2024</a> from March 19-22</li>



<li><a href="https://www.apollographql.com/supergraph/">Learn</a> more about supergraphs</li>



<li><a href="https://www.apollographql.com/graphos/">Build </a>a GraphQL API platform today</li>



<li><a href="https://www.apollographql.com/tutorials/certifications/apollo-graph-professional/learning-path/">Become certified </a>as an Apollo GraphQL developer</li>



<li><a href="https://discord.com/invite/yFZJH2QYrK">Join</a> the Apollo GraphQL Community on Discord</li>



<li>For more information on the CNCF or to see the full list of new members, read the <a href="https://www.cncf.io/announcements/2024/03/20/45-new-members-join-the-cloud-native-computing-foundation/">press release</a></li>
</ul>



<h2 class="wp-block-heading"><a href="#about-apollo-graphql" aria-hidden="true" class="aal_anchor" id="about-apollo-graphql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>About Apollo GraphQL</strong></h2>



<p class="wp-block-paragraph"><a href="https://apollographql.com">Apollo GraphQL </a>helps developers help the world by providing a better API platform across teams. Apollo’s open-source software is downloaded 25M times per month and its commercial GraphQL technologies power the most innovative brands today. Teams at Netflix, Snap, and the New York Times ship personalized, omnichannel experiences faster with a supergraph – a self-service GraphQL platform that spans any number of backend services. Serving over 5T requests in 2023, the Apollo GraphOS platform simplifies API development with workflows and infrastructure to build, test, and ship supergraphs at any scale. Based in San Francisco, Apollo is backed by Insight Partners, Andreessen Horowitz, Matrix Partners, and Trinity Ventures. Learn more at: <a href="https://www.apollographql.com">https://www.apollographql.com</a>.</p>


Apollo GraphQL to join Cloud Native Computing Foundation Membership as Silver Sponsor


<p class="wp-block-paragraph">As an engineering organization grows, the quality of its internal developer platforms directly influences its ability to execute. It’s why <a href="https://www.gartner.com/en/articles/what-is-platform-engineering">80% of large software organizations are expected to establish platform engineering teams by 2026</a> and why many existing platform teams are turning to federated GraphQL APIs, known as <a href="https://www.apollographql.com/docs/resources/glossary/#supergraph">supergraphs</a>, to build self-service API platforms. Client teams leverage these platforms to quickly build features without orchestrating APIs, and backend teams autonomously contribute services from their respective domains via modules called subgraphs.</p>



<p class="wp-block-paragraph">However, contributions that affect the <em>shape</em> of your supergraph (i.e. the schema) still require cross-team coordination to ensure (1) we are designing the schema in a way that continues to benefit developer velocity, (2) that we don’t break client apps, and (3) that our changes don’t conflict with other backend teams’ subgraph schemas. The modularity of the supergraph can make this coordination tricky since each subgraph schema may live in a different codebase, and not every required contributor or approver may have access to each of those codebases.</p>



<p class="wp-block-paragraph">Apollo aims to make it easy for any number of teams to better collaborate and contribute to a supergraph. Today, we are excited to announce general availability of <a href="https://www.apollographql.com/docs/graphos/delivery/schema-proposals">GraphOS Schema Proposals</a> – a new centralized change management workflow in GraphOS Studio that streamlines the process of proposing, reviewing, and approving schema changes to a supergraph.</p>



<h2 class="wp-block-heading"><a href="#centrally-manage-changes-with-integrated-checks" aria-hidden="true" class="aal_anchor" id="centrally-manage-changes-with-integrated-checks"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Centrally manage changes with integrated checks</h2>



<p class="wp-block-paragraph">Developers contributing to a supergraph are typically distributed across multiple teams, making it difficult to take advantage of traditional change management workflows that application teams use across a particular codebase. Although these workflows provide the right tooling, they are implemented at too granular of a level, failing to provide the visibility into the overall impact to the supergraph that platform teams require.&nbsp;</p>



<p class="wp-block-paragraph">GraphOS Schema Proposals provide a purpose-built change management workflow for the API platform layer, allowing developers and platform engineers across multiple teams to propose, review, and approve schema changes.</p>



<h3 class="wp-block-heading"><a href="#propose-and-test-schema-changes" aria-hidden="true" class="aal_anchor" id="propose-and-test-schema-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Propose and test schema changes</h3>



<p class="wp-block-paragraph">Proposing a schema change in GraphOS is the first step to making a change to a supergraph. GraphOS Studio now has an integrated schema editor that subgraph developers can use to make changes to existing subgraph schemas or even create new subgraph schemas from scratch.&nbsp;</p>



<p class="wp-block-paragraph">The schema editor is integrated with all of the other great features of GraphOS Studio, allowing authors to see GraphQL-aware diffing in real time and run linter checks as they work.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="820" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor.png" alt="" class="wp-image-23342" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-300x154.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-1024x525.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-768x394.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-1536x787.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-1200x615.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p class="wp-block-paragraph">Whenever someone saves a revision on a proposal, GraphOS Studio will automatically run <a href="https://www.apollographql.com/docs/graphos/delivery/schema-checks/">schema checks</a> to validate that the proposed schema changes will compose with other existing subgraphs and won’t break client operations.</p>



<h3 class="wp-block-heading"><a href="#review-and-approve-schema-changes" aria-hidden="true" class="aal_anchor" id="review-and-approve-schema-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Review and approve schema changes</h3>



<p class="wp-block-paragraph">Once someone on your team has drafted a schema proposal, the author can mark it as <code class="" data-line="">OPEN FOR FEEDBACK</code><em> </em>to make it visible to other subgraph, platform, and client developers with the proper permissions. If the proposal needs approval from specific reviewers like a team lead or a potentially affected client developer, the author can request a review from those users.&nbsp;</p>



<p class="wp-block-paragraph">If your organization has a governance policy that requires certain users to approve every schema change for a graph – a platform team lead, for example – graph admins can add those users as <em>default</em> reviewers from the graph settings page. Admins can also set a minimum number of reviewers required for a proposal to be <code class="" data-line="">APPROVED</code>.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="662" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request.png" alt="" class="wp-image-23344" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-300x124.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-1024x424.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-768x318.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-1536x636.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-1200x497.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p class="wp-block-paragraph">Once the minimum number of approvals has been reached and any mandatory default reviewers have approved the proposal, the proposal is marked as <code class="" data-line="">APPROVED</code> and is ready for publishing.</p>



<h2 class="wp-block-heading"><a href="#publish-approved-changes" aria-hidden="true" class="aal_anchor" id="publish-approved-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Publish approved changes</h2>



<p class="wp-block-paragraph">In addition to editing and reviews, GraphOS Schema Proposals also provides developers with a streamlined workflow for implementing approved changes locally and safeguards to prevent unapproved changes from being published.</p>



<p class="wp-block-paragraph">Once a developer has created a proposal, subgraph developers can use Apollo’s Rover CLI to quickly <a href="https://www.apollographql.com/docs/graphos/delivery/schema-proposals/implementation#pull-proposed-schemas-with-rover">pull associated subgraph schemas</a> with rover subgraph fetch. From this point, subgraph developers can then follow the standard steps for developing and delivering changes to their subgraph:</p>



<ol class="wp-block-list">
<li>Make local changes to subgraph server code, including updating or writing new resolvers</li>



<li>Run GraphOS schema checks locally using the Rover CLI (including a new Proposals task to verify that schema changes have a matching approved proposal in GraphOS)</li>



<li>Publish the subgraph schema to GraphOS</li>



<li>Deploy changes to your subgraph server</li>
</ol>



<p class="wp-block-paragraph"><em>(Note: the Schema Proposals workflow </em><strong><em>does not</em></strong><em> automate the above steps, but </em><a href="https://www.apollographql.com/docs/rover/ci-cd/"><em>they can be automated in your CI/CD pipelines using the Rover CLI</em></a><em>)</em></p>



<h3 class="wp-block-heading"><a href="#preventing-publishing-of-unapproved-changes" aria-hidden="true" class="aal_anchor" id="preventing-publishing-of-unapproved-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Preventing publishing of unapproved changes</h3>



<p class="wp-block-paragraph">Although the proposals workflow does not automate the deployment process for schema changes, the new Proposal task in the schema checks workflow does provide a safeguard against publishing unapproved changes. Graph Admins can enable or disable the Proposal task in graph settings, and they can also configure the severity of the check to <code class="" data-line="">Error</code> or <code class="" data-line="">Warn</code>.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="797" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff.png" alt="" class="wp-image-23346" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-300x149.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-1024x510.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-768x383.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-1536x765.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-1200x598.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p class="wp-block-paragraph">Setting the Proposal task severity to <code class="" data-line="">Error</code> will cause schema checks to fail if any schema changes do not have a matching approved proposal. This includes schema checks that are run locally as well as when a schema is published to GraphOS, ensuring that unapproved changes are never published to the supergraph.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="488" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity.png" alt="" class="wp-image-23348" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-300x92.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-1024x312.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-768x234.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-1536x468.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-1200x366.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p class="wp-block-paragraph">Schema Proposals are generally available today for all <a href="https://apollographql.com/pricing">GraphOS Enterprise</a> customers. To create a proposal, navigate to your graph in GraphOS Studio, and open the Proposals page from the left navigation. For a full walkthrough of creating and managing proposals, head over to the <a href="https://www.apollographql.com/docs/graphos/delivery/schema-proposals/">Schema Proposals documentation</a>.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="429" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav.png" alt="" class="wp-image-23350" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-300x80.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-1024x275.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-768x206.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-1536x412.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-1200x322.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p class="wp-block-paragraph">To learn more about GraphOS Schema Proposals and agile API platform development, <a href="https://bit.ly/42E9vd9">join Apollo’s webinar</a> on February 22, 2024 with Parul Schroff, product manager for GraphOS Schema Proposals! Here are a few things the talk will cover:</p>



<ul class="wp-block-list">
<li>How federated GraphQL enables platform engineering teams to build a self-serve API platform</li>



<li>How Apollo GraphOS can help your team operationalize delivering a federated graph</li>



<li>How to leverage GraphOS Schema proposals to streamline federated schema design, review, and implementation</li>
</ul>



<p class="wp-block-paragraph">We hope to see you there!</p>


GraphOS Schema Proposals: a principled development workflow for GraphQL API platforms


<p class="wp-block-paragraph">Over the past two years, the emergence of AI-driven tools has significantly transformed the tech landscape. Among these innovations, tools designed specifically for code generation—such as Copilot, CodeLlama, and others—have garnered particular attention from developers.&nbsp;</p>



<p class="wp-block-paragraph">According to a survey conducted by GitHub, 92% of U.S.-based developers are already using AI coding tools both in and outside of work <a href="https://github.blog/2023-06-13-survey-reveals-ais-impact-on-the-developer-experience/">(source)</a>.</p>



<p class="wp-block-paragraph">These tools offer immense value for tasks like rapid prototyping and brainstorming, serving as powerful allies in the development process. However, despite their advanced capabilities, a notable gap exists in their ability to generate high-quality GraphQL schemas.</p>



<p class="wp-block-paragraph">I&#8217;m sure most, if not all of us, wish to craft the finest GraphQL schema possible—even if it&#8217;s just for a prototype. If you’ve watched my <a href="https://www.youtube.com/watch?v=p4jP2xnImAM">“Let&#8217;s Build a Supergraph Using ChatGPT” talk at GraphQL Summit</a>, you might know some of the ways you can steer tools like ChatGPT to improve the output of the generated code.</p>



<p class="wp-block-paragraph">But let&#8217;s be real. The results aren&#8217;t always perfect, and it almost feels like ChatGPT clings onto some less-than-desirable practices! Consider this scenario: when I request ChatGPT to construct a schema for a note-taking application, this is the outcome:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">type Query {
  getNotes: [Note]
  getNoteById(id: ID!): Note
  getTags: [Tag]
}

type Mutation {
  createNote(title: String!, body: String!): Note
  createTag(name: String!): Tag
  addTagToNote(noteId: ID!, tagId: ID!): Note
}

type Note {
  id: ID!
  title: String!
  body: String!
  tags: [Tag]
}

type Tag {
  id: ID!
  name: String!
  notes: [Note]
}
</code></pre>



<p class="wp-block-paragraph">Clearly, this schema has room for improvement. It includes generally discouraged practices like utilizing &#8216;get&#8217; in query fields and lacking important elements like pagination. It also overlooks important components such as mutation payloads and input types, essential for successful schema evolution.</p>



<p class="wp-block-paragraph">During my presentation, I shared our experience with fine-tuning GPT-3.5 for optimized GraphQL schema generation. We did notice improvements on schema generation from the standard models, but it wasn&#8217;t flawless. On numerous occasions, the model failed to meet our set guidelines for schema generation or it was generating schemas that were less than ideal.</p>



<p class="wp-block-paragraph">So we’ve been working more to make the output much better and make sure it would follow the best practices as often as possible, and we are finally ready to share it with you all!</p>



<p class="wp-block-paragraph">To try it is pretty simple! <a href="https://discord.gg/SzeywawCa6">Join our Discord server</a>, go to the <strong>#ai-schema-design</strong> forum and post a message describing the schema you’d like to create, for example:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph"><strong>Title:</strong> Note taking application&nbsp;</p>



<p class="wp-block-paragraph">I&#8217;m building a note taking application. Users can create notes, and each note has a title and a body. Users can also create tags, and each tag has a name. Users can add tags to notes, and notes can have multiple tags.</p>
</blockquote>



<p class="wp-block-paragraph">Then after submitting the bot will create a schema based on your inputs! The more specific you are the better the schema will be 😊And you’ll be able to keep iterating with the bot to improve the schema or even to see some operation that you could run with your schema</p>



<p class="wp-block-paragraph">Here’s an example of the schema generator in action:</p>



<figure class="wp-block-video"><video height="1886" style="aspect-ratio: 2868 / 1886;" width="2868" autoplay controls loop muted src="https://wp.apollographql.com/wp-content/uploads/2024/02/CleanShot-2024-02-05-at-18.48.38.mov" playsinline></video></figure>



<p class="wp-block-paragraph">I hope this will be useful for your schema design journey, and remember we’ll always be happy to help you with your schemas, so feel free to ping me or any other Developer Advocate in <a href="https://discord.gg/SzeywawCa6">our Discord server</a>.&nbsp;</p>


Fun with AI – Generating GraphQL Schemas in Discord


<p class="wp-block-paragraph">Modern apps must support real-time use cases like flight changes, team collaboration, or live score updates for the big game. GraphQL subscriptions push events in a more efficient and performant way compared to traditional client-side polling of RESTful services that try to pull new events every few seconds. Instead of polling, clients can subscribe to the specific data they require, and the graph immediately delivers those events as they occur, reducing backend load and providing faster real-time updates.</p>



<p class="wp-block-paragraph">Traditionally, GraphQL subscriptions have been implemented with WebSockets, an approach with many issues, including compression, debugging, scalability, and compatibility with firewalls, load-balancers, and other networking infrastructure.</p>



<p class="wp-block-paragraph">We addressed the frontend portion of the WebSocket problem in June 2023, when we announced <a href="https://www.apollographql.com/blog/federated-subscriptions-in-graphos-real-time-data-at-scale" target="_blank" rel="noreferrer noopener">Federated subscriptions in GraphOS</a> with support for a new <a href="https://www.apollographql.com/docs/react/data/subscriptions/#subscriptions-via-multipart-http" target="_blank" rel="noreferrer noopener">HTTP multipart protocol</a> based on the underlying protocol for GraphQL @defer support in <a href="https://www.apollographql.com/docs/router/executing-operations/defer-support/" target="_blank" rel="noreferrer noopener">Apollo Router</a>. This makes hosting a real-time API in any cloud environment easier, with all the benefits of a standard HTTP connection.</p>



<p class="wp-block-paragraph">However, on the backend, Apollo Router supports legacy WebSocket protocols for compatibility with existing subgraph APIs, which is inefficient at scale. For example, if a subscription can’t be <a href="https://www.apollographql.com/docs/router/executing-operations/subscription-support/#subscription-deduplication" target="_blank" rel="noreferrer noopener">deduplicated</a>, 1 million client subscriptions would require 1 million backend WebSockets connections.&nbsp;</p>



<p class="wp-block-paragraph">Today, we are excited to announce the GA release of Apollo Router 1.37 with <a href="https://www.apollographql.com/docs/router/executing-operations/subscription-callback-protocol/" target="_blank" rel="noreferrer noopener">HTTP callback support</a>, designed in partnership with the GraphQL community. HTTP callback support solves the backend WebSocket problem and dramatically reduces the number of open subgraph connections. This results in the same great performance but with more efficiency at scale and reduces real-time cloud spend for router and subgraph deployments.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="2560" height="1118" src="https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-scaled.jpg" alt="" class="wp-image-23275" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-scaled.jpg 2560w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-300x131.jpg 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-1024x447.jpg 1024w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-768x335.jpg 768w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-1536x671.jpg 1536w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-2048x894.jpg 2048w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-1200x524.jpg 1200w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-1980x865.jpg 1980w" sizes="auto, (max-width: 2560px) 100vw, 2560px" /></figure>



<p class="wp-block-paragraph">Subscription callbacks offer new levels of flexibility and interoperability between the router and underlying services. By default, federated subscriptions use WebSockets, which requires two long-lived connections for every client: one between the client and the router and one between the router and the subgraph. Additionally, these long-lived connections aren’t well suited for serverless infrastructures.&nbsp;</p>



<p class="wp-block-paragraph">With HTTP callbacks, on the other hand, the router no longer manages a WebSocket connection with subgraphs, and it’s flexible enough to be used with other Pub/Sub architectures that can support HTTP requests.</p>



<h2 class="wp-block-heading"><a href="#http-callbacks-for-federated-subscriptions" aria-hidden="true" class="aal_anchor" id="http-callbacks-for-federated-subscriptions"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>HTTP Callbacks for Federated Subscriptions</h2>



<p class="wp-block-paragraph">Here’s what you’ll need to use federated subscriptions with self-hosted instances of Apollo Router:</p>



<ol class="wp-block-list">
<li>An active Apollo GraphOS Enterprise plan</li>



<li>A federated GraphQL API with
<ol class="wp-block-list">
<li>One or more HTTP callback-compatible GraphQL servers, such as <a href="https://www.apollographql.com/docs/apollo-server/api/plugin/subscription-callback" target="_blank" rel="noreferrer noopener">Apollo Server</a> &gt;= 4.10.0 or <a href="https://github.com/apollographql/federation-jvm/tree/main/spring-subscription-callback#usage" target="_blank" rel="noreferrer noopener">Spring GraphQL</a> &gt;= 4.3.0</li>



<li><a href="https://github.com/apollographql/router/releases/tag/v1.37.0" target="_blank" rel="noreferrer noopener">Apollo Router v1.37</a> or greater</li>
</ol>
</li>



<li>The latest version of Apollo Client (Web, iOS, or Kotlin) with HTTP-based subscriptions support.</li>
</ol>



<p class="wp-block-paragraph">If you don’t have a GraphOS Enterprise plan and you need to self-host the Apollo Router for an enterprise-scale deployment, try out <a href="https://studio.apollographql.com/signup?type=enterprise-trial&amp;referrer=blog" target="_blank" rel="noreferrer noopener">GraphOS Enterprise</a> for free for 28 days.</p>



<h3 class="wp-block-heading"><a href="#migrating-from-the-preview-to-ga" aria-hidden="true" class="aal_anchor" id="migrating-from-the-preview-to-ga"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Migrating from the preview to GA</h3>



<p class="wp-block-paragraph">If your application already uses the preview of subscription callbacks, there are a few things to change in your Router configuration to migrate to the GA:</p>



<ol class="wp-block-list">
<li>Change the name of the option from <code class="" data-line="">subscription.mode.preview_callback</code> to <code class="" data-line="">subscription.mode.callback</code>. Failure to use the updated option name when running the router will result in an error, and the router won&#8217;t start.</li>



<li>Update the <code class="" data-line="">public_url</code> field to include the full URL of your callback endpoint. Previously, in the preview, the public URL used by the router was the automatic concatenation of the <code class="" data-line="">public_url</code> and <code class="" data-line="">path</code> fields. In GA, the behavior has changed, and the router uses the value set in <code class="" data-line="">public_url</code>. This enables you to configure your public URL, for example, if you have a proxy in front of the router and want to configure redirection with the public URL.</li>



<li>Configure the new <code class="" data-line="">heartbeat_interval</code> field to set the period that a heartbeat must be sent to the callback endpoint for the subscription operation. The default heartbeat interval is 5 seconds. You can turn off heartbeats, for example, if you’re operating in a serverless architecture without long-lived processes, by setting <code class="" data-line="">heartbeat_interval: disabled</code>.</li>
</ol>



<h2 class="wp-block-heading"><a href="#try-it-today" aria-hidden="true" class="aal_anchor" id="try-it-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try it today!</h2>



<p class="wp-block-paragraph">We’re excited for you to try <a href="https://www.apollographql.com/docs/router/executing-operations/subscription-callback-protocol/" target="_blank" rel="noreferrer noopener">HTTP callbacks in GraphOS</a> and would love to hear your thoughts. If you have any questions or feedback for the team, feel free to reach out to us in our<a href="https://discord.com/invite/graphos" target="_blank" rel="noreferrer noopener"> Discord</a>.</p>


Reduce real-time cloud spend with Federated Subscriptions support for HTTP Callbacks


<p class="wp-block-paragraph">With the release of Apollo Client 3.9, we&#8217;re excited to announce a host of new features and improvements, including:</p>



<ul class="wp-block-list">
<li>Suspense-enabled data fetching in response to user interaction with <code class="" data-line="">useLoadableQuery</code></li>



<li>Preloading data outside of React with <code class="" data-line="">createQueryPreloader</code> and <code class="" data-line="">preloadQuery</code></li>



<li>Memory usage optimizations</li>



<li>A new&nbsp;<code class="" data-line="">useQueryRefHandlers</code>&nbsp;hook for accessing <code class="" data-line="">refetch</code> and <code class="" data-line="">fetchMore</code> for a given <code class="" data-line="">queryRef</code></li>



<li>Multipart subscriptions network adapters for Relay and urql</li>



<li><code class="" data-line="">MockedProvider</code> improvements</li>
</ul>



<p class="wp-block-paragraph">Let&#8217;s dive in!</p>



<h2 class="wp-block-heading"><a href="#suspense-enabled-data-fetching-in-response-to-user-interaction-with-useloadablequery" aria-hidden="true" class="aal_anchor" id="suspense-enabled-data-fetching-in-response-to-user-interaction-with-useloadablequery"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Suspense-enabled data fetching in response to user interaction with <code class="" data-line="">useLoadableQuery</code></h2>



<p class="wp-block-paragraph">When it comes to Suspense-enabled data fetching in Apollo Client, <code class="" data-line="">useSuspenseQuery</code> and <code class="" data-line="">useBackgroundQuery</code> are useful for loading data as soon as the component calling the hook mounts. But what about loading a query in response to user interaction? For example, you may want to start loading some data when a user hovers on a link.</p>



<p class="wp-block-paragraph">Introducing the <code class="" data-line="">useLoadableQuery</code> hook 🎉 For more information, see <a href="https://www.apollographql.com/docs/react/data/suspense#fetching-in-response-to-user-interaction">its documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#preloading-data-outside-of-react-with-createquerypreloader-and-preloadquery" aria-hidden="true" class="aal_anchor" id="preloading-data-outside-of-react-with-createquerypreloader-and-preloadquery"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Preloading data outside of React with <code class="" data-line="">createQueryPreloader</code> and <code class="" data-line="">preloadQuery</code></h2>



<p class="wp-block-paragraph">Starting with Apollo Client 3.9, queries can be initiated outside of React. This allows your app to begin fetching data <em>before</em> React renders your components, and can provide performance benefits.</p>



<p class="wp-block-paragraph">To preload queries, you first need to create a preload function with <code class="" data-line="">createQueryPreloader</code>. <code class="" data-line="">createQueryPreloader</code> takes an <code class="" data-line="">ApolloClient</code> instance as an argument and returns a function that, when called, initiates a network request.</p>



<p class="wp-block-paragraph">The preload function returns a <code class="" data-line="">queryRef</code> that is passed to <a href="https://www.apollographql.com/docs/react/api/react/hooks/#usereadquery"><code class="" data-line="">useReadQuery</code></a> to read the query data and suspend the component while loading. <code class="" data-line="">useReadQuery</code> will ensure that your component is kept up-to-date with cache updates for the preloaded query.</p>



<p class="wp-block-paragraph">This feature pairs nicely with popular routers such as React Router and TanStack Router, both of which provide APIs for loading data before route components render (such as the <a href="https://reactrouter.com/en/main/route/route#loader"><code class="" data-line="">loader</code> function</a> from React Router). It provides the benefits of earlier fetching without sacrificing the ability to automatically re-render when future cache updates occur.</p>



<p class="wp-block-paragraph">This feature is in alpha in 3.9 and may be subject to change before 3.10. If you&#8217;d like to provide feedback before it&#8217;s stabilized, please visit <a href="https://github.com/apollographql/apollo-client/issues/11519">#11519</a> and add a comment.</p>



<p class="wp-block-paragraph">For more information, see <a href="https://www.apollographql.com/docs/react/data/suspense#initiating-queries-outside-react">its documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#introducing-a-new-usequeryrefhandlers-hook" aria-hidden="true" class="aal_anchor" id="introducing-a-new-usequeryrefhandlers-hook"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Introducing a new&nbsp;<code class="" data-line="">useQueryRefHandlers</code>&nbsp;hook</h2>



<p class="wp-block-paragraph"><code class="" data-line="">useQueryRefHandlers</code> is a hook that returns <code class="" data-line="">refetch</code> and <code class="" data-line="">fetchMore</code> functions for a given <code class="" data-line="">queryRef</code>. It&#8217;s useful for gaining access to these handlers for a <code class="" data-line="">queryRef</code> that was created by <code class="" data-line="">createQueryPreloader</code>, or to avoid passing these handlers down through your component tree.</p>



<p class="wp-block-paragraph">For more information, see <a href="https://www.apollographql.com/docs/react/api/react/hooks/#usequeryrefhandlers">its documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#memory-usage-optimizations" aria-hidden="true" class="aal_anchor" id="memory-usage-optimizations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Memory usage optimizations</h2>



<p class="wp-block-paragraph">Spanning over twenty memory-related pull requests, 3.9 includes a host of improvements and optimizations related to memory usage.</p>



<p class="wp-block-paragraph">You can find a comprehensive list in <a href="https://www.apollographql.com/blog/author/lenz">Lenz</a>&#8216;s December <a href="https://www.apollographql.com/blog/apollo-3-9-beta-feature-spotlight-the-memory-story">blog post</a>, but at a high level this work includes many fixes and improvements and introduces <strong>the ability to granularly configure Apollo Client’s internal memoization</strong>.</p>



<p class="wp-block-paragraph">Memoization is always a trade-off between processing time and memory, and some of our old cache limits erred on the side of consuming more memory. While the new defaults should be sufficient for most applications, we know that some will need to make different trade-offs so we made each cache size individually configurable, both before and after the Apollo Client has been initialized. </p>



<p class="wp-block-paragraph">For more information, see our new <a href="https://www.apollographql.com/docs/react/caching/memory-management/">documentation page for memory management</a> and share your <code class="" data-line="">ApolloClient.getMemoryInternals()</code> values <a href="https://github.com/apollographql/apollo-client/issues/11444">in this issue</a>!</p>



<h2 class="wp-block-heading"><a href="#multipart-subscriptions-network-adapters-for-relay-and-urql" aria-hidden="true" class="aal_anchor" id="multipart-subscriptions-network-adapters-for-relay-and-urql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Multipart subscriptions network adapters for Relay and urql</h2>



<p class="wp-block-paragraph">With the launch of <a href="https://www.youtube.com/watch?v=-4R6rLMZ9mc&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=5">federated subscriptions</a> in the Apollo Router last year, Apollo Client added support for GraphQL <a href="https://www.apollographql.com/docs/react/data/subscriptions/#subscriptions-via-multipart-http">subscriptions over HTTP</a>.</p>



<p class="wp-block-paragraph">In 3.9, we&#8217;re shipping network adapters for Relay and urql to make consuming subscriptions via multipart HTTP a breeze no matter which client library you&#8217;re using. For more information, see <a href="https://www.apollographql.com/docs/react/data/subscriptions/#http">the documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#mockedprovider-improvements" aria-hidden="true" class="aal_anchor" id="mockedprovider-improvements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code class="" data-line="">MockedProvider</code> improvements</h2>



<p class="wp-block-paragraph">This release also introduces two frequently requested improvements to the testing utility, <code class="" data-line="">MockedProvider</code>:</p>



<ul class="wp-block-list">
<li><strong>Reusing mocks:</strong> By default, a mock is only used once. If you want to reuse a mock for multiple operations, you can now set the <code class="" data-line="">maxUsageCount</code> field to a number indicating how many times the mock should be used.</li>



<li><strong>Dynamic variables:</strong> The <code class="" data-line="">MockedResponse</code> object now takes a <code class="" data-line="">variableMatcher</code> property that is a function that takes the variables and returns a boolean indication if this mock should match the invocation for the provided query. This can be useful when the exact value of the variables being passed are not known, or for asserting specific variables individually.</li>
</ul>



<p class="wp-block-paragraph">For more on these enhancements, see our complete documentation on <a href="https://www.apollographql.com/docs/react/development-testing/testing/#testing-the-loading-and-success-states">testing React components</a>. Finally, to keep an eye on future testing improvements slated for 3.10, this <a href="https://github.com/apollographql/apollo-client/issues/9738">GitHub issue</a> is the one to watch.</p>



<p class="wp-block-paragraph">You can browse the <a href="https://github.com/apollographql/apollo-client/releases/tag/v3.9.0">full changelog</a> on GitHub. Happy querying!</p>



<p class="wp-block-paragraph"><a href="https://github.com/apollographql/apollo-client/blob/main/ROADMAP.md#future-3x-releases"></a></p>


What’s new in Apollo Client 3.9


<p class="wp-block-paragraph">As platforms, teams, and products evolve, we sometimes need new or different ways to deploy our APIs. Strong Continuous Integration / Continuous Deployment (CI/CD) practices and recovery strategies are necessary components of any <a href="https://aws.amazon.com/blogs/mt/establishing-rpo-and-rto-targets-for-cloud-applications/" target="_blank" rel="noreferrer noopener">Recovery Time Objective (RTO) and Recovery Point Objective (RPO)</a>. </p>



<p class="wp-block-paragraph">The recommended GraphOS <a href="https://www.apollographql.com/tutorials/workshop-summit-graphos-basics/08-changes-process" target="_blank" rel="noreferrer noopener">continuous deployment</a> process uses <a href="https://www.apollographql.com/docs/federation/managed-federation/uplink/" target="_blank" rel="noreferrer noopener">Apollo Uplink</a> to update the Router fleet in place with new supergraph schemas that pass checks in the GraphOS build pipeline along with automated testing in lower environments such as dev or test. However, some organizations have specific deployment needs that rely on an immutable schema for blue-green deploys or canary releases.</p>



<p class="wp-block-paragraph">Today, Apollo is excited to release enhanced GraphOS Platform APIs that streamline integration with immutable blue-green and canary deployments workflows beyond the in-place continuous GraphOS updates that most customers use today:</p>



<ol class="wp-block-list">
<li><a href="https://studio.apollographql.com/graph/apollo-platform/variant/main/schema/reference/objects/GraphMutation?_gl=1*1yu3yv*_ga*NDMzNzY1NzQ4LjE3MDI5MTM0MDk.*_ga_0BGG5V2W2K*MTcwNTEwMzIwNC4zMi4xLjE3MDUxMDM1NzEuMC4wLjA.#publishSubgraphs" target="_blank" rel="noreferrer noopener">PublishSubgraphsMutation</a> will publish all of the releases’ subgraphs as a single unit and return the associated launch and downstream Contract launches.</li>



<li><a href="https://studio.apollographql.com/graph/apollo-platform/variant/main/schema/reference/objects/Launch#status" target="_blank" rel="noreferrer noopener">PollLaunchStatusQuery</a> will poll for the status of any individual launch by ID.</li>



<li><a href="https://studio.apollographql.com/graph/apollo-platform/variant/main/schema/reference/scalars/GraphQLDocument" target="_blank" rel="noreferrer noopener">FetchSupergraphSDLQuery</a> will fetch the supergraph schema of the launch.</li>
</ol>



<p class="wp-block-paragraph">These GraphOS Platform API updates are versatile enough to support many deployment strategies.</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/docs/federation/managed-federation/deployment/#example-blue-green-deployment" target="_blank" rel="noreferrer noopener">Blue-green deployment</a> involves maintaining two identical production environments: the &#8220;Blue&#8221; and the &#8220;Green.&#8221; Only one of these environments is live at any given time. When it&#8217;s time to deploy an update to a supergraph, the team releases it to the inactive environment. For instance, the new version is deployed to “Green” if “Blue” is live. Once the new “Green” version is thoroughly tested and deemed stable, the team switches traffic from “Blue” to “Green.” With these updates to the GraphOS Platform API, <a href="https://www.apollographql.com/docs/graphos/metrics/" target="_blank" rel="noreferrer noopener">metrics and insights</a> for both stages, the “Blue” and the “Green,” are available in a consolidated place under a single Production variant, which has a single launch history to track schema changes over time.</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/docs/federation/managed-federation/deployment/#example-canary-deployment" target="_blank" rel="noreferrer noopener">Canary deployment</a>, on the other hand, is a more gradual process. It involves first rolling out the new supergraph updates to a small subset of users rather than switching simultaneously. This subset, or &#8220;canary group,&#8221; receives the update and is closely monitored by the platform team for any issues. If the deployment is successful, the team rolls out the update to a more significant portion of the user base and eventually to all users.</p>



<p class="wp-block-paragraph">While we recommend rolling forward to recover in most cases, <a href="https://www.apollographql.com/docs/federation/managed-federation/deployment/#rolling-back-a-deployment" target="_blank" rel="noreferrer noopener">rollbacks</a> can be helpful in some scenarios. For example, consider a blue-green deployment where a team deploys the Router and all subgraphs as a single versioned release and houses <strong>immutable schemas</strong> within each Docker image. Then, if the need arises for a rollback, they can simply re-deploy the old Docker images, and the correct supergraph schema will be used. This helps ensure compatibility with existing blue-green workflows that assume an immutable infra mindset.</p>



<p class="wp-block-paragraph">For platform teams looking to enhance their GraphQL platform stance, stay tuned for additional GraphOS Platform API updates and learn more about <a href="https://www.apollographql.com/docs/federation/managed-federation/deployment/" target="_blank" rel="noreferrer noopener">deployment and rollback examples in the GraphOS documentation</a>.</p>


New GraphOS Platform APIs Enable Blue-Green and Canary Deployments


<p class="wp-block-paragraph">Building a scalable and effective enterprise <a href="https://www.apollographql.com/blog/introducing-apollo-graphos">supergraph</a> is challenging, and often feels like there are countless numbers of ways to approach the challenges that arise without evidence of efficacy. Companies searching the GraphQL community for recommendations leads to&nbsp; a lack of consistency across the industry and doing things that may prove to be ineffective, thus requiring changes later down the line. These challenges can often be exacerbated by the lack of consensus both internally and externally, making it difficult to know what works best.</p>



<p class="wp-block-paragraph">Apollo aims to simplify this process for both existing and new GraphQL practitioners and today we’re excited to share the <a href="https://saf.apollographql.com">Supergraph Architecture Framework (SAF)</a>, which is the culmination of years of learning by Apollo’s Solutions Architecture team after working with some of the largest enterprise organizations in the world as a way to answer questions about how to best enable your organization to scale GraphQL effectively.</p>



<h2 class="wp-block-heading"><a href="#what-is-the-saf" aria-hidden="true" class="aal_anchor" id="what-is-the-saf"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is the SAF?</h2>



<p class="wp-block-paragraph">The SAF explains key concepts, design principles, and architectural best practices for running a supergraph in production. The five SAF pillars provide an ideal foundation for a supergraph, ensuring your team can get up and running successfully in less time.&nbsp;</p>



<p class="wp-block-paragraph">The SAF is a short assessment to help you and your organization better understand how to improve your supergraph, grouped into five pillars. These questions are based on best practices we’ve seen at other companies who have deployed a supergraph at enterprise scale.</p>



<p class="wp-block-paragraph">The pillars are:&nbsp;</p>



<ul class="wp-block-list">
<li><strong>Operational Excellence</strong>: How you efficiently operate, maintain, and manage your supergraph. This pillar primarily focuses on the interpersonal skills and processes that are paramount to running a successful supergraph.</li>



<li><strong>Security</strong>: How you secure your organization’s supergraph to prevent misuse.&nbsp;</li>



<li><strong>Reliability</strong>: How you build and maintain a scalable supergraph with high availability in mind.</li>



<li><strong>Performance</strong>: How you can create a performant supergraph and ensure performance is monitored at your organization.</li>



<li><strong>Developer Efficiency</strong>: This discusses ways to increase your developer velocity through process improvements.&nbsp;</li>
</ul>



<p class="wp-block-paragraph">Once completed, you’ll be able to get a report of how your organization is performing, alongside a list of action items and their associated impact and level of effort.</p>



<p class="wp-block-paragraph">The SAF is intended to be run multiple times as your journey progresses, and can be helpful at any stage of the process; whether that be the beginning or midway through implementation, or reviewing an existing implementation to make changes.</p>



<h2 class="wp-block-heading"><a href="#how-do-i-get-started" aria-hidden="true" class="aal_anchor" id="how-do-i-get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How do I get started?</h2>



<p class="wp-block-paragraph">To get started with the SAF, visit <a href="https://saf.apollographql.com">https://saf.apollographql.com</a>, log in with your Apollo Studio organization, and begin your assessment. Once you’ve started, you’ll be shown a list of questions and multiple choices to fill out, such as the questions below.&nbsp;</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1018" height="581" src="https://wp.apollographql.com/wp-content/uploads/2024/01/image-1.png" alt="" class="wp-image-23187" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/image-1.png 1018w, https://wp.apollographql.com/wp-content/uploads/2024/01/image-1-300x171.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/image-1-768x438.png 768w" sizes="auto, (max-width: 1018px) 100vw, 1018px" /></figure>



<p class="wp-block-paragraph">Once finished, you’ll get a report, which can be exported as a PDF, that you can share with members of your organization:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="846" height="716" src="https://wp.apollographql.com/wp-content/uploads/2024/01/image.png" alt="" class="wp-image-23185" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/image.png 846w, https://wp.apollographql.com/wp-content/uploads/2024/01/image-300x254.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/image-768x650.png 768w" sizes="auto, (max-width: 846px) 100vw, 846px" /></figure>



<p class="wp-block-paragraph">The SAF provides free guidelines to immediately improve your organization’s supergraph. Leverage Apollo’s experience, and ensure your work is backed by other companies’ learnings. </p>



<p class="wp-block-paragraph"><br>Visit the <a href="http://saf.apollographql.com">Supergraph Architecture Framework</a> site to get started. If you’re an enterprise customer, please reach out to your Apollo account team to review your results.</p>


The Apollo Supergraph Architecture Framework


<ul class="wp-block-list">
<li><em>GraphQL Leader Adds Executives from Atlassian and Twilio; Aditya Phadke Appointed Chief Customer Officer and Rob Brazier Named VP of Product</em></li>



<li><em>Unwavering GraphQL Adoption and Customer Focus Continue to Drive Major Product Enhancements at Apollo GraphQL&nbsp;</em></li>
</ul>



<p class="wp-block-paragraph">Apollo GraphQL, the supergraph company, today announced it has made two significant additions to its leadership team, welcoming Aditya Phadke as Chief Customer Officer and Rob Brazier as VP of Product. These new appointments build on the successes felt in 2023, as GraphQL saw a rise in usage and success within API platform teams for globally recognized brands like <a href="https://www.youtube.com/watch?v=b78Q7qY4IpI&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=7">Netflix</a>, <a href="https://www.youtube.com/watch?v=sNqcow1psEA&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=24">Wayfair</a>, and <a href="https://www.youtube.com/watch?v=GB-THCI0Mw0&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=36">Intuit</a>.</p>



<p class="wp-block-paragraph">Phadke joins Apollo GraphQL from Atlassian, where he played a crucial role in unlocking customer success and building its pre-sales &amp; post-sales customer motions as it scaled from a startup to a public market leader worth $62B; he will be responsible for building the post-sales group fostering long-term customer relationships and evolving the customer adoption journey. Brazier most recently joins from Grammarly, where he led their developer platform efforts and, prior to that, was the VP of Product at Twilio, where he focused on Twilio Flex, Voice and Video, and other product lines for the company. He brings his background in platforms, developer-facing products and cloud, alongside experience with top-down and bottom-up sales motions, to further advance all aspects of the Apollo GraphQL product portfolio that is seeing significant adoption as the leader of GraphQL products in the market. Additionally, Robbie Petrie joined as Chief Financial Officer earlier in 2023 from Twilio to round out the leadership team.</p>



<figure class="wp-block-pullquote"><blockquote><p>“In 2024, brands are delivering personalized, AI-driven applications across multiple channels to keep up in today&#8217;s market. They’re finding that it’s hard to do this at the pace today’s world requires without a new approach to APIs. Rather than building handwritten experience APIs for each customer interface, enterprises are taking a platform approach with GraphQL so they can gain composability, developer velocity, and efficient integration of diverse cloud resources. And that’s why they’re turning to Apollo GraphQL as the creators of the industry standard GraphQL platform for the future,” said Geoff Schmidt, CEO and co-founder at Apollo GraphQL. “We are expanding our executive team to better service our customers and meet demands for their long-term growth and success. Aditya brings a track record of nurturing customer relationships and Rob brings years of developer platform success and expertise. Both make ideal additions to the Apollo GraphQL leadership team to help developers build the next generation of applications and deliver profound, efficient, and meaningful user experiences.”</p></blockquote></figure>



<p class="wp-block-paragraph">Half of the Fortune 100 embraced GraphQL in 2023 and Apollo GraphQL experienced 40% growth in new customers. Significant customers include <a href="https://www.youtube.com/watch?v=CJRgtuSMV_Q">Ford Credit, Sony Playstation,</a> and <a href="https://www.youtube.com/watch?v=w07Z572q3kg&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=2">Realtor.com</a>, who along with 40 others, talked about how Apollo GraphQL is helping their businesses at the GraphQL Summit in 2023. Apollo GraphQL provides an API integration layer across teams with its supergraph – a GraphQL layer that sits atop existing APIs and enables developers to fetch data from a single endpoint. By building a supergraph with the Apollo GraphOS platform instead of handwriting a sprawl of countless backends-for-frontends or experience APIs, software teams and platform engineers can focus less time on service aggregation or orchestration and more on the features that fuel growth. Apollo GraphQL’s product portfolio and services now include:&nbsp;</p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/blog/federated-subscriptions-in-graphos-real-time-data-at-scale"><strong>Real-time data at scale with federated subscriptions in GraphOS</strong></a> &#8211; GraphOS has subscriptions which allow developers to deliver up-to-the-second updates to application experiences without writing new code, regardless of how many APIs they consume.</li>



<li><strong>Comprehensive platform approach to API Security</strong> &#8211; GraphOS allows platform teams to deliver velocity at scale without compromising security and compliance. GraphOS Authorization now centrally <a href="https://www.apollographql.com/blog/centrally-enforce-policy-as-code-for-graphql-apis">enforces policy as code for GraphQL APIs</a>. Enterprises can also eliminate unauthorized access to services with persisted queries, which provide <a href="https://www.apollographql.com/blog/graphos-persisted-queries-are-generally-available">a registered list of known queries</a> that can access the graph in production.&nbsp;</li>



<li><strong>API conformance and governance </strong>&#8211; As GraphQL gains traction among more and more developers, enterprise teams must provide tools to ensure code quality and consistency at all times. API platform owners can now automate and streamline code review with <a href="https://www.apollographql.com/blog/standardize-graphql-schema-linting-policies-with-graphos">schema linting in GraphOS</a>.</li>



<li><strong>Significant performance gains and capabilities with Apollo Router</strong> &#8211; Apollo Router, a high-performance GraphQL gateway and query planner, has successfully undergone rigorous testing for over a year in highly demanding production environments. The significant investments made in enhancing runtime performance and efficiency reflect Apollo’s commitment to delivering maximum cost savings and ensuring low-latency user experiences.</li>



<li><a href="https://www.apollographql.com/blog/announcing-official-apollo-federation-support-for-net-with-hot-chocolate-and-federation-2"><strong>Official Support for Microsoft .NET</strong></a><strong>:</strong> Apollo GraphQL recently furthered its commitment to the Microsoft ecosystem by announcing formal support for a .NET library, ensuring that over 6 million .NET developers can effectively contribute to a supergraph. Apollo GraphQL now supports 40+ GraphQL frameworks, enabling diverse teams to contribute to their API platforms.</li>
</ul>



<p class="wp-block-paragraph">Apollo GraphQL has received recognition by third-party research firms and saw significant growth in its vibrant community:</p>



<ul class="wp-block-list">
<li>Apollo GraphQL was named a GraphQL API Sample Vendor for 3 consecutive years in the <a href="https://www.gartner.com/en/documents/4564799">Gartner® Hype Cycle™ for APIs, 2023</a>.<sup>1 </sup>Additionally, a Gartner survey found that “API design and API management skills” were rated one of the most highly important software engineering skill, second only to application security skills.<sup>2</sup></li>



<li>Apollo GraphQL’s developer adoption continues to grow with 25M open-source downloads per month and 5T requests served in GraphOS. Additionally, GraphQL is on the rise as an emerging skill with 4K new jobs posted on LinkedIn.com requiring it, 21k users completing courses on Apollo GraphQL’s <a href="https://apollographql.com/tutorials">learning platform Odyssey</a>, and 4k users earning certifications as an Apollo GraphQL Developer.</li>



<li>Apollo GraphQL was named one of <a href="https://www.fastcompany.com/90847317/most-innovative-companies-enterprise-2023">Fast Company’s Most Innovative Companies in Enterprise of 2023</a>.</li>
</ul>



<p class="wp-block-paragraph">To learn more, visit <a href="http://www.apollographql.com">www.ApolloGraphQL.com</a> and the below resources.</p>



<p class="wp-block-paragraph"><strong>Further Resources:</strong></p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/supergraph/">Learn</a> more about supergraphs</li>



<li><a href="https://www.apollographql.com/graphos/">Build </a>a GraphQL API platform today</li>



<li><a href="https://www.apollographql.com/tutorials/certifications/apollo-graph-professional/learning-path/">Become certified </a>as an Apollo GraphQL developer</li>



<li><a href="https://discord.com/invite/yFZJH2QYrK">Join</a> the Apollo GraphQL Community on Discord</li>
</ul>



<p class="wp-block-paragraph"><sup>1 </sup>Gartner, <a href="https://www.gartner.com/en/documents/4564799">Hype Cycle for APIs</a>, 2023, By Mark O&#8217;Neill, John Santoro, July 25, 2023. Gartner and Hype Cycle are registered trademarks of Gartner, Inc. and/or its affiliates in the U.S. and internationally and are used herein with permission. All rights reserved. Note: Apollo GraphQL was referred to as Apollo in the 2022 and 2021 Gartner Hype Cycle for APIs and was recognized for Graph APIs.</p>



<p class="wp-block-paragraph"><sup>2 </sup>Gartner, <a href="https://www.gartner.com/en/documents/4539999">Top Software Engineering Skills and Skill-Building Techniques</a>, By Shivica Mathur, July 18, 2023.</p>



<p class="wp-block-paragraph"><em>Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.</em></p>



<p class="wp-block-paragraph"><strong>About Apollo GraphQL</strong></p>



<p class="wp-block-paragraph"><a href="https://apollographql.com">Apollo GraphQL </a>helps developers help the world by providing a better API platform across teams. Apollo’s open-source software is downloaded 25M times per month and its commercial GraphQL technologies power the most innovative brands today. Teams at Netflix, Snap, and the New York Times ship personalized, omnichannel experiences faster with a supergraph – a self-service GraphQL platform that spans any number of backend services. Serving over 5T requests in 2023, the Apollo GraphOS platform simplifies API development with workflows and infrastructure to build, test, and ship supergraphs at any scale. Based in San Francisco, Apollo is backed by Insight Partners, Andreessen Horowitz, Matrix Partners, and Trinity Ventures. Learn more at: <a href="https://www.apollographql.com">https://www.apollographql.com</a>.</p>


This image displays a headshot of Aditya Phadke and a headshot of Rob Brazier, new executives on the Apollo GraphQL team. Consistent with the visual image, the text displayed says "Welcome to Apollo GraphQL!"

Apollo GraphQL Expands Leadership Team To Meet Demand for GraphQL in the Enterprise


<p class="wp-block-paragraph">Although many in the industry consider GraphQL a replacement for existing API technologies, it is at its most powerful when used as a central orchestration layer between apps and existing services. This layer, implemented as a federated graph (or <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph</a>, for short), acts as a self-service API platform that accelerates development velocity for both frontend and backend teams. However, speed of delivery can’t come at the expense of a strong authorization model that protects personal identifiable information, financial data, and other sensitive information.</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/graphos">Apollo GraphOS</a> provides GraphQL-native workflows to implement access control declaratively across an entire supergraph. Rather than relying only on distributed enforcement or fragile custom gateway logic to secure the graph, teams using GraphOS can enforce policies at the type or field level in their router by decorating schemas with the <code class="" data-line="">@requiresScopes</code>, <code class="" data-line="">@authenticated</code>, and new <code class="" data-line="">@policy</code> directives. These directives provide the freedom to integrate with any authorization system, including policy engines like <a href="https://casbin.org/">Casbin</a> or <a href="https://www.openpolicyagent.org/">Open Policy Agent</a> (OPA). By proactively enforcing policies as code, API platform teams can ensure compliance at all times without sacrificing developer velocity.</p>



<p class="wp-block-paragraph">These directives are generally available for all GraphOS Enterprise customers starting today.</p>



<h2 class="wp-block-heading"><a href="#durable-auditable-authorization-for-supergraphs" aria-hidden="true" class="aal_anchor" id="durable-auditable-authorization-for-supergraphs"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Durable, auditable authorization for supergraphs</h2>



<p class="wp-block-paragraph">Supergraphs expose a unified, versionless GraphQL endpoint for all connected services. While this offers a host of benefits for frontend development, it makes it tricky to centralize authorization with traditional API gateways designed to enforce policies at the endpoint level. These gateways are unaware of the shape of the supergraph, so policies need to be mapped to individual types and fields with custom logic that must be kept in lockstep coordination with any schema changes.</p>



<p class="wp-block-paragraph">An authorization model that is instead integrated directly into a supergraph’s schema is far more durable and can still be centrally audited and enforced in the router. <code class="" data-line="">@authenticated</code> and <code class="" data-line="">@requiresScopes</code>, <a href="https://www.apollographql.com/blog/announcement/backend/build-centralized-graphql-authorization-with-apollo-graphos/">which we launched in preview</a> earlier this year, allow you to define access control policies for types and fields directly in the schema, restricting access to only authenticated requests or requests with certain scopes, respectively. Subgraph developers simply add the directives to the parts of the schema they want to enforce.</p>



<p class="wp-block-paragraph">For example, let’s say you’re building a simple social media app. The app should allow unauthenticated users to view a post&#8217;s title, author, and content, but only authenticated users to see the number of views a post has received, and only certain users with required permissions to view email addresses. The relevant part of your schema may look something like this:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">type Query {
  me: User @authenticated 
  post(id: ID!): Post
}

type User {
  id: ID!
  username: String
  email: String @requiresScopes(scopes: [[&quot;read:email&quot;]])
  posts: [Post!]!
}

type Post {
  id: ID!
  author: User!
  title: String!
  content: String!
  views: Int @authenticated 
}</code></pre>



<p class="wp-block-paragraph">However, many organizations may require more complex policy evaluation and often leverage external tools like OPA or Casbin. For these more complex scenarios, GraphOS now supports a third authorization directive: <code class="" data-line="">@policy</code>.</p>



<h2 class="wp-block-heading"><a href="#offload-policy-definition-and-resolution-with-policy" aria-hidden="true" class="aal_anchor" id="offload-policy-definition-and-resolution-with-policy"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Offload policy definition and resolution with @policy</h2>



<p class="wp-block-paragraph">The new <code class="" data-line="">@policy</code> directive allows you to integrate your predefined policies from policy engines like OPA and Casbin into your supergraph schema and enforce them in your router. For example, let’s say in your example social media app, you only want users to have access to their own personal information and credit card information. Validating this requires more than the scopes of an access token, so you can use <code class="" data-line="">@policy</code> to offload policy resolution for the relevant parts of your schema:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">type Query {
  me: User @authenticated @policy(policies: [[&quot;read_profile&quot;]])
  post(id: ID!): Post
}

type User {
  id: ID!
  username: String
  email: String @requiresScopes(scopes: [[&quot;read:email&quot;]])
  posts: [Post!]!
  credit_card: String @policy(policies: [[&quot;read_credit_card&quot;]])
}

type Post {
  id: ID!
  author: User!
  title: String!
  content: String!
  views: Int @authenticated
}</code></pre>



<p class="wp-block-paragraph">The <code class="" data-line="">@policy</code> directive allows you to use your supergraph as a central enforcement point for any services you’ve connected to your graph without refactoring the authorization model that you’ve already defined.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="800" src="https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram.png" alt="" class="wp-image-23033" srcset="https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram.png 1600w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-1200x600.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p class="wp-block-paragraph"><code class="" data-line="">@policy</code> loosely couples policy enforcement in your GraphOS router and the policy definition in your existing policy engine, giving you the flexibility to evolve how your application resolves policies without altering your GraphQL schema or infrastructure. For example, if your application needs to perform complex authorization validation, such as inspecting specific values in headers, <code class="" data-line="">@policy</code> can be used to validate in a coprocessor or Rhai script.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p class="wp-block-paragraph">Schema-driven authorization with <code class="" data-line="">@authenticated</code>, <code class="" data-line="">@requiresScopes</code>, and <code class="" data-line="">@policy</code> is generally available for all GraphOS Enterprise customers today. To start centralizing authorization enforcement with GraphOS, head over to the <a href="https://www.apollographql.com/docs/router/configuration/authorization">Authorization in the Apollo Router documentation</a>.</p>



<p class="wp-block-paragraph">If you’re new to GraphOS, you can <a href="https://studio.apollographql.com/signup?type=enterprise-trial&amp;_gl=1*1czaoty*_ga*NjU4MjMwOTQ0LjE2MzIxNTUyNDc.*_ga_0BGG5V2W2K*MTcwMTk3NjAwMy4xMDU4LjEuMTcwMTk3NjEwNy4wLjAuMA..">try out GraphOS Enterprise</a> free for 28 days.</p>


Centrally enforce policy as code for GraphQL APIs


<p class="wp-block-paragraph">As <a href="https://www.youtube.com/watch?v=CJRgtuSMV_Q">API platform teams continue to back Apollo Federation</a> as the standard for GraphQL architecture at scale, graphs have rapidly become more sophisticated — expanding across innumerable teams, services, clients, and business units. As sophistication increases, so too does the need for powerful and user-friendly observability, tailored to the needs of graph owners. </p>



<p class="wp-block-paragraph">Today, Apollo is excited to release a new and improved insights dashboard in GraphOS Studio to provide scalable observability tools to API owners operating a supergraph.</p>



<p class="wp-block-paragraph">Within the new insights dashboard you’ll find:</p>



<ul class="wp-block-list">
<li>A consolidated and streamlined experience for accessing operation and field insights</li>



<li>Fast and intuitive search for quickly finding a specific field or operation</li>



<li>Filterable field and operation lists</li>



<li>Significant improvements to list load times for large graphs</li>
</ul>



<p class="wp-block-paragraph">And much more!</p>



<figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex">
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="642" data-id="22859" src="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-1024x642.png" alt="" class="wp-image-22859" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-1024x642.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-300x188.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-768x481.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-1200x752.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new.png 1493w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="642" data-id="22861" src="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-1024x642.png" alt="" class="wp-image-22861" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-1024x642.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-300x188.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-768x481.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-1200x752.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new.png 1493w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="642" data-id="22863" src="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-1024x642.png" alt="" class="wp-image-22863" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-1024x642.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-300x188.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-768x481.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-1200x752.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new.png 1493w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>
</figure>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p class="wp-block-paragraph">The new insights experience is available today for all GraphOS users. To get started, <a href="https://www.apollographql.com/signin">sign into GraphOS Studio</a> and navigate to Insights in the left navigation.</p>



<p class="wp-block-paragraph">Happy querying!</p>


New GraphQL observability and insights in GraphOS Studio


<p class="wp-block-paragraph">Apollo Federation is an open specification for exposing API services as a single GraphQL access layer, known as a supergraph. In a supergraph, you connect and curate your services through smaller, modular graphs called subgraphs. There’s a vibrant ecosystem of community-led frameworks that let you write subgraphs in <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs">every common language</a>, bolstered by official Apollo Federation support libraries for JavaScript and Java. </p>



<p class="wp-block-paragraph">Today, we’re excited to announce a new <a href="https://www.nuget.org/packages/ApolloGraphQL.HotChocolate.Federation">official Apollo Federation support library for Hot Chocolate</a> — a popular .NET GraphQL framework — including full <a href="https://www.apollographql.com/blog/announcement/backend/announcing-federation-2/">Federation 2</a> support for field migrations, entity interfaces, and more flexible type ownership!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="753" src="https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-1024x753.png" alt="" class="wp-image-22807" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-1024x753.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-300x221.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-768x565.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-1536x1130.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-1200x883.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs.png 1728w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#a-growing-ecosystem-of-frameworks" aria-hidden="true" class="aal_anchor" id="a-growing-ecosystem-of-frameworks"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A growing ecosystem of frameworks</h2>



<p class="wp-block-paragraph">With the help of Apollo&#8217;s official Federation support libraries, the community has added Federation support to over <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs">30+ GraphQL frameworks</a> that you can use to build subgraphs today.</p>



<p class="wp-block-paragraph">The Apollo-maintained <code class="" data-line="">subgraph-js</code> library <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs/#javascript--typescript">enables Federation in JavaScript/TypeScript subgraphs</a>:</p>



<ul class="wp-block-list">
<li>Adds Federation support to Apollo Server, Express GraphQL, NestJS, Yoga, and more.</li>



<li>Builds on top of the core <code class="" data-line="">graphql-js</code> library, to enable the entire JavaScript ecosystem.</li>



<li>Apollo helps actively maintain <code class="" data-line="">graphql-js</code> as a key reference implementation across language ecosystems.</li>
</ul>



<p class="wp-block-paragraph">The Apollo-maintained <code class="" data-line="">federation-jvm</code> library <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs/#java--kotlin">powers Federation in Java/Kotlin subgraphs</a>:</p>



<ul class="wp-block-list">
<li>Adds Federation support to Spring GraphQL, Netflix’s DGS Framework, and more.</li>



<li>Builds on top of the core <code class="" data-line="">graphql-java</code> library to enable the whole Java ecosystem.</li>
</ul>



<h3 class="wp-block-heading"><a href="#expanding-official-support-to-net" aria-hidden="true" class="aal_anchor" id="expanding-official-support-to-net"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Expanding official support to .NET</h3>



<p class="wp-block-paragraph">With momentum building in the .NET community, more and more subgraphs are being created using community support for Federation in popular GraphQL packages like GraphQL .NET and Hot Chocolate. To better support the growing number of .NET subgraphs, we&#8217;re excited to announce official Apollo support for .NET with a new v1.0 <a href="https://www.nuget.org/packages/ApolloGraphQL.HotChocolate.Federation">Apollo Federation support library for Hot Chocolate</a>. It’s an open source library that adds Federation support to the main Hot Chocolate GraphQL server and is based on the previous community-led implementation for backwards compatibility. We’ve fixed a few things, overhauled the docs, and added support for Federation 2!</p>



<p class="wp-block-paragraph">Official <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs/#c--net">compatibility testing for C# / .NET</a> shows comprehensive Federation 2 support for Hot Chocolate:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="779" src="https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-1024x779.png" alt="" class="wp-image-22809" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-1024x779.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-300x228.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-768x584.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-1200x913.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/image-15.png 1422w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#quick-start-template-for-hot-chocolate-subgraphs" aria-hidden="true" class="aal_anchor" id="quick-start-template-for-hot-chocolate-subgraphs"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Quick start template for Hot Chocolate subgraphs</h2>



<p class="wp-block-paragraph">The <a href="https://www.apollographql.com/docs/rover/commands/template">Rover CLI</a> now supports .NET and a new <a href="https://github.com/apollographql/subgraph-csharp-hotchocolate-annotation">Hot Chocolate subgraph template</a> that includes:</p>



<ul class="wp-block-list">
<li>Annotation-based Federation for clean idiomatic C# code.</li>



<li>GitHub actions configured for CI/CD using GraphOS schema checks and publishing.</li>



<li>Railway one click deploy template.</li>
</ul>



<p class="wp-block-paragraph">To bootstrap a new Hot Chocolate subgraph project, run:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">rover template use --template subgraph-csharp-hotchocolate-annotation</code></pre>



<p class="wp-block-paragraph">Federation 2 is configured into your Hot Chocolate subgraph in <code class="" data-line="">Program.cs</code></p>



<pre class="wp-block-prismatic-blocks"><code class="language-csharp" data-line="">using ApolloGraphQL.HotChocolate.Federation;

var builder = WebApplication.CreateBuilder(args);

builder.Services
    .AddGraphQLServer()
    .AddApolloFederationV2() 
    // register your types and services
    ;

var app = builder.Build();
app.MapGraphQL();
app.Run();</code></pre>



<p class="wp-block-paragraph">Root query fields for your subgraph are defined in <code class="" data-line="">Query.cs</code>, which federate into your supergraph for apps to use:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-csharp" data-line="">public class Query
{
    public Thing? Thing([ID] string id, Data repository)
        =&gt; repository.Things.FirstOrDefault(t =&gt; t.Id.Equals(id));
}</code></pre>



<p class="wp-block-paragraph">Entity classes like <code class="" data-line="">Thing.cs</code> define a <code class="" data-line="">Key</code> , <code class="" data-line="">ID</code>, and <code class="" data-line="">Reference Resolver</code> to enable joining data across subgraphs:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-csharp" data-line="">[Key(&quot;id&quot;)]
public class Thing
{
    [ID]
    public string Id { get; }

    public string? Name { get; }

    [ReferenceResolver]
    public static Thing? GetThingById(
        string id,
        Data repository)
        =&gt; repository.Things.FirstOrDefault(t =&gt; t.Id.Equals(id));
}</code></pre>



<h2 class="wp-block-heading"><a href="#upgrade-an-existing-hot-chocolate-subgraph-to-federation-2" aria-hidden="true" class="aal_anchor" id="upgrade-an-existing-hot-chocolate-subgraph-to-federation-2"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Upgrade an existing Hot Chocolate subgraph to Federation 2</h2>



<p class="wp-block-paragraph">Update your <code class="" data-line="">.csproj</code> file:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-markup" data-line="">  &lt;ItemGroup&gt;
    &lt;PackageReference Include=&quot;HotChocolate.AspNetCore&quot; Version=&quot;13.5.1&quot; /&gt;
    &lt;PackageReference Include=&quot;ApolloGraphQL.HotChocolate.Federation&quot; Version=&quot;1.0.0&quot; /&gt;
  &lt;/ItemGroup&gt;</code></pre>



<p class="wp-block-paragraph">Use the new official Apollo Federation support library and configure your subgraph to use Federation 2:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-csharp" data-line="">using ApolloGraphQL.HotChocolate.Federation;

var builder = WebApplication.CreateBuilder(args);

builder.Services
    .AddGraphQLServer()
    .AddApolloFederationV2() 
    // ...
    ;

var app = builder.Build();
app.MapGraphQL();
app.Run();</code></pre>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What&#8217;s next?</h2>



<p class="wp-block-paragraph">Starting today, Apollo will continue to maintain official Federation subgraph support for Hot Chocolate. You can expect ongoing improvements and fixes, as well as full support for the latest Apollo Federation spec changes.</p>



<p class="wp-block-paragraph">We also plan to work with the community to add <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs/#c--net">Federation 2 support for other popular .NET packages like GraphQL .NET</a>.</p>



<h2 class="wp-block-heading"><a href="#learn-more" aria-hidden="true" class="aal_anchor" id="learn-more"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Learn more</h2>



<ul class="wp-block-list">
<li>Checkout the <a href="https://www.nuget.org/packages/ApolloGraphQL.HotChocolate.Federation">updated docs</a> to learn more!</li>



<li>If you have a specific question about the library or code, please start a discussion in the <a href="https://community.apollographql.com/">Apollo community forums</a> or start a conversation on our <a href="https://discord.gg/graphos">Discord server</a>.</li>



<li>If you have improvements you’d like to see please let us know by <a href="https://github.com/apollographql/federation-hotchocolate/issues/new">opening a GitHub issue</a>!</li>
</ul>


Announcing official Apollo Federation support for .NET with Hot Chocolate and Federation 2!


<p class="wp-block-paragraph">Unbounded operations are generally considered a benefit of GraphQL, giving client developers unprecedented flexibility when experimenting and developing apps. However, while this flexibility is greatly appreciated in development environments, allowing it in production adds unnecessary surface area to GraphQL endpoints which generally serve only first-party clients.</p>



<p class="wp-block-paragraph">Instead, your production graph should adhere to the principle of least privilege. If your first-party apps only require <code class="" data-line="">QueryA</code>, <code class="" data-line="">QueryB</code>, and <code class="" data-line="">QueryC</code> to operate properly, your graph should only allow <code class="" data-line="">QueryA</code>, <code class="" data-line="">QueryB</code>, and <code class="" data-line="">QueryC</code>. Any tolerance for ad hoc operations creates unnecessary exposure.</p>



<p class="wp-block-paragraph">If you have a GraphQL monolith serving just a few clients, building a custom safelisting system to enforce this behavior is relatively straightforward. However, as the graph scales to serve dozens of clients and takes on a supergraph architecture, the complexity of maintaining such a system becomes prohibitive.</p>



<p class="wp-block-paragraph">Apollo now offers a scalable solution for mitigating the risks of unbounded operations in supergraphs: <strong>GraphOS Persisted Queries</strong>. Persisted queries enable your platform team to limit the attack surface area of your supergraph by centrally registering trusted GraphQL operations and safelisting them in any instance of the Apollo Router.</p>



<h2 class="wp-block-heading"><a href="#a-graphql-platform-approach-to-api-security" aria-hidden="true" class="aal_anchor" id="a-graphql-platform-approach-to-api-security"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A GraphQL platform approach to API security</h2>



<p class="wp-block-paragraph">A supergraph is a self-service API platform designed to empower frontend and backend teams to consume and build services independently, but equally important is its ability to systematically centralize access control policy enforcement. By choosing to leverage the supergraph for policy enforcement, API platform teams can protect any number of backend services with layers of access control without heavy-handed manual review.</p>



<p class="wp-block-paragraph">GraphOS Persisted Queries is one such layer that centralizes policies defining which <em>operations</em> should be allowed access to the supergraph. Rather than relying on platform teams to create and maintain this policy manually, GraphOS provides a workflow for <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries#implementation-steps">discovering and registering known operations</a> that can be integrated directly into client CI/CD pipelines.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="444" src="https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1024x444.png" alt="" class="wp-image-22725" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1024x444.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-300x130.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-768x333.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1536x667.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-2048x889.png 2048w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1200x521.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1980x859.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#flexibility-in-development-discretion-in-production" aria-hidden="true" class="aal_anchor" id="flexibility-in-development-discretion-in-production"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flexibility in development, discretion in production</h2>



<p class="wp-block-paragraph">In most cases, your production API only needs to execute a finite number of GraphQL operations from a set pool of stable, first-party applications. In this environment, safelisting limits the exposure of your graph by blocking any unknown operations.&nbsp;</p>



<p class="wp-block-paragraph">However, in development environments, it’s important to allow developers the flexibility to experiment with unbounded operations. To do so, you can configure your router to simply <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries#security-levels">log any unregistered operations</a> rather than block them. This is also useful when you’re getting started with Persisted Queries, and you haven’t yet registered all known operations from existing clients. However, it can be useful to pair this mode with some <a href="https://www.apollographql.com/docs/router/configuration/operation-limits/">operation limits</a> that prevent any intentional or unintentional misuse of the graph.</p>



<h2 class="wp-block-heading"><a href="#expanding-security-options-for-your-graphql-platform" aria-hidden="true" class="aal_anchor" id="expanding-security-options-for-your-graphql-platform"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Expanding security options for your GraphQL platform</h2>



<p class="wp-block-paragraph">GraphOS Persisted Queries are one of the many ways you can <a href="https://www.apollographql.com/blog/graphql/security/enforcing-graphql-security-best-practices-with-graphos/">use GraphOS to improve the security posture of your GraphQL platform</a>. Persisted Queries are generally available for GraphOS Enterprise today and coming soon for GraphOS Cloud. To get started, head over to the <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries/">GraphOS documentation</a>.</p>



<p class="wp-block-paragraph">For platform teams looking to further leverage their supergraph to improve API security, stay tuned for additional GraphOS security features and look out for more GraphQL security content at <a href="https://summit.graphql.com/event/c51538f6-4b76-44e3-871e-54180c77cad8/summary">GraphQL Summit</a>.</p>


GraphOS Persisted Queries are generally available


<p class="wp-block-paragraph"><em>An Integrated Blueprint from Kong and Apollo</em> </p>



<p class="wp-block-paragraph">Not a day goes by where the tech press fails to mention industry advancements in AI, connected devices, or personalization. Consumers can now use AI to create anything from digital illustrations to vacation ideas. At the core of these initiatives is one tried-and-true constant – APIs. If an organization cannot safely and securely deliver service updates across any number of interfaces, these modernization initiatives will fail to gain traction.</p>



<p class="wp-block-paragraph">APIs are more heterogeneous than ever though. An enterprise considering incorporating gRPC APIs may still have legacy SOAP APIs in the mix. A new feature could require data from 20 different services – all of which are managed by different teams at different cadences using varying protocols. If a Product Manager wants to incorporate data from legacy APIs as well as new options like ChatGPT, how can API platform teams provide a standardized means to iterate, secure access, and scale all of them? And then how do they ensure that client teams can get the data they need in a self-service fashion?</p>



<p class="wp-block-paragraph">Kong and Apollo are industry leaders in the API space. Our customers come to us with these very real problems everyday. The API ecosystem often positions REST and GraphQL as competing technologies, but they are highly complementary and are instrumental in developing a modern API platform that accomplishes the goals above. Through a balanced exploration of Kong&#8217;s perspective on flexible, heterogeneous API ecosystems and Apollo&#8217;s expertise in GraphQL, we’ve captured the vendor-neutral best practices that combine API management and GraphQL into a unified reference architecture for building and operating a modern API platform.</p>



<p class="wp-block-paragraph">Learn more with our joint <a href="https://new.apollographql.com/leveraging-graphql-for-next-generation-api-platforms.pdf">paper and reference architecture</a> that shows how to:</p>



<ol class="wp-block-list">
<li>Leverage GraphQL and a supergraph as a new layer in the stack atop existing microservices and API management.</li>



<li>Streamline the developer experience in building and consuming APIs.</li>



<li>Ensure secure, efficient runtime connectivity and implement robust governance mechanisms with API management best practices.</li>
</ol>



<p class="wp-block-paragraph"> </p>


Leveraging GraphQL for Next-Generation API Platforms


<p class="wp-block-paragraph"><em>December 2023 update: GraphOS authorization enforcement is <strong>now generally available</strong>, including the <code class="" data-line="">@requiresScopes</code>, <code class="" data-line="">@authenticated</code>, and <strong>new</strong> <code class="" data-line="">@policy</code> directives. <a href="https://www.apollographql.com/blog/announcement/backend/centrally-enforce-policy-as-code-for-graphql-apis/">Read the GA announcement</a>.</em></p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph">Implementing a durable access control system for APIs is critical to prevent data breaches, monetary losses, and potential denial of services. GraphQL presents API owners with a unique challenge in this regard because it is designed for maximum flexibility.</p>



<p class="wp-block-paragraph">In general, there are two choices for enforcing access control for GraphQL APIs, neither of which scale particularly well. You can write custom logic to centralize enforcement — which must be kept in lock-step coordination with changes to the graph — or you can distribute enforcement across multiple GraphQL endpoints — eliminating much of the flexibility GraphQL provides to app developers.</p>



<p class="wp-block-paragraph">Apollo GraphOS and <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph architecture</a> are eliminating this trade-off. Starting today, graph owners can enforce centralized authorization across any number of connected services in the graph.</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/docs/router/configuration/authorization/">Authz enforcement</a> is available<strong> in preview today</strong> for all customers on the GraphOS Enterprise plan running self-hosted instances of Apollo Router.</p>



<h2 class="wp-block-heading"><a href="#durable-graph-native-authz" aria-hidden="true" class="aal_anchor" id="durable-graph-native-authz"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Durable, graph-native authz</h2>



<p class="wp-block-paragraph">When you operate a supergraph with GraphOS, you can now use the <code class="" data-line="">@requiresScopes</code> and <code class="" data-line="">@authenticated</code> <a href="https://www.apollographql.com/docs/router/configuration/authorization/#authorization-directives">directives</a> to define the authorization model for individual types and fields in each of your services declaratively. Rather than relying on custom logic or per-service access control, GraphOS uses these directives to compose a single federated authorization model. It then enforces that model in your <a href="https://www.apollographql.com/docs/router/">graph router</a> at the edge of the API stack to optimize query execution and improve defense-in-depth.</p>



<h3 class="wp-block-heading"><a href="#limit-access-to-certain-scopes" aria-hidden="true" class="aal_anchor" id="limit-access-to-certain-scopes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Limit access to certain scopes</h3>



<p class="wp-block-paragraph">The <strong><code class="" data-line="">@requiresScopes</code> </strong>directive is useful in cases where certain data or experiences should be available to a subset of users, but not all. It allows you to define granular access control by specifying an array of scopes that are required to access the type or field. If GraphOS receives a request that is missing the required scopes for certain fields, it will automatically filter out those fields before executing the operation. [<a href="https://www.apollographql.com/docs/router/configuration/authorization/#example-requiresscopes-use-case">Example use case</a>]&nbsp;</p>



<h3 class="wp-block-heading"><a href="#require-authentication" aria-hidden="true" class="aal_anchor" id="require-authentication"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Require authentication</h3>



<p class="wp-block-paragraph">The <strong><code class="" data-line="">@authenticated</code></strong> directive is useful when you need to limit access to unauthenticated users (or when you want to cut off unauthenticated access entirely). It provides binary access control, limiting marked types and fields to authenticated requests. When GraphOS receives an unauthenticated request, it filters out all fields marked with <code class="" data-line="">@authenticated</code> before execution. [<a href="https://www.apollographql.com/docs/router/configuration/authorization/#example-authenticated-use-case">Example use case</a>]</p>



<h2 class="wp-block-heading"><a href="#optimize-query-execution" aria-hidden="true" class="aal_anchor" id="optimize-query-execution"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Optimize query execution</h2>



<p class="wp-block-paragraph">The best way to combat DoS attacks is to enforce access control well before traffic ever reaches your mission-critical services. With an access control model defined in your schema, the GraphOS runtime plane acts as a central control point that does just that. In the simplest case, GraphOS will immediately terminate requests lacking the proper authorization to access any fields, preventing them from ever reaching your services. However, GraphOS can also optimize the execution of partially authenticated requests and deduplicate requests to your services.</p>



<h3 class="wp-block-heading"><a href="#eliminate-unauthorized-subqueries" aria-hidden="true" class="aal_anchor" id="eliminate-unauthorized-subqueries"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Eliminate unauthorized subqueries</h3>



<p class="wp-block-paragraph">Let’s say we’re building the profile page for a social media app that shows profile information like a name and profile image to all users, but only shows the posts associated with the profile to authenticated users. We have one service in our federated graph that handles user information — the Users API — and another that handles post information — the Posts API. We can restrict access to data resolved by the Posts API to authenticated users with <code class="" data-line="">@authenticated</code>.</p>



<p class="wp-block-paragraph">Now, when GraphOS receives the query used to populate the profile page, it will first check if the user has the proper claims to access fields resolved by the Posts API. Here’s the fun part – if the request doesn’t have the proper claims, GraphOS will eliminate the entire subquery to the Posts API, preventing that service from ever seeing the traffic.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="512" src="https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-1024x512.png" alt="" class="wp-image-22526" srcset="https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-1200x600.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#deduplicate-subqueries" aria-hidden="true" class="aal_anchor" id="deduplicate-subqueries"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deduplicate subqueries</h3>



<p class="wp-block-paragraph">GraphOS also reduces load on your services by accounting for authorization when <a href="https://www.apollographql.com/docs/router/configuration/traffic-shaping/#query-deduplication"><em>deduplicating</em> simultaneous subqueries</a>. If your router is simultaneously processing two or more requests that after authz enforcement require identical subqueries, GraphOS will fulfill both requests using a single subquery.</p>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p class="wp-block-paragraph">Implementing centralized GraphQL authorization with GraphOS eliminates the need for maintaining custom gateway code or bespoke authorization models for every one of your services. On top of that, it optimizes the performance of your services by eliminating unnecessary load from unauthorized requests.</p>



<p class="wp-block-paragraph">Starting today, all customers on the GraphOS Enterprise plan can start using <code class="" data-line="">@requiresScopes</code> and <code class="" data-line="">@authenticated</code> to enforce declarative, graph-native authorization in the GraphOS runtime plane. To get started, head over to the <a href="https://www.apollographql.com/docs/router/configuration/authorization/">GraphOS documentation</a>.</p>



<p class="wp-block-paragraph">If you aren&#8217;t a GraphOS Enterprise customer and you want to start building authz enforcement with GraphOS, you can <a href="https://studio.apollographql.com/signup?type=enterprise-trial" data-type="link" data-id="https://studio.apollographql.com/signup?type=enterprise-trial&amp;_gl=1*7g1bty*_ga*NjU4MjMwOTQ0LjE2MzIxNTUyNDc.*_ga_0BGG5V2W2K*MTY5MzkyOTcyOC45NjcuMS4xNjkzOTM1MTEzLjAuMC4w">try it out for free</a> for 28 days.</p>


Build centralized GraphQL authorization with Apollo GraphOS


<p class="wp-block-paragraph">When you’re building a federated GraphQL API that spans multiple backend teams and services, it can be difficult to ensure that the schema for your graph stays consistent from subgraph to subgraph. For example, how do you ensure that a type defined as an entity in one subgraph is also defined as an entity in all other subgraphs?</p>



<p class="wp-block-paragraph">Today, we’re making it easier for API platform teams to enforce schema consistency across multiple subgraphs by adding composition rules to the <a href="https://www.apollographql.com/blog/announcement/platform/standardize-graphql-schema-linting-policies-with-graphos/">Apollo GraphOS linter</a>. Now, you can configure the GraphOS checks workflow to flag inconsistent elements across subgraphs, overridden or unused elements, and issues with Federation directives.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="658" src="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-1024x658.png" alt="" class="wp-image-22422" srcset="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-1024x658.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-300x193.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-768x493.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-1536x987.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-1200x771.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM.png 1650w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#configure-composition-rule-severity" aria-hidden="true" class="aal_anchor" id="configure-composition-rule-severity"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Configure composition rule severity</h2>



<p class="wp-block-paragraph">Like other linter rules in GraphOS, you can enable or disable each composition rule independently and set its severity to <code class="" data-line="">Warn</code> or <code class="" data-line="">Error</code>. Violations of rules set to <code class="" data-line="">Error</code> will cause the checks workflow to fail outright (useful for changes pushed to production graphs) while <code class="" data-line="">Warn</code> violations will allow the checks workflow to pass but output a warning.</p>



<figure class="wp-block-image size-large is-style-default"><img loading="lazy" decoding="async" width="1024" height="543" src="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-1024x543.png" alt="" class="wp-image-22425" srcset="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-1024x543.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-300x159.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-768x407.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-1200x636.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM.png 1400w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#integrate-with-development-workflows" aria-hidden="true" class="aal_anchor" id="integrate-with-development-workflows"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Integrate with development workflows</h2>



<p class="wp-block-paragraph">Composition rules are enforced by GraphOS linter checks, which you can integrate into your existing delivery processes:</p>



<ol class="wp-block-list">
<li><strong>CI/CD pipelines</strong> — Centrally enforce composition rules in your existing CI/CD pipelines by <a href="https://www.apollographql.com/docs/rover/ci-cd/">installing Rover in your CI/CD environment</a>.&nbsp;</li>



<li><strong>The GraphOS registry</strong> — Enforce composition rules for all schema changes pushed to the GraphOS registry — the final checkpoint before your schema is used in production.</li>
</ol>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p class="wp-block-paragraph">Composition rules for the GraphOS schema linter are available starting today for all GraphOS users. To get started, head to the Checks Configuration page for your graph in GraphOS Studio or <a href="https://www.apollographql.com/docs/graphos/delivery/linter-rules/#composition-rules">read the docs</a> for a step-by-step setup guide.</p>


Enforce schema consistency across federated graphs with GraphOS


<p class="wp-block-paragraph">Last year, we announced the End-of-Life for Apollo Server 3, originally scheduled for October 22, 2023. Apollo Server has widespread adoption, and we&#8217;ve heard feedback that some in the community would appreciate more time for the migration process. In light of this, <strong>we&#8217;re extending the End-of-Life date for Apollo Server 3 to October 22, 2024</strong>. Apollo will continue to provide security patches and fixes for major regressions until October 2024, after which Apollo Server 3 will no longer be maintained by Apollo. </p>



<p class="wp-block-paragraph">To learn how to migrate to Apollo Server 4, see the <a href="https://www.apollographql.com/docs/apollo-server/migration/">migration guide</a>. Additionally, you can find more information about End-of-Life stages in the <a href="https://www.apollographql.com/docs/resources/product-launch-stages/#end-of-life">Apollo Launch Stages definitions</a>.</p>



<p class="wp-block-paragraph">At Apollo, our priorities have always been driven by the community and businesses that rely on us. We value your input and encourage you to keep sharing it with us. If you haven&#8217;t already, join the official <a href="https://discord.gg/graphos">Apollo GraphQL Discord</a> to keep the conversation going.</p>


Apollo Server 3 end-of-life extension


<p class="wp-block-paragraph">GraphQL is designed to offer a more flexible, self-serve developer experience, but its open-ended approach often raises questions about its security model. The most common objection is that GraphQL APIs allow unbounded operations — a trait that can degrade performance or result in denial-of-service if too many complex queries are sent to the endpoint. A <a href="https://www.apollographql.com/blog/the-supergraph-a-new-way-to-think-about-graphql/">supergraph architecture</a> can compound this risk since it generally composes many services across an organization, significantly increasing the potential complexity of executing queries.</p>



<p class="wp-block-paragraph">In order to deliver performance and security at all times, API platform teams should have the means to eliminate exposure to the potential performance impacts of excessively complex queries. In the spirit of a true platform, teams should be able to <strong>proactively define safelisted queries upfront in a way that encourages iteration in development but provides mission-critical security in production</strong><em>.&nbsp;</em></p>



<h2 class="wp-block-heading"><a href="#proactively-safelist-with-graphos" aria-hidden="true" class="aal_anchor" id="proactively-safelist-with-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Proactively safelist with GraphOS</h2>



<p class="wp-block-paragraph">Today, Apollo is introducing a new approach for preventing unbounded access to GraphQL APIs: <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries"><strong>GraphOS persisted query safelisting</strong></a>. With persisted query safelisting, API teams can prevent service degradation from complex queries by centrally safelisting known operations in <a href="https://www.apollographql.com/docs/router/">Apollo Router</a> — Apollo’s blazing-fast GraphQL gateway and query planner.&nbsp;</p>



<p class="wp-block-paragraph">GraphOS offers varying levels of safelist restrictions that enable incremental adoption and flexibility in development environments without sacrificing security in production. The <em>audit-only</em> configuration gives teams a frictionless way to get started with safelisting by logging unknown operation shapes without terminating the request. Meanwhile, production environments demanding maximum security and performance can use an <em>ID-only</em> configuration to accept only requests with a known hash, terminating all others.</p>



<p class="wp-block-paragraph">Persisted query safelisting is available in preview today for Apollo customers on the GraphOS Enterprise plan – read the docs and try it out! We would love to hear your thoughts and learn how we can make safelisting work better for your use case. Over the coming weeks, we’ll be using your feedback to polish up the user experience ahead of the GA release.&nbsp; <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries">Head to the docs</a> to get started or read on to learn more about how you can configure safelisting for your development lifecycle.</p>



<h2 class="wp-block-heading"><a href="#how-safelisting-works-in-graphos" aria-hidden="true" class="aal_anchor" id="how-safelisting-works-in-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How safelisting works in GraphOS</h2>



<p class="wp-block-paragraph">Nearly all APIs are designed to serve a finite set of first-party client apps, and, by their very nature, GraphQL services are aware of the shape of data requested by those applications. In this closed development ecosystem, we have the tools to implement a GraphQL gateway that significantly limits surface area by <em>only</em> allowing known operations from our first-party apps.&nbsp;</p>



<h3 class="wp-block-heading"><a href="#register-operations-from-first-party-apps" aria-hidden="true" class="aal_anchor" id="register-operations-from-first-party-apps"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Register operations from first-party apps</h3>



<p class="wp-block-paragraph">GraphOS gives client teams a self-serve experience for registering queries from their first-party apps to a central graph registry. Simply generate a persisted query manifest file for any app using Apollo Client (web, iOS, or Kotlin) and register it to a graph in GraphOS using the Rover CLI. The persisted query manifest includes a unique <em>persisted query ID</em> hash for each operation which can be used in place of the query string to improve app performance once persisted queries are configured in the router.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="572" src="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1024x572.png" alt="" class="wp-image-22331" srcset="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1024x572.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-300x168.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-768x429.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1536x858.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-2048x1144.png 2048w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1200x670.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1980x1106.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#configure-safelisting-incrementally" aria-hidden="true" class="aal_anchor" id="configure-safelisting-incrementally"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Configure safelisting incrementally</h3>



<p class="wp-block-paragraph">After client teams register known queries to a graph in GraphOS, API platform owners can enable persisted queries for connected instances of Apollo Router. Once enabled, the router pulls the list of persisted query strings and IDs from the graph registry and stores them in memory to be used for safelisting and ID-only operations.&nbsp;</p>



<p class="wp-block-paragraph">Enforcing severe safelisting rules in the router is as simple as updating a few lines of router config, but to prevent any breaking changes in your apps, it is best to start with a flexible configuration and incrementally move to a more restrictive approach in production. In the remainder of this post, we’ll walk through the various ways you can adapt safelisting to your use case.</p>



<h2 class="wp-block-heading"><a href="#flexible-safelisting-for-every-stage-of-development" aria-hidden="true" class="aal_anchor" id="flexible-safelisting-for-every-stage-of-development"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flexible safelisting for every stage of development</h2>



<p class="wp-block-paragraph">Generally, you should configure your router to be more restrictive in production environments and less restrictive in development environments, but your particular use case and GraphQL client may limit how restrictive your router can be. GraphOS offers the ability to enforce more severe or less severe safelisting restrictions depending on your use case.&nbsp;</p>



<h3 class="wp-block-heading"><a href="#audit-only-for-agile-development-and-adoption" aria-hidden="true" class="aal_anchor" id="audit-only-for-agile-development-and-adoption"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Audit-only for agile development and adoption</h3>



<p class="wp-block-paragraph">In development environments or when you’re just getting started with safelisting, it is generally best to simply log any unregistered operations without terminating them. The audit-only configuration provides this flexibility, helping you determine if any operations are missing from the registry in GraphOS. Here’s how you can configure your router for audit-only:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml" data-line=""># router.yaml

preview_persisted_queries:
  enabled: true
  log_unknown: true</code></pre>



<h3 class="wp-block-heading"><a href="#lock-down-and-optimize-production-endpoints" aria-hidden="true" class="aal_anchor" id="lock-down-and-optimize-production-endpoints"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Lock down and optimize production endpoints</h3>



<p class="wp-block-paragraph">When you’re confident that all supported operations are registered in GraphOS, you can enable more restrictive safelisting in production environments.</p>



<h4 class="wp-block-heading"><a href="#maximize-security-and-performance-with-id-only-operations" aria-hidden="true" class="aal_anchor" id="maximize-security-and-performance-with-id-only-operations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Maximize security and performance with ID-only operations</h4>



<p class="wp-block-paragraph">ID-only operations are the most restrictive, but they also are the most efficient since the router can avoid processing any complex, freeform query strings (similar to <a href="https://www.apollographql.com/docs/router/configuration/distributed-caching/"><em>automatic</em> persisted query caching</a>). In this mode, <strong>clients are required to send requests to the router with <em>only</em> a unique persisted query ID</strong> which the router can use to identify the requested operation. The router will reject any requests with an invalid ID or a freeform query string.&nbsp;</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml" data-line=""># router.yaml

preview_persisted_queries:
  enabled: true
  safelist:
    enabled: true
    require_id: true</code></pre>



<p class="wp-block-paragraph">ID-only operations are supported by all Apollo Clients — web, iOS, and Kotlin — but support in other libraries may vary.&nbsp;</p>



<h4 class="wp-block-heading"><a href="#allow-any-known-shapes-for-more-flexible-enforcement" aria-hidden="true" class="aal_anchor" id="allow-any-known-shapes-for-more-flexible-enforcement"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Allow any known shapes for more flexible enforcement</h4>



<p class="wp-block-paragraph">In the case that your GraphQL client does not support ID-only operations, you can use less stringent shape-based safelisting. Shape-based safelisting is also useful in cases where ID-only operations are excessively restrictive. For example, it may be useful for pre-production apps to query a staging graph using the full query string for easier debugging. In these cases, you can use the default option for safelisting which will accept operations without a persisted query ID as long as they match the shape of a registered operation:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line=""># router.yaml

preview_persisted_queries:
  enabled: true
  safelist:
    enabled: true</code></pre>



<h2 class="wp-block-heading"><a href="#defense-in-depth" aria-hidden="true" class="aal_anchor" id="defense-in-depth"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Defense-in-depth</h2>



<p class="wp-block-paragraph">Safelisting known operations in your router contributes yet another layer to your defense-in-depth strategy for your API platform. However, like any security measure, is most effective when layered with additional checks.</p>



<h3 class="wp-block-heading"><a href="#govern-operation-shape" aria-hidden="true" class="aal_anchor" id="govern-operation-shape"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Govern operation shape</h3>



<p class="wp-block-paragraph">One of the best checks to combine with safelisting is a general <a href="https://www.apollographql.com/docs/router/configuration/operation-limits/">limit on operation complexity</a>. Setting a maximum height, depth, number of aliases, and number of root fields for any given operation creates a safety net to prevent accidentally or intentionally malformed queries from impacting the performance of your API.&nbsp;</p>



<p class="wp-block-paragraph">These limits are table-stakes for public endpoints where safelisting isn’t an option but are also helpful in-house to prevent excessively complex operations from accidentally being safelisted.</p>



<h3 class="wp-block-heading"><a href="#limit-scope-of-access" aria-hidden="true" class="aal_anchor" id="limit-scope-of-access"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Limit scope of access</h3>



<p class="wp-block-paragraph">Safelisting restricts incoming requests to preregistered operations, but for compliance purposes, you may also need to limit the scope of data available in a particular endpoint. For example, if you have a supergraph that contains PCI, you may need a separate endpoint for client apps that removes that information.</p>



<p class="wp-block-paragraph">With GraphOS you can use <a href="https://www.apollographql.com/docs/graphos/delivery/contracts/">contracts</a> to systematically create filtered endpoints that remove any sensitive or unnecessary information. For each of your filtered endpoints, you can create a tailored query safelist specific to its clients.</p>



<h2 class="wp-block-heading"><a href="#get-started-with-safelisting" aria-hidden="true" class="aal_anchor" id="get-started-with-safelisting"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started with safelisting</h2>



<p class="wp-block-paragraph">Regardless of where you are in your journey with GraphQL, persisted query safelisting is a great way to reduce your exposure to malformed or malicious requests. Customers on the Apollo GraphOS Enterprise plan or <a href="https://studio.apollographql.com/signup?type=enterprise-trial&amp;referrer=blog">Enterprise Trial</a> can start using safelisting today. To get started, head over to the <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries">GraphOS docs</a>!</p>


Secure your GraphQL platform by safelisting known queries

Announcing Apollo Client 3.8 With React Suspense Integration

Wait for it… Announcing Apollo Client 3.8 with React Suspense Integration

Federated subscriptions in GraphOS: real-time data at scale


<p class="wp-block-paragraph">We’re happy to introduce an <a href="https://github.com/apollographql/apollo-kotlin">Apollo Kotlin</a> plugin for Android Studio and IntelliJ IDEA, to help you work with the library and improve your productivity.</p>



<p class="wp-block-paragraph">This preview release can be tried out today.</p>



<h2 class="wp-block-heading"><a href="#features" aria-hidden="true" class="aal_anchor" id="features"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Features</h2>



<h3 class="wp-block-heading"><a href="#on-the-fly-code-generation" aria-hidden="true" class="aal_anchor" id="on-the-fly-code-generation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>On-the-fly code generation</h3>



<p class="wp-block-paragraph">Apollo Kotlin is a strongly-typed client library that generates models from your GraphQL queries. This works thanks to a Gradle plugin that triggers the code generation at build time. Normally, after touching a graphql file, to be able to use the up-to-date generated models in your Kotlin code, you would need to manually run the codegen Gradle task.</p>



<p class="wp-block-paragraph">With the IDE plugin, this is done automatically: the codegen is run in the background whenever you touch your GraphQL queries, so you can use the models immediately.</p>



<figure class="wp-block-video"><video height="1762" style="aspect-ratio: 2200 / 1762;" width="2200" controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/00-on-the-fly-codegen.mov"></video><figcaption class="wp-element-caption">On-the-fly code generation</figcaption></figure>



<h3 class="wp-block-heading"><a href="#migration-helpers" aria-hidden="true" class="aal_anchor" id="migration-helpers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Migration helpers</h3>



<p class="wp-block-paragraph">Apollo Kotlin 3 was a major version that introduced quite a few changes compared to version 2. While some of <a href="https://www.apollographql.com/docs/kotlin/migration/3.0/">these changes</a> require manual tweaks to the code, a lot of these can be automated. Which is what the “Migrate to Apollo Kotlin 3” action does. If you are still on version 2, now is a good time to migrate!</p>



<figure class="wp-block-video"><video height="1080" style="aspect-ratio: 1920 / 1080;" width="1920" controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/01-migration-apollo2-to-3.mp4"></video><figcaption class="wp-element-caption">Migrate to Apollo Kotlin 3</figcaption></figure>



<p class="wp-block-paragraph">If you are using Apollo Kotlin 3 with <a href="https://www.apollographql.com/docs/kotlin/migration/3.0/#codegen">the <code class="" data-line="">compat</code> codegen</a>, which was meant to ease the migration from version 2 (and will be discontinued in the upcoming version 4 release), the plugin can also help with this: “Migrate to <code class="" data-line="">operationBased</code> Codegen”.</p>



<figure class="wp-block-video"><video height="2234" style="aspect-ratio: 3456 / 2234;" width="3456" controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/02-migration-compat-to-operationbased.mov"></video><figcaption class="wp-element-caption">Migrate to operationBased codegen</figcaption></figure>



<h3 class="wp-block-heading"><a href="#navigation" aria-hidden="true" class="aal_anchor" id="navigation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigation</h3>



<p class="wp-block-paragraph">When editing Kotlin code that references GraphQL queries, it is often useful to go to their definition &#8211; for instance, if you need to add a field to the selection. The natural way to do that in Android Studio is to <code class="" data-line="">Cmd/Ctrl + click</code> (or <code class="" data-line="">Cmd/Ctrl + b</code> on the keyboard) on the symbol. However without any special knowledge of Apollo Kotlin or GraphQL, this would go to the generated code, which is not as useful. Not anymore! The plugin adds target to go to the GraphQL definition:</p>



<figure class="wp-block-video"><video height="1762" style="aspect-ratio: 2098 / 1762;" width="2098" controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/03-go-to-declaration.mov"></video><figcaption class="wp-element-caption">Go to GraphQL definition</figcaption></figure>



<p class="wp-block-paragraph">Note that the generated code destination is still there, as it is sometimes handy to have a look at it.</p>



<p class="wp-block-paragraph">We’ve also added these nifty GraphQL icons in the gutter next to operation and fragment references. Click on them to go to the definition.</p>



<p class="wp-block-paragraph">To go to the Schema instead, use “Go To Type Declaration” (<code class="" data-line="">Cmd/Ctrl + Shift + click</code>, or <code class="" data-line="">Cmd/Ctrl + Shift + b</code>):</p>



<figure class="wp-block-video"><video height="1762" style="aspect-ratio: 2098 / 1762;" width="2098" controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/04-go-to-type-declaration.mov"></video><figcaption class="wp-element-caption">Go to the schema</figcaption></figure>



<p class="wp-block-paragraph">The reverse works too if you need it: “Find Usages” on your GraphQL operation will list Kotlin files referencing them:</p>



<figure class="wp-block-video"><video height="2234" style="aspect-ratio: 3456 / 2234;" width="3456" controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/05-find-usages.mov"></video><figcaption class="wp-element-caption">Find code usages</figcaption></figure>



<p class="wp-block-paragraph">We hope to add “Find Usages” on fields as well in the future.</p>



<h3 class="wp-block-heading"><a href="#more-to-come" aria-hidden="true" class="aal_anchor" id="more-to-come"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>More to come</h3>



<p class="wp-block-paragraph">We are working on adding more features and your ideas are very welcome! Please don’t hesitate to submit feature requests on <a href="https://github.com/apollographql/apollo-kotlin/issues/new/choose">the issue tracker</a>.</p>



<h2 class="wp-block-heading"><a href="#try-it-out" aria-hidden="true" class="aal_anchor" id="try-it-out"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try it out!</h2>



<p class="wp-block-paragraph">To install the plugin:</p>



<ol class="wp-block-list">
<li>During the preview phase, you will need to add a dedicated plugin repository:<br><br>&#8211; <code class="" data-line="">Settings</code> &gt; <code class="" data-line="">Plugins</code> &gt; <code class="" data-line="">⚙️</code> &gt; <code class="" data-line="">Manage Plugin Repositories</code> &gt; <code class="" data-line="">➕</code> &gt; <code class="" data-line="">https://plugins.jetbrains.com/plugins/preview/20645</code><br><br>&#8211; If you want the cutting edge, use this “snapshots” URL instead (new versions once a week): <code class="" data-line="">https://raw.githubusercontent.com/apollographql/apollo-kotlin/main/intellij-plugin/snapshots/plugins.xml</code></li>



<li><code class="" data-line="">Marketplace</code> &gt; Search for &#8220;Apollo GraphQL&#8221; &gt; <code class="" data-line="">Install</code></li>
</ol>



<p class="wp-block-paragraph">Detailed instructions are available <a href="https://github.com/apollographql/apollo-kotlin/tree/main/intellij-plugin">here</a>.</p>



<h2 class="wp-block-heading"><a href="#conclusion" aria-hidden="true" class="aal_anchor" id="conclusion"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Conclusion</h2>



<p class="wp-block-paragraph">We hope this plugin will make your experience with Apollo Kotlin a delightful one and will help you build great apps. Stay tuned for more, and as always, your feedback is welcome! You can reach out on <a href="https://github.com/apollographql/apollo-kotlin">GitHub</a>, the <a href="https://discord.gg/graphos">Apollo Community</a>, or the <a href="https://slack.kotl.in/">Kotlin Slack</a>!</p>


Announcing the Apollo Kotlin plugin for Android Studio and IntelliJ IDEA


<p class="wp-block-paragraph">When it comes to writing code collaboratively, consistency is everything. APIs are no exception. In fact, APIs are perhaps the most important place to ensure consistency, since they act as a vein for collaboration across nearly every developer in an organization&#8217;s ecosystem.</p>



<p class="wp-block-paragraph">For GraphQL APIs, the schema is at the heart of all collaboration and consumption, but ensuring consistency in a graph that spans many teams, tools, and workflows is no easy task. Today, we’re excited to make things a bit easier by adding <a href="https://www.apollographql.com/docs/graphos/delivery/schema-linter">schema linting</a> to Apollo GraphOS!&nbsp;</p>



<p class="wp-block-paragraph">As an API platform owner, linter checks in GraphOS will help you keep your schema syntax clean and consistent by validating that schema changes pass pre-defined formatting and naming rules like:</p>



<ul class="wp-block-list">
<li>Field names should be <code class="" data-line="">camelCase</code></li>



<li>Input type names should be suffixed with <code class="" data-line="">Input</code></li>



<li>The <code class="" data-line="">@tag</code> directive should use a pre-approved value for its <code class="" data-line="">name</code> argument</li>
</ul>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="868" src="https://wp.apollographql.com/wp-content/uploads/2023/06/image2-1024x868.png" alt="" class="wp-image-21398" srcset="https://wp.apollographql.com/wp-content/uploads/2023/06/image2-1024x868.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2-300x254.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2-768x651.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2-1536x1302.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2-1200x1017.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2.png 1628w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"><strong>Starting today, schema linting is available for all orgs on the GraphOS Enterprise and Serverless plans.</strong> Linter checks will automatically run whenever new schema changes are published to GraphOS, but you can also run checks manually on a local schema or in a separate CI/CD pipeline using the Rover CLI.</p>



<h2 class="wp-block-heading"><a href="#consistency-at-every-stage-of-graph-development" aria-hidden="true" class="aal_anchor" id="consistency-at-every-stage-of-graph-development"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Consistency at every stage of graph development</h2>



<p class="wp-block-paragraph">GraphOS schema linting is designed to integrate seamlessly into your existing processes to ensure that your schema’s syntax stays consistent at every stage of graph development.</p>



<h3 class="wp-block-heading"><a href="#lint-locally-with-the-rover-cli" aria-hidden="true" class="aal_anchor" id="lint-locally-with-the-rover-cli"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Lint locally with the Rover CLI</h3>



<p class="wp-block-paragraph">No one wants to reread all of the code they just wrote to figure out where they miscapitalized one field. Using <a href="https://www.apollographql.com/docs/rover">the Rover CLI</a>, devs can run schema linting on their local schema as they work to ensure that their changes pass when published.</p>



<p class="wp-block-paragraph">To run schema linting locally, just <a href="https://www.apollographql.com/docs/rover/getting-started">install Rover</a>, authenticate, and run <a href="https://www.apollographql.com/docs/rover/commands/graphs#graph-lint"><code class="" data-line="">rover graph lint</code></a> or <a href="https://www.apollographql.com/docs/rover/commands/subgraphs#subgraph-lint"><code class="" data-line="">rover subgraph lint</code></a>.</p>



<h3 class="wp-block-heading"><a href="#integrate-into-ci-cd" aria-hidden="true" class="aal_anchor" id="integrate-into-ci-cd"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Integrate into CI/CD</h3>



<p class="wp-block-paragraph">Linting locally helps individual developers work quickly, but keeping a cross-team code base consistent requires enforcing linter rules centrally. Similar to other linting tools you may use, GraphOS schema linting can be integrated directly into your existing CI/CD pipelines to ensure that every schema change is checked before being published, no matter who it comes from.</p>



<p class="wp-block-paragraph">To run schema linting in a third-party CI/CD tool, just <a href="https://www.apollographql.com/docs/rover/ci-cd/">install the Rover CLI as part of your pipeline</a>.</p>



<h3 class="wp-block-heading"><a href="#linter-checks-on-published-schemas-in-graphos" aria-hidden="true" class="aal_anchor" id="linter-checks-on-published-schemas-in-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Linter checks on published schemas in GraphOS&nbsp;</h3>



<p class="wp-block-paragraph">GraphOS gives you a central source of truth for all of your schemas and, if you have a <a href="https://apollographql.com/docs/federation">federated graph</a>, acts as the final checkpoint for your schema before your graph router uses it in production.&nbsp;</p>



<p class="wp-block-paragraph">Running linter checks for new changes published to your schema in GraphOS ensures consistency in all of your running graphs.</p>



<p class="wp-block-paragraph">If you already have schema checks set up in GraphOS, linter checks will automatically be added to your checks workflow! You can review the status of linter checks on the checks page in GraphOS Studio.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="578" src="https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1024x578.png" alt="" class="wp-image-21412" srcset="https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1024x578.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-300x169.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-768x434.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1536x867.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-2048x1156.png 2048w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1200x678.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1980x1118.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#configuring-the-linter-in-graphos-studio" aria-hidden="true" class="aal_anchor" id="configuring-the-linter-in-graphos-studio"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Configuring the linter in GraphOS Studio</h2>



<p class="wp-block-paragraph">The linter in GraphOS comes with a pre-defined list of rules that cover common best practices for writing GraphQL schemas. You can customize the severity of each rule independently to <code class="" data-line="">Off</code>, <code class="" data-line="">Warn</code>, or <code class="" data-line="">Error</code> in GraphOS Studio under Checks &gt; Configuration &gt; Linter.</p>



<p class="wp-block-paragraph">When set to <code class="" data-line="">Warn</code>, a rule violation will allow the checks workflow to pass but output a warning, whereas a violation of a rule set to <code class="" data-line="">Error</code> will cause the checks workflow to <em>fail</em> outright.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="471" src="https://wp.apollographql.com/wp-content/uploads/2023/06/image1-1024x471.png" alt="" class="wp-image-21403" srcset="https://wp.apollographql.com/wp-content/uploads/2023/06/image1-1024x471.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1-300x138.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1-768x353.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1-1536x706.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1-1200x552.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1.png 1766w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">You can also choose to have the linter ignore definitions marked with <code class="" data-line="">@deprecated</code> or <code class="" data-line="">@inaccessible</code> to prevent errors caused by outdated or private definitions.</p>



<h2 class="wp-block-heading"><a href="#start-linting" aria-hidden="true" class="aal_anchor" id="start-linting"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Start linting!</h2>



<p class="wp-block-paragraph">Starting today, linting is enabled for every organization on GraphOS Enterprise and Serverless plans. All you need to do to get started is publish a change to your graph! If you have schema checks enabled, you’ll automatically see linter checks as a new step.&nbsp;</p>



<p class="wp-block-paragraph">If you want to change the linter configuration for your graph, head to the “Checks” tab in GraphOS Studio → Configuration → Linter. Or if you haven’t set up schema checks yet for your graph, check out <a href="https://www.apollographql.com/docs/graphos/delivery/schema-checks">the documentation</a> to get started.</p>


Standardize GraphQL schema linting policies with GraphOS


<p class="wp-block-paragraph">A GraphQL API with the power to give app developers everything they need in a single query is excellent for delivery velocity, but it also could have the potential to enable improper access to data if not secured correctly.&nbsp;</p>



<p class="wp-block-paragraph">With supergraph architecture, you can mitigate this risk by implementing the proper security controls in each subgraph, but Apollo GraphOS is helping platform teams add an additional layer of security in front of subgraphs by building controls into the graph router itself.</p>



<p class="wp-block-paragraph">Router security is one of the key themes in our 2023 GraphOS roadmap, and today we’re excited to ship a preview of our newest router security feature for GraphOS Enterprise: operation size and complexity limiting.</p>



<h2 class="wp-block-heading"><a href="#centralized-protection-from-misuse" aria-hidden="true" class="aal_anchor" id="centralized-protection-from-misuse"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Centralized protection from misuse</h2>



<p class="wp-block-paragraph">For production graphs, preventing accidental or intentional misuse is a key requirement. If not protected properly, client apps can issue expensive queries that cause excessive load on the server potentially resulting in denial of service. Even in less extreme cases, poorly formed queries can still impact the performance of client apps and lead to a slower user experience.</p>



<p class="wp-block-paragraph">There are a variety of packages designed to limit operation complexity and cost at the server level; however, as a federated graph grows, it can become increasingly difficult to set, standardize, and maintain these limits across many subgraphs owned by different teams. Luckily, supergraph architecture presents us with the unique opportunity to centralize control in a single point: the router.</p>



<p class="wp-block-paragraph">Enforcing operation size and complexity limits in the graph router makes it far easier to standardize policies for a large graph and alleviates the burden of coordinating limits across every subgraph.</p>



<h2 class="wp-block-heading"><a href="#limit-depth-height-root-fields-and-aliases" aria-hidden="true" class="aal_anchor" id="limit-depth-height-root-fields-and-aliases"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Limit depth, height, root fields, and aliases</h2>



<p class="wp-block-paragraph">Just like it sounds! With GraphOS Enterprise, you can now configure your router to limit the depth, height, number of root fields, and number of aliased fields of any incoming GraphQL operation. If an operation exceeds any of the set limits, the router will reject it before attempting to resolve the request with a <code class="" data-line="">400 BAD_REQUEST</code> status code.</p>



<p class="wp-block-paragraph">All of these limits can be configured in the <code class="" data-line="">router.yaml</code> file for any router authenticated with your GraphOS Enterprise credentials:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml" data-line="">preview_operation_limits:
  max_depth: 100
  max_height: 200
  max_root_fields: 40
  max_aliases: 30</code></pre>



<p class="wp-block-paragraph">Optionally, you can also configure the router to only log a warning message for operations that exceed the set limits rather than rejecting the operation outright:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml" data-line="">preview_operation_limits:
  # some limits
  warn_only: TRUE</code></pre>



<p class="wp-block-paragraph"><code class="" data-line="">warn_only</code> defaults to <code class="" data-line="">FALSE</code>, but it can be useful to set it to <code class="" data-line="">TRUE</code> in development environments for testing purposes.</p>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p class="wp-block-paragraph">The feature preview for operation size and complexity limits is available now for all users with a GraphOS Enterprise plan. To get started, make sure that your router is authenticated with your GraphOS Enterprise credentials and is running the <a href="https://github.com/apollographql/router/releases" target="_blank" rel="noreferrer noopener">latest version of Apollo Router</a>. Then, head to <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/router/configuration/operation-limits" target="_blank">the documentation</a> for detailed information about configuring limits in your <code class="" data-line="">router.yaml</code> file.</p>



<p class="wp-block-paragraph">If you&#8217;re not a GraphOS Enterprise customer yet, <a href="https://www.apollographql.com/contact-sales">get in touch with us</a> to learn more and start a trial!</p>



<p class="wp-block-paragraph">We’re excited for you to start setting some limits and to hear what you think! If you encounter any problems or have feedback, feel free to <a href="https://github.com/apollographql/router/issues">open an issue</a>. That being said, this feature is still in preview, so there may be some final adjustments before we mark it as GA. To stay up to date, be sure to bookmark the <a href="https://github.com/apollographql/router/blob/dev/CHANGELOG.md">Apollo Router changelog</a>.</p>



<p class="wp-block-paragraph">Happy querying!</p>


Prevent graph misuse with operation size and complexity limits


<p class="wp-block-paragraph">Just over a year ago, we introduced Apollo Router, the graph router that is now at the heart of Apollo GraphOS. Unlike its predecessor <a href="https://www.apollographql.com/docs/apollo-server/using-federation/api/apollo-gateway/">Apollo Gateway</a>, Apollo Router was designed to&nbsp;maximize the performance benefits of GraphQL and <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph architecture</a>, while being secure by default. After switching to the router, one customer reported a <strong>93% reduction in gateway cloud spend</strong>, a <strong>30x reduction in Kubernetes Pod counts</strong>, and 70% less code to maintain – while delivering even faster response times, with <strong>a 70% reduction in request latencies</strong>!&nbsp;</p>



<p class="wp-block-paragraph">Today, some of the world’s largest companies rely on GraphOS for their mission-critical graph API infrastructure. Routers have processed 100% of Black Friday traffic for top-100 retail companies, and major fintech organizations are trusting their routers to handle tax season.</p>



<p class="wp-block-paragraph"><em>So what’s next?</em></p>



<p class="wp-block-paragraph">Many of Apollo Router’s initial users are running billions of operations each month with GraphOS. The features in this release focus on the challenges of operating a graph router at massive scale: <strong>defense in depth, maximizing performance, and extensibility</strong>. Today, we are excited to make three new features generally available to GraphOS Enterprise customers running a self-hosted router: JWT auth, distributed APQ caching, and support for external coprocessors.</p>



<h2 class="wp-block-heading"><a href="#supergraph-defense-in-depth" aria-hidden="true" class="aal_anchor" id="supergraph-defense-in-depth"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Supergraph defense-in-depth</h2>



<p class="wp-block-paragraph"><strong>Block malicious traffic at the edge of your graph with new JWT auth support in the router.</strong></p>



<p class="wp-block-paragraph">Previously, the router could only forward user access tokens (JWT) generated by identity providers like Auth0 or Okta onto subgraphs and underlying REST APIs. Keeping your supergraph secure meant doing JWT checks in every subgraph or REST API which allows attackers deeper into your graph – and missing a single check often results in security holes.</p>



<p class="wp-block-paragraph">Now, with the router as a <a href="https://doyensec.com/resources/Doyensec_Apollo_Report_Q22022_v4_AfterRetest.pdf">security-hardened</a> entry point to your graph, you can reject malicious traffic early and shield your subgraphs and REST APIs from unwanted traffic. Router v1.12 adds support for <a href="https://www.apollographql.com/docs/router/configuration/authn-jwt">JWT validation, claim extraction, and custom security policies in Rhai scripting</a> to reject bad traffic at the edge of the graph – for enhanced zero-trust and defense-in-depth. Extracting claims once in the router and securely forwarding them to subgraphs has several key benefits, including: </p>



<ul class="wp-block-list">
<li><strong>Reducing operational burden on backend API teams</strong> &#8211; no JWT keys to manage</li>



<li><strong>Reducing latency due to JWT processing</strong> &#8211; since the JWT is processed only once in the router</li>



<li><strong>Speeding up response times</strong> &#8211; by selectively forwarding JWT claims for increased <a href="https://www.apollographql.com/docs/router/configuration/traffic-shaping/#query-deduplication">query deduplication</a></li>
</ul>



<p class="wp-block-paragraph">These performance benefits compound at scale, particularly if the router is simultaneously processing similar queries.</p>



<h2 class="wp-block-heading"><a href="#maximize-performance-at-scale" aria-hidden="true" class="aal_anchor" id="maximize-performance-at-scale"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Maximize performance at scale</h2>



<p class="wp-block-paragraph"><strong>Reduce p99 latency during peak traffic with Distributed APQ (automatic persisted query) caching with Redis.</strong></p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/docs/apollo-server/performance/apq/">APQ</a> can drastically reduce response latency by allowing clients to send only a unique hash over the wire instead of a large query document, providing a fast path to query execution. You may already have in-memory APQ configured for your router, however when load balancing requests over a large fleet of router instances, the in-memory cache won’t be consistently hot. Unlucky users, especially during scaling events, will hit cold caches and experience slower response times as the APQ cache must be built individually in each router instance.</p>



<p class="wp-block-paragraph">With Router v1.12 , you can now use <a href="https://www.apollographql.com/docs/router/configuration/distributed-caching">distributed APQ caching</a> to improve p99 latencies during peak times. A shared Redis instance can now be used by the entire router fleet to build the APQ cache faster and share existing APQ cache with new router instances that are spun up during scaling events – when they need it most. This ensures the fast path to query execution is consistently available to all users even during peak load.</p>



<h2 class="wp-block-heading"><a href="#extensibility-with-coprocessors" aria-hidden="true" class="aal_anchor" id="extensibility-with-coprocessors"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Extensibility with coprocessors</h2>



<p class="wp-block-paragraph"><strong>Extend the router in your language of choice using new external coprocessor support.</strong></p>



<p class="wp-block-paragraph">To create common customizations for Apollo Gateway like header propagation and error handling, you have to code plugins and middleware directly into a custom gateway package. These monolithic gateway packages must be built and deployed as a single unit, often requiring coordination across teams. Since everything is run in a single process, errors in the custom code can crash the whole Gateway, and it’s not clear which team should be paged at 3 am to resolve the issue.</p>



<p class="wp-block-paragraph">With Apollo Router, most common customizations are built directly into the stock binary and <a href="https://www.apollographql.com/docs/router/configuration/overview">can be configured with YAML</a>. YAML config alone allowed one of our largest Enterprise customers to eliminate 70% of their custom Gateway code.</p>



<p class="wp-block-paragraph">In cases where the YAML config isn’t enough, Router also supports Rhai scripting (similar to Lua in NGINX and Envoy) which can be used for in-memory manipulation of headers, cookies, and more with a well-defined <a href="https://www.apollographql.com/docs/router/customizations/rhai-api">Rhai API reference</a>. Rhai scripts are great for lightweight customizations and provide a safe, sandboxed way to customize the Router’s request flow.</p>



<p class="wp-block-paragraph">For more powerful customizations, the Router now supports <a href="https://www.apollographql.com/docs/router/configuration/external">external coprocessors</a> written in the programming language of your choice. Coprocessors run with full isolation and a clean separation of concerns, that decouples delivery and provides fault isolation. Low overhead can be achieved by running coprocessors alongside the router on the same host or in the same Kubernetes Pod as a sidecar. Coprocessors can be used to speed Gateway migrations, support bespoke use cases, or integrate the router with existing network services for custom auth (JWT mapping, claim enrichment), service discovery integration, and more!</p>



<p class="wp-block-paragraph">However, our goal is to eliminate as much custom code as possible, so if you have a common use case that you think should be supported in the stock Apollo Router binary, be sure to <a href="https://github.com/apollographql/router/issues">open an issue</a>.</p>



<h2 class="wp-block-heading"><a href="#enabling-graphos-enterprise-features" aria-hidden="true" class="aal_anchor" id="enabling-graphos-enterprise-features"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Enabling GraphOS Enterprise features</h2>



<p class="wp-block-paragraph"><strong>Upgrade to Router v1.12 and ensure they are connected to GraphOS with an Enterprise plan.</strong></p>



<p class="wp-block-paragraph">All Apollo GraphOS Enterprise customers can access these features today for self-hosted instances of Apollo Router. If your router is already connected to GraphOS Studio using your <code class="" data-line="">APOLLO_KEY</code> and <code class="" data-line="">APOLLO_GRAPH_REF</code>, and you’re running the latest version of Apollo Router, no further action is required! You can set up all of these features in your existing router config. See <a href="https://www.apollographql.com/docs/router/enterprise-features">the documentation</a> for additional details.</p>



<p class="wp-block-paragraph">These are just the first of many router features on the roadmap for GraphOS. We have exciting security and performance features coming up soon for GraphOS Enterprise as well as GraphOS Cloud, so stay tuned!</p>



<h2 class="wp-block-heading"><a href="#optimize-apollo-router-with-tips-from-the-apollo-community" aria-hidden="true" class="aal_anchor" id="optimize-apollo-router-with-tips-from-the-apollo-community"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Optimize Apollo Router with tips from the Apollo community</h2>



<p class="wp-block-paragraph">The Apollo Router is a core part of the Apollo stack, and we want you to feel confident to trust it with your queries in production. The Apollo Champions community features many customers who have already made this switch and have insights that can help, including the team at Wayfair. They&nbsp;switched to Apollo Router from Gateway before Black Friday. The Wayfair team will discuss how they made the switch as well as the improvements they saw as a result. Be sure to tune in to the <a href="https://bit.ly/3liIeLY" data-type="URL" data-id="https://bit.ly/3liIeLY">Apollo Champion’s Corner on March 23rd</a> to learn more.</p>


New in Apollo Router v1.12: Improved router security, performance, and extensibility


<p class="wp-block-paragraph"><br>Are you looking to learn how to build a GraphQL API using Typescript with Apollo Server? Then join the Apollo Developer Advocates for a live stream event on 3/22 at 9:00 AM PST! The event will be hosted in the <a rel="noreferrer noopener" href="https://discord.com/invite/graphos" target="_blank">Apollo Discord</a> with a live Q&amp;A session at the end. We&#8217;ll also be trying this live stream directly from our <a href="https://www.youtube.com/@ApolloGraphQL">YouTube</a> so you can subscribe to get a notification of the event.</p>



<p class="wp-block-paragraph">During this live stream, we will provide a step-by-step guide to help you build your subgraph starting with a template using Schema Definition Language (SDL). This will include everything you need to get started along with important toolings like codegen and <a href="https://www.apollographql.com/docs/graphos/">GraphOS</a>. Plus, they will answer any questions you have along the way. </p>



<p class="wp-block-paragraph">If you want to learn more about Apollo Server + Typescript, this is the perfect opportunity for you. So don’t miss out and join the Apollo Developer Advocates to get your questions answered! We&#8217;ll be updating this post with the video recording once it is available.</p>


Building a GraphQL API in Typescript with Apollo Server


<p class="wp-block-paragraph">Are you interested in building a successful GraphQL API? Then you won&#8217;t want to miss the upcoming Tech Talk + Workshop that dive deep into Schema Design Best Practices. The event is split into two sessions, the first being a Tech Talk on March 9th at 10am PT, and the second being a Workshop on March 16th at 9am PT.</p>



<p class="wp-block-paragraph">During the Tech Talk, you&#8217;ll learn about the common GraphQL schema design best practices that apply to supergraphs, and gain valuable tips from Erik on how to create and iterate on the type definitions that they contribute to the overall schema efficiently, without unexpected breaking changes for clients. This session is perfect for those who are already familiar with GraphQL and are looking to deepen their understanding of schema design.</p>



<p class="wp-block-paragraph">If you&#8217;re looking for a more hands-on experience, then the Workshop is for you. In this course, you&#8217;ll get hands-on training to build readable, scalable, well-documented schemas with GraphQL. You&#8217;ll learn how to build a strong GraphQL schema that serves as the foundation of any successful GraphQL project.</p>



<p class="wp-block-paragraph">Both sessions are packed with valuable information and practical tips that you can immediately apply to your own GraphQL projects. Whether you&#8217;re a beginner or an experienced GraphQL developer, you&#8217;re sure to benefit from attending this event.</p>



<p class="wp-block-paragraph">The workshop is led by Moon Highway, a company that specializes in providing expert training and consulting services for web developers. Don&#8217;t miss this opportunity to learn from their team of experienced GraphQL developers and take your GraphQL skills to the next level. <a href="https://www.apollographql.com/events/tech-talk-workshop/register/deep-dive-into-schema-design-best-practices/">Register now for free</a> and get ready to dive deep into schema design best practices!</p>


Virtual Events – Deep Dive into Schema Design Best Practices


<p class="wp-block-paragraph">The Apollo CLI <code class="" data-line="">service</code> commands are now officially deprecated and will reach their <strong>final end of life on April 28th, 2023.</strong></p>



<p class="wp-block-paragraph"><strong>Note: </strong>Apollo will continue to provide support for the Apollo CLI <code class="" data-line="">client</code> commands.</p>



<p class="wp-block-paragraph">Rover is the command line interface for managing and maintaining graphs through GraphOS with over 10 million all-time downloads and over 4 million command invocations per day. If you are still using Apollo CLI’s <code class="" data-line="">service</code> commands and would like to migrate to the Rover CLI, please refer to this migration <a href="https://www.apollographql.com/docs/rover/migration/">guide</a>.</p>



<p class="wp-block-paragraph">For more information regarding Apollo’s software lifecycle policies and an up-to-date list of actively maintained software versions, please visit the Apollo launch stages <a href="https://www.apollographql.com/docs/resources/product-launch-stages/">documentation</a>.</p>


Announcing the end-of-life schedule for Apollo CLI service commands


<p class="wp-block-paragraph">Almost a year ago we introduced <a href="https://www.apollographql.com/blog/announcement/platform/save-and-share-your-graphql-operations-in-apollo-explorer/">operation collections</a> in GraphOS as a way to save your frequently used operations in Explorer and share them with your team. Today, we are making saved operations even more useful with operation scripts! Now, you can write scripts for your saved operations to build automated testing workflows that call other saved operations.</p>



<h2 class="wp-block-heading"><a href="#what-are-operation-scripts" aria-hidden="true" class="aal_anchor" id="what-are-operation-scripts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What are operation scripts?</strong></h2>



<p class="wp-block-paragraph">Operation scripts are a brand new, <strong>free 🎊</strong> feature in GraphOS Studio that let you write scripts that run before your operation to execute JavaScript code, make HTTP requests, and run other saved operations before your current operation. You may think this sounds a lot like what you can do with <a href="https://www.apollographql.com/blog/announcement/tooling/automatically-authenticate-with-preflight-scripts-in-apollo-studio-explorer/">preflight scripts</a>, and you would be correct! An operation script, at a high level, is a preflight script that is defined <em>per operation</em> instead of <em>per variant</em>.</p>



<p class="wp-block-paragraph">With operation scripts you and your team can:</p>



<ul class="wp-block-list">
<li>Easily debug the behavior of individual operations when they’re provided various values</li>



<li>Design and write scripted workflows with your saved operations for testing</li>
</ul>



<h2 class="wp-block-heading"><a href="#adding-an-operation-script" aria-hidden="true" class="aal_anchor" id="adding-an-operation-script"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Adding an operation script</strong></h2>



<p class="wp-block-paragraph">Adding operation scripts to your saved operations is easy. To get started, head to Explorer in GraphOS Studio, open up the Operation Collections tab on the left panel, and open the operation you would like to write a script for. In the bottom pane, you’ll see a new tab named Script.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="879" src="https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-1024x879.png" alt="" class="wp-image-19904" srcset="https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-1024x879.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-300x257.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-768x659.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-1200x1030.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM.png 1436w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">Click on the “Add Script” button to open up the operation script editor panel. To help you start writing your script, there are code snippets to the left of the editor. Clicking on the plus icon next to a snippet will insert it in the editor.</p>



<p class="wp-block-paragraph">To run your operation script with your current operation, just save your operation and turn on the operation script setting within Explorer Settings &gt; Personal Settings.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="704" src="https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-1024x704.png" alt="" class="wp-image-19901" srcset="https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-1024x704.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-300x206.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-768x528.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-1200x824.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM.png 1406w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">ℹ️ <strong>Note</strong>: Operation scripts are not only limited to GraphOS Explorer, they can also be created in Sandbox and within Explorer or Sandbox embeds!</p>



<h2 class="wp-block-heading"><a href="#calling-saved-operations-with-runoperation" aria-hidden="true" class="aal_anchor" id="calling-saved-operations-with-runoperation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Calling saved operations with runOperation</strong></h2>



<p class="wp-block-paragraph">In your script, you can also run <em>other</em> saved operations from any variant of your graph against your current endpoint using the <code class="" data-line="">runOperation</code> command. This allows you to use values from the output of those operations as GraphQL variables for your current operation.&nbsp;</p>



<p class="wp-block-paragraph">Below is an example of using <code class="" data-line="">runOperation</code> to get a list of ships from the SpaceX GraphQL API and then passing the ID of the <code class="" data-line="">firstShip</code> to an environment variable.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-javascript" data-line="">const response = await explorer.runOperation({
 scope: &#039;shared&#039;,
 graphRef: &#039;SpaceX-pxxbxen@current&#039;,
 collectionName: &#039;Mission Control&#039;,
 operationName: &#039;Ships&#039;,
})

const firstShipID = response.result.data.ships[0].id

explorer.environment.set(&#039;shipID&#039;, firstShipID)</code></pre>



<p class="wp-block-paragraph">From here you can use any environment variables set in your script by passing them into the GraphQL variables panel. For instance, if I had this script set on a mutation that takes in a <code class="" data-line="">shipID</code> and then sets the <code class="" data-line="">status</code> of the ship to <code class="" data-line="">Launched</code>, I would use the following GraphQL variables in my variables panel:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">{
  &quot;shipID&quot;: &quot;{{ shipID }}&quot;,
  &quot;status&quot;: &quot;Launched&quot;,
}</code></pre>



<p class="wp-block-paragraph">When you run your operation, it will run your script, populate your variables, and then run the current operation. Amazing! Now you can build operation workflows without you having to go back and forth between tabs copying and pasting values! And, if you forget the names of your saved operations or collections, the script editor provides automatic IntelliSense to suggest names of collections and operation names. To trigger it you can start typing <code class="" data-line="">&#039;&#039;</code> and it will provide a dropdown for you to choose from.</p>



<figure class="wp-block-image size-full is-style-default"><img loading="lazy" decoding="async" width="1000" height="636" src="https://wp.apollographql.com/wp-content/uploads/2023/03/7341589aaef2707bbb952f65cc2bdaa6.gif" alt="" class="wp-image-19907"/></figure>



<h3 class="wp-block-heading"><a href="#chaining-operation-scripts-with-runoperation" aria-hidden="true" class="aal_anchor" id="chaining-operation-scripts-with-runoperation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Chaining operation scripts with runOperation</strong></h3>



<p class="wp-block-paragraph">In addition to running GraphQL operations, runOperation will also run any operation scripts that are saved to the operation if they exist. This allows you and your team to write chains of scripts to automate entire workflows!</p>



<p class="wp-block-paragraph">ℹ️ <strong>Note:</strong> Be sure that you have the operation script flag turned on in your Explorer settings to test and chain operation scripts.</p>



<h2 class="wp-block-heading"><a href="#start-writing-your-operation-scripts-today" aria-hidden="true" class="aal_anchor" id="start-writing-your-operation-scripts-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Start writing your Operation Scripts today!</strong></h2>



<p class="wp-block-paragraph">Head over to <a href="https://studio.apollographql.com">GraphOS Studio</a> to start writing scripts and automating testing workflows for your GraphQL operations! Learn more about this feature <a href="https://www.apollographql.com/docs/graphos/explorer/connecting-authenticating/#operation-scripts">here</a> and as always we love hearing from you, so if you have any feedback, feel free to leave a comment in our <a href="https://github.com/apollographql/apollo-studio-community">Studio Community GitHub repository.</a></p>


Automate GraphQL query testing in GraphOS Explorer!


<p class="wp-block-paragraph">You’ve heard it a million times: <em>everything you need, and nothing more, all in a single query</em>. It’s the core promise of GraphQL, but it presents a challenge. To truly get everything in a single query, you need to put everything you have<em> </em>into a single graph.</p>



<p class="wp-block-paragraph">At Apollo, we’ve spent the better part of three years designing a GraphQL architecture to address that challenge — we call it <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph architecture</a>. Its main component is a graph router, which sits in front of your GraphQL servers and has a query planner to execute queries across multiple connected graphs. Just over a year ago, we released Apollo Router, our graph router binary, which is now used by Fortune 500 companies to run billions of operations each month for mission-critical applications.</p>



<p class="wp-block-paragraph">But Apollo Router enables much more than just scale. It enables faster, more reliable, and more intelligent query execution for any GraphQL API by layering in support for directives like <code class="" data-line="">@defer</code> and entity types. We want to bring these benefits and more to every developer in the world that uses GraphQL, not just those in a massive company.</p>



<p class="wp-block-paragraph">That’s why today, we’re excited to announce general availability of <strong>Apollo GraphOS Cloud</strong> — a cloud-hosted platform with instant-on access to blazing-fast graph routing for any GraphQL API and integrated tools for rapid query development, collaboration, and schema design. Anyone with a GraphQL API can <a href="https://studio.apollographql.com/signup">start using GraphOS Cloud</a> today with 10 million free queries per month our Serverless plan. Serverless is a great way for developers and teams to evaluate GraphOS or even GraphQL. From startups to proofs-of-concept for your enterprise, Serverless is an easy way to try all that Apollo GraphOS has to offer.</p>



<h2 class="wp-block-heading"><a href="#faster-apps-with-hosted-graph-routing" aria-hidden="true" class="aal_anchor" id="faster-apps-with-hosted-graph-routing"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Faster apps with hosted graph routing</h2>



<p class="wp-block-paragraph">At the heart of GraphOS Cloud is an edge graph router (built on Apollo Router) that enhances your existing GraphQL API with the latest runtime features of GraphOS. The router in GraphOS Cloud is so much more than just a GraphQL API gateway. It’s a runtime that is fully aware of the structure of data available to your connected GraphQL server, and it can manipulate how queries are executed to improve performance.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="520" src="https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-1024x520.png" alt="" class="wp-image-19859" srcset="https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-1024x520.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-300x152.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-768x390.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-1536x780.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-1200x610.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router.png 1626w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#defer-for-any-server" aria-hidden="true" class="aal_anchor" id="defer-for-any-server"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code class="" data-line="">@defer</code> for any server</h3>



<p class="wp-block-paragraph">With GraphOS Cloud, you can use <code class="" data-line="">@defer</code> with any existing GraphQL server to improve time-to-interactive. When writing a query, you can simply add the <code class="" data-line="">@defer</code> directive to slower fields, and GraphOS will automatically return those fields incrementally.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1918" height="864" src="https://wp.apollographql.com/wp-content/uploads/2022/11/explorer-defer-1.gif" alt="" class="wp-image-17955"/></figure>



<h3 class="wp-block-heading"><a href="#subscriptions-caching-and-more-coming-soon" aria-hidden="true" class="aal_anchor" id="subscriptions-caching-and-more-coming-soon"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Subscriptions, caching, and more coming soon</h3>



<p class="wp-block-paragraph"><code class="" data-line="">@defer</code> is just the first of many features coming to GraphOS Cloud that will enhance performance for your GraphQL API. Support for subscriptions, response caching, and more are coming up soon on the roadmap!</p>



<h2 class="wp-block-heading"><a href="#develop-save-and-test-queries" aria-hidden="true" class="aal_anchor" id="develop-save-and-test-queries"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Develop, save, and test queries</h2>



<p class="wp-block-paragraph">GraphOS Cloud automatically registers the schema from your GraphQL API and integrates your hosted router with Explorer — our GraphQL IDE with IntelliSense. With Explorer, you can create queries for your graph with just a click, save queries to reuse later, and even write scripts that chain scripts together for automated testing workflows! Try it out on our <a href="https://studio.apollographql.com/public/apollo-retail-supergraph/explorer?explorerURLState=N4IgzghgbgpgJgYQPYBsUwMYBcCWSB2AknCAFwgCccEADAEYQAsdAtAIwBMcbLjMdrABwUBLOvEZM4jAOwA2AGYKQAGnDR4yNJlwEAoviwAnAJ7EyIAMwBWOh34YKLDBArXeM6wpaDGlmSwygnLcgmwYgnAcNCAAvkA&amp;referrer=operation_collections&amp;variant=prod">demo graph</a>.</p>



<h2 class="wp-block-heading"><a href="#scale-and-collaborate-with-ease" aria-hidden="true" class="aal_anchor" id="scale-and-collaborate-with-ease"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Scale and collaborate with ease</h2>



<p class="wp-block-paragraph">Most graphs start out small, but they can be a headache to scale across teams when the time comes. GraphOS Cloud has built-in support for Apollo Federation, so you can easily add to your graph modularly with subgraphs whenever you need to. It also automatically keeps your hosted router up-to-date with the latest version of Apollo Router, so you never need to worry about new version rollout.</p>



<p class="wp-block-paragraph">GraphOS Cloud also integrates your router with a delivery pipeline to prevent breaking changes when collaborating on a graph with multiple subgraphs and client apps. Whenever GraphOS detects a change to one of your schemas, it will automatically recompose a supergraph schema for your router, check it against historic operations from registered client apps, and update your router with the new supergraph schema.</p>



<h2 class="wp-block-heading"><a href="#get-started-with-graphos-cloud-for-free" aria-hidden="true" class="aal_anchor" id="get-started-with-graphos-cloud-for-free"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started with GraphOS Cloud for free</h2>



<p class="wp-block-paragraph">Anyone with a GraphQL API can <a href="https://studio.apollographql.com/signup?referrer=blog">start using GraphOS Cloud for free</a> today on our Serverless plan. On the Serverless plan, you can run up to 10 million operations per month through GraphOS Cloud for free! If 10 million isn’t enough, you can pay as you go for additional operations.</p>



<h2 class="wp-block-heading"><a href="#help-us-build-the-roadmap-for-graphos-cloud" aria-hidden="true" class="aal_anchor" id="help-us-build-the-roadmap-for-graphos-cloud"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Help us build the roadmap for GraphOS Cloud</h2>



<p class="wp-block-paragraph">We’re actively building the next generation of GraphOS Cloud to improve governance and throughput for production graphs. We would love to hear feedback, feature requests, and questions you have. Reach out at <a href="mailto:cloud@apollographql.com">cloud@apollographql.com</a>.</p>


Supercharge your GraphQL stack with GraphOS Cloud

Apollo Federation and GraphOS add support for entity interfaces to streamline collaboration


<p class="wp-block-paragraph">Today, we’re launching our new <a href="https://apollographql.com/trust">Trust Center</a>, a single source of truth for Apollo’s security, compliance, reliability, and legal documentation.&nbsp;</p>



<p class="wp-block-paragraph">Here’s what you need to know.&nbsp; </p>



<h2 class="wp-block-heading"><a href="#understanding-the-apollo-trust-center" aria-hidden="true" class="aal_anchor" id="understanding-the-apollo-trust-center"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Understanding the Apollo Trust Center</h2>



<p class="wp-block-paragraph">The Apollo Trust Center is for anyone with questions or needs concerning Apollo’s compliance, security, reliability, or legal policies. From the Trust Center, you can learn about Apollo’s approach to earning customer trust, and, most importantly, you can request and download a wide variety of Apollo’s security, compliance, and legal documentation including:</p>



<ul class="wp-block-list">
<li>Apollo’s SOC 2 report</li>



<li>Summaries of third-party penetration tests for Apollo GraphOS and Apollo Router</li>



<li>Prefilled industry-standard security questionnaires</li>



<li>All of our published reliability metrics</li>



<li>Apollo’s legal documentation required for privacy alignment</li>
</ul>



<p class="wp-block-paragraph">It’s everything that we expect from vendors, in a single portal, tied with a bow 🎀</p>



<h2 class="wp-block-heading"><a href="#compliance-and-security" aria-hidden="true" class="aal_anchor" id="compliance-and-security"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Compliance and security</h2>



<p class="wp-block-paragraph">In the Trust Center, you’ll find a <a href="https://www.apollographql.com/trust/compliance-and-security">Compliance and Security page</a> with answers to questions about the security of the Apollo GraphOS platform and how we can strengthen your posture. We offer information on vulnerability patching, internal and third-party penetration testing, and testing practices for our Business Continuity Plan.&nbsp;</p>



<p class="wp-block-paragraph">Bookmark the Trust Center for annual refreshers and ongoing compliance needs like SOC 2 reports. The Compliance and Security page has everything you need to evaluate before using us and each year going forward.</p>



<h3 class="wp-block-heading"><a href="#reliability" aria-hidden="true" class="aal_anchor" id="reliability"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Reliability</h3>



<p class="wp-block-paragraph">GraphOS is a critical part of our customers’ stack, so reliability is a critical concern for us at Apollo. Our customers need confidence that features like Uplink, the schema registry, and Contracts will be available. For cloud customers who trust Apollo to manage routing infrastructure in the critical path, this is even more important. On the <a href="https://www.apollographql.com/trust/reliability">Reliability page</a>, you can read more about how we approach matters like failovers, backups, and redundancy.</p>



<h3 class="wp-block-heading"><a href="#legal-and-privacy" aria-hidden="true" class="aal_anchor" id="legal-and-privacy"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Legal and privacy</h3>



<p class="wp-block-paragraph">Lastly, we’ve put all paperwork associated with legal and privacy compliance on the <a href="https://www.apollographql.com/trust/legal-and-privacy">Legal page</a>. There, you’ll find information about how Apollo’s legal team helps customers comply with the European Union’s GDPR, California’s Consumer Privacy Act, and more. Working with Apollo means one less scavenger hunt for privacy policies and data processing addendums.</p>



<h2 class="wp-block-heading"><a href="#finding-the-right-security-resources" aria-hidden="true" class="aal_anchor" id="finding-the-right-security-resources"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Finding the right security resources</h2>



<p class="wp-block-paragraph">Apollo’s Trust Center is designed to help you quickly and securely onboard Apollo into your stack and maintain our security health together each year.</p>



<p class="wp-block-paragraph">If you&#8217;re interested in Apollo GraphOS technical content about cross-origin request forgery protection, access control in the Apollo Router, and similar materials, check out the <a href="https://www.apollographql.com/resources">Resources portal</a>.</p>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next?</h2>



<p class="wp-block-paragraph">One of the most exciting offshoots of the Trust Center that we’re most excited about is creating new GraphOS security content. Security is one of the most requested topics customers ask us about and we can’t wait to talk about it. So go check out the <a href="https://www.apollographql.com/trust/">Trust Center</a>. Click around, download a security report, and explore. If you’ve got feedback, questions, or suggestions, we’d love to hear from you on the Apollo Community forum.</p>


Introducing the Apollo Trust Center


<p class="wp-block-paragraph">We’re building so much great stuff at Apollo that it can be tricky to keep track of it all! To help with that, we’re kicking off our Changelog series to cover exciting releases for GraphOS and our open-source projects. We’ll also let you know about upcoming live events and new educational content to help you expand and sharpen your graph expertise. So without further ado, let’s see what’s new!</p>



<h2 class="wp-block-heading"><a href="#boost-app-responsiveness-with-defer-in-graphos" aria-hidden="true" class="aal_anchor" id="boost-app-responsiveness-with-defer-in-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Boost app responsiveness with @defer in GraphOS</h2>



<p class="wp-block-paragraph">If a query includes a field that takes a long time to resolve, it can delay your graph’s entire response, making your apps feel less responsive. With GraphOS support for the @defer directive (now generally available!), your graph can respond to the client with most of the response data almost immediately, then follow up with slower fields when they’re ready.</p>



<p class="wp-block-paragraph">To learn more, check out <a rel="noreferrer noopener" href="https://www.apollographql.com/blog/announcement/platform/rethinking-react-components-with-defer/" target="_blank">the announcement blog post</a> and <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/graphos/routing/defer" target="_blank">the docs</a>. Make sure to set your graph’s federation version to 2.1 or higher in Apollo Studio!</p>



<figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2023/01/in_AdobeExpress.gif" alt="An animation shows the process of switching the federation version to 2.1 in Apollo Studio. First, click settings, then &quot;Edit Configuration&quot;, then change the &quot;Supergraph Pipeline Track&quot; to &quot;Federation 2.1 (default)&quot;. Finally, click &quot;Save&quot;." class="wp-image-19379" width="598" height="370"/></figure>



<h2 class="wp-block-heading"><a href="#livestreams-with-library-maintainers" aria-hidden="true" class="aal_anchor" id="livestreams-with-library-maintainers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Livestreams with library maintainers</h2>



<p class="wp-block-paragraph">This week we kicked off a new livestream series in the <a rel="noreferrer noopener" href="https://discord.gg/graphos" target="_blank">Apollo GraphQL Discord</a> where maintainers and community experts demonstrate building subgraphs with different libraries and languages. To start, we built a subgraph live using Python and <a rel="noreferrer noopener" href="https://strawberry.rocks/" target="_blank">Strawberry</a>. Next up, we’ll do the same with Rust and <a rel="noreferrer noopener" href="https://async-graphql.github.io/async-graphql/en/index.html" target="_blank">async-graphql</a> on February 22. All of our livestreams are in <a rel="noreferrer noopener" href="https://discord.gg/graphos" target="_blank">Discord</a>, so make sure to join so you don’t miss out!</p>



<h2 class="wp-block-heading"><a href="#graphos-introduction-video" aria-hidden="true" class="aal_anchor" id="graphos-introduction-video"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphOS introduction video</h2>



<p class="wp-block-paragraph">Your graph’s README page in <a rel="noreferrer noopener" href="https://studio.apollographql.com/" target="_blank">GraphOS Studio</a> now features a friendly introductory video and some handy links to help you get the most out of GraphOS from day one! Look for this section to the right of your README:<br></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="797" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM-797x1024.png" alt="A screen shot of a section of Apollo Studio titled &quot;New to GraphOS Studio?&quot;. It says &quot;Check out a few quick tips and links from the Apollo team, designed to get you up and running.&quot; There is then a still of a video showing Apollo studio, followed by three links: &quot;Get to know your supergraph&quot;, &quot;Automate tasks with Rover CLI&quot;, and &quot;Build custom tools with the GraphOS Platform API&quot;." class="wp-image-19381" srcset="https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM-797x1024.png 797w, https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM-233x300.png 233w, https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM-768x987.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM.png 856w" sizes="auto, (max-width: 797px) 100vw, 797px" /></figure>



<h2 class="wp-block-heading"><a href="#keeping-you-in-suspense" aria-hidden="true" class="aal_anchor" id="keeping-you-in-suspense"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Keeping you in suspense</h2>



<p class="wp-block-paragraph">Can’t wait to use React 18’s Suspense feature when fetching data with your GraphQL queries? Try our new <code class="" data-line="">useSuspenseQuery</code> hook today with <a rel="noreferrer noopener" href="https://www.npmjs.com/package/@apollo/client/v/3.8.0-alpha.5" target="_blank">Apollo Client 3.8.0-alpha.5</a>. Install it with <code class="" data-line="">npm i @apollo/client@alpha</code>, then check out <a rel="noreferrer noopener" href="https://github.com/apollographql/apollo-client/issues/10231" target="_blank">the RFC</a> for more details. We can’t wait to hear your feedback!</p>



<h2 class="wp-block-heading"><a href="#rapid-roundup" aria-hidden="true" class="aal_anchor" id="rapid-roundup"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Rapid roundup</h2>



<p class="wp-block-paragraph">Here are a few more changes and version updates you might want to check out:</p>



<ul class="wp-block-list">
<li><a href="https://github.com/apollographql/apollo-server/releases/tag/%40apollo%2Fserver%404.3.1" target="_blank" rel="noreferrer noopener">Apollo Server 4.3.1 was released with a few bug fixes</a></li>



<li><a href="https://github.com/apollographql/apollo-kotlin/releases/tag/v3.7.4" target="_blank" rel="noreferrer noopener">Apollo Kotlin 3.7.4 shipped with some minor improvements</a></li>



<li><a href="https://github.com/apollographql/apollo-client/releases/tag/v3.7.4" target="_blank" rel="noreferrer noopener">Apollo Client 3.7.4 squashed some bugs</a></li>



<li><a href="https://github.com/apollographql/apollo-ios/releases/tag/1.0.6">Apollo iOS 1.0.6 addressed some community requests and bugs </a></li>



<li><a rel="noreferrer noopener" href="https://github.com/apollographql/apollo-rs/releases/tag/apollo-compiler%400.6.0" target="_blank">apollo-compiler 0.6.0 brings API enhancements to your Rust code</a></li>



<li>All GraphOS <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/graphos/routing/cloud" target="_blank">cloud supergraphs</a> have been updated to use version <a rel="noreferrer noopener" href="https://github.com/apollographql/router/releases/tag/v1.6.0" target="_blank">1.6.0</a> of the Apollo Router</li>



<li><a rel="noreferrer noopener" href="https://www.apollographql.com/docs/technotes/TN0029-relay-style-connections/" target="_blank">We’ve added an FAQ about Relay Connections</a> to our tech notes</li>



<li>You can now <a rel="noreferrer noopener" href="https://github.com/apollographql/hack-the-supergraph#deploy-to-railway-and-graphos" target="_blank">deploy our “Hack the Supergraph” example</a> to Railway with just a couple of clicks using a template</li>
</ul>



<h2 class="wp-block-heading"><a href="#performance-corner" aria-hidden="true" class="aal_anchor" id="performance-corner"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Performance corner</h2>



<p class="wp-block-paragraph">Are you using data loaders in all of your graph’s resolvers? If you aren’t yet, learn all about <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/federation/entities-advanced/#handling-the-n1-problem" target="_blank">handling the N+1 problem</a>.</p>



<p class="wp-block-paragraph">That’s all for now! We’ll be back soon with another update. In the meantime, <a href="https://discord.gg/graphos" target="_blank" rel="noreferrer noopener">join our Discord server</a> to stay up to date with future programs and announcements. That’s also where you can give us feedback on this new format and request changes or additions. Happy querying!</p>


Announcement