Enhance customer experiences with Apollo GraphOS


<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">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"><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

Deep Dive: Telemetry cardinality in the Apollo GraphOS Router

Introducing Response Caching: GraphQL‑aware performance for your graph 


<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

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


<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">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


<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 GraphOS now supports custom schema checks, a new feature that addresses API platform teams’ demand for enhanced schema governance capabilities. This functionality allows organizations to integrate their own business logic, security policies, and rules into Apollo&#8217;s existing schema check workflow, ensuring that every schema change adheres to company-specific standards. The result is a more robust, flexible, and secure approach to maintaining schema integrity, allowing platform teams to uphold organizational standards in an automated manner while adhering to stringent organizational requirements.</p>



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



<p class="wp-block-paragraph">API governance encompasses the policies and standards that an engineering organization employs to secure, standardize, and maintain its APIs over time. Engineers utilize various methods to manage changes to their APIs, one of which involves centralizing a space where these policies can be enforced. Governance policies may cover non-functional requirements, like enforcing style guidelines and ensuring that all changes align with established standards, or more complex workflows, such as conducting automated testing and leveraging historical data to ensure backward compatibility.</p>



<p class="wp-block-paragraph">GraphOS currently offers several tools that help automate API governance, including operation checks, schema linting, composition checks, and proposal checks. <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/checks#operations-checks">Operation checks</a> compare proposed schema changes against historical operations to verify whether the changes break any of your graph&#8217;s active clients. <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/linting">Schema linting</a> allows you to configure style guidelines and analyze proposed schema changes for violations of formatting rules. <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/proposals/configure#configure-schema-checks">Proposal checks</a> validate whether your proposed schema changes have matching and approved schema proposals, and finally, <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/contracts/create#run-contract-checks">downstream checks</a> ensure that proposed schema changes don’t break any downstream contract variants.</p>



<p class="wp-block-paragraph">As organizations grow and APIs scale, there are going to be facets of governance that extend outside the realm of what is offered by GraphOS. Because of this, we built custom schema checks to offer a hook into the GraphOS schema check workflow to support the injection of custom business logic or rules. This allows users to implement their own checks and push results into GraphOS for viewing in Studio while maintaining a unified check workflow, acting as a safeguard within their continuous integration pipelines for schema modifications.</p>



<h2 class="wp-block-heading"><a href="#how-to-set-up-a-custom-check" aria-hidden="true" class="aal_anchor" id="how-to-set-up-a-custom-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>How to set up a custom check</h2>



<p class="wp-block-paragraph">Custom schema checks require an HTTPS endpoint that is accessible over the public internet. We offer an <a href="https://github.com/apollosolutions/custom-check-examples/">example implementation</a> for using an open-source linter, graphql-eslint, to lint the subgraph schemas modified by the check request. This sample is set up as a <a href="https://www.netlify.com/platform/core/functions/">Netlify function</a> but could be adapted to run on any serverless architecture or containerized system.</p>



<p class="wp-block-paragraph">After checking out the code and following the steps in the README to deploy it, we can enable it in Studio through the custom check configuration page. After that, we can test our integration with an empty payload by clicking the “Send test notification” button.</p>



<p class="wp-block-paragraph"><img loading="lazy" decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXehd-VSLdSR_OZrwz45lg6SrCzrFhXFWqk3p3zrWoK7UHaSyrSMx_NofzLLK3lv2VWJ8BASrQlvjilWz2bPXot46a4tyGY3QkH545hKAfADdpzJpQ_RmZsquTrh4ixK6lxhlpgCmYnyF2wfMTH1q_HNpYM?key=4rXqpQwA4wPdxVzCiNTZCg" width="624" height="231"></p>



<p class="wp-block-paragraph">If everything looks good in the function logs, we can then run a schema check using the <a href="https://www.apollographql.com/docs/rover/commands/subgraphs#subgraph-check">rover CLI</a>, and our endpoint will be called.&nbsp;</p>



<p class="wp-block-paragraph"><img loading="lazy" decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfCrh2mn7VqyiPQFAfOt7DNjOemAoloWaVDCdIQfrZcc58j-mOs7GgR1qeAllY5hJ6xs9_OB2qKY7NZ2a0oaDpdmFY5tlqkqA5nTownCtu9tKRe8R4Zfe2PwFgKQ-T-OnQMZql46balKGyyhIeueQLeIMur?key=4rXqpQwA4wPdxVzCiNTZCg" width="624" height="305"></p>



<p class="wp-block-paragraph">The schema information will be passed to our endpoint, which will lint the schema and return the results to GraphOS. These results from our custom check task will be stored and viewable in Studio.</p>



<p class="wp-block-paragraph"><img loading="lazy" decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdl2aDeG2Jt8a9ideekPxnipH8qTElM7O1abofJAfqnTMsHGjhAfoQ8KS4MfNN7smuQyrXZbqXabngEhSuCHkALw2L8Icj0bRb_Y3wOy1L2ETqcdSa0Ns8ibiiXRsoMWtDJrvgkdcG7KXskmgziWFjt3WPC?key=4rXqpQwA4wPdxVzCiNTZCg" width="624" height="333"></p>



<p class="wp-block-paragraph">The architecture we recommend for a custom check worker consists of two main components: one to receive the payload and the second to execute the business logic.</p>



<p class="wp-block-paragraph">The first component is responsible for receiving the <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/checks/custom#webhook-format">webhook payload</a> containing the metadata of the check request. It places this information onto a worker queue and promptly responds with a 200 OK status. This response indicates to GraphOS that the check request has been received.</p>



<p class="wp-block-paragraph">The second component retrieves check requests from the queue and executes the necessary business logic, such as downloading schemas, performing custom linting, or implementing other schema governance tasks, and then calls back to the GraphOS Platform API with the results of the custom check.</p>



<p class="wp-block-paragraph">There is no need to perform a custom check synchronously because the state machine that manages schema check workflows will wait up to 10 minutes for the callback mutation to be received. If no callback is received, the custom check tasks will be marked as failed with a timeout.&nbsp;</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">With custom schema checks, API platform teams can integrate their own custom business logic, security policies, and governance rules into the schema check workflow. This feature improves an API governance posture by allowing organizations to enforce company-specific standards, automate schema validation, and maintain a unified, flexible workflow for schema modifications. Custom checks are now available in GA for GraphOS Enterprise plans.<br>If you want to enable the custom configuration for your graph, head to the “Checks” tab in GraphOS Studio → Configuration → Custom checks. Or, if you haven’t set up schema checks yet for your graph, check out the <a href="https://www.apollographql.com/docs/graphos/delivery/schema-checks">documentation</a> to get started.</p>


Enforce Flexible Governance in GraphOS using Custom Checks


<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">Today, we’re excited to announce improvements to the GraphOS local development experience. These improvements make it faster for developers to contribute to the supergraph using the <a href="https://www.apollographql.com/docs/rover/">Rover CLI</a>. Rover provides all the functionality you need to compose schemas, test changes locally, and publish schemas to the GraphOS schema registry. And with today’s release, testing changes locally gets even faster.</p>



<h3 class="wp-block-heading"><a href="#get-started-locally-in-seconds-with-subgraph-mirroring" aria-hidden="true" class="aal_anchor" id="get-started-locally-in-seconds-with-subgraph-mirroring"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 locally in seconds with subgraph mirroring</strong></h3>



<p class="wp-block-paragraph">We heard from customers that they wanted to make it faster for new contributors to get up and running with a copy of their supergraph locally. <a href="https://www.apollographql.com/docs/rover/commands/dev/">Rover dev</a> is the CLI command that enables developers to spin up a local router instance and test changes to their graph; and now it supports <a href="https://www.apollographql.com/docs/rover/commands/dev//#starting-a-session-from-a-graphos-studio-variant">subgraph mirroring</a>. Subgraph mirroring makes it easy to bootstrap a locally running supergraph in seconds. Just pull down subgraph routing URLs and schemas from a GraphOS Studio variant to your rover dev session, and get started.</p>



<p class="wp-block-paragraph">Previously, you had to manually <a href="https://github.com/apollosolutions/supergraph-yaml-generator">generate</a> and maintain a supergraph config that contained all your routing URLs and subgraph schemas. For teams maintaining supergraphs with dozens or hundreds of subgraphs, rover dev with graph ref support drastically reduces time spent getting up and running locally.  As an additional perk, subgraph mirroring saves subgraph contributors who aren’t Federation experts from wasting time writing or debugging supergraph configs.</p>



<p class="wp-block-paragraph">To start a local router instance using a GraphOS Studio variant, include the variant&#8217;s graph ref with the &#8211;graph-ref option like so:</p>



<pre class="wp-block-code"><code class="" data-line="">rover dev --graph-ref platform@staging</code></pre>



<h3 class="wp-block-heading"><a href="#quickly-test-subgraph-changes-before-publishing" aria-hidden="true" class="aal_anchor" id="quickly-test-subgraph-changes-before-publishing"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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>Quickly test subgraph changes before publishing</strong></h3>



<p class="wp-block-paragraph">Subgraph mirroring is particularly useful when testing subgraph changes or adding new subgraphs altogether. The &#8211;graph-ref option also supports passing a supergraph config so you can override specific subgraphs or test new Federation versions. For example, if you’re moving a type or modifying an entity, you may want to test these schema changes locally before publishing them. Now, you can maintain a simpler supergraph config with just the subgraphs you want to override. In the example below, we can override the movies subgraph for your theater booking service:</p>



<pre class="wp-block-code"><code class="" data-line="">subgraphs:
&nbsp;&nbsp;&nbsp;movies:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;routing_url: http://localhost:4000
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;schema:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;file: ./movies.graphql</code></pre>



<p class="wp-block-paragraph">And then with the command:</p>



<pre class="wp-block-code"><code class="" data-line="">rover dev --graph-ref platform@staging --supergraph-config subgraphs.yaml</code></pre>



<h3 class="wp-block-heading"><a href="#wait-theres-more" aria-hidden="true" class="aal_anchor" id="wait-theres-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><strong>Wait, there’s more!</strong></h3>



<p class="wp-block-paragraph">Alongside subgraph mirroring, we’ve been hard at work increasing the release cadence for Rover and have tackled some long standing customer requests. In the previous v0.24 release, we shipped a host of quality-of-life improvements like more helpful linting messages, better support for router customizations, native Apple Silicon binaries, a bug fix for managing your Rover installation with pnpm/npm, and <a href="https://github.com/apollographql/rover/pull/1973">several other fixes</a>.</p>



<p class="wp-block-paragraph">Subgraph mirroring brings Studio and Rover closer together, and we’re working on other major improvements to the Federation contributor experience across all of Apollo’s local development tools including Sandbox, Explorer, and Rover. We’d love to <a href="mailto:cloud@apollographql.com">hear from you</a> if you have any feedback on your experience developing a federated supergraph.</p>



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


Accelerating graph development with subgraph mirroring in the Rover CLI


<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">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">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">Apollo doesn’t just build Federation – we use it internally as well. Like many of our customers, we recently upgraded a fleet of Apollo Gateway instances to Apollo Router. This fleet ran the superschema for our &#8220;Apollo Studio&#8221; graph in multiple variants: development, staging, and production.</p>



<p class="wp-block-paragraph">Our team recently upgraded to the Apollo Router with very positive results which we’d like to share alongside some helpful tips.</p>



<h2 class="wp-block-heading"><a href="#replacing-a-gateway-with-the-apollo-router" aria-hidden="true" class="aal_anchor" id="replacing-a-gateway-with-the-apollo-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><strong>Replacing a Gateway with the Apollo Router</strong></h2>



<p class="wp-block-paragraph">The Apollo Router is Apollo&#8217;s replacement for the Gateway @apollo/gateway, and provides higher performance with lower resource consumption. It was an easy choice to replace the existing gateway fleets with new router fleets to serve the various Apollo Studio graph variants.</p>



<p class="wp-block-paragraph">Migrating from gateway to router requires a bit of a mindset shift. The gateway is essentially a JavaScript toolkit intended to be highly customizable with all users providing their own customizations for their own particular execution environment. The Apollo Router is a product. It leverages the experience and knowledge of Apollo to provide a performant, scalable GraphQL Federation experience while still offering customization to users.</p>



<p class="wp-block-paragraph">Apollo had deployed a highly customized gateway and migrating to the router was largely a task of mapping custom gateway functionality to standard router functionality. Most of this was driven by router configuration (header forwarding). We also wrote a Rhai script for simple header and cookie manipulation and a coprocessor that provided custom logging in a different language (TypeScript).</p>



<p class="wp-block-paragraph">Once we had figured out how to migrate our custom gateway functionality, it was then simple to adopt the standard router container image and deploy this via a custom Helm chart which leveraged the standard router Helm Chart to do the heavy lifting. You can read more details about this in the Kubernetes section below.</p>



<p class="wp-block-paragraph">Because the router provides a standard, configuration-driven execution environment, it is simpler to utilize standard tools such as Helm to manage deployments. This drive to standardization delivers benefits to Apollo in terms of product feature development speed and for customers, since it is much simpler to deploy a standard router than it is to develop and deploy your own custom gateway.</p>



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



<p class="wp-block-paragraph">When Apollo migrated to the Apollo Router, we were looking for improvements in resilience, scalability, responsiveness, and resource consumption. Let&#8217;s take a look at some of the details of our migration.</p>



<h3 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><strong>Resources</strong></h3>



<p class="wp-block-paragraph">Our router CPU consumption is approximately 60% that of the gateway. Router memory consumption is approximately 13% of the gateway. That&#8217;s a substantial operational cost-saving reduction.</p>



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



<p class="wp-block-paragraph">Our existing gateway configuration is fairly consistent across our three environments. Since there is no standard Helm Chart for deploying the gateway, we have a custom deployment mechanism and this doesn&#8217;t take advantage of features such as affinity, pod disruption budgets, or autoscaling. There is minimal variation in CPU and memory requests with a varying number of fixed deployments of each according to environment.</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Environment</strong></td><td><strong>Instances</strong></td><td><strong>CPU (Request, Limit)</strong></td><td><strong>Memory (Request, Limit)</strong></td></tr><tr><td>Development</td><td>1</td><td>0.25, 1</td><td>512Mi, 512Mi</td></tr><tr><td>Staging</td><td>30</td><td>0.25, 1</td><td>2Gi, 2Gi</td></tr><tr><td>Production</td><td>40</td><td>0.5, 1</td><td>2Gi, 2Gi</td></tr><tr><td><strong>Totals</strong></td><td><strong>71</strong></td><td><strong>27.75, 71</strong></td><td><strong>140.5Gi, 140.5Gi</strong></td></tr></tbody></table></figure>



<p class="wp-block-paragraph">The &#8220;Totals&#8221; figures are approximate and based on the observation that resource consumption measurements indicate that for most of the time requested resource is sufficient.</p>



<p class="wp-block-paragraph">There are no affinity, pod disruption budgets or autoscaling configuration.</p>



<h4 class="wp-block-heading"><a href="#router" aria-hidden="true" class="aal_anchor" id="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><strong>Router</strong></h4>



<p class="wp-block-paragraph">The Apollo Router comes with a maintained Helm chart which makes it simple to set features such as pod disruption budgets, affinities, autoscaling, and many other enterprise Kubernetes features. We take advantage of the router Helm chart to vary the resource requirements across environments with more flexibility than we have with our gateway.</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Environment</strong></td><td><strong>Instances</strong></td><td><strong>CPU (Request, Limit)</strong></td><td><strong>Memory (Request, Limit)</strong></td></tr><tr><td>Development</td><td>2-12</td><td>0.7, 1.5</td><td>1.5Gi, 1.5Gi</td></tr><tr><td>Staging</td><td>2-12</td><td>2, 3.5</td><td>1.5Gi, 2Gi</td></tr><tr><td>Production</td><td>3-12</td><td>4, 6</td><td>4Gi, 5Gi</td></tr><tr><td><strong>Totals</strong></td><td><strong>7-36</strong></td><td><strong>17.4, 28</strong></td><td><strong>18Gi, 22Gi</strong></td></tr></tbody></table></figure>



<p class="wp-block-paragraph">I&#8217;ve aggregated the requests and limits for the main containers within a router pod: router and the coprocessor. The resources are approximately 50/50 for each container.</p>



<p class="wp-block-paragraph">Because we are using horizontal pod autoscaling (HPA) with the router, it&#8217;s harder to calculate the &#8220;Totals&#8221; figure. However, we note that autoscaling is never triggered in development or staging. In production it is triggered, but fairly infrequently, so that the net result is approximately the same as running 3 routers constantly.</p>



<p class="wp-block-paragraph">The router is configured to have affinity with our Istio mesh ingresses, anti-affinity with other router pods (to improve node throughput and reliability) and we have a pod disruption budget set to a maximum unavailability of 1 (to improve reliability). We have configured horizontal pod autoscaling from a minimum of 2 (3 in production) and a maximum of 12, with triggering set for 75% CPU consumption.</p>



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



<p class="wp-block-paragraph">The primary measure of responsiveness is request duration, as measured from arriving at the router from a client to sending the response to the client.</p>



<figure class="wp-block-table"><table><tbody><tr><td><strong>Federator</strong></td><td><strong>Average Response Time (ms)</strong></td></tr><tr><td>Gateway</td><td>510</td></tr><tr><td>Router</td><td>165</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">We couldn&#8217;t directly compare gateway and router responsiveness over the exact same time interval since we were not mirroring traffic but directing traffic to one or the other. For purposes of this comparison, we collected the data on multiple, separate days across the same time period (8 hours) in each day and averaged the results.</p>



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



<p class="wp-block-paragraph">Our production workload varies over the course of 24 hours, with a peak during U.S. working hours and quieter times during the rest of the day. In a typical week, we are processing about 70M requests.</p>



<p class="wp-block-paragraph">In this scenario, we&#8217;re measuring Client Request Rate per Second (RRS). We have sized our router fleet based on the following data:</p>



<p class="wp-block-paragraph">Average RRS: 115 (70M / 604800) Peak RRS: 815 Baseline Subgraph Latency: 150ms Average Client Request Size: 1k Average Client Response Size: 1m Number of Instances: 3 &#8211; 12</p>



<h2 class="wp-block-heading"><a href="#kubernetes" aria-hidden="true" class="aal_anchor" id="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><strong>Kubernetes</strong></h2>



<p class="wp-block-paragraph">We use Helm to manage our Kubernetes router fleet. We have an Apollo in-house Helm chart which provides Apollo-specific configuration details such as:</p>



<ul class="wp-block-list">
<li>Rhai Scripts</li>



<li>Istio configuration</li>
</ul>



<p class="wp-block-paragraph">The in-house Helm chart makes use of the Router Helm Chart to provide most of the heavy lifting for the configuration of:</p>



<ul class="wp-block-list">
<li>Router (header propagation, max request sizes, introspection, etc&#8230;)</li>



<li>Standard Kubernetes Functionality (Resources, Affinity, Pod Disruption Budgets, Sidecars, etc&#8230;)</li>
</ul>



<p class="wp-block-paragraph">We separate our Helm configuration files (values.yaml) into a common file and an environment-specific file. We make use of the fashion in which Helm progressively applies values, by ordering the files for application with common values first and environment-specific values following later in the command.</p>



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



<p class="wp-block-paragraph">The router ships with a lot of observability for tracing, metrics, and logging. Most of this is easily configurable or can be enhanced with Rhai scripts or external coprocessors.</p>



<p class="wp-block-paragraph">We use <a href="https://www.datadoghq.com/" data-type="link" data-id="https://www.datadoghq.com/">DataDog</a> to visualize the captured metrics.</p>



<h2 class="wp-block-heading"><a href="#getting-started-with-the-apollo-router" aria-hidden="true" class="aal_anchor" id="getting-started-with-the-apollo-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><strong>Getting started with the Apollo Router</strong></h2>



<p class="wp-block-paragraph">Apollo has many resources to help you get up and running with the Apollo Router.&nbsp;</p>



<ul class="wp-block-list">
<li>Watch this Apollo tech talk to <a href="https://www.apollographql.com/events/tech-talk/extending-apollo-router-3/">learn more about the Apollo Router’s extensibility model</a>.</li>



<li><a href="https://www.apollographql.com/events/champions-corner/how-wayfair-slashed-costs-simplified-infra-and-cut-latency-in-half-with-apollo-router/">This Champions Corner with Wayfair</a> discusses how they scaled their router during Black Friday.</li>



<li><a href="https://www.apollographql.com/docs/router/">The updated docs</a> now include more how-tos and reference guides for <a href="https://www.apollographql.com/docs/router/containerization/kubernetes/">deploying the Apollo Router in Kubernetes</a>.</li>
</ul>



<p class="wp-block-paragraph">You can also connect with us as well as other users in our <a href="https://events097286.typeform.com/joincommunity">Apollo Champions Slack community</a>. You can also <a href="https://discord.com/invite/VZNZV2ujaY" data-type="link" data-id="https://discord.com/invite/VZNZV2ujaY">find us on Discord</a> if you prefer that channel.  Let us know if you have any questions!</p>


Deploying the Apollo Router at Apollo


<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">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">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">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

Federated subscriptions in GraphOS: real-time data at scale


<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">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">Since the rise of the frontend framework and the framework wars of the 2010s, we’ve all gotten pretty used to the idea of building single-page apps that load a JavaScript bundle and then send queries to a server dynamically as a user clicks around. The move to single-page apps was driven by the need to create faster, more interactive user experiences.</p>



<p class="wp-block-paragraph">As with every great innovation, solving one problem just opens your eyes to the next one. As we all settled into the new normal of building apps with UI frameworks, the next major challenge presented itself: data fetching. Over the last 6 years, GraphQL has once again innovated on the frontend developers&#8217; experience, bringing UI-driven API design, automatic state management, strong types, and much more to the world of building interfaces.</p>



<p class="wp-block-paragraph">And as someone who’s been building apps with GraphQL for a while, there’s one major ergonomic thing that has bothered me all that time: the relationship between queries and component structure. It’s common to create symmetry between the shape of a GraphQL query and the data that’s rendered in a UI component, but up until now, there has been no way to decouple the query itself from the importance of each field it holds. If you want some fields to load faster than others, or you know there’s a slow field and you don’t want your whole query’s response to be held up, you have to split those into multiple queries. This creates a lot of spaghetti code in components; something simple from a UI and schema design perspective just got complicated due to server implementation.</p>



<p class="wp-block-paragraph">This isn’t a GraphQL problem–we had it with REST too–but GraphQL is uniquely positioned to solve it because we can annotate each field with metadata!</p>



<p class="wp-block-paragraph"><strong>Introducing, <code class="" data-line="">@defer</code></strong></p>



<p class="wp-block-paragraph">&nbsp;<code class="" data-line="">@defer</code> is a directive you can add to queries that will tell your server it can respond to this query in multiple parts. Do you know a particular field is slow? Defer it! This means your server can respond with an initial response to your end-user much faster and fill in the rest when it gets there.</p>



<p class="wp-block-paragraph">For the last several months, we’ve been working to support <code class="" data-line="">@defer</code> across the Apollo stack, and today we’re excited to announce full supergraph support for&nbsp;<code class="" data-line="">@defer</code> in GraphOS.<em> </em>You don&#8217;t even need to make any changes to your existing GraphQL API to use it, <em>it just works</em>.</p>



<h2 class="wp-block-heading"><a href="#using-defer-with-your-existing-graphql-api" aria-hidden="true" class="aal_anchor" id="using-defer-with-your-existing-graphql-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><strong>Using <code class="" data-line="">@defer</code> with your existing GraphQL API</strong></h2>



<p class="wp-block-paragraph">To use <code class="" data-line="">@defer</code>, you just need to have a supergraph router between your GraphQL server and your client (even if you only have one GraphQL server that isn’t using Apollo Federation). The easiest way to create a router is to set up a free serverless instance of Apollo Router with <a href="https://apollographql.com/graphos/">Apollo GraphOS</a>. You can also use <a href="https://www.apollographql.com/docs/rover">Rover</a>, the GraphOS CLI, to start up a local instance of the router. <code class="" data-line="">@defer</code> can be used on the root <code class="" data-line="">Query</code> field and the router will break the query into multiple GraphQL requests. We can test this out using <strong>any</strong> GraphQL endpoint and <code class="" data-line="">rover dev</code>.</p>



<p class="wp-block-paragraph">In this post, we will use the SpaceX API to see how this works. Remember, the SpaceX example <em>does not</em> use Apollo Federation. First, we use the <code class="" data-line="">rover dev</code> command to start up a local instance of the router pointing at <a href="https://spacex-production.up.railway.app/">https://spacex-production.up.railway.app/</a>:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">rover dev --name=spacex --url=https://spacex-production.up.railway.app/</code></pre>



<p class="wp-block-paragraph">Now you can open up <a href="http://localhost:3000">http://localhost:3000</a> and try executing a query using <code class="" data-line="">@defer</code> on the root <code class="" data-line="">Query</code>:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql" data-line="">query Launches {
  launches {
    id
    details
    rocket {
      rocket_name
    }
  }
  ... @defer {
    deferredLaunchDetails: launches {
      id
      upcoming
    }
  }
}</code></pre>



<p class="wp-block-paragraph">Notice we&#8217;re aliasing the root query field to isolate a single field. An upgraded query planner instructs the router to fetch the deferred portions of a query:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="726" height="512" src="https://wp.apollographql.com/wp-content/uploads/2023/01/spacex-defer-queryplan.png" alt="A Query Plan showing two fetch requests to the SpaceX API where one fetch is being deferred" class="wp-image-19235" srcset="https://wp.apollographql.com/wp-content/uploads/2023/01/spacex-defer-queryplan.png 726w, https://wp.apollographql.com/wp-content/uploads/2023/01/spacex-defer-queryplan-300x212.png 300w" sizes="auto, (max-width: 726px) 100vw, 726px" /></figure>



<p class="wp-block-paragraph">We can see that the generated query plan shows the router breaking our query into two requests to the SpaceX GraphQL API. Now you can <code class="" data-line="">@defer</code> any field in your current API without making any changes 🚀</p>



<h2 class="wp-block-heading"><a href="#using-defer-on-any-entity-in-the-supergraph" aria-hidden="true" class="aal_anchor" id="using-defer-on-any-entity-in-the-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><strong>Using <code class="" data-line="">@defer</code> on any Entity in the supergraph</strong></h2>



<p class="wp-block-paragraph">When <a href="https://www.apollographql.com/docs/federation/entities/">entities</a> are used in the supergraph, they define an additional execution boundary for the deferred portions of a query with additional benefits like being able to <code class="" data-line="">@defer</code> on nested fragments within a single root query.</p>



<p class="wp-block-paragraph">Entities in the supergraph are traditionally used to split the implementation of an entity into multiple subgraph modules for a better <a href="https://www.apollographql.com/docs/federation/#separation-of-concerns">separation of concerns</a>. The supergraph router can then perform API-side joins by fetching the entity data from individual subgraphs and flattening the results into the requested query shape.</p>



<p class="wp-block-paragraph">Since the Router uses the existing <a href="https://www.apollographql.com/docs/federation/subgraph-spec/">subgraph specification</a> supported in <a href="https://www.apollographql.com/docs/federation/supported-subgraphs/">over 24 languages and frameworks</a>, app developers can start using <code class="" data-line="">@defer</code> in their client queries without any backend changes to existing subgraphs.</p>



<p class="wp-block-paragraph">In this post, we&#8217;re going to use the <a href="https://github.com/apollographql/hack-the-supergraph">Apollo Hack the Supergraph demo</a> for the hosted subgraphs. We&#8217;ll still use <code class="" data-line="">rover dev</code> to try this out. In separate terminal windows, start a rover dev session for these subgraphs:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash" data-line="">rover dev --name=products --url=https://hts-products-production.up.railway.app/

# In a new terminal window
rover dev --name=reviews --url=https://hts-reviews-production.up.railway.app/</code></pre>



<p class="wp-block-paragraph">Now you can open up <a href="http://localhost:3000">http://localhost:3000</a> and try executing a query using <code class="" data-line="">@defer</code> on the product reviews:</p>



<pre class="wp-block-prismatic-blocks"><code class="" data-line="">fragment ProductReviewsFragment on Product {
  reviews {
    content
  }
}

query ExampleQuery {
  products {
    id
    title
    description
    price {
      amount
    }
    ...ProductReviewsFragment @defer
  }
}</code></pre>



<p class="wp-block-paragraph">You should see the <code class="" data-line="">data.products.reviews</code> be deferred in the response and query plan:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1918" height="834" src="https://wp.apollographql.com/wp-content/uploads/2023/01/@defer-gif.gif" alt="" class="wp-image-19289"/></figure>



<h2 class="wp-block-heading"><a href="#start-using-defer-today" aria-hidden="true" class="aal_anchor" id="start-using-defer-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 using <code class="" data-line="">@defer</code> today</strong></h2>



<p class="wp-block-paragraph">The easiest way to get started with the Apollo Router is to <a href="https://www.apollographql.com/docs/graphos/quickstart/cloud">create a serverless instance</a> with <a href="https://studio.apollographql.com/signup?referrer=blog">GraphOS</a>. Once you&#8217;ve added your existing GraphQL API in GraphOS, you&#8217;ll need to be on the latest version of Apollo Client (<a href="https://www.apollographql.com/docs/react/data/defer/">React</a>, <a href="https://www.apollographql.com/docs/kotlin/fetching/defer/">Kotlin</a>, <a href="https://github.com/apollographql/apollo-ios/issues/2395">iOS support coming soon</a>). That&#8217;s it, you can start using <code class="" data-line="">@defer</code> in your apps 🎉.</p>



<p class="wp-block-paragraph">Want to dig deeper into <code class="" data-line="">@defer</code> and GraphOS? <a href="https://discord.gg/graphos">Join our Discord</a> to continue the discussion! We’ll be live streaming about this topic and more!</p>


Rethinking React components with @defer


<p class="wp-block-paragraph">As of today, you can now use our new public API to integrate with the Apollo GraphOS platform.</p>



<p class="wp-block-paragraph">We built this API to enable those using GraphOS to easily automate operations in their own systems and CI workflows. In fact, this is the same API that the <a href="https://www.apollographql.com/docs/rover/">Rover CLI</a> uses to run schema checks and publish schemas to Apollo Studio.</p>



<p class="wp-block-paragraph">Under the hood, the GraphOS platform API uses schema <a href="https://www.apollographql.com/blog/announcement/platform/contracts-are-now-generally-available/">contracts</a> to make our private platform API publicly available. By creating a contract, we can filter out the necessary subset of our private platform API schema, all the while keeping the public schema in sync with the source.</p>



<p class="wp-block-paragraph">See the <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main">API’s readme</a> to get started, and check out the operation collections in Explorer to see example GraphQL queries and mutations you can use for your own graphs.&nbsp;</p>



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



<p class="wp-block-paragraph">So, let’s try it out! We’ve embedded the API’s Explorer from Studio below. (Yes, you can <a href="https://www.apollographql.com/docs/studio/explorer/embed-explorer/">embed the Explorer</a> for any of your graphs managed in Studio!)&nbsp;</p>



<p class="wp-block-paragraph">Here are some examples of what you can do with the GraphOS platform API:</p>



<ul class="wp-block-list"><li>Retrieve a list of your GraphQL supergraphs</li><li>Fetch a graph for a specific environment (such as staging)</li><li>Publish your supergraph’s schema</li><li>Check your supergraph’s schema for errors</li></ul>



<p class="wp-block-paragraph">Note: Some of these operations, like publishing a new graph, require that you set your own Studio API key. See the <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main">readme</a> for instructions.&nbsp;<br>Check out our operations collections and try running some queries, read the API’s inline documentation, or see the <a href="https://studio.apollographql.com/public/apollo-platform/schema/reference?variant=main">schema reference</a> to view all the API’s types and fields:</p>



<div style="width: 100%; height: 500px;" id="embedded-explorer"></div>
<script src="https://embeddable-explorer.cdn.apollographql.com/_latest/embeddable-explorer.umd.production.min.js"></script> 
<script>
  new window.EmbeddedExplorer({
    target: '#embedded-explorer',
    graphRef: 'apollo-platform@main',
    persistExplorerState: true,
    initialState: {
      document: ` # Fetches basic details about a single Studio graph
# by its ID.
#
# By default, this fetches details for the
# apollo-platform graph and its main variant, 
# which you're currently querying! You can provide a 
# different graph ID in the Variables panel.
#
# ⚠️ If you provide a non-public graph ID, you
#    need to provide a valid API key in the
#    X-API-KEY header!
query GetGraph($graphId: ID!, $name: String!) {
  graph(id: $graphId) {
    id
    title
    myRole # Null if querying a public graph anonymously
    variant(name: $name) {
      id
      url
    }
  }
}`,
      variables: {
  "graphId": "apollo-platform",
  "name": "main"
},
      headers: {"apollographql-client-name":"explorer","apollographql-client-version":"1.0"},
      displayOptions: {
        showHeadersAndEnvVars: true, 
        docsPanelState: 'closed', 
        theme: 'dark',
      },
    },
  });
</script>



<h2 class="wp-block-heading"><a href="#when-to-use-the-api-and-when-to-use-rover" aria-hidden="true" class="aal_anchor" id="when-to-use-the-api-and-when-to-use-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>When to use the API and when to use Rover</h2>



<p class="wp-block-paragraph">In most cases, you’ll want to use the Apollo Rover CLI to manage and publish your GraphQL supergraph schema. As developers iterate on their subgraphs, we recommend regularly running schema checks to ensure that their updated graphs properly compose into a supergraph. If you use continuous integration (CI), we recommend integrating Rover into your pipeline. <a href="https://www.apollographql.com/docs/rover/ci-cd">Here’s how to get started</a>.</p>



<p class="wp-block-paragraph">If you need to do more complex operations, then you might want to use the GraphOS platform API. For instance, you might want your CI pipeline to create a new Studio variant for each test run, then delete that variant when the run finishes. To accomplish this, you can do the following using the Platform API:</p>



<ul class="wp-block-list"><li>Create a test variant by <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main#publishing-schemas">Publishing your schema(s) to it</a>.</li><li>Perform any desired tests (such as <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main#running-schema-checks">schema checks</a>) on the test variant.</li><li>Delete the variant with the corresponding <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main#destructive-actions">destructive action</a>.</li></ul>



<p class="wp-block-paragraph">In the near future, we will post about other ways to integrate with the GraphOS platform, such as using the platform API with your governance workflows for your supergraphs. We also look forward to learning how you will use the API!</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">This is just the start for the GraphOS platform API! We are continuing to add new features to both GraphOS and the platform API to make it easier for you to get your schema changes safely to production, to keep your teams up-to-date, and to ensure that clients consuming your graph never experience breaking changes.</p>



<p class="wp-block-paragraph">To stay up-to-date on what’s coming next with the GraphOS platform API, <a href="https://github.com/apollographql/apollo-studio-community">star and watch the Apollo Studio Community GitHub project</a>. We will be sharing more about the GraphOS platform API roadmap there and here in the Apollo blog.</p>



<p class="wp-block-paragraph">You can help us by letting us know what you’d like added to the API by creating a GitHub issue or by giving us feedback in the <a href="https://community.apollographql.com/">Apollo Community</a>.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#get-started-with-graphos" aria-hidden="true" class="aal_anchor" id="get-started-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>Get started with GraphOS</h2>



<p class="wp-block-paragraph">Still getting started with a single GraphQL server or new to GraphQL? No problem. We&#8217;ve made it easier than ever to leverage all of the analytics and automation of supergraphs in Studio. <a href="https://apollographql.com/tutorials?ref=www">Create your first graph</a> and make your first graph query in under an hour.</p>


Integrate with GraphOS using the new Platform API


<p class="wp-block-paragraph">When we built Apollo in 2016, we had a vision. We set out to build one distributed and scalable data layer that could connect to anything we need, no matter the client, the architecture, the source, the language. It was a lofty goal, but work worth doing, because solving this gets to the heart of how to make app development more approachable and productive.</p>



<p class="wp-block-paragraph">We realized this vision with <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">the supergraph</a>, a new layer of the stack that unifies an organization’s data, services, and capabilities, built around three underlying principles: 1) One unified composition layer; 2) Built in modules; 3) That evolves over time.</p>



<p class="wp-block-paragraph">Today, we’re announcing Apollo GraphOS, a complete cloud platform that lets anyone build, connect, and scale any supergraph. GraphOS is the execution fabric for the supergraph – a powerful runtime that connects backend and frontend systems in a modular way. It also has an integrated control plane to help developers manage, evolve, and collaborate on the supergraph.&nbsp;</p>



<p class="wp-block-paragraph">GraphOS lets you connect all your data and services seamlessly with federation. It gives you advanced capabilities like <code class="" data-line="">@defer</code> without having to write any code or sign up for any ops burden. And it’s secure – we’ve achieved SOC 2 Type 2 compliance, and passed a full audit by Doyensec with flying colors.</p>



<h2 class="wp-block-heading"><a href="#why-graphos" aria-hidden="true" class="aal_anchor" id="why-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>Why GraphOS?</strong></h2>



<p class="wp-block-paragraph">We hear a lot from developers that they want to do more with the graph. They want to scale, but they really don’t want to have to think about it. They just want to build products.</p>



<p class="wp-block-paragraph">We wanted to solve this. Not everyone has a big ops team or the GraphQL expertise or the desire to run infrastructure for the supergraph themselves. They need something that’s easy to start with and that can grow along with them – a supergraph operating system that can scale to any number of subgraphs, across every continent, at lightning speed.</p>



<p class="wp-block-paragraph">So we built one.</p>



<h2 class="wp-block-heading"><a href="#whats-in-it" aria-hidden="true" class="aal_anchor" id="whats-in-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><strong>What’s in it?</strong></h2>



<p class="wp-block-paragraph">Apollo Router is the heart of GraphOS – built in Rust, designed for performance. We partnered with Fly.io to build our own cloud-based supergraph runtime on top of Apollo Router, designed for exactly what the supergraph needs. It gives us the global reach of an edge network with the core computing capability and performance to support new and upcoming features like query planning, @defer, live queries, and so much more to come.</p>



<p class="wp-block-paragraph">We paired this global supergraph runtime with our complete set of schema delivery, collaboration, and observability tools so developers can publish changes to the supergraph and seamlessly deliver them across all their apps. And, last but not least, we included a supergraph development kit that can connect any existing graph to the supergraph.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#our-supergraph-development-kit" aria-hidden="true" class="aal_anchor" id="our-supergraph-development-kit"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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>Our supergraph development kit&nbsp;</strong></h2>



<p class="wp-block-paragraph">We hear from thousands of GraphQL developers that there is a disconnect between how they start building graphs, and how they scale them. That disconnect leads to breaking changes, bloated schemas, and uncertainty about the path forward.</p>



<p class="wp-block-paragraph">If we have learned one thing about graphs, it is that they MUST mature, change, and adapt. The supergraph doesn’t work if it requires a rewrite of the entire existing system. It’s not the v2 of a schema. It’s about modularizing what already exists –&nbsp; transforming an existing graph into a module and elevating it into a full-fledged supergraph.</p>



<p class="wp-block-paragraph">What if you could take what you’ve already built, and say: ok this isn’t the end. This is just my first module. Where can I go from here? What else can I build from here?&nbsp;</p>



<p class="wp-block-paragraph">Let’s add a new service; a new function.&nbsp;</p>



<p class="wp-block-paragraph">And another.&nbsp;</p>



<p class="wp-block-paragraph">And another.&nbsp;</p>



<p class="wp-block-paragraph">All individual and unique, each written in whatever language I choose, each independent and flexible. But all connected.&nbsp;</p>



<p class="wp-block-paragraph">The supergraph development kit is here to make this all possible with three components that create a seamless developer experience:</p>



<ul class="wp-block-list">
<li><strong><code class="" data-line="">rover dev</code>:</strong> Spins up a supergraph and runtime locally, making the graph you have your first module.</li>



<li><strong><code class="" data-line="">rover template use</code>:</strong> Gives anyone access to a cookbook of templates for adding new modules in all the most popular languages and frameworks.&nbsp;</li>



<li><strong>Sandbox:</strong> A GraphQL IDE designed for local supergraph development and testing.</li>
</ul>



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



<p class="wp-block-paragraph">Alongside GraphOS we are launching a new <a href="https://apollographql.com/pricing">usage-based pricing</a> model that matches how developers build and scale the graph.</p>



<p class="wp-block-paragraph">It starts free with a generous free quota to get you on the supergraph – 10M queries every month.</p>



<p class="wp-block-paragraph">Beyond that, it’s priced as it should be – by the query on a pay-as-you-go basis.</p>



<p class="wp-block-paragraph">GraphOS is an essential part of the toolkit for any GraphQL developer who is looking to build better apps fast while avoiding technical debt, mitigating risks, and staying competitive in a demand-driven world.&nbsp;</p>



<p class="wp-block-paragraph">It’s free and takes just a few minutes to get started. We can&#8217;t wait for you to <a href="https://studio.apollographql.com/signup?referrer=blog" data-type="URL" data-id="https://studio.apollographql.com/signup">get on the supergraph</a>.</p>


Introducing Apollo GraphOS


<p class="wp-block-paragraph">For federated graph variants, Apollo offers schema checks to ensure that proposed changes to subgraphs won’t break supergraph composition (build checks) or your active clients (operation checks).&nbsp;</p>



<p class="wp-block-paragraph">Today, we’re excited to extend this capability to <a href="https://www.apollographql.com/blog/announcement/platform/contracts-are-now-generally-available/">contracts</a>!</p>



<h2 class="wp-block-heading"><a href="#what-are-contract-checks" aria-hidden="true" class="aal_anchor" id="what-are-contract-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>What are contract checks?</h2>



<p class="wp-block-paragraph">Contract checks ensure that changes made to a source variant’s subgraphs or to the contract filtering configuration won’t cause breaking changes to any downstream contract variant’s schema or active clients. Each contract check runs two types of tasks to do this:</p>



<ol class="wp-block-list"><li><strong>Build tasks</strong>: Build tasks verify that downstream contract variants build successfully and that filtering rules continue to work as expected.</li><li><strong>Operation tasks:</strong> Operation tasks check proposed schema changes against historical operations to the contract variant (and any other selected variant) to verify whether the changes will break any of the contract variant’s active clients.</li></ol>



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



<p class="wp-block-paragraph">Contract checks are triggered in two scenarios:&nbsp;</p>



<p class="wp-block-paragraph"><strong>1. Changes are made to the source variant’s subgraphs and source variants checks are run</strong></p>



<p class="wp-block-paragraph">When a source variant has downstream contracts associated with it, Apollo will run an additional task in the checks workflow called a <strong>downstream task</strong>.&nbsp;</p>



<p class="wp-block-paragraph">When a change is made to any of the source variant’s subgraphs, the checks workflow begins, and the downstream task runs contract checks for all of the downstream contract variants.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1433" height="791" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image2.gif" alt="" class="wp-image-16051"/></figure>



<p class="wp-block-paragraph"><strong>2. Contract filter configuration is edited in Studio</strong></p>



<p class="wp-block-paragraph">When you edit the filtering configuration for a contract in Studio, contract checks will run to make sure that the new filter rules can apply without build errors and without causing breaking changes that affect operations from the contract variant’s active clients.&nbsp;</p>



<p class="wp-block-paragraph">If any checks fail, you’ll see a warning when reviewing the new contract schema, but you can still choose to update the contract even if there are warning or if checks haven’t finished running.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1435" height="786" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image3.gif" alt="" class="wp-image-16053"/></figure>



<h2 class="wp-block-heading"><a href="#blocking-downstream-contract-variants" aria-hidden="true" class="aal_anchor" id="blocking-downstream-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>Blocking downstream contract variants</h2>



<p class="wp-block-paragraph">When checks for a source variant are triggered, checks for all associated contract variants will also run. You can decide which of those contract variants you’d like to mark as <code class="" data-line="">BLOCKING</code>.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="558" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1024x558.png" alt="" class="wp-image-16057" srcset="https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1024x558.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-300x163.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-768x418.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1536x837.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1200x654.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1980x1079.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">If a contract variant is marked as <code class="" data-line="">BLOCKING</code> and a check for that contract <em>fails</em>, then the source variant’s check status would also be evaluated as <em>failed</em>.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="437" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1024x437.png" alt="" class="wp-image-16059" srcset="https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1024x437.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-300x128.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-768x328.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1536x655.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1200x512.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1980x845.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></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">Contracts checks are available today on Apollo’s Enterprise plan! Head over to checks configuration in Studio to select which contract variants should be blocking your source variant checks to fail. If you aren’t on Apollo Enterprise and would like to try it out, <a href="https://www.apollographql.com/contact-sales/">talk to us</a> about an Enterprise trial.</p>



<p class="wp-block-paragraph">ℹ️ If you are using the Rover CLI to run checks in your CI/CD pipelines, you must upgrade to at least Rover v0.8.2 to get the best and full functionality of contract checks. If you are using Rover v0.8.0 or v0.8.1, your source variants that have associated contract variants <em>will</em> start triggering contract checks as described above, however, if a contract check fails, it won’t cause <code class="" data-line="">rover subgraph check</code> to fail, affecting the accuracy of your CI/CD pipeline.</p>



<p class="wp-block-paragraph">⚠️ <strong>Note: </strong>Please make sure you are on the latest version of the Studio UI. Click on the bell icon at the top right corner of Studio and if you see <em>“Update available, click to relaunch”</em> at the bottom left of the modal then click that to get the latest version.</p>


Prevent breaking changes in downstream variants with contract checks


<p class="wp-block-paragraph">A healthy graph is never still — new features appear, old ones are pruned, and regretful decisions are repaired (“at last, my schema is perfect” &#8211; said no one ever).</p>



<p class="wp-block-paragraph">But planning for change requires graph maintainers to tread carefully &#8211; the more you know about how your schema is being used, the more confidently and quickly you can move. With the new Field Insights page in Apollo Studio, safe and rapid innovation of your graph just got a whole lot easier.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="600" height="450" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image-3.png" alt="My schema is perfect - said no one ever." class="wp-image-15888" srcset="https://wp.apollographql.com/wp-content/uploads/2022/09/image-3.png 600w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-3-300x225.png 300w" sizes="auto, (max-width: 600px) 100vw, 600px" /></figure>



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



<h3 class="wp-block-heading"><a href="#fields-as-features" aria-hidden="true" class="aal_anchor" id="fields-as-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>Fields as <em>features</em></h3>



<p class="wp-block-paragraph">Fields are the last stop for querying data from the graph. They represent the atoms of information that are exposed to the outside world. They are also functions &#8211; when used in a mutation, they are the entry points that trigger actions in the graph. Every field is literally a “feature” of the graph, and if we want to measure the usage or health of our graph’s features, the field is a great place to start. Maintaining a graph comes with a mindset of continuous curation, and knowing where to focus our improvements is key.</p>



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



<p class="wp-block-paragraph">Crucially, fields also model the relationships that bind objects together. This is what makes GraphQL uniquely powerful — queries can move freely about the graph, jumping from one entity to the next and fetching as much or as little data as they need along the way. But if one of these links breaks down, entire subtrees can go dark. This is of special concern in a federated context where fields provide the bridge between the business domains in your API.</p>



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



<p class="wp-block-paragraph">Viewing usage data through the lens of your fields unlocks some essential graph health workflows. With field insights, we are bringing these capabilities into focus for your graph:</p>



<ol class="wp-block-list"><li><strong>Understand usage and adoption patterns.</strong> Client usage breakdowns make it easy to see how client applications and operations are using the field, and field usage over time tells you whether field usage is ramping up or down.</li><li><strong>Identify impact on user-facing apps.</strong> Understand earlier in the schema lifecycle the changes that are likely to impact end-users and other team members based on observed usage.</li><li><strong>Guide change workflows</strong>. Confidently deprecate and remove outdated or unused fields. See the first and last time a field was used, then verify changes with <a href="https://www.apollographql.com/docs/studio/schema-checks">schema checks</a> at release time.</li><li><strong>Assess field-level health.</strong> Per-field error rates and latency histograms help you pinpoint health issues in your graph to target optimization work and validate improvements.</li><li><strong>Understand federation dependencies.</strong> Discover which subgraphs participate in resolving a field as teams work together to build the graph. (Hint: use the <code class="" data-line="">@contact</code> directive in your subgraphs to let teams know how to get in touch with one another!)</li></ol>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="584" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-1024x584.png" alt="" class="wp-image-15890" srcset="https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-1024x584.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-300x171.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-768x438.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-1200x684.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-4.png 1371w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>New field-level insights for your graph.</figcaption></figure>



<p class="wp-block-paragraph">The amazing flexibility of GraphQL has been game-changing for app developers, but it does present an observability challenge. With operations of all shapes and sizes, how can we best understand which parts of the graph are being used, how much, and by whom? What parts of the schema are unhealthy or causing performance bottlenecks for the graph? With the new Field Insights page, you’ll have a powerful new tool to answer these kinds of questions.</p>



<p class="wp-block-paragraph">Field Insights are available to all organizations, with longer data retention offered on paid Apollo plans. As always, we’d <a href="https://docs.google.com/forms/d/1lC-7aWNe4pnxcAPTB-W4-N8jZoyD_xQXzVByD6HOZpc/edit">love your feedback</a> on how we could further improve your graph workflows.</p>



<p class="wp-block-paragraph">⚠️ <em>Note that field latency and execution stats require the use of field-level instrumentation in your server or subgraph &#8211; for details on how to configure your server, see </em><a href="https://www.apollographql.com/docs/studio/metrics/field-usage"><em>our documentation.</em></a></p>


Continuously improve your graph with field-level usage and health metrics from Apollo Studio.


<p class="wp-block-paragraph">We recently added filters to the Schema Reference page in Studio to make the schema browsing experience easier and more intuitive, especially as your supergraph schemas grow!&nbsp;</p>



<p class="wp-block-paragraph">Head over to the Schema Reference page in Apollo Studio and try it out.</p>



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



<p class="wp-block-paragraph">Filter elements of your schema that match to multiple types of filters. You can AND across filters and OR within a single filter.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="349" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1024x349.png" alt="" class="wp-image-15618" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1024x349.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-300x102.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-768x262.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1536x524.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1200x409.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1980x676.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p class="wp-block-paragraph">Any filter results are highlighted for easy visibility. In the left menu, you can see how many elements matched for each type in the parenthesis.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="421" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1024x421.png" alt="" class="wp-image-15622" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1024x421.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-300x123.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-768x316.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1536x632.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1200x493.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1980x814.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">You can also type a word and see matching elements. If you prefix the word with a <code class="" data-line="">.</code> then filters are only applied to fields, and if you suffix the word with a <code class="" data-line="">.</code> then the filter is only applied to the types.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="389" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1024x389.png" alt="" class="wp-image-15624" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1024x389.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-300x114.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-768x292.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1536x584.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1200x456.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1980x753.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p class="wp-block-paragraph">When you type a word, Studio might suggest some hints associated with supported filter types for better results.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="525" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1024x525.png" alt="" class="wp-image-15626" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1024x525.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-300x154.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-768x394.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1536x787.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1200x615.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1980x1015.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3.png 1982w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p class="wp-block-paragraph">With the right permissions, you can view and filter by different tag names in the schema reference page.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="523" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1024x523.png" alt="" class="wp-image-15628" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1024x523.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-300x153.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-768x392.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1536x784.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1200x612.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1980x1010.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#and-finally-share-your-filter-query-with-your-teammates" aria-hidden="true" class="aal_anchor" id="and-finally-share-your-filter-query-with-your-teammates"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 finally, share your filter query with your teammates</h2>



<p class="wp-block-paragraph">You can share your filter query so that your teammates can look at the same resulting schema elements. Either copy the URL directly, or click on the share icon. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="240" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1024x240.png" alt="" class="wp-image-15630" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1024x240.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-300x70.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-768x180.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1536x360.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1200x281.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1980x464.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p class="wp-block-paragraph">Head over to the Schema Reference page for your graphs in Apollo Studio and try out these filters! This is our first iteration and we hope to continue to provide you with the best schema browsing experience, so if you have any feedback, please fill out this <a href="https://forms.gle/z1pofnxnxwe2YxpG6">feedback</a> form or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>



<p class="wp-block-paragraph">⚠️ <strong>Note:</strong> If you do not see this capability on Apollo Studio, make sure you are on the latest version of the UI. Click on the bell icon at the top right corner of Studio and if you see <em>“Update available, click to relaunch”</em> at the bottom left of the modal then click that to get the latest version.</p>


Quickly find what you need in your GraphQL schema with filters


<p class="wp-block-paragraph">We’re excited to announce that Apollo is now SOC 2 Type II certified, an incredibly important milestone for us that demonstrates the investment we’ve put into building a safe and secure product and organization over the years.&nbsp;</p>



<p class="wp-block-paragraph">SOC 2 Type II certification is a third-party audit that’s part of the American Institute of CPA’s (AICPA) <a href="https://us.aicpa.org/interestareas/frc/assuranceadvisoryservices/aicpasoc2report">Service Organization Control reporting platform</a>. It’s a necessity for any cloud SaaS business today. In order to achieve SOC 2 compliance, companies like Apollo must undergo a rigorous audit of the security policies and controls it has in place to protect its customers’ data. This certification means that Apollo has written – and operates our business – based on a set of comprehensive information security policies and procedures.</p>



<p class="wp-block-paragraph">You can request a copy of our Type II audit through your customer success team.</p>



<h2 class="wp-block-heading"><a href="#apollo-values-your-security" aria-hidden="true" class="aal_anchor" id="apollo-values-your-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><strong>Apollo values your security</strong></h2>



<p class="wp-block-paragraph">One of our core company values is empowering others –&nbsp;setting people up, both inside and outside the company, to do their best work. This certification demonstrates that value by letting our customers know that every bit of information they put into their supergraph is being handled safely and securely. We will continue to focus on, and extend our commitment to security so that,&nbsp;as more and more companies use the supergraph to power the world&#8217;s most important apps, they will know Apollo takes their data security seriously.</p>


Apollo earns SOC 2 Type II compliance


<p class="wp-block-paragraph"><strong>Embed private graphs, use embeds to invite new users, and use improved Apollo Client Dev Tools.</strong></p>



<p class="wp-block-paragraph">Explorer is an incredible GraphQL IDE that makes it quick and easy to browse schemas and run operations against them. It’s so awesome, that our community asked us to make it embeddable so that it could be used anywhere – and last year, <a href="https://www.apollographql.com/blog/announcement/platform/embed-apollo-explorer-anywhere/">we did just that</a>! But at the time, you could only embed public graph variants. Now, we are happy to announce that you can embed Explorer on <strong>any website</strong> with <strong>any graph variant</strong> – even private variants!&nbsp;</p>



<p class="wp-block-paragraph">You can provide the experience of Explorer on any of your internal or external documentation, dev portals, and websites to onboard new consumers to your graphs.</p>



<h2 class="wp-block-heading"><a href="#embedding-the-explorer-graphql-ide" aria-hidden="true" class="aal_anchor" id="embedding-the-explorer-graphql-ide"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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>Embedding the Explorer GraphQL IDE</strong></h2>



<p class="wp-block-paragraph">To embed Explorer for a specific graph, first open Explorer for that graph in Apollo Studio. Click on the chevron next to the share icon in the editor pane and select “Share as embed”. This will open a modal that gives you a few different options for embedding.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="235" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1024x235.png" alt="" class="wp-image-14019" srcset="https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1024x235.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-300x69.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-768x176.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1536x352.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1200x275.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1980x454.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">💡Embedded Explorer uses the graph ref from Apollo Studio. Since your graph is registered in Studio, embedded Explorer is always kept up to date with the schema changes in Studio. You can take your schema anywhere by embedding Explorer while Studio’s registry acts as its single source of truth behind the scenes. How neat is that?!</p>



<h3 class="wp-block-heading"><a href="#how-does-embedded-explorer-work-for-private-graph-variants" aria-hidden="true" class="aal_anchor" id="how-does-embedded-explorer-work-for-private-graph-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>How does embedded Explorer work for private graph variants?</h3>



<p class="wp-block-paragraph">If the graph variant you want to embed isn’t public (meaning it’s gated behind Studio authentication), then the embedded Explorer will request the visitor to authorize access before proceeding.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1425" height="861" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image2.gif" alt="" class="wp-image-14021"/></figure>



<p class="wp-block-paragraph">If the visitor has never interacted with Apollo Studio before &#8211; no problem! They can sign up and be invited from the embed itself.</p>



<p class="wp-block-paragraph">If your Studio org is using SSO, users are invited with the role that is default selected for your org.&nbsp;</p>



<p class="wp-block-paragraph">Otherwise, while copying the embed code from the modal in Apollo Studio, admins can configure whether they would like to invite visitors to the organization and select the role to invite with.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1431" height="791" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image3.gif" alt="" class="wp-image-14023"/></figure>



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



<p class="wp-block-paragraph">As the person embedding Explorer, graph producers can <a href="https://www.apollographql.com/blog/announcement/platform/save-and-share-your-graphql-operations-in-apollo-explorer/">share collections of example operations</a> to get their consumers started. Any collection in the “Shared” workspace will be available as default once the embedded Explorer is made available. Visitors can also create their personal collections by signing in.</p>



<h2 class="wp-block-heading"><a href="#improved-explorer-in-apollo-client-dev-tools" aria-hidden="true" class="aal_anchor" id="improved-explorer-in-apollo-client-dev-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><strong>Improved Explorer in Apollo Client Dev Tools</strong></h2>



<p class="wp-block-paragraph">With this release, we have also improved the Apollo Client Dev Tools by enabling it to securely pull in a graph ref from Apollo Studio if it is unable to introspect the graph from the browser.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="500" src="https://wp.apollographql.com/wp-content/uploads/2022/06/dev-tools-embed.gif" alt="" class="wp-image-14025"/></figure>



<h2 class="wp-block-heading"><a href="#start-embedding-your-graphs-with-explorer-today" aria-hidden="true" class="aal_anchor" id="start-embedding-your-graphs-with-explorer-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 embedding your graphs with Explorer today!</strong></h2>



<p class="wp-block-paragraph">Sharing graphs with a broader audience using Apollo Explorer’s amazing experience could not get any easier. <a href="https://studio.apollographql.com/sandbox/explorer?endpoint=https%3A%2F%2Fapi.spacex.land%2Fgraphql%2F&amp;explorerURLState=N4IgJg9gxgrgtgUwHYBcQC4QEcYIE4CeABADICGMSUAFggM5HAA6SRRANhVbQ862xy40A%2BgQRk8LAUTgBLOnVkQkwpGURSiAXxZaQAGhAA3CbLIAjdvQwgQWoA">Head over to Apollo Studio</a> and get started! For detailed instructions on embedding Explorer, check out the <a href="https://www.apollographql.com/docs/studio/explorer/embed-explorer/">docs</a>. As always, we love hearing from you, so if you have any feedback, please drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>



<p class="wp-block-paragraph"><strong>⚠️  Note</strong>: Make sure you are on the latest version of the UI. Click on the bell icon at the top right corner of Studio and if you see “Update available, click to relaunch” at the bottom left of the modal then click that to get the latest version.</p>


Improved embedding for Apollo Explorer!


<p class="wp-block-paragraph">We’ve had a busy month at Apollo. Over the last several weeks we’ve released some significant updates to the Apollo stack. Last month we shipped <a href="https://www.apollographql.com/blog/announcement/backend/apollo-federation-2-is-now-generally-available/">Federation 2</a>, a sophisticated and more flexible approach to GraphQL composition. And last week we made <a href="https://www.apollographql.com/blog/announcement/platform/contracts-are-now-generally-available/">Contracts</a> generally available, a way to tailor your graph to specific use cases like mobile development or creating public GraphQL APIs.</p>



<p class="wp-block-paragraph">Today we’re launching updates to two more components of our stack: the <a href="https://apollographql.com/blog/apollo-router-is-now-generally-available">GA release of Apollo Router</a> – our new high-performance runtime for federated GraphQL APIs – and a <a href="https://apollographql.com/blog/schema-checks-and-launches-are-now-available-for-free-in-apollo-studio/">new cloud-hosted build pipeline</a> for delivering changes to a graph.</p>



<p class="wp-block-paragraph">We’ve been building these tools together to help teams implement a more advanced GraphQL architecture – one that delivers essential capabilities for operating mission-critical graphs in organizations with many teams, programming languages, and technologies. That architecture is now at the heart of API strategy at companies like Netflix, Walmart, Expedia, Zillow, RetailMeNot, Paypal, Major League Baseball, and many more.&nbsp;</p>



<p class="wp-block-paragraph">We think it’s time to give this architecture a name, and after talking about it with the developers that have pioneered this approach in their companies, we’re calling it <strong>the supergraph</strong>.</p>



<h2 class="wp-block-heading"><a href="#the-principles-of-supergraph-architecture" aria-hidden="true" class="aal_anchor" id="the-principles-of-supergraph-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>The principles of supergraph architecture</h2>



<p class="wp-block-paragraph">The essential ideas of the supergraph are going to be <a href="https://principledgraphql.com/">pretty familiar to those who’ve been following Apollo for a while</a>. It comes down to three core principles.</p>



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



<p class="wp-block-paragraph">The supergraph is a new way to think about implementing GraphQL that goes far beyond the technical benefits of replacing data fetching and BFF code with schema and queries. It’s a unified network of a company’s data, microservices, and digital capabilities that serves as the “composition layer” for the whole organization.&nbsp;</p>



<p class="wp-block-paragraph">The supergraph empowers everyone to create richer, more engaging experiences for their users and customers by bringing everything into a single point of collaboration.</p>



<h3 class="wp-block-heading"><a href="#2-a-modular-architecture" aria-hidden="true" class="aal_anchor" id="2-a-modular-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>2: a modular architecture</h3>



<p class="wp-block-paragraph">Supergraph architecture is declarative and modular. Just as React and Kubernetes leverage modularity to scale UI development and service deployment, the supergraph leverages modularity to scale the API layer as it grows beyond a single team.&nbsp;</p>



<p class="wp-block-paragraph">Apollo Federation has always been about bringing modularity to the API layer – letting you scale a graph without bottlenecking developers on a single monolith or creating a single point of failure.&nbsp;</p>



<p class="wp-block-paragraph">Of course, Apollo Federation offers a lot of additional advantages along the way: programmable configuration, standardized tooling, analyzable query plans, strict validation at build-time instead of run-time, great support for heterogeneous environments, a structured on-ramp for new developers, and many more.</p>



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



<p class="wp-block-paragraph">The supergraph enables an agile bottom-up approach. Traditionally, APIs tend to be fairly static. Because it’s so hard to change an API, the tendency is to waterfall a design that anticipates future requirements. But products change constantly, driven by evolving user requirements and feedback.&nbsp;</p>



<p class="wp-block-paragraph">The supergraph works harmoniously with rapidly changing products because it empowers developers to ship schema changes swiftly and safely to support their own initiatives, causing the schema to naturally evolve based on actual usage and the needs of the business.</p>



<h2 class="wp-block-heading"><a href="#on-to-the-supergraph" aria-hidden="true" class="aal_anchor" id="on-to-the-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>On to the supergraph</h2>



<p class="wp-block-paragraph">We’ve seen case after case of the supergraph architecture – a unified layer, made from modules, continuously evolving – emerging organically at companies we respect and admire. So we’re focused on this idea of the supergraph and our ambition is to help every team have one. Here’s how all that we’ve been building helps with that goal.</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/05/supergraph-runtime-plane.png" alt="" class="wp-image-20799" srcset="https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane.png 1600w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-1200x600.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



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



<p class="wp-block-paragraph">Apollo Federation is our open specification for composing subgraphs – modular GraphQL services – together into a single supergraph. Each subgraph is a self-contained component with its own schema and server, so it can be developed, tested, and deployed independently.&nbsp;</p>



<p class="wp-block-paragraph">Rather than relying on custom code to combine subgraphs, subgraphs reference and extend each other through a principled set of primitives. Thanks to our incredible developer community, Federation supports subgraphs written in over <a href="https://www.apollographql.com/docs/federation/other-servers">20 programming languages</a> and a growing number of GraphQL-native services and products.</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/blog/announcement/backend/apollo-federation-2-is-now-generally-available/">Federation 2</a> builds on what we’ve learned from our community. It adds more complete support for the GraphQL spec including interfaces and new directives which can eliminate much of the boilerplate code that came with Federation 1.&nbsp;</p>



<p class="wp-block-paragraph">Federation 2 also streamlines cross-team collaboration with a flexible shared ownership model that allows multiple subgraphs to implement overlapping, complementary parts of types and schemas. New governance directives like <code class="" data-line="">@inaccessible</code>, <code class="" data-line="">@shareable</code>, and <code class="" data-line="">@override</code> give teams fine-grained control over the composition process and resulting supergraph schema.</p>



<p class="wp-block-paragraph">TLDR; Apollo Federation is now more approachable and incrementally adoptable for anyone interested in building a supergraph, and it scales seamlessly all the way into enterprises with thousands of developers collaborating on the largest rapidly-evolving supergraphs. Check out <a href="https://www.apollographql.com/docs/federation/quickstart/setup/">the Federation quickstart</a> to learn more.</p>



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



<p class="wp-block-paragraph">So you’ve created a federated schema, but how do you run it? At a minimum, the runtime for a supergraph has to receive client requests, build an execution plan, route requests to the proper subgraphs, assemble the results back together, and return it back to the client. We launched Apollo Gateway — an add-on to Apollo Server — alongside Apollo Federation to serve this purpose, but we quickly realized that we needed to build a more elegant solution that was purpose-built for the task. We decided to call it a <strong>graph router</strong>.</p>



<p class="wp-block-paragraph">A graph router does far more than a traditional API gateway. Like a relational database, it requires a sophisticated implementation that shields users from unwanted details of execution while still providing a principled way to analyze and control the system when necessary. Critical infrastructure like this is better written in a lower-level systems language that offers a smaller operational footprint, so we opted for Rust instead of Node.js.</p>



<p class="wp-block-paragraph">At the end of 2021, we released the world’s first and only graph router: Apollo Router. The performance advantages are significant: Apollo Router processes requests with <strong>10x lower latency</strong>, <strong>10x higher throughput</strong>, and <strong>12x lower variance</strong> compared to Apollo Gateway, its JavaScript predecessor. Take a look at the benchmark below to get a sense of how much better it is.</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/2022/05/Frame-3-1-1024x512.png" alt="" class="wp-image-13769" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-1200x600.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Response latency vs request throughput for Gateway, Router, and direct-to-subgraph</figcaption></figure>



<p class="wp-block-paragraph">There are other benefits too, like an <a href="https://www.apollographql.com/docs/router/customizations/rhai">extension facility</a> that lets you replace custom gateway code with configuration (this should sound familiar!) and comprehensive support for <a href="https://www.apollographql.com/docs/router/configuration/tracing">OpenTelemetry</a>.</p>



<p class="wp-block-paragraph">As of today, <a href="https://apollographql.com/blog/apollo-router-is-now-generally-available">Apollo Router is generally available</a>, free for anyone to use. Check out the <a href="https://www.apollographql.com/docs/router/">Router docs</a> to learn more.</p>



<h3 class="wp-block-heading"><a href="#graphos-studio-the-control-plane" aria-hidden="true" class="aal_anchor" id="graphos-studio-the-control-plane"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 Studio: the control plane</h3>



<p class="wp-block-paragraph">GraphOS Studio is the final piece of the puzzle for building and operating a supergraph. Its delivery pipeline provides the validation, automation, and observability you need to deliver changes rapidly and safely, making it possible to constantly evolve the supergraph schema, particularly when teams leverage and extend each other’s contributions.</p>



<p class="wp-block-paragraph"><a href="https://www.apollographql.com/docs/studio/schema-checks">Schema Checks</a> and <a href="https://www.apollographql.com/docs/studio/launches">Launches</a> prevent breaking changes before they happen by automatically validating your supergraph schema in development and giving visibility into past and in-progress changes to the supergraph.</p>



<p class="wp-block-paragraph">Previously only available on our Enterprise plan, <a href="https://apollographql.com/blog/schema-checks-and-launches-are-now-available-for-free-in-apollo-studio/">today we are making Studio’s delivery pipeline available to everyone</a>.</p>



<h2 class="wp-block-heading"><a href="#whats-next-for-the-supergraph" aria-hidden="true" class="aal_anchor" id="whats-next-for-the-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>What’s next for the supergraph</h2>



<p class="wp-block-paragraph">We’re excited to get the core components of the supergraph architecture in your hands. We can’t wait to build with you and we are eager to work together on what’s next.</p>


The supergraph: a new way to think about GraphQL


<p class="wp-block-paragraph">Today, we’re updating Apollo Studio to make its <a href="https://apollographql.com/blog/the-supergraph-a-new-way-to-think-about-graphql">supergraph</a> delivery pipeline, including <a href="https://www.apollographql.com/docs/studio/schema-checks">Schema Checks</a> and <a href="https://www.apollographql.com/docs/studio/launches">Launches</a>, available for anyone to use for free.</p>



<p class="wp-block-paragraph">We’ve made a lot of exciting announcements about supergraphs recently. In April, we announced the <a href="https://apollographql.com/blog/apollo-federation-2-is-now-generally-available/">general availability of Federation 2</a>, an improved version of Federation that makes it easier for anyone to build a supergraph. And just today, we announced <a href="https://apollographql.com/blog/apollo-router-is-now-generally-available">general availability of Apollo Router</a>, our next generation supergraph runtime written in Rust. </p>



<p class="wp-block-paragraph">With Federation and Router, anyone can build and run a supergraph. But the needs of your users evolve rapidly, and like any other layer of your stack, your supergraph needs to evolve with them. That’s where Apollo Studio comes in.</p>



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



<p class="wp-block-paragraph">The days of lockstep deployments are over. Teams need the ability to deploy changes many times a day without worrying about breaking production.&nbsp;</p>



<p class="wp-block-paragraph">We built Apollo Studio’s delivery pipeline to help you evolve and iterate on your supergraph schema with speed and confidence. It’s a single source of truth that provides the automation, validation, and observability you need to deliver changes rapidly and safely. After building a supergraph and adopting a Studio’s delivery pipeline, <a href="http://apollographql.com/customers/retailmenot">RetailMeNot</a> saw a 7X reduction in time spent deploying schema changes and eliminated production outages. Schema Checks and Launches are two core delivery features that make this possible.</p>



<h3 class="wp-block-heading"><a href="#schema-checks" aria-hidden="true" class="aal_anchor" id="schema-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>Schema checks</h3>



<p class="wp-block-paragraph">Schema checks validate changes to your supergraph schema so that you can be confident that it&#8217;s ready for production. There are two types of schema checks that Apollo Studio runs for supergraphs: composition checks and operation checks.</p>



<p class="wp-block-paragraph">Composition checks validate that subgraphs compose successfully into the overall Supergraph schema. If composition succeeds, operation checks then validate that your composed supergraph schema will serve all of your client applications by checking it against historical operations on your supergraph.</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/2022/05/Frame-4-1024x512.png" alt="" class="wp-image-13725" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-1200x600.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">The best part: schema checks can be run within existing CI/CD tools using Apollo’s Rover CLI to create a seamless integration with your existing software delivery pipelines.</p>



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



<p class="wp-block-paragraph">One of the fantastic benefits of GraphQL that a supergraph inherits is that it’s versionless. But even without a version, it’s still extremely important to understand how your supergraph has evolved over time and if new changes are live. Launches in Apollo Studio are how you do that.</p>



<p class="wp-block-paragraph">Launches give you a way to reason about the lifecycle of your supergraph. In Apollo Studio, a launch represents the complete process of an update to your deployed supergraph running through Studio’s delivery pipeline. An update to your supergraph could include:</p>



<ul class="wp-block-list"><li>Adding, removing, or modifying types and fields in a subgraph schema</li><li>Adding or removing entire subgraphs</li><li>Migrating types or fields between subgraphs</li></ul>



<p class="wp-block-paragraph">The Launches page in Apollo Studio gives you visibility into in-progress and past launches for your supergraph. It’s a dashboard that summarizes how launches over time have evolved your supergraph, helping you track when new changes are reflected in production and debug when something goes wrong.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="616" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-1024x616.png" alt="" class="wp-image-13727" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-1024x616.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-300x180.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-768x462.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-1536x924.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-1200x722.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#the-supergraph-pipeline-for-everyone" aria-hidden="true" class="aal_anchor" id="the-supergraph-pipeline-for-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>The supergraph pipeline for everyone</h2>



<p class="wp-block-paragraph">Supergraphs are transformational for developers, and we believe that everyone should be able to start building one. To make that a reality, as of today Apollo Studio’s end-to-end delivery pipeline is now available to everyone.</p>



<p class="wp-block-paragraph">You can start using Schema Checks and Launches for free in Apollo Studio today. For instructions on how to get started, head over to the <a href="https://www.apollographql.com/docs/studio/schema-checks">Schema Checks</a> and <a href="https://www.apollographql.com/docs/studio/launches">Launches</a> docs.</p>



<p class="wp-block-paragraph">If you don’t have a supergraph yet, check out <a href="https://apollographql.com/blog/the-supergraph-a-new-way-to-think-about-graphql">this post</a> to learn about Apollo’s supergraph stack and how to get started!</p>


Schema Checks and Launches are now available for free in Apollo Studio


<p class="wp-block-paragraph">At GraphQL Summit last year, we announced the <a href="https://www.apollographql.com/blog/announcement/platform/introducing-contracts-serve-many-audiences-with-a-unified-graph/">preview release of Contracts</a> on Apollo’s Enterprise plan. Contracts allow you to create tailored graphs for different audiences by applying filters to a single unified graph. Today, we are excited to announce that Contracts are generally available!</p>



<h2 class="wp-block-heading"><a href="#one-graph-many-representations" aria-hidden="true" class="aal_anchor" id="one-graph-many-representations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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>One graph &#8211; many representations</strong></h2>



<p class="wp-block-paragraph">Building a unified graph is incredibly beneficial. It gives you a single source of truth for all your organization’s data, services, and business capabilities and allows developers to deliver better, faster apps with less overhead. However, unification can introduce new challenges at scale:</p>



<ul class="wp-block-list"><li>How do you create varying levels of access for different personas or types of users like customers, employees, suppliers, or partners?</li><li>How do you provide partners and public API users with a schema scoped for their integration and app development needs?</li><li>How do you maintain client-specific BFFs and experience-driven schemas alongside a canonical domain-driven schema?</li><li>How do you restrict access to experimental or non-stable parts of the graph, but still allow access for testing and early adopters?</li></ul>



<p class="wp-block-paragraph">In summary, <strong>“how do I serve multiple different audiences with a single graph?”</strong> The answer: <strong>Contracts</strong>!</p>



<p class="wp-block-paragraph">Using Contracts, you can take your unified graph and create filtered variants of that graph that contain only a subset of its types and fields. Contracts can power separate graphs for partner developers, specific client applications, public APIs, experimental features, and more without losing any of the benefits of the unified graph.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="2118" height="972" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM.png" alt="" class="wp-image-13587" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM.png 2118w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-300x138.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-1024x470.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-768x352.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-1536x705.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-2048x940.png 2048w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-1200x551.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-1980x909.png 1980w" sizes="auto, (max-width: 2118px) 100vw, 2118px" /></figure>



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



<p class="wp-block-paragraph">Since announcing the preview, we’ve been hard at work making sure that Contracts integrates seamlessly with all of the other great features of Apollo Studio. We’ve even added in some net new functionality based on customer feedback! Here are some of the improvements we’ve made:</p>



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



<p class="wp-block-paragraph">Earlier this year we added <a href="https://www.apollographql.com/blog/announcement/platform/introducing-contract-launches-see-the-lifecycle-of-contract-schemas-in-apollo-studio/">Contract Launches</a> to the Launches dashboard in Apollo Studio. This gives you full visibility into the lifecycle of your contract schemas and helps you understand which contracts launched from a given source variant.</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/2022/05/image5-1024x572.png" alt="" class="wp-image-13589" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1024x572.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-300x167.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-768x429.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1536x858.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1200x670.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1980x1105.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p class="wp-block-paragraph">In case you missed it, <a href="https://www.apollographql.com/blog/announcement/backend/apollo-federation-2-is-now-generally-available/">Federation 2</a> &#8211; with a much improved shared ownership model, enhanced type merging, and cleaner syntax for a smoother developer experience &#8211; was made generally available recently. If you have migrated your graph variants to Federation 2, you can now create contracts from them.&nbsp;</p>



<p class="wp-block-paragraph">Additionally, if your graph variants are on Federation 2, you can hide additional schema elements like input arguments, input types and fields and enums, which is currently not possible with Federation 1. </p>



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



<p class="wp-block-paragraph">We have also added the ability to see a <em>before</em> and <em>after</em> view of your contract schema once you have applied your filter configurations. This will allow you to quickly verify the changes you are making against the source variant schema or latest successful contract schema.&nbsp;</p>



<p class="wp-block-paragraph">When creating or updating a contract schema, you can click on Generate Preview to see the number of types and fields the proposed contract schema will have. You can also see any errors that occur when generating the contract schema with the selected filter configuration.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="762" src="https://wp.apollographql.com/wp-content/uploads/2022/05/image1-1024x762.png" alt="" class="wp-image-13591" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/image1-1024x762.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1-300x223.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1-768x572.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1-1536x1143.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1-1200x893.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1.png 1620w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">On proceeding to Review, you can now see the changes that are being made based on the selected filter configuration. You can compare your proposed changes to the contract schema against the last successful contract schema build or to the source variant schema. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="820" src="https://wp.apollographql.com/wp-content/uploads/2022/05/image3-1024x820.png" alt="" class="wp-image-13593" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/image3-1024x820.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3-300x240.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3-768x615.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3-1536x1230.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3-1200x961.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3.png 1618w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">You can also select whether you want to compare API Schema or Supergraph Schema.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="774" src="https://wp.apollographql.com/wp-content/uploads/2022/05/image2-1024x774.png" alt="" class="wp-image-13595" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/image2-1024x774.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2-300x227.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2-768x581.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2-1536x1161.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2-1200x907.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2.png 1706w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></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><strong>Getting Started</strong></h2>



<p class="wp-block-paragraph">Contracts are generally available today on Apollo’s Enterprise plan! To learn how to create your first contract, check out our documentation.</p>



<p class="wp-block-paragraph">To get the most out of Contracts, we recommend migrating your source variants (from which contracts schemas are created) to Federation 2. Federation 1 supports Contracts as well, but it does not support tagging of input and enum types and fields.</p>



<p class="wp-block-paragraph">If you aren’t on Apollo Enterprise and would like to try it out, <a href="https://www.apollographql.com/contact-sales/">talk to us</a> about an Enterprise trial.</p>



<p class="wp-block-paragraph"><strong>⚠️ Note:</strong> Make sure you are on the latest version of the UI. Click on the bell icon at the top right corner of Studio and if you see “Update available, click to relaunch” at the bottom left of the modal then click that to get the latest version.</p>



<p class="wp-block-paragraph"><em>(Contracts are patent pending)</em></p>


Contracts are now generally available


<p class="wp-block-paragraph">If you’re running services in the cloud, what do you do when your cloud provider goes down? Even if you don’t follow the news, you know that this is something that happens a little too often. The way to protect your services is to make sure you are not reliant on only one cloud provider. You can work to make your own services multi-cloud, and you should, but of course you also need to make sure that the services you rely on are also multi-cloud. That’s why we are so happy to introduce multi-cloud support for Apollo Uplink.</p>



<p class="wp-block-paragraph">Apollo Uplink is a free service that provides federated Apollo Gateways with a Supergraph Schema, which is just plain GraphQL. If you are using Apollo Managed Federation, then you publish your subgraph schemas into the Apollo Schema registry. Apollo Studio composes the subgraph schemas into a Supergraph schema and makes those schemas available via the Uplink service. Every Apollo Gateway polls Apollo Uplink to see when a new schema is available for download. Now, Apollo Uplink is more reliable because it is multi-cloud.</p>



<p class="wp-block-paragraph">The diagram below, from the&nbsp;<a href="https://www.apollographql.com/docs/federation/managed-federation/uplink/">Apollo Studio documentation about Uplink</a>, illustrates how Uplink works.</p>



<figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-03-at-8.29.29-AM.png" alt="" class="wp-image-13522" width="711" height="212" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-03-at-8.29.29-AM.png 948w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-03-at-8.29.29-AM-300x90.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-03-at-8.29.29-AM-768x229.png 768w" sizes="auto, (max-width: 711px) 100vw, 711px" /></figure>



<p class="wp-block-paragraph"><strong>How do you use multi-cloud Uplink?</strong></p>



<p class="wp-block-paragraph">To start using multi-cloud Uplink, all you need to do is upgrade the&nbsp;<code class="" data-line="">@apollo/gateway</code>&nbsp;package to the latest version, multi-cloud was introduced in v0.36.0. If you’re running Federation one, then you would do this with:</p>



<p class="wp-block-paragraph"><code class="" data-line="">npm install @apollo/gateway@latest-1</code></p>



<p class="wp-block-paragraph">And of if you’re running Federation 2 then you’ve been running with multi-cloud Uplink already since Gateway version v2.0.0-alpha.3. To upgrade to the latest Federation use the latest-2 tag like so:</p>



<p class="wp-block-paragraph"><code class="" data-line="">npm install @apollo/gateway@latest-2</code></p>



<p class="wp-block-paragraph"><strong>How does multi-cloud Uplink work?</strong></p>



<p class="wp-block-paragraph">Uplink is now implemented as two independent end-points, one running on Google Cloud (GCP) and one on Amazon Web Services (AWS). When you publish a schema to Apollo Studio, that schema will be made available on both cloud providers. When Apollo Gateway requests schemas from Apollo Uplink, it will alternate between those two providers. If a schema request fails, Apollo Gateway will try the other end-point. If both end-points are down, Gateway will fall back to the previously fetched schema. That means that your Apollo Gateway will not be impacted if one of our two cloud providers is down.</p>



<p class="wp-block-paragraph"><strong>You can customize Apollo Uplink, but you probably won’t need to</strong></p>



<p class="wp-block-paragraph">Most users will be happy with Apollo Gateway’s default Apollo Uplink setup, but Uplink is configurable. You may want to configure the Apollo Gateway to use only one Apollo Uplink endpoint or maybe add your own Uplink end-point. Adding your own Uplink end-point is beyond the scope of this blog post.</p>



<p class="wp-block-paragraph"><strong>What’s next?</strong></p>



<p class="wp-block-paragraph">Apollo Uplink was already a very reliable service providing 99.97% uptime and we&#8217;re excited to provide even more stability with our Multi-cloud support. If you’re using Uplink, your next step is to upgrade to the latest Gateway release and enjoy increased reliability just by taking the defaults! And if you’re not using Uplink, maybe you should be. It’s a free service you can rely on to deploy changes to your Apollo Gateways 🚀</p>


Introducing multi cloud support for Apollo Uplink

Introducing multi-cloud support for Apollo Uplink


<p class="wp-block-paragraph">Last year on popular request, we brought <a rel="noreferrer noopener" href="https://www.apollographql.com/blog/tooling/graphql-ide/were-shipping-3-of-our-most-requested-features/#1-tabs-in-explorer" data-type="URL" data-id="https://www.apollographql.com/blog/tooling/graphql-ide/were-shipping-3-of-our-most-requested-features/#1-tabs-in-explorer" target="_blank">tabs</a> to Explorer. And today, we are taking it up another notch! You can now save your operations in Explorer and share them with your team using Operation Collections!</p>



<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="Operation Collections: Save and share GraphQL queries" width="580" height="326" src="https://www.youtube.com/embed/o0C5FkT7gk4?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>



<h2 class="wp-block-heading"><a href="#what-is-an-operation-collection" aria-hidden="true" class="aal_anchor" id="what-is-an-operation-collection"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 an Operation Collection?</h2>



<p class="wp-block-paragraph">Operation Collections are a new, <strong>free</strong> feature in Apollo Studio that help you save and organize operations in folders that align to different use cases, client apps, personas and more.&nbsp;</p>



<p class="wp-block-paragraph">Saving your operations into a collection in Explorer means that you and your team can:</p>



<ul class="wp-block-list"><li>Stop writing the same operation over and over</li><li>Organize common operations by how they&#8217;re used and who uses them</li><li>Design, execute, and share operations all in a single interface</li><li>More easily onboard new team members</li></ul>



<p class="wp-block-paragraph"><img loading="lazy" decoding="async" width="295" height="466" src="https://lh3.googleusercontent.com/L0uf1ugErGINiTA4ZJL-5aUZWg1wkDaRvo7mjx0D7yLhxSmdGdIPmaiFxr-tPo6FR_n8qaaBj3Ht2-mpJj_3nN0BjMSp0V6PPlwFUULCaGnuRfpzFYDqxFpve5pL1l03MWtvlBbY"></p>



<p class="wp-block-paragraph">Let’s see how!</p>



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



<p class="wp-block-paragraph">To get started, head over to the Explorer in Apollo Studio and select any graph/variant combination that you want to create a collection for. Now let’s create a new collection:</p>



<ol class="wp-block-list"><li>In Explorer on the left panel, click on the bookmark icon and click on <code class="" data-line="">+Create collection</code>.&nbsp;</li><li>A collection can be created as Personal or Shared. Personal collections are only visible to you while shared collections are visible to all Studio org members who have access to that variant. Configure collection details in the modal and hit Add.&nbsp;</li><li>That is it! You should see your newly created collection in the Operation Collection index 🥳</li></ol>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1424" height="782" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image1.gif" alt="" class="wp-image-12669"/></figure>



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



<p class="wp-block-paragraph">Now let’s save an operation to the newly created collection:</p>



<ol class="wp-block-list"><li>Navigate to any tab in the Explorer with an operation, or build a query using the Explorer’s query builder.&nbsp;</li><li>Click on the save icon in the editor pane, left of the run button. You can also use the keyboard shortcut of <code class="" data-line="">Cmd/Ctrl+S</code>.&nbsp;</li><li>Give the operation a name, select the collection to save in, and hit Save!&nbsp;</li><li>Your operation is now saved and available for access within that collection 🎊</li></ol>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1426" height="783" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image2.gif" alt="" class="wp-image-12672"/></figure>



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



<p class="wp-block-paragraph">A collection created as Shared for a graph/variant is automatically visible to every member of the Studio organization who has access to that graph/variant. Shared collections are editable by any graph or org admin. Optionally, editing settings can also be given to other roles in the org.&nbsp;</p>



<p class="wp-block-paragraph">⚠️ <strong>Note:</strong> If you are an enterprise user, you can configure granular <a href="https://www.apollographql.com/docs/studio/org/members/">role</a> level permissions, otherwise you can choose whether you want to grant edit permissions to all org users.</p>



<figure class="wp-block-image size-large is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image4-962x1024.png" alt="" class="wp-image-12699" width="481" height="512" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/image4-962x1024.png 962w, https://wp.apollographql.com/wp-content/uploads/2022/03/image4-282x300.png 282w, https://wp.apollographql.com/wp-content/uploads/2022/03/image4-768x818.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/image4.png 1170w" sizes="auto, (max-width: 481px) 100vw, 481px" /></figure>



<p class="wp-block-paragraph">But that’s not it! Here are a few ways to make it even easier for your team to find shared operations:</p>



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



<p class="wp-block-paragraph">You can also give team members a link directly to a particular shared collection or operation. To do so, click the <code class="" data-line="">•••</code> button next to any shared collection or operation in the list and select the Copy Link option.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="653" src="https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-1024x653.png" alt="" class="wp-image-12713" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-1024x653.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-300x191.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-768x490.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-1536x979.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-1200x765.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#2-embed-in-your-graphs-readme" aria-hidden="true" class="aal_anchor" id="2-embed-in-your-graphs-readme"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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>2. Embed in your graph’s README</strong></h3>



<p class="wp-block-paragraph">Have you added a README for your graph yet? If not, no better time like the present! We added the <a href="https://www.apollographql.com/blog/announcement/platform/create-a-readme-to-onboard-developers-to-the-graph/">README page</a> last year to make it easy for graph producers to onboard new developers on their graphs.&nbsp;</p>



<p class="wp-block-paragraph">Now you can embed saved operations and collections directly into your README:</p>



<ol class="wp-block-list"><li>Click on the edit icon on the README.&nbsp;</li><li>Using the graph shortcodes, select a saved operation or a collection to embed.&nbsp;</li><li>Check out the preview to make sure everything looks good, and then click Update.</li><li>Tada! 🎉 With a few clicks you’ve added an example set of operations to the README.&nbsp;</li></ol>



<p class="wp-block-paragraph">Now any developer looking to explore the graph can get started right away!</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1432" height="790" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image9.gif" alt="" class="wp-image-12684"/></figure>



<h3 class="wp-block-heading"><a href="#3-create-a-collection-for-a-public-graph" aria-hidden="true" class="aal_anchor" id="3-create-a-collection-for-a-public-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>3. Create a collection for a public graph</strong></h3>



<p class="wp-block-paragraph">If you have a <a href="https://www.apollographql.com/blog/announcement/tooling/make-your-graphql-schema-publicly-visible-without-introspection/">public graph</a>, you can publish a collection of example operations to help developers accessing the public graph onboard quickly. Any developer accessing the public graph can view and execute operations in a public collection, without having to login!&nbsp;</p>



<p class="wp-block-paragraph">⚠️ <strong>Note:</strong> Unauthenticated users do not have edit access for collections</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="326" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1024x326.png" alt="" class="wp-image-12701" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1024x326.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-300x96.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-768x245.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1536x489.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1200x382.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1980x631.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p class="wp-block-paragraph">Now you might be thinking, “this is great! But I use Sandbox for my local development. Can I save my operations in collections in Sandbox too?” <strong>Yes you can!</strong></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1999" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image7.png" alt="" class="wp-image-12704" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/image7.png 1999w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-300x154.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-1024x525.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-768x393.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-1536x787.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-1200x615.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-1980x1014.png 1980w" sizes="auto, (max-width: 1999px) 100vw, 1999px" /></figure>



<p class="wp-block-paragraph">In fact, not only can you save operations in collections across all of your Sandbox endpoints, you can also access collections for any registered graph that you have access to! That means that when you’re using Sandbox to build or make changes to a registered graph in Apollo Studio, you can test out operations in collections for the registered graph and edit them directly as you are making your schema changes!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="816" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image10-1024x816.png" alt="" class="wp-image-12708" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/image10-1024x816.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/image10-300x239.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/image10-768x612.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/image10-1200x956.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/image10.png 1230w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p class="wp-block-paragraph">You thought that was it? Not quite.&nbsp;</p>



<p class="wp-block-paragraph"><strong>After you have created a collection you can:</strong></p>



<ul class="wp-block-list"><li>Edit its configuration.&nbsp;</li><li>Duplicate the collection between graphs, including between sandbox and registered graphs.<ul><li>You can also choose to make the copy public or shared.</li><li>Duplicating a collection does not keep the copy in-sync with the original.</li></ul></li><li>Mark it as favorite, to keep it at the top of the list. ⭐</li></ul>



<p class="wp-block-paragraph"><strong>After you have created an operation you can:</strong></p>



<ul class="wp-block-list"><li>Rename the operation.</li><li>Save a copy of the operation.</li><li>Drag and drop the operation between collections!</li></ul>



<h2 class="wp-block-heading"><a href="#so-what-are-you-waiting-for-save-and-share-your-operations-today" aria-hidden="true" class="aal_anchor" id="so-what-are-you-waiting-for-save-and-share-your-operations-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>So what are you waiting for? Save and share your operations today!</h2>



<p class="wp-block-paragraph">Head over to Apollo Studio or Apollo Sandbox, and save, organize and share your frequently used operations today! And as always, we love hearing from you, so if you have any feedback, please fill out this <a href="https://forms.gle/CbY8mEp5vK7hgYgA9">feedback</a> form or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>



<p class="wp-block-paragraph">⚠️ <strong>Note:</strong> If you do not see Operation Collections in your Explorer, make sure you are on the latest version of the UI. Click on the bell icon at the top right corner of Studio or Sandbox and if you see <em>“Update available, click to relaunch”</em> at the bottom left of the modal then click that to get the latest version.</p>


Save and share your GraphQL operations in Apollo Explorer!


<p class="wp-block-paragraph"><em>🚀 🎉  Heads up &#8211; Federation 2 and Gateway 2.x are now GA! Check out the <a href="https://www.apollographql.com/blog/apollo-federation-2-is-now-generally-available/" data-type="URL" data-id="https://www.apollographql.com/blog/apollo-federation-2-is-now-generally-available/">GA announcement blog</a> or head over to the <a href="https://www.apollographql.com/docs/federation/" data-type="URL" data-id="https://www.apollographql.com/docs/federation/">Federation docs</a> to get started.</em></p>



<hr class="wp-block-separator"/>



<p class="wp-block-paragraph">Four months ago we announced Apollo Federation 2 &#8211; the next generation of Federation with <a href="https://www.apollographql.com/blog/announcement/backend/announcing-federation-2/">new features</a> designed to improve the graph developer experience and make it easy for anyone to build, manage, and scale a unified graph. </p>



<p class="wp-block-paragraph">Since then, we’ve been collecting feedback from members of the community and our customers that have tried out the alpha release and have been iterating on the Federation 2 spec to make it viable for the larger GraphQL ecosystem.&nbsp;</p>



<p class="wp-block-paragraph">With the improvements we’ve made in recent months, we’re excited to move <a href="https://www.apollographql.com/docs/federation/v2/">Federation 2</a> along with <a href="https://www.apollographql.com/docs/federation/v2/gateway/">Apollo Gateway 2.0</a> out of alpha into public preview!</p>



<h2 class="wp-block-heading"><a href="#what-you-need-to-know-about-the-preview" aria-hidden="true" class="aal_anchor" id="what-you-need-to-know-about-the-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 need to know about the preview</h2>



<p class="wp-block-paragraph">With Federation 2 and Gateway 2.0 now in preview, here are some highlights and improvements to be aware of:</p>



<ul class="wp-block-list"><li>There are <strong>no breaking changes</strong> between Federation 2 alpha and preview.</li><li>Apollo Gateway 0.X does not support Federation 2. If you would like to use Apollo Gateway with Federation 2, you must use Gateway 2.0 or higher.</li><li>Graphs in Apollo Studio with Federation 2 composition enabled will automatically be updated from <code class="" data-line="">alpha</code> to <code class="" data-line="">preview</code>.</li><li>If you have Federation 2 composition enabled, Federation 1 subgraphs will automatically be converted to Federation 2 during composition. You can continue to use your Federation 1 subgraphs as long as you like.</li><li><code class="" data-line="">@link</code> and <code class="" data-line="">@shareable</code> are now supported in the Fed 2 subgraph syntax.</li><li><code class="" data-line="">subgraph-js</code> subgraph library now supports Fed 2 subgraph syntax.</li></ul>



<h2 class="wp-block-heading"><a href="#getting-started-with-federation-2-gateway-2-0" aria-hidden="true" class="aal_anchor" id="getting-started-with-federation-2-gateway-2-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>Getting started with Federation 2 &amp; Gateway 2.0</h2>



<p class="wp-block-paragraph">Ready to start using Federation 2? <strong>Check out our </strong><a href="https://www.apollographql.com/docs/federation/v2/federation-2/moving-to-federation-2"><strong>docs on moving to Federation 2</strong></a><strong>.</strong> Here’s a quick overview of the steps you’ll need to take:</p>



<h3 class="wp-block-heading"><a href="#1-upgrade-apollo-gateway" aria-hidden="true" class="aal_anchor" id="1-upgrade-apollo-gateway"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. Upgrade <code class="" data-line="">@apollo/gateway</code></h3>



<p class="wp-block-paragraph">To use Federation 2, you must be using Gateway 2.0 or higher (or <a href="https://www.apollographql.com/blog/announcement/backend/apollo-router-our-graphql-federation-runtime-in-rust/">Apollo Router</a>). Upgrading from Gateway 0.X to Gateway 2.0 is as easy as bumping the version in your <code class="" data-line="">package.json</code>.</p>



<p class="wp-block-paragraph">Gateway 2.0 is still compatible with Federation 1, so you can upgrade without breaking your existing graph.</p>



<h3 class="wp-block-heading"><a href="#2-turn-on-federation-2-composition" aria-hidden="true" class="aal_anchor" id="2-turn-on-federation-2-composition"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. Turn on Federation 2 composition</h3>



<p class="wp-block-paragraph">Once your runtime is compatible with Federation 2, you’ll need to take a moment to turn on Fed 2 composition for Managed Federation or for the Rover CLI, depending on how you compose your federated graph.</p>



<p class="wp-block-paragraph">Federation 2 composition is backward compatible with Federation 1 subgraphs (🎉), so turning it on won’t break your existing graph.</p>



<p class="wp-block-paragraph"><strong>Managed Federation</strong></p>



<p class="wp-block-paragraph">If you use managed Federation, you can turn on Fed 2 composition for specific variants. Navigate to the “Manage Variants” section of your graph’s settings page and click the meatball menu next to a variant.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh5.googleusercontent.com/qfapzHPkVsn7KDhBrs-x-CRWPT1yLOiu5BzS3krUHAXpC489sApWL5jqf4F64vbc79HMR1AQPnrpECb3-63vTRgt_baqGdHr-1yy6zRbl6majExI73FaiiBif4o63_wZWOwj4vsZ" alt=""/></figure>



<p class="wp-block-paragraph">Click “Edit Build Configuration” and select Federation 2 under the “Federation Version” dropdown.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh4.googleusercontent.com/cTbU2CnbeZa_gWjO7QkZ4Phh3o97axRZCBAcazYIaidBBkExnwACRqTGtSgXiWYwg829jE4UM-lQiVk0NOnnk_QYwswQJq_Wh5b5QUEXycbCE9ISYs8Scfp4pAdHd4cPbMe7NZ-Z" alt=""/></figure>



<p class="wp-block-paragraph"><strong>Rover CLI</strong></p>



<p class="wp-block-paragraph">If you use the Rover CLI for Federation composition, you’ll need to install the latest version of Rover and install the Federation 2 plugin. You can find detailed instructions on how to do so <a href="https://www.apollographql.com/docs/federation/v2/federation-2/moving-to-federation-2/#using-the-rover-cli">here</a>.</p>



<h3 class="wp-block-heading"><a href="#3-modify-your-subgraphs-at-your-own-pace" aria-hidden="true" class="aal_anchor" id="3-modify-your-subgraphs-at-your-own-pace"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. Modify your subgraphs at your own pace</h3>



<p class="wp-block-paragraph">At this point, your graph is already running on Federation 2 &#8211; congrats! Now, to make the most out of Fed 2, you’ll want to modify your subgraphs to take advantage of its more flexible composition model.&nbsp;</p>



<p class="wp-block-paragraph">Since Fed 2 composition is backwards compatible with Fed 1 subgraphs, service teams can modify their subgraphs at their own pace without breaking composition! You can learn about all of the improvements available in the Fed 2 subgraph syntax in the <a href="https://www.apollographql.com/docs/federation/v2/federation-2/new-in-federation-2/#more-flexible-composition">documentation</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">We can’t wait for you to experience the next generation of Apollo Federation and Gateway 2.0! 🚀&nbsp;If you’re currently using Federation 1, check our guide on <a href="https://www.apollographql.com/docs/federation/v2/federation-2/moving-to-federation-2/">moving to Federation 2</a>, or if you’re new to Federation, our <a href="https://www.apollographql.com/docs/federation/v2/quickstart/setup/">quickstart guide</a> is a great place to get started. And don’t forget, we would love to know about your experience with Federation 2, so be sure to leave us your thoughts on <a href="https://community.apollographql.com">community.apollographql.com</a>.</p>


Apollo Federation 2 and Gateway 2.0 are now available in preview


<p class="wp-block-paragraph">Today we’re excited to show off some recent upgrades to Operation Insights in Apollo Studio. This update features three significant enhancements which make it easier to understand the usage and data flow of operations in your graph.</p>



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



<p class="wp-block-paragraph">First, we brought the operation signature front and center so that you can quickly understand the shape of fields being requested by the operation.  The signature now appears as a side-panel that you can resize instead of hidden behind another tab.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="621" src="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-1024x621.png" alt="" class="wp-image-12391" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-1024x621.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-300x182.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-768x465.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-1536x931.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-1200x727.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1.png 1650w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>Easier to find operation signatures.</figcaption></figure>



<h2 class="wp-block-heading"><a href="#2-which-subgraphs-are-used-by-an-operation" aria-hidden="true" class="aal_anchor" id="2-which-subgraphs-are-used-by-an-operation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. Which subgraphs are used by an operation?</h2>



<p class="wp-block-paragraph">In the same panel, we added the ability to view the federation query plan for an operation.  The query plan lets you see how Apollo Gateway or Router is working under the hood, describing how data from your subgraphs is woven together to build a full query response.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1024" height="768" src="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-2.png" alt="" class="wp-image-12397" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-2.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-2-300x225.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-2-768x576.png 768w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>See query plans and subgraph dependencies for federated operations.</figcaption></figure>



<p class="wp-block-paragraph">Similar to features found in Apollo Explorer, you can view the query plan as either a text document or visualized as a tree of subgraphs. (<span class="has-inline-color has-accent-color">Only available to federated graphs. Learn more about <a href="https://www.apollographql.com/docs/federation/query-plans/">Apollo Federation Query Plans</a></span>).</p>



<h2 class="wp-block-heading"><a href="#3-which-clients-are-using-this-operation" aria-hidden="true" class="aal_anchor" id="3-which-clients-are-using-this-operation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. Which clients are using this operation?</h2>



<p class="wp-block-paragraph">Last but not least, we introduced a way to understand which clients are using an operation in a new Client Usage display. The most active clients are sorted to the top of the list based on the number of requests reported to Apollo Studio via <a href="https://www.apollographql.com/docs/studio/metrics/usage-reporting/">usage reporting</a>.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="621" src="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-1024x621.png" alt="" class="wp-image-12400" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-1024x621.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-300x182.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-768x465.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-1536x931.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-1200x727.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3.png 1650w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>See client usage breakdowns for operations.</figcaption></figure>



<h3 class="wp-block-heading"><a href="#now-available-in-apollo-studio" aria-hidden="true" class="aal_anchor" id="now-available-in-apollo-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>Now Available in Apollo Studio!</h3>



<p class="wp-block-paragraph"><span class="has-inline-color has-primary-color">As a reminder, you can find all of these features by visiting the Operations tab in Apollo Studio and then choosing a single operation from the operations drop-down. Note that you can also get to insights for individual operations from field usage details, failed operation checks, client breakdowns, and Slack daily reports.</span></p>



<h2 class="wp-block-heading"><a href="#explore-operation-insights-today" aria-hidden="true" class="aal_anchor" id="explore-operation-insights-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>Explore Operation Insights today</h2>



<p class="wp-block-paragraph">When utilizing <a href="https://www.apollographql.com/docs/studio/metrics/usage-reporting/">Apollo usage reporting</a> for your graph, you’ll have access to these insights and more.</p>



<p class="wp-block-paragraph"><a href="https://studio.apollographql.com/">Visit Apollo Studio</a> to start using these tools and more today.  And as always, we love hearing from you, so if you have any feedback, please fill out this <a href="https://forms.gle/Ep9cRWq9j3hwdmTL6">feedback form </a>or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


New Operation Insights with Client Usage and Federation Query Plans


<p class="wp-block-paragraph">When you’re a developer working on a federated graph, you likely work on a single subgraph locally before publishing it to Apollo Studio as part of the supergraph. We created <a href="https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development/">Apollo Sandbox</a> to give developers a great tool for working on locally-running graphs, but wouldn’t it be great if could get the same functionality when working with subgraphs? And even better &#8211; what if you could use Sandbox to run checks to check that your local changes won’t break composition or operations against the federated graph? Well, now you can!</p>



<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="Introducing Apollo Sandbox" width="580" height="326" src="https://www.youtube.com/embed/0jzqqHZU00Q?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>



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



<p class="wp-block-paragraph">When working off a subgraph, head over to <a href="http://studio.apollographql.com/sandbox/">Apollo Sandbox</a> and connect to your subgraph localhost via the Sandbox endpoint field (or you can connect to a remote endpoint if you like). You will notice that a <code class="" data-line="">SUBGRAPH</code> badge appears next to the endpoint. Your subgraph schema is loaded and ready to be queried!&nbsp;</p>



<p class="wp-block-paragraph">Explore your subgraph schema on the Schema page and run operations in Explorer. As you make changes to your subgraph schema, changes are automatically updated in Sandbox without any manual refresh.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1434" height="793" src="https://wp.apollographql.com/wp-content/uploads/2022/02/subgraph-sandbox-1.gif" alt="" class="wp-image-12331"/></figure>



<h2 class="wp-block-heading"><a href="#compare-your-subgraph-schema-to-a-registered-subgraph-in-studio" aria-hidden="true" class="aal_anchor" id="compare-your-subgraph-schema-to-a-registered-subgraph-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>Compare your subgraph schema to a registered subgraph in Studio</h2>



<p class="wp-block-paragraph">Navigate to the Diffs tab and sign into Studio to select a registered subgraph to diff your local schema against. Without going anywhere, you can see how your changes compare to the existing subgraph. You can also see a summary of how many types and fields have been added or removed.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1433" height="788" src="https://wp.apollographql.com/wp-content/uploads/2022/02/subgraph-sandbox-2.gif" alt="" class="wp-image-12333"/></figure>



<h2 class="wp-block-heading"><a href="#check-supergraph-composition-and-prevent-breaking-changes" aria-hidden="true" class="aal_anchor" id="check-supergraph-composition-and-prevent-breaking-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>Check supergraph composition and prevent breaking changes</h2>



<p class="wp-block-paragraph">You can ensure that your changes won’t break the supergraph schema composition and or affect any operations to the federated graph by clicking on the “Run a check” button in the loaded diff view or by heading over to the checks tab. If all of your checks pass, you can publish your changes to the registered schema in Apollo Studio with complete confidence!</p>



<p class="wp-block-paragraph">If you want to see even more details about checks, you can navigate to the main checks page on Studio. You can always move back and forth between Sandbox and full Studio experience using the box icon on the top right corner in the navigation bar.</p>



<p class="wp-block-paragraph"><strong>⚠️</strong> <strong>Note:</strong> For checks to work, you’ll need to have a Studio account with access to Checks, which is available on Team and Enterprise plans only.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1433" height="789" src="https://wp.apollographql.com/wp-content/uploads/2022/02/subgraph-sandbox-3.gif" alt="" class="wp-image-12335"/></figure>



<h2 class="wp-block-heading"><a href="#start-working-on-your-subgraphs-in-sandbox-today" aria-hidden="true" class="aal_anchor" id="start-working-on-your-subgraphs-in-sandbox-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 working on your subgraphs in Sandbox today!</h2>



<p class="wp-block-paragraph"><a href="https://studio.apollographql.com/sandbox/">Head over to Apollo Sandbox</a>, point it to a subgraph and try out these new features! And as always, we love hearing from you, so if you have any feedback, please fill out this <a href="https://forms.gle/4G2cEumrh85jgDF1A">feedback form</a> or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


Introducing subgraph support in Apollo Sandbox


<p class="wp-block-paragraph">Since releasing <a href="https://www.apollographql.com/blog/announcement/platform/introducing-contracts-serve-many-audiences-with-a-unified-graph/">contracts</a> as a way to serve many audiences with a unified graph, we’ve received great feedback from developers adopting contracts and championing the graph. However, one question we frequently hear is: “how can I reason about contracts with respect to my publishing pipeline?”</p>



<p class="wp-block-paragraph">As of today, we are thrilled to introduce Contract Launches in Apollo Studio to answer this very question. With Contract Launches, you can use the Launches page in Studio that provides better visibility into the lifecycle of your contract schemas and helps you understand which contracts launched from a given source variant.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="4857" height="2710" src="https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall.png" alt="" class="wp-image-12141" srcset="https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall.png 4857w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-300x167.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-1024x571.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-768x429.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-1536x857.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-2048x1143.png 2048w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-1200x670.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-1980x1105.png 1980w" sizes="auto, (max-width: 4857px) 100vw, 4857px" /></figure>



<h2 class="wp-block-heading"><a href="#lifecycle-of-a-contract-launch" aria-hidden="true" class="aal_anchor" id="lifecycle-of-a-contract-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>Lifecycle of a Contract Launch</h2>



<p class="wp-block-paragraph">Every contract is built from an existing source variant. Publishing updates to your source variant triggers downstream launches for any contract built from that source.</p>



<p class="wp-block-paragraph">Let&#8217;s look in more detail what this looks like:</p>



<ol class="wp-block-list"><li>You publish an update to your source variant</li><li>A launch initiates for the source variant</li><li>If the launch was successful a core schema is the output artifact</li><li>The core schema is then approved and made available to gateways</li><li>A launch for each contract is initiated<ol><li>The core schema is used as the build input to contract launches</li></ol></li><li>The schema is then filtered into a contract schema</li><li>If the launch was successful a contract schema is the output artifact</li><li>The contract schema is then approved and made available to gateways</li></ol>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1020" height="892" src="https://wp.apollographql.com/wp-content/uploads/2022/02/contract-launches.gif" alt="" class="wp-image-12143"/><figcaption>The lifecycle of a contract launch</figcaption></figure>



<h2 class="wp-block-heading"><a href="#launch-status" aria-hidden="true" class="aal_anchor" id="launch-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>Launch status</h2>



<p class="wp-block-paragraph">For any launch that triggers a contract launch, you can see a summary of how many downstream launches succeeded or failed:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="229" src="https://wp.apollographql.com/wp-content/uploads/2022/02/image-5-1024x229.png" alt="" class="wp-image-12145" srcset="https://wp.apollographql.com/wp-content/uploads/2022/02/image-5-1024x229.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-5-300x67.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-5-768x172.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-5.png 1179w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">You can also take a look at the Launch Sequence to see the status of each contract launch individually. To debug a failed launch, you can navigate to the Launches page for a contract by clicking the desired contract launch item.</p>



<p class="wp-block-paragraph">A contract launch that completes successfully is made available to running gateways via Uplink.</p>



<p class="wp-block-paragraph">⚠️ <strong>Note:</strong> Checks for contracts are not currently supported but are in active research and development.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="872" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2022/02/image-6-872x1024.png" alt="" class="wp-image-12147" srcset="https://wp.apollographql.com/wp-content/uploads/2022/02/image-6-872x1024.png 872w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-6-256x300.png 256w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-6-768x901.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-6.png 978w" sizes="auto, (max-width: 872px) 100vw, 872px" /></figure>



<h2 class="wp-block-heading"><a href="#reviewing-changes" aria-hidden="true" class="aal_anchor" id="reviewing-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>Reviewing changes</h2>



<p class="wp-block-paragraph">Any update to your graph will also update your contracts. To help you keep track of these changes, there’s a convenient link to the contracts changelog. The changelog page shows you any types or fields from your contract schema that have been added, removed, or modified.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="518" src="https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1024x518.png" alt="" class="wp-image-12149" srcset="https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1024x518.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-300x152.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-768x389.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1536x777.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-2048x1036.png 2048w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1200x607.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1980x1002.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<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">Apollo Contracts is currently in public preview on Apollo’s Enterprise plan. Feedback from our community and customers is crucial to the success of Apollo, and the feedback we’ve received from pilot users so far has been instrumental in ensuring that contracts can serve many use cases while still giving teams full visibility and control over changes.</p>



<p class="wp-block-paragraph">If you’re interested in learning more about Contracts, visit the <a href="https://www.apollographql.com/docs/studio/contracts/">documentation</a>. We’re excited to see what you’ll build!</p>


Introducing Contract Launches: see the lifecycle of contract schemas in Apollo Studio


<p class="wp-block-paragraph">When you’re making changes to your GraphQL schema, you probably make those changes locally before you publish them to a graph registry like Apollo Studio. </p>



<p class="wp-block-paragraph">We created <a href="https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development/">Apollo Sandbox</a> so that you can use the best GraphQL IDE when working locally, but wouldn’t it be great if you could easily see the diff between your local schema and the existing schema in Studio? </p>



<p class="wp-block-paragraph">And even better &#8211; what if you could run checks to see if your local changes could break operations against the production graph? Well, now you can do both right from Apollo Sandbox! Let’s take a look at how:</p>



<h2 class="wp-block-heading"><a href="#validate-your-schema-changes-before-publishing-them-to-studio" aria-hidden="true" class="aal_anchor" id="validate-your-schema-changes-before-publishing-them-to-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>Validate your schema changes before publishing them to Studio!</h2>



<p class="wp-block-paragraph">Want to feel confident about your schema changes before publishing them to Studio? Simply head over to <a href="http://studio.apollographql.com/sandbox/">Apollo Sandbox</a> and connect to your localhost via the Sandbox endpoint field (or you can connect to a remote endpoint if you like).</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1433" height="829" src="https://wp.apollographql.com/wp-content/uploads/2021/12/image1.gif" alt="" class="wp-image-11504"/></figure>



<h3 class="wp-block-heading"><a href="#compare-your-schema-to-a-registered-graph-in-studio" aria-hidden="true" class="aal_anchor" id="compare-your-schema-to-a-registered-graph-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>Compare your schema to a registered graph in Studio</h3>



<p class="wp-block-paragraph">Go to the Diffs tab and sign into Studio to select a registered graph to diff your local schema against and explore your diff! See a summary of how many types and fields have been added or removed and select to view it as a line wrap if needed.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1434" height="829" src="https://wp.apollographql.com/wp-content/uploads/2021/12/image4.gif" alt="" class="wp-image-11510"/></figure>



<h3 class="wp-block-heading"><a href="#make-sure-there-are-no-breaking-changes" aria-hidden="true" class="aal_anchor" id="make-sure-there-are-no-breaking-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>Make sure there are no breaking changes</h3>



<p class="wp-block-paragraph">Try running an operation check on your local schema by either:</p>



<ol class="wp-block-list"><li>Using the Run check button from the loaded diff view or</li><li>Going to the Checks tab and selecting a registered graph to check against</li></ol>



<p class="wp-block-paragraph">Once you see a summary of results, you can also view more details by navigating to the main checks page on Studio.</p>



<p class="wp-block-paragraph">Remember, you can always move back and forth between Sandbox and the full Studio experience by clicking the box icon in the top righthand corner in the navigation bar.</p>



<p class="wp-block-paragraph">⚠️ <strong>Note:</strong> For checks to work, you’ll need to have a Studio account with a registered graph that is receiving traffic and access to Checks, which is available on Team and Enterprise plans only.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1430" height="824" src="https://wp.apollographql.com/wp-content/uploads/2021/12/image3.gif" alt="" class="wp-image-11507"/></figure>



<h2 class="wp-block-heading"><a href="#try-these-new-improvements-out-today" aria-hidden="true" class="aal_anchor" id="try-these-new-improvements-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 these new improvements out today!</h2>



<p class="wp-block-paragraph"><a href="https://studio.apollographql.com/sandbox/">Head over to Apollo Sandbox</a> and compare your local changes with registered graphs and ensure there are no breaking changes! And as always, we love hearing from you, so if you have any feedback, please fill out this <a href="https://forms.gle/4G2cEumrh85jgDF1A">feedback form</a> or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


How to run diffs and operation checks in Apollo Sandbox


<p class="wp-block-paragraph">The Apollo Studio Explorer is an incredible GraphQL IDE that makes it quick and easy to browse schemas and run operations against them. But wouldn’t it be awesome if you could embed the Explorer into external pages so that you could use it inside your product documentation, internal wiki, or blog post? Now you can! Let’s take a look at how.&nbsp;</p>



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



<p class="wp-block-paragraph">Making your graph publicly visible is as easy as flipping a switch. Simply navigate to the Settings page for your graph in Apollo Studio and under the Access tab, set a variant of your choosing as “public.” That particular variant of your graph is now publicly visible in Apollo Studio! When a variant of a graph is set to public, anyone can navigate to the public Studio URL for that variant and access the README, schema reference, changelog, and Explorer (this is equivalent to <a href="https://www.apollographql.com/blog/announcement/platform/sharing-your-graph-just-got-a-whole-lot-easier-announcing-unlimited-consumer-seats/">Consumer-level access</a>).&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh5.googleusercontent.com/pW9HiTs_J8dA1QhnrQryA59ueVwl5MQ7mEwMuKMK_SyF9zqgOVyolSFsP2kDwkoy-Rj33p0SZ8cal8DiUd1MsbjQyJS_yyE2FZuaXUB228HeB0GhgAJLoEYzBo1AUPLTQhF838ie" alt=""/></figure>



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



<p class="wp-block-paragraph">Now that your graph is public, head over to Explorer for that graph. If you would like to embed Explorer with a default operation, enter the operation in the editor pane in Explorer before copying the embed snippet (also, maybe test it out first to make sure it works 😄). Then click on the meatball menu right of your operation and click on “Embed this operation.” You can also find the action to embed under the Explorer Settings tab in Explorer.&nbsp;&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh6.googleusercontent.com/XRgQ7j_JjZL6F4abOOnySqohxEq6w_S0JyR70EB7X6l4TfZHmbEUJ_NeZS5jnHpxfDvN6ASdTyrIHfsuyAgYyNa2mAA1otknS69127ZDJKIoNX2MvPmKwkjw-ZDThM4EFUYW8oJy" alt=""/></figure>



<p class="wp-block-paragraph">In the embed modal, you can also toggle any configuration options that you would like such as embedded Explorer with dark theme and keeping the docs panel closed by default. Once you have configured it to your liking, copy the code snippet to embed!</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh6.googleusercontent.com/5brrxUjyTiICqeeApWh2uh4FQ_dW_GEZ4Vw-snud_9sJ2-hINyfx6dXUKOEqbysPo1Ey0khiQUUYFxLjLCMk7eIXpBRzDld0sJF9BVbtgzMuQdt65WV7lG6t9tgK4qvWyy4SeoZT" alt=""/></figure>



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



<p class="wp-block-paragraph">Now all you have to do is take the embed code snippet and paste it in the code of any webpage where you would like to embed Explorer like we have done here! Try the embedded Explorer for yourself below.</p>



<div style="width: 100%; height: 500px;" id="embedded-explorer"></div>
<script src="https://embeddable-explorer.cdn.apollographql.com/_latest/embeddable-explorer.umd.production.min.js"></script> 
<script>
  setTimeout(() => new window.EmbeddedExplorer({
    target: '#embedded-explorer',
    graphRef: 'SpaceX-pxxbxen@current',
    endpointUrl: 'https://api.spacex.land/graphql/',
    persistExplorerState: false,
    initialState: {
      document: `query ExampleQuery {
  company {
    ceo
  }
  roadster {
    apoapsis_au
  }
}`,
      variables: {},
      headers: {},
      displayOptions: {
        showHeadersAndEnvVars: false, 
        docsPanelState: 'closed', 
        theme: 'dark',
      },
    },
  }), 1000);
</script>



<h2 class="wp-block-heading"><a href="#embed-your-graphs-with-explorer-today" aria-hidden="true" class="aal_anchor" id="embed-your-graphs-with-explorer-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>Embed your graphs with Explorer today!</h2>



<p class="wp-block-paragraph">Excited? We hope so! Sharing graphs with a broader audience on your own documentation portals using Apollo Explorer’s amazing experience could not get any easier. <a href="https://studio.apollographql.com/sandbox/explorer?endpoint=https%3A%2F%2Fapi.spacex.land%2Fgraphql%2F&amp;explorerURLState=N4IgJg9gxgrgtgUwHYBcQC4QEcYIE4CeABADICGMSUAFggM5HAA6SRRANhVbQ862xy40A%2BgQRk8LAUTgBLOnVkQkwpGURSiAXxZaQAGhAA3CbLIAjdvQwgQWoA">Head over to Studio</a> and get wider adoption of your graph today! And as always, we love hearing from you, so if you have any feedback, please drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


Embed Apollo Explorer Anywhere


<p class="wp-block-paragraph">At Apollo, we talk a lot about building a unified graph, and for good reason. A unified graph provides incredible benefits &#8211; a single source of truth for all services, faster apps, faster delivery, less maintenance overhead, and more.&nbsp;</p>



<p class="wp-block-paragraph">But unification introduces new challenges, especially at scale;</p>



<p class="wp-block-paragraph"><em>“How do I support different experiences and levels of access for different personas or types of users like customers, employees, suppliers, and partners?”</em></p>



<p class="wp-block-paragraph"><em>“How do I provide my partners and public API users with a schema scoped for their integration and app development needs?”</em></p>



<p class="wp-block-paragraph"><em>“How do I provide client-specific BFFs and experience-driven schemas alongside a canonical domain-driven schema?”</em></p>



<p class="wp-block-paragraph"><em>“How do I restrict access to experimental or non-stable parts of the schema, but still allow access for testing and early adopters?”</em></p>



<p class="wp-block-paragraph">These common challenges boil down to one question: <strong>“how do I serve multiple different audiences with a single unified graph?”</strong> Today, we’re excited to announce Contracts, a new feature in preview on Apollo’s Enterprise plan that allows you to create tailored graphs for different audiences by applying filters to a single unified graph.</p>



<h2 class="wp-block-heading"><a href="#modularity-when-consuming-the-graph" aria-hidden="true" class="aal_anchor" id="modularity-when-consuming-the-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>Modularity when consuming the graph</h2>



<p class="wp-block-paragraph">We often discuss consolidating APIs, but there are benefits to separation as well. Separate APIs can be managed by independent backend teams with less coordination. They can also be tailored to whoever will be consuming them and individually governed for granular access control.&nbsp;</p>



<p class="wp-block-paragraph">We want to unify our services into a single graph to reduce manual API maintenance and improve delivery velocity, but we don’t want to lose the benefits of separate APIs. Apollo Federation accomplishes this for the backend by modularizing the graph into subgraphs that can be modified asynchronously, allowing service teams to build a unified graph while still operating independently. Contracts deliver the same modularity for the frontend.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh4.googleusercontent.com/C7ycR2cyk5VACxMpjCNerLEc4vf7VgJlPe8HArwSnkw8RTSMxaZkfjKdvoYHTpOCND1DUuDOnzsCArDtat1hoaD7TCOxmauJG5aTiAGLFH0LEWKG3w8lAl63TdeVwO8Fceh46D86" alt=""/></figure>



<p class="wp-block-paragraph">With Contracts, graph platform teams can create tailored experiences for multiple audiences by creating contract graphs that contain a filtered subset of the unified graph. Each contract can align with a particular developer audience to streamline the graph experience, rather than providing the entire graph to every internal and external developer. </p>



<p class="wp-block-paragraph">Using contracts you can create separate graphs for partner developers, specific client applications, public APIs, experimental features, and more without losing any of the benefits of the unified graph.</p>



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



<p class="wp-block-paragraph">Contracts work with a simple but powerful new <code class="" data-line="">@tag</code> directive which you can apply to fields, interfaces, objects, and unions in your subgraph schemas. You then create filter rules which include or exclude certain tags. Anything not included in the contract will be removed from the client-facing schema for that contract but will still be included in the internal supergraph schema to be used for Federation and routing.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh3.googleusercontent.com/V-ik_hqpTy-DVEAc5xkokOWohdmOjPJxGeMdw9LJkIv2oUSd6wqNz3eVk3q382a0TZI9CcsCAfaAvMwMsOBEc05fIicHxTBVJd6jH5i7byd6lUR0cOq2jcJpK8NpXJkIPvS7zO-e" alt=""/></figure>



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



<p class="wp-block-paragraph">There are two ways you can use a contract schema &#8211; as documentation or as a running endpoint.&nbsp;</p>



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



<p class="wp-block-paragraph">You might use a contract schema just for documentation if you simply want to streamline the graph experience for internal developers by only showing them the fields they need from the graph. For example, you could create a mobile contract schema that only includes parts of the graph that are relevant to mobile developers and removes unnecessary parts that may only be useful for web or IoT applications.&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh3.googleusercontent.com/y_CGjvKlyyQzkjf26IxM_asEz_wQt-q0nmHnVYohm86YXqsK494uYMGicqDzQlCrpC86NSXs_JbTwtRQTdrUjYHAvsA9vcPzQIbG2uQunP8AkUl65-92ckPVJz1dFBriVy2Nga0I" alt=""/><figcaption><meta charset="utf-8"><em>Documentation contract</em></figcaption></figure>



<p class="wp-block-paragraph">With Apollo Studio you can point consumers at the tailored contract schema so that they get the full Studio experience with a changelog, comprehensive schema reference, and interactive Explorer scoped to the relevant subset of the graph.</p>



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



<p class="wp-block-paragraph">There may be times, however, when we want to restrict not only what appears in the documentation, but also what can actually be queried by a particular audience. To accomplish this, we can deploy a dedicated Apollo Gateway or Router to run the contract schema as a separate endpoint.&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh5.googleusercontent.com/CFHUa0cKxHz4zBzLtWflZm6Fx8vkGAK5Ma4ueehqJX9dQUEzqC3T5POt84Y9zN_6xTDsHEYHDA61mBM1JbYqIxw8ZtxbjNKcP6nCVLZ1oW2qM4UtPsSgmRa229YQeFY4GNMUiQGl" alt=""/><figcaption><em>Deployed contract</em></figcaption></figure>



<p class="wp-block-paragraph">Developers accessing the deployed contract endpoint will only be able to query parts of the graph that exist in the contract schema and will encounter an error if they try to query for fields that are not included in the contract. This can be particularly useful for building endpoints for external partners or for a public-facing API.</p>



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



<p class="wp-block-paragraph">BFFs and other customized APIs for different audiences are fantastic for providing a streamlined developer experience, but they also create overhead for whoever maintains them. One of the best things about contracts is that they automatically remain up-to-date without any manual work when combined with Apollo Managed Federation.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh3.googleusercontent.com/Y8eIp6JgHd123W0MoVL_Odzun7AVC4iST_ajRRz1bVoIANjAfmvXCm_Tn71-WJscA-YXHvVbDr9UN50fWnDGTXWRn-CfsfJT9qNQdc9lxGoEDlRKPzpEKL1a_ugBIOs3VadAp2xB" alt=""/></figure>



<p class="wp-block-paragraph">With Managed Federation in Apollo Studio, independent backend service teams publish subgraph schema updates into Apollo, including any tags to be used for contracts. The subgraph schemas are composed together into a supergraph schema which is then used to power a graph router like the Apollo Gateway or Apollo Router. Using the included tags, contract filters are run on the unified supergraph schema automatically deriving subset contract schemas.</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">Contracts are available in preview today on Apollo’s Enterprise plan! If you’d like to learn more about Contracts, check out our <a href="https://www.apollographql.com/docs/studio/contracts/">documentation</a> or join us virtually today at <a href="https://summit.graphql.com/">GraphQL Summit</a> where we’ll be doing a deep dive and demo on contracts during the “How to Serve Many Audiences with One Graph” talk! If you aren’t on Apollo Enterprise and would like to try it out, <a href="https://www.apollographql.com/contact-sales/">talk to us</a> about an Enterprise trial.</p>


Introducing Contracts: serve many audiences with a unified graph

Launch with confidence: introducing the Apollo Studio Launches dashboard


<p class="wp-block-paragraph">Intrigued? We hope so! We recently introduced three of the most requested features from our developer community &#8211; tabs in Explorer, offline support for local development in Sandbox, and an improved integration experience between VS Code and Apollo Studio. The request for tabs in Explorer, especially, has been overwhelming:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="322" src="https://wp.apollographql.com/wp-content/uploads/2021/10/image-3-1024x322.png" alt="" class="wp-image-9472" srcset="https://wp.apollographql.com/wp-content/uploads/2021/10/image-3-1024x322.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/10/image-3-300x94.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/10/image-3-768x242.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/10/image-3.png 1068w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">We even dedicated a Slack emoji to it!</p>



<figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2021/10/tab-msg.gif" alt="" class="wp-image-9474" width="600" height="199"/></figure>



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



<p class="wp-block-paragraph">Need I say more? Test out <a href="https://www.apollographql.com/blog/tooling/graphql-ide/the-5-most-useful-features-of-apollo-studio-explorer-that-you-didnt-know-existed/#:~:text=1.%20Multiple%20operations">multiple operations in the same tab</a> or multiple operations in different tabs when exploring your GraphQL endpoint in Explorer! Testing and managing multiple operations in Explorer could not get any easier.&nbsp;</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1435" height="788" src="https://wp.apollographql.com/wp-content/uploads/2022/01/Screen-Recording-2022-01-27-at-10.53.12-AM.gif" alt="" class="wp-image-11987"/></figure>



<h2 class="wp-block-heading"><a href="#2-offline-support-for-local-development-in-sandbox" aria-hidden="true" class="aal_anchor" id="2-offline-support-for-local-development-in-sandbox"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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>2. Offline support for local development in Sandbox</strong></h2>



<p class="wp-block-paragraph">We launched <a href="https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development/">Apollo Sandbox</a> three months ago. And now, we are making it available offline for local development. Flaky internet? Worry no more! If you are developing <em>locally</em> using Sandbox, you can continue to work without any internet connection.&nbsp;</p>



<p class="wp-block-paragraph">⚠️ <strong>Note:</strong> you’ll need to load at least one Sandbox tab while you’re connected to the internet to update to the latest bundle, but after that, you can continue to work without any internet connection.</p>



<h2 class="wp-block-heading"><a href="#3-run-operations-in-apollo-studio-from-vscode" aria-hidden="true" class="aal_anchor" id="3-run-operations-in-apollo-studio-from-vscode"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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>3. Run operations in Apollo Studio from VSCode</strong></h2>



<p class="wp-block-paragraph">The final feature that we recently added is the “Run in Studio” button in our <a href="https://marketplace.visualstudio.com/items?itemName=apollographql.vscode-apollo">VS Code extension</a>. There is now a hover on the play button in VS Code, which opens the exact operation and fragments that you want to test in Apollo Studio Explorer, saving you dozens of clicks and the tedious task of setting up an operation to test!</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1266" height="877" src="https://wp.apollographql.com/wp-content/uploads/2021/10/Screen-Recording-2021-09-23-at-08.29.42-PM.gif" alt="" class="wp-image-9446"/></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><strong>Get Started!</strong></h2>



<p class="wp-block-paragraph">So what are you waiting for? All these features are now available in Apollo Studio Explorer and Apollo Sandbox. <a href="https://studio.apollographql.com/sandbox/explorer?endpoint=https%3A%2F%2Fapi.spacex.land%2Fgraphql%2F&amp;explorerURLState=N4IgJg9gxgrgtgUwHYBcQC4QEcYIE4CeABADICGMSUAFggM5HAA6SRRANhVbQ862xy40A%2BgQRk8LAUTgBLOnVkQkwpGURSiAXxZaQAGhAA3CbLIAjdvQwgQWoA">Head over there</a> and try them out! And as always, we love hearing from you, so if you have any feedback, please drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


We’re shipping 3 of our most requested features!


<p class="wp-block-paragraph">When you’re maintaining a graph that’s used by multiple developers, it’s important to make sure everyone is on the same page by providing instructions on how to get started with consuming and contributing to the graph. Today, we’re introducing a way to do that natively in Apollo Studio with the new README page.</p>



<p class="wp-block-paragraph">The README appears as a new 🏠 icon in the left nav in Apollo Studio and will now be the default page shown when navigating to any graph in Apollo.</p>



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



<p class="wp-block-paragraph">The new page includes helpful graph metadata like its name, when it was last updated, its endpoint, the most recent commit hash, links to Explorer and its changelog, and, most importantly, a README! As more developers and teams begin to use your graph, the README ensures that everyone has the information they need to onboard quickly and more independently.</p>



<figure class="wp-block-image size-large is-style-default"><img loading="lazy" decoding="async" width="1024" height="520" src="https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1024x520.png" alt="" class="wp-image-9251" srcset="https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1024x520.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-300x152.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-768x390.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1536x780.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-2048x1040.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1200x609.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1980x1005.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p class="wp-block-paragraph">The README for each variant contains default markdown content to help get you started, but it can easily be updated to include any pertinent information for your graph like:</p>



<ul class="wp-block-list"><li>A description of your graph</li><li>Instructions for access and authentication</li><li>Example operations to showcase how the graph can be used</li><li>And more!</li></ul>



<p class="wp-block-paragraph">Unlike a plain markdown document, the README in Apollo Studio also offers graph shortcodes that allow you to reference graph variables with just a click.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="450" src="https://wp.apollographql.com/wp-content/uploads/2021/09/readme.gif" alt="" class="wp-image-9272"/></figure>



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



<p class="wp-block-paragraph">The README is available right now in Apollo Studio, so what are you waiting for? <a href="http://studio.apollographql.com">Head over there</a> and make an awesome README to help developers make the most of your graph! And as always, we love hearing from you, so if you have any feedback on the README feature in Apollo Studio, please fill out our <a href="https://docs.google.com/forms/d/e/1FAIpQLScIBKsl_s7GO7ebwG3JAbPdcszn5IErni3nyyjMW9lfnXsUpw/viewform?usp=sf_link">feedback survey</a>!</p>


Create a README to onboard developers to the graph


<p class="wp-block-paragraph">Today, we’re introducing audit logs in Apollo Studio Enterprise. With audit logs, you can export a data file with key actions taken within your organization.</p>



<p class="wp-block-paragraph">As your graph scales to more teams in your organization, you need visibility into all of the potential change points on your graph that could affect its stability or performance. We built audit logs to give you more confidence in your graph governance and help you meet any compliance or security requirements.</p>



<p class="wp-block-paragraph"><strong>Use Cases for Audit Log</strong></p>



<ul class="wp-block-list">
<li>Investigate an incident and see what actions lead up to that incident by exporting a log for a time period and graph</li>



<li>See what actions an individual has taken within a time period</li>



<li>Investigate your automated systems that are changing the graph</li>
</ul>



<p class="wp-block-paragraph"><strong>Some actions tracked by audit log:</strong></p>



<ul class="wp-block-list">
<li>Creating a graph or variant</li>



<li>Publishing of schema/subschema</li>



<li>Provisioning or inviting users</li>



<li>Adjusting billing</li>



<li>Provisioning or deleting an API key</li>



<li>Adjustments to settings for schema checks</li>
</ul>



<p class="wp-block-paragraph">This is a partial list of what audit logs track, you can see the more complete list of actions tracked in our <a href="https://www.apollographql.com/docs/studio/audit-log/" target="_blank" rel="noreferrer noopener">docs</a>. Audit logs include actions done by individuals as well as automated actions via the API or CLI. Data for the audit log is retained for up to 180 days<strong>.</strong></p>



<p class="wp-block-paragraph"><p><strong>How to download an audit log</strong></p><p>Audit logs are accessible by organization admins via a new Audit tab inside Apollo Studio UI. When requesting a log, you can filter your exports to a specific actor, action on a specific graph, and/or specific time window. Once an audit log export is requested you’ll receive an on-screen indication as well as an email notification when the log is ready for download.</p></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="857" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2021/08/image-1-857x1024.png" alt="Generate an audit log" class="wp-image-8261" srcset="https://wp.apollographql.com/wp-content/uploads/2021/08/image-1-857x1024.png 857w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1-251x300.png 251w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1-768x918.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1.png 1200w" sizes="auto, (max-width: 857px) 100vw, 857px" /><figcaption class="wp-element-caption">Create a customized audit log </figcaption></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="399" src="https://wp.apollographql.com/wp-content/uploads/2021/08/image-1024x399.png" alt="Historical records of audit logs" class="wp-image-8259" srcset="https://wp.apollographql.com/wp-content/uploads/2021/08/image-1024x399.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-300x117.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-768x300.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1536x599.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-2048x799.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1200x468.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1980x772.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">View all of the audit <em>logs</em> that have been requested</figcaption></figure>



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



<p class="wp-block-paragraph"><strong>Get started</strong><br>Audit logs are part of the Studio Enterprise plan. Please <a href="https://www.apollographql.com/contact-sales/?referrer=blog" data-type="URL" target="_blank" rel="noreferrer noopener">reach out to us </a>if you are interested in this feature.</p>


Audit Logs now available in Apollo Studio Enterprise


<p class="wp-block-paragraph">Today, we’re introducing <a href="https://sandbox.apollo.dev" target="_blank" rel="noreferrer noopener">Apollo Sandbox</a> &#8211; the quickest way to navigate and test your GraphQL endpoints. At the end of 2020, we launched development graphs with the goal of making Apollo tools more accessible and valuable for every GraphQL developer. Sandbox takes us another step closer to that goal by making the Apollo Explorer openly available to any developer, with no login required. We’re excited to give back to the GraphQL community with Sandbox, and we think you’ll love using it. Here are a few reasons why:</p>



<h2 class="wp-block-heading"><a href="#1-one-click-query-building-in-explorer" aria-hidden="true" class="aal_anchor" id="1-one-click-query-building-in-explorer"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. One-click query building in Explorer</h2>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1278" height="754" src="https://wp.apollographql.com/wp-content/uploads/2021/06/Screen-Recording-2021-06-11-at-12.39.29-PM-2.gif" alt="" class="wp-image-7755"/></figure>



<p class="wp-block-paragraph">Typing out GraphQL queries by hand is time-consuming at best and a frustrating minefield of confusing paths, missed brackets, and incorrect variables at worst. Explorer offers no-code query-building to eliminate syntax errors and help you be more productive. Of course, if you still need to add hand-written code, you can do just that with Explorer’s editor with query linting and autocomplete.</p>



<h2 class="wp-block-heading"><a href="#2-%e2%8c%98-k-field-and-path-search" aria-hidden="true" class="aal_anchor" id="2-%e2%8c%98-k-field-and-path-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>2. <code class="" data-line="">⌘ + K</code> field and path search</h2>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1278" height="754" src="https://wp.apollographql.com/wp-content/uploads/2021/06/Screen-Recording-2021-06-11-at-01.01.41-PM.gif" alt="" class="wp-image-7757"/></figure>



<p class="wp-block-paragraph">Your graph may be very deep and have thousands of fields and types. You know what data you&#8217;re looking for but the more your graph scales, the more difficult it becomes to navigate the graph to get there. Explorer’s <code class="" data-line="">⌘ + K</code> intelligent search shows you all of the possible paths to a field or type. Choose the path you want to use, and our one-click query builder will add your query to the sandbox without writing a single line of code.</p>



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



<p class="wp-block-paragraph">Once you’ve built your query, Explorer shows you the response in an interactive JSON or table format with collapsible sections and data sorting by clicking on table headers. You can also copy the response to your clipboard, download it as a CSV, or download the JSON.</p>



<h2 class="wp-block-heading"><a href="#4-explore-and-test-your-local-graphql-server" aria-hidden="true" class="aal_anchor" id="4-explore-and-test-your-local-graphql-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>4. Explore and test your local GraphQL server</h2>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1246" height="870" src="https://wp.apollographql.com/wp-content/uploads/2021/06/Screen-Recording-2021-06-11-at-01.24.51-PM.gif" alt="" class="wp-image-7759"/></figure>



<p class="wp-block-paragraph">Just because you’re working on your schema locally doesn’t mean that you shouldn’t have the best tools for the job. You can point Sandbox at any local GraphQL server and use it just as easily as other tools like GraphiQL or GraphQL Playground with zero setup.<br><br>If you want to, you can even use Sandbox with production GraphQL APIs, although introspection needs to be enabled, and APIs that enforce CORS will need to <a href="https://www.apollographql.com/docs/studio/explorer/#cors-policies">allow our URL</a>. That being said, here are a few public endpoints that you can try with Sandbox:</p>



<ul class="wp-block-list"><li><a href="http://sandbox.apollo.dev/?endpoint=https://rickandmortyapi.com/graphql" data-type="URL" data-id="sandbox.apollo.dev/?endpoint=https://rickandmortyapi.com/graphql" target="_blank" rel="noreferrer noopener">sandbox.apollo.dev/?endpoint=https://rickandmortyapi.com/graphql</a></li><li><a href="http://sandbox.apollo.dev/?endpoint=https://api.spacex.land/graphql/" data-type="URL" data-id="sandbox.apollo.dev/?endpoint=https://api.spacex.land/graphql/" target="_blank" rel="noreferrer noopener">sandbox.apollo.dev/?endpoint=https://api.spacex.land/graphql/</a></li><li><a href="http://sandbox.apollo.dev/?endpoint=https://spotify-graphql-server.herokuapp.com/graphql" data-type="URL" data-id="sandbox.apollo.dev/?endpoint=https://spotify-graphql-server.herokuapp.com/graphql" target="_blank" rel="noreferrer noopener">sandbox.apollo.dev/?endpoint=https://spotify-graphql-server.herokuapp.com/graphql</a></li></ul>



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



<p class="wp-block-paragraph">You can use the Schema Reference and Explorer in Sandbox with your GraphQL endpoint just by going to <a href="http://studio.apollographql.com/sandbox">sandbox.apollo.dev</a>. You’ll never have to create an account or log in, though if you do we can show you your query history and open up some additional customization settings.</p>



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



<p class="wp-block-paragraph">We’re excited for you to get hands-on with Sandbox and start using all of the awesome features we highlighted in this post and others that we didn’t mention yet like like Traces, editor hints with response previews, a <code class="" data-line="">graphql-lodash</code> integration, variable auto-creation, data mocking, and more! You can also get even more Sandbox features like query history and advanced Explorer settings by logging into Apollo.<br><br>We deeply value your feedback, so as you try it out, don’t hesitate to let us know what you think. You can leave feedback on Sandbox through <a href="https://forms.gle/qnfPc5n2vhm1JsS58">this form</a>, and if you have any questions or open-ended thoughts, drop them in our community forum.</p>


Apollo Sandbox: an open GraphQL IDE for local development


<p class="wp-block-paragraph">Last year, when we launched <a href="https://www.apollographql.com/blog/introducing-the-apollo-explorer/">Apollo Explorer </a>and our schema reference and changelog, we wanted to help you put the power of your graph into the hands of as many people as possible. Starting today, we&#8217;re making it even easier. You can invite everyone in your organization to explore your graph in Apollo Studio using the new Consumer user role. Consumers will have access only to your graph’s Explorer, the schema changelog, and schema reference documentation. Graph champions now have a way to safely bring the graph to every single person in your company, putting the power of your graph in the hands of everyone who would benefit from it.</p>



<p class="wp-block-paragraph">Even better, you can invite an unlimited number of your team members with a Consumer role in all plan tiers, including our Free and Team plans. Previously, Free and Teams plans only offered admin-level access to your graph, which limited the number of people who could have visibility and access to your graph.</p>



<h3 class="wp-block-heading"><a href="#what-does-the-consumer-role-have-access-to" aria-hidden="true" class="aal_anchor" id="what-does-the-consumer-role-have-access-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><strong>What does the Consumer role have access to?</strong></h3>



<p class="wp-block-paragraph">With the Consumer role, you can provide visibility and discoverability while preventing people from making unwanted changes. Consumers won’t be able to change any settings, see any operational data or metrics, or make any changes to your schema. These restrictions make it suitable to give out safely to anyone casually using your graph or getting started building applications against your graph. All Consumer users will have instant access to:</p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/docs/studio/explorer/">Apollo Studio Explorer</a>, a feature-packed IDE for formulating and executing sample queries. Users can search for fields and find direct paths that can be run as queries, as well as output data in tables along with lots of other conveniences.</li>
</ul>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/docs/studio/explorer/#the-documentation-tab">Schema reference</a> for automated documentation of your graph’s types and operations. By registering your schema in Apollo Studio you get instant reference material for all of your users.</li>



<li><a href="https://www.apollographql.com/docs/studio/org/graphs/#tracking-schema-changes">Changelog</a> for an automated view of changes between each new schema published in the registry. Make it easy to see the evolution of your graph over time.</li>
</ul>



<h3 class="wp-block-heading"><a href="#inviting-the-consumers-to-studio" aria-hidden="true" class="aal_anchor" id="inviting-the-consumers-to-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><strong>Inviting the Consumers to Studio</strong></h3>



<p class="wp-block-paragraph">There are two ways you can <a href="https://www.apollographql.com/docs/studio/org/members/#inviting-members">invite</a> people to be Consumers:</p>



<ol class="wp-block-list">
<li>Directly invite members, pre-assigning them the Consumer Role. This can be done from the “Members” tab of your organization’s settings page inside Apollo Studio.<br><img loading="lazy" decoding="async" src="https://lh5.googleusercontent.com/I20p3C0AWQUDNNSjvGi3iqfPCP_H2J_Dh9sBb-yXDdnk5nXAbPSHbjJXzAT7hWV7I3K__ZTq_T4yUYu5Kx0BygMKGEzzqfgJM5GdBL9PH-R1IOcm_JC6LNRVhaXRmkBbpNS9-1TK" width="442" height="259"></li>
</ol>



<ol class="wp-block-list" start="2">
<li>Create a shareable invite link, assigning the default role as Consumer. This can be done from the “Settings” tab of your organization’s settings page inside Apollo Studio.<br><img loading="lazy" decoding="async" src="https://lh3.googleusercontent.com/wiG_NNRB-N8nnMpyLo_21s4ib0HlVRixiYY3SvdWQyGeXVkAUXJ-FR2iYPyAqf1OcBWuW1B95xklXOKlYTkP4mJN6yb90djSyyyo9EdkmjL9D9Gg5a3Nri1UfeZHPWNUW2QupdWO" width="624" height="96"></li>
</ol>



<h3 class="wp-block-heading"><a href="#what-if-i-need-more-granular-permissions" aria-hidden="true" class="aal_anchor" id="what-if-i-need-more-granular-permissions"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 if I need more granular permissions?</strong></h3>



<p class="wp-block-paragraph"><a href="httpw://www.apollographql.com/pricing">Apollo Studio Enterprise</a> has unlimited access to the Consumer role as well as Enterprise-only roles of Observer, Contributor, and Graph Admin, along with graph-level roles and protected variants that restrict who can make changes to production or other sensitive environments. To learn more about the Enterprise-only user permissions features visit our <a href="https://www.apollographql.com/docs/studio/org/members/">docs</a>.</p>



<h3 class="wp-block-heading"><a href="#we-would-love-to-hear-from-you" aria-hidden="true" class="aal_anchor" id="we-would-love-to-hear-from-you"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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>We would love to hear from you!</strong></h3>



<p class="wp-block-paragraph">Come visit our discussion <a href="https://github.com/apollographql/apollo-studio-community/discussions/68">thread</a> about the new Consumer role to let us know what you think.</p>



<h3 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><strong>Get started today</strong></h3>



<p class="wp-block-paragraph">If you aren’t yet using Apollo Studio, you can sign up today for <a href="https://studio.apollographql.com/signup?referrer=blog">free</a>.</p>


Sharing your graph just got a whole lot easier – Announcing unlimited Consumer seats


<p class="wp-block-paragraph">Building software for the internet in 2021 is hard. It’s no longer just HTML, CSS, and JavaScript. We now have to deliver our products beyond just websites to mobile, voice, in-store, chat, TV, and more—while integrating data from many services and delivering on time. One of the biggest things that slow down developers is waiting to align work with other teams. It is common to get blocked while waiting to coordinate or waiting for their backlog to free up.<br><br></p>



<p class="wp-block-paragraph">We launched Apollo because we believe GraphQL transforms how product engineering teams build new experiences by unblocking teams and allowing them to work in parallel. Front-end teams can build new experiences faster by directly querying the graph and not waiting for new REST endpoints to be built. As each new capability is added to the graph, it&#8217;s available for all other teams to take advantage of it.</p>



<p class="wp-block-paragraph">As we worked with early GraphQL adopters, we realized they needed a solution that could serve the needs of engineering organizations that were running at scale. They wanted the power of a single endpoint coupled with the flexibility of distributed ownership. So in 2019, we launched <a href="https://www.apollographql.com/blog/apollo-federation-f260cf525d21/">Apollo Federation</a> and Apollo Gateway, a Federation-compatible graph router, to help teams use GraphQL in distributed architectures. With Federation, each service or domain team can own their part of the graph schema, known as the subgraph, while building a unified common graph for their developers.</p>



<p class="wp-block-paragraph"><br><br>Next, we launched Apollo’s <a href="https://www.apollographql.com/blog/announcing-managed-federation-265c9f0bc88e/)">Managed Federation,</a> a hosted solution for scaling changes to your federated graph pipelines across many teams. Managed federation helps you reliably deploy schema changes to your Apollo Gateway, including checks for composition integrity. It prevents shipping breaking change by using your live traffic as an automated test suite. We’re thrilled by the growth and acceptance of Managed Federation by hundreds of the world’s most innovative companies. Apollo customers now run more than 2 billion queries a day through Apollo federated data graphs, representing a 400% annual growth.</p>



<p class="wp-block-paragraph"><br><br>Equally validating is the industry adoption of the Federation Specification. In addition to Apollo’s Server, there are now more than a dozen <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/federation/other-servers/" target="_blank">GraphQL servers</a> that support federation. Netflix open-sourced their <a rel="noreferrer noopener" href="https://netflix.github.io/dgs/" target="_blank">DGS</a> GraphQL Server that was built for SpringBoot and they are<a rel="noreferrer noopener" href="https://www.infoq.com/presentations/netflix-api-graphql-federation/" target="_blank"> betting their entire graph strategy</a> on Federation. Companies including <a rel="noreferrer noopener" href="https://medium.com/adobetech/graphql-making-sense-of-enterprise-microservices-for-the-ui-46fc8f5a5301" target="_blank">Adobe</a>, <a rel="noreferrer noopener" href="https://medium.com/walmartglobaltech/federated-graphql-walmart-bfc85c2553de" target="_blank">Walmart</a>, and <a rel="noreferrer noopener" href="https://www.apollographql.com/blog/9-lessons-from-a-year-of-apollo-federation/" target="_blank">StockX</a> are all choosing Federation. Database vendors are also adopting Apollo Federation as a graph integration strategy. The latest to join is DataStax whose engineers are adding Apollo Federation to the open-source data gateway <a rel="noreferrer noopener" href="https://stargate.io/" target="_blank">Stargate</a>, delivering Federation-ready GraphQL APIs to access Apache Cassandra™ stored data.</p>



<p class="wp-block-paragraph"><br><br>The most important signal that Federation is solving real-world problems are the stories we’re hearing from our customers:</p>



<h2 class="wp-block-heading"><a href="#fast-moving-startups-powering-their-product-development-with-federation" aria-hidden="true" class="aal_anchor" id="fast-moving-startups-powering-their-product-development-with-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><strong>Fast-moving startups powering their product development with Federation</strong></h2>



<p class="wp-block-paragraph"><a href="http://modernhealth.com">Modern Health</a>, a startup founded in 2017, chose Apollo Federation to help power their service-oriented architecture strategy and fulfill their mission of democratizing access to mental health.</p>



<p class="wp-block-paragraph"><br><br><em>&#8220;We chose Apollo so we can continue to focus on our company mission &#8211; destigmatizing and making mental health more accessible for employees across the world. Apollo’s Federation empowers our engineering teams to work independently while collaborating on a rapidly growing graph that is becoming central to how we deliver industry-leading products and features to our growing global customer base.&#8221;</em>&#8211; Nick DiRienzo, Software Engineer, Modern Health</p>



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



<p class="wp-block-paragraph">We’re excited that Federation has become the industry-standard choice for distributed GraphQL and today our teams are announcing several new integrated Federation tools including composition validation and webhooks in Apollo Studio as well as:</p>



<ul class="wp-block-list"><li><strong><a href="https://github.com/apollographql/apollo-workbench-vscode">Workbench</a></strong> is a VS Code plugin that helps developers collaborate on schema design in a federated graph</li><li><strong><a href="https://www.apollographql.com/docs/rover/">Rover CLI</a></strong> is a new tool to access all the power of Federation from the command-line and integrates well in all languages and CI environments.</li></ul>



<p class="wp-block-paragraph">You can learn more about these tools <a href="https://www.apollographql.com/blog/powerful-new-graphql-tools-for-apollo-federation">here</a> and at <a href="https://summit.graphql.com/">GraphQL Summit Worldwide</a> on April 7th where we will be talking about some of the new enhancements to our platform, and <a href="https://summit.graphql.com/webinars/graphql-summit-scale-presented-by-apollo/">GraphQL Summit Scale </a>on April 8th where we will talk about the technical, cultural and organizational best practices for scaling GraphQL.<br></p>


Unblocking teams to go faster with Apollo Federation


<p class="wp-block-paragraph">Developers love GraphQL because of its amazing developer experience.</p>



<p class="wp-block-paragraph">Yet even the best software has rough edges. This year, we embarked on a mission to identify challenges with current GraphQL tools in hopes that we could make an amazing developer experience even better.</p>



<p class="wp-block-paragraph">We chatted with dozens of developers, and the pain points and workarounds we heard were all too familiar. One web developer with over 20 years of experience avoided rebooting their computer while using GraphiQL so they wouldn’t lose their queries. A technical product manager described searching through their graph with 4,000 types as a scavenger hunt, even if they knew what they were looking for. And engineers of all levels lamented the repetitive, error-prone nature of typing out GraphQL syntax for variables and fragments.</p>



<p class="wp-block-paragraph">There had to be a better way! So we put our heads together to imagine the GraphQL IDE of the future.</p>



<p class="wp-block-paragraph">Our first major milestone was releasing the free&nbsp;<strong><a href="https://www.apollographql.com/blog/introducing-the-apollo-explorer/">Apollo Studio Explorer</a></strong>&nbsp;back in June, which only supported registered production graphs. Today, we’re thrilled to announce&nbsp;<strong>development graphs</strong>, which enable you to use all of Apollo Explorer’s powerful features (like intelligent search and variable extraction) with your locally running GraphQL server! 🚀</p>



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



<p class="wp-block-paragraph"><a href="http://studio.apollographql.com/?referrer=blog">Apollo Studio</a> is our cloud service for developing and delivering a data graph. While Apollo Studio also includes tools for GraphQL CI/CD and observability, we’re going to focus on the <strong>Apollo Studio Explorer</strong> in this post.</p>



<p class="wp-block-paragraph">The&nbsp;<strong>Apollo Explorer&nbsp;</strong>is a GraphQL IDE in the cloud specifically tailored to GraphQL developers. Connecting your GraphQL IDE to the cloud unlocks a whole new world of possibilities that aren’t achievable with existing open source tools. Worried about losing your query history? Apollo Explorer saves your query history to the cloud automatically, so you can seamlessly pick up where you left off even after you shut down your computer for the day.</p>



<p class="wp-block-paragraph">Up until now, the Apollo Explorer was only usable with registered graphs in production. With development graphs, you can take advantage of all the cool features Apollo Explorer offers (like extracting variables, one-click query building, and intelligent search) in your local development environment. Just like the rest of Apollo Explorer, development graphs are free to use forever with no limitations, whether you’re just getting started or have a graph with 4,000 types.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="354" src="https://wp.apollographql.com/wp-content/uploads/2021/01/dev-graphs_diagram_blog-1024x354.png" alt="" class="wp-image-6576" srcset="https://wp.apollographql.com/wp-content/uploads/2021/01/dev-graphs_diagram_blog-1024x354.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/01/dev-graphs_diagram_blog-300x104.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/01/dev-graphs_diagram_blog-768x265.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/01/dev-graphs_diagram_blog-1536x531.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/01/dev-graphs_diagram_blog-2048x708.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/01/dev-graphs_diagram_blog-1200x415.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/01/dev-graphs_diagram_blog-1980x684.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></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">Setting up Apollo Explorer with your local graph should be faster than making a pot of coffee. No code changes are required. If it’s not,&nbsp;<a href="https://github.com/apollographql/apollo-studio-community/issues">let us know</a>&nbsp;where you get stuck so we can help you through it.</p>



<p class="wp-block-paragraph">First, you’ll run your GraphQL server locally. Development graphs work great with Apollo Server, or any spec-compliant GraphQL server in other languages like Java, Rust, and Python. If you don’t have a graph handy, you can&nbsp;<a href="https://github.com/apollographql/fullstack-tutorial">clone our tutorial graph</a>&nbsp;and run&nbsp;<code class="" data-line="">cd final/server &amp;&amp; npm install &amp;&amp; npm start</code>.</p>



<p class="wp-block-paragraph">Next, you’ll head to <a href="http://studio.apollographql.com/dev?referrer=blog">studio.apollographql.com/dev</a>. If you don’t have an Apollo Studio account, you will need to create one by signing up with your GitHub account or email address.</p>



<p class="wp-block-paragraph">Finally, choose a name for your graph, select the “Development” graph type, add your localhost endpoint (Apollo Server’s default is&nbsp;<code class="" data-line="">http://localhost:4000</code>), and click “Create Graph”.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="935" src="https://wp.apollographql.com/wp-content/uploads/2020/12/image-1024x935.png" alt="Screen Shot 2020-12-03 at 10.48.40 PM.png" class="wp-image-6431" srcset="https://wp.apollographql.com/wp-content/uploads/2020/12/image-1024x935.png 1024w, https://wp.apollographql.com/wp-content/uploads/2020/12/image-300x274.png 300w, https://wp.apollographql.com/wp-content/uploads/2020/12/image-768x701.png 768w, https://wp.apollographql.com/wp-content/uploads/2020/12/image.png 1148w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">&nbsp;And that’s it! You’re ready to start querying.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="457" src="https://wp.apollographql.com/wp-content/uploads/2020/12/apollo-studio-explorer-1-1024x457.png" alt="Screenshot of the Apollo Studio Explorer" class="wp-image-6466" srcset="https://wp.apollographql.com/wp-content/uploads/2020/12/apollo-studio-explorer-1-1024x457.png 1024w, https://wp.apollographql.com/wp-content/uploads/2020/12/apollo-studio-explorer-1-300x134.png 300w, https://wp.apollographql.com/wp-content/uploads/2020/12/apollo-studio-explorer-1-768x343.png 768w, https://wp.apollographql.com/wp-content/uploads/2020/12/apollo-studio-explorer-1-1536x686.png 1536w, https://wp.apollographql.com/wp-content/uploads/2020/12/apollo-studio-explorer-1-2048x915.png 2048w, https://wp.apollographql.com/wp-content/uploads/2020/12/apollo-studio-explorer-1-1200x536.png 1200w, https://wp.apollographql.com/wp-content/uploads/2020/12/apollo-studio-explorer-1-1980x884.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph">&nbsp;When you make changes to your schema, Apollo Explorer will pick them up automatically with no reloading required on your end. The graph you query will always reflect what’s on your local machine.</p>



<p class="wp-block-paragraph">Since development graphs run locally through introspection, they are completely private to you. Development graphs enable you to build, test, and document your schema changes locally, as well as preview graph changes in local branches and PRs.</p>



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



<p class="wp-block-paragraph">We think you’re going to love developing your graph locally with Apollo Explorer. Our team has been using Apollo Explorer to build the graph powering our cloud service for a couple months now.</p>



<p class="wp-block-paragraph">Spoiler alert: the developer experience has been awesome! Apollo Explorer development graphs have given our engineers a major productivity boost, which is something we all need in 2020. 😂 Here are just a few of our team’s favorite time-saving features:</p>



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



<p class="wp-block-paragraph">Typing out GraphQL queries by hand is error-prone, even for GraphQL experts. Not only do missing brackets and incorrect variables present a formidable learning curve for newcomers, they also slow experienced developers down. Apollo Explorer’s no-code query building experience helps you fetch your data faster without the headache of GraphQL syntax errors.</p>



<p class="wp-block-paragraph">If you need to augment your queries with hand-written code, Apollo Explorer’s editor, based on Monaco, has rich autocomplete and IntelliSense so you can intuitively find the fields you’re looking for.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="954" height="544" src="https://wp.apollographql.com/wp-content/uploads/2020/12/point-and-click.gif" alt="One-click query building in the Apollo Studio Explorer" class="wp-image-6440"/><figcaption class="wp-element-caption">One-click query building saves you time writing GraphQL queries</figcaption></figure>



<h3 class="wp-block-heading"><a href="#intelligent-search" aria-hidden="true" class="aal_anchor" id="intelligent-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>Intelligent search</h3>



<p class="wp-block-paragraph">As your graph grows, search becomes critical for quickly discovering fields and types. To save you the scavenger hunt, we’ve designed an intelligent search experience for navigating graphs of any size, even graphs with thousands of types.</p>



<p class="wp-block-paragraph">Type ⌘ + K to open the search window, then enter what you’re looking for. Once you find your desired result, one click will show you all possible paths so you can add the field to your query immediately without writing any code.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1217" height="616" src="https://wp.apollographql.com/wp-content/uploads/2020/12/search-1-1.gif" alt="Intelligent search in Apollo Studio Explorer" class="wp-image-6478"/><figcaption class="wp-element-caption">Intelligent search helps you navigate large graphs</figcaption></figure>



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



<p class="wp-block-paragraph">Nearly every GraphQL query we write uses variables or fragments. To save time typing out the syntax, we built a neat shortcut that extracts inline variables and fragments.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="600" height="538" src="https://wp.apollographql.com/wp-content/uploads/2020/12/inline-extract-vars.gif" alt="Extracting variables in Apollo Studio Explorer" class="wp-image-6448"/><figcaption class="wp-element-caption">Extracting variables reduces frustrating syntax errors</figcaption></figure>



<h2 class="wp-block-heading"><a href="#but-wait-theres-more" aria-hidden="true" class="aal_anchor" id="but-wait-theres-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>But wait, there’s more!</h2>



<p class="wp-block-paragraph">There are so many other features we built to help save you time, like&nbsp;<em>inline hints</em>,&nbsp;<em>operation history</em>,&nbsp;<em>mock responses</em>,&nbsp;<em>inlined performance traces</em>, and&nbsp;<em>response display modes</em>, but we’ll leave it to you to try them out and let us know how you like ‘em!&nbsp;</p>



<p class="wp-block-paragraph">You can also <a href="https://www.apollographql.com/docs/studio/explorer?referrer=blog">read the docs on the Explorer</a> for a full list of what you can do.</p>



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



<p class="wp-block-paragraph">Thanks so much for embarking on this journey with us to build the GraphQL IDE of the future! If you enjoyed this post, we encourage you to <a href="http://studio.apollographql.com/dev?referrer=blog">test out Apollo Studio with your local graph</a>. Ultimately, we want to make your experience building and querying your graph more productive and enjoyable so you can focus on shipping features.</p>



<p class="wp-block-paragraph">As you try things out, please know that we deeply value your feedback, and that we read and consider everything you share with us:</p>



<ul class="wp-block-list">
<li><a href="https://forms.gle/hhfA72JPC3fw43Wx5">Please use this form</a>&nbsp;to share feedback on Apollo Explorer</li>



<li>Submit open-ended suggestions and bug reports on our&nbsp;<a href="https://github.com/apollographql/apollo-studio-preview-docs#try-studio-with-the-github-graph">feedback repository</a>.</li>
</ul>



<p class="wp-block-paragraph">We’re excited to hear from you. Happy querying! 🚀</p>


Apollo Studio Explorer development graphs

Apollo Studio: A GraphQL IDE for every environment


<p class="wp-block-paragraph">We&#8217;re all used to celebrating big, sparkly successes, like major releases, new customer successes, and the end of a long saga of re-architecture. My favorite kind of success, however, often goes unnoticed:&nbsp;<strong>the success of&nbsp;<em>avoiding failure</em></strong><em>.</em></p>



<p class="wp-block-paragraph">In our day-to-day lives as engineers, sadly, these events come to pass without much recognition: the sweet quietude of an incident avoided, rolling out a new feature with only a few code changes thanks to a sound architecture, automation set up behind the scenes, keeping your monitors silent. One of my favorite features of Apollo Studio enables exactly this characteristic, and it&#8217;s probably not the one you&#8217;re thinking of! I&#8217;m talking about&nbsp;<strong>GraphQL client awareness</strong>&nbsp;— the ability to understand&nbsp;<em>which clients</em>&nbsp;are using&nbsp;<em>which fields</em>&nbsp;of your graph.</p>



<p class="wp-block-paragraph">In this article, I&#8217;ll talk about what GraphQL client awareness is, the kinds of workflows it enables, and how we&#8217;ve used it for our own graph at Apollo (I know, I know — I&#8217;m biased) to avoid incidents and speed up development.</p>



<h2 class="wp-block-heading"><a href="#maintaining-a-single-client" aria-hidden="true" class="aal_anchor" id="maintaining-a-single-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>Maintaining a single client</h2>



<p class="wp-block-paragraph">At Apollo, we started with one main client for our GraphQL API: Apollo Studio&#8217;s web UI.&nbsp;</p>



<p class="wp-block-paragraph">With only a single client, it was easy to determine the context of fields in use. Whenever we wanted to perform a breaking change, like removing a field relied on by a page in the app, it was easy enough to accomplish: add the new field, change the client to use the new one, and remove the old field. Voila!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="992" height="556" src="https://wp.apollographql.com/wp-content/uploads/2020/08/Screen-Shot-2020-07-14-at-11.37.30-AM.png" alt="" class="wp-image-4341" srcset="https://wp.apollographql.com/wp-content/uploads/2020/08/Screen-Shot-2020-07-14-at-11.37.30-AM.png 992w, https://wp.apollographql.com/wp-content/uploads/2020/08/Screen-Shot-2020-07-14-at-11.37.30-AM-300x168.png 300w, https://wp.apollographql.com/wp-content/uploads/2020/08/Screen-Shot-2020-07-14-at-11.37.30-AM-768x430.png 768w" sizes="auto, (max-width: 992px) 100vw, 992px" /><figcaption><em><em>Apollo Studio made it easy for us to determine&nbsp;</em><strong><em>which fields</em></strong><em>&nbsp;were in use, but sometimes it was important to know who was using them, and how!</em></em></figcaption></figure>



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



<p class="wp-block-paragraph">However, as time went on, we added ad-hoc scripts, an admin application, partner integrations, a CLI tool, and a handful of other clients, only known to exist based on tribal knowledge.&nbsp;</p>



<p class="wp-block-paragraph">With Apollo Studio, it&#8217;s easy to keep track of the fields currently being utilized, but that information is incomplete without&nbsp;<strong>knowing which clients are using them</strong>. If we want to remove a field that&#8217;s out of date or modify a default argument, just knowing that the field is in use is insufficient. We need to know&nbsp;<strong>which clients are using the field</strong>,&nbsp;<strong>how to assess the cost of a breaking change</strong>, and&nbsp;<strong>how to move forward</strong>.</p>



<p class="wp-block-paragraph">The desire to have these kinds of insights led us to build client awareness at the end of 2018.</p>



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



<p class="wp-block-paragraph"><strong>Client awareness</strong>&nbsp;is a feature from Apollo Studio that enables you to view operation metrics for each of your application&#8217;s different clients (such as web and iOS) and client versions (such as 1.0 and 1.1). It helps you understand how each one interacts with your data graph.&nbsp;</p>



<p class="wp-block-paragraph">For me, client awareness has always been one of the most valuable insights into our GraphQL layer. It&#8217;s saved our team cumulative weeks of engineering time by making usage information readily available as we&#8217;re making schema changes.</p>



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



<p class="wp-block-paragraph">Here&#8217;s a good example. As we added more functionality to one of the features in our CLI, we realized that a dependency in our legacy code was slowing us down quite a bit, causing us to over-abstract to maintain backward compatibility support. This legacy code supported a deprecated field in our schema, but Apollo Studio showed that field still had usage! However, just one click of investigation revealed that&nbsp;<strong>the only client using the field was a version of our CLI we had deprecated months before</strong>. Usage was meager enough to justify removing it, and we rejoiced to discard the legacy code we&#8217;d been dragging along with every commit 🎉.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="855" height="814" src="https://wp.apollographql.com/wp-content/uploads/2020/08/image-9.png" alt="" class="wp-image-4345" srcset="https://wp.apollographql.com/wp-content/uploads/2020/08/image-9.png 855w, https://wp.apollographql.com/wp-content/uploads/2020/08/image-9-300x286.png 300w, https://wp.apollographql.com/wp-content/uploads/2020/08/image-9-768x731.png 768w" sizes="auto, (max-width: 855px) 100vw, 855px" /><figcaption>Guess we won’t be making any breaking changes to this field any time soon!</figcaption></figure>



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



<p class="wp-block-paragraph">Beyond the ability to know&nbsp;<strong>who will be affected</strong>&nbsp;by schema changes, we&#8217;ve found another use case for client awareness on the other side of the stack:&nbsp;<strong>understanding the schema when building out operations</strong>. Of course, in an ideal world, all fields would have a thorough description and notes on usage, but we have all run into confusingly named and under-specified parts of our API, and scratched our heads as to what they&nbsp;<em>actually</em>&nbsp;do!</p>



<p class="wp-block-paragraph">The other day, when I was trying to understand&nbsp;<em>what a field did</em>, I got a rush from deducing its nature by figuring out which client used it &amp; diving into that client&#8217;s source code to understand its use case.&nbsp;</p>



<h3 class="wp-block-heading"><a href="#managing-graph-access-with-client-awareness" aria-hidden="true" class="aal_anchor" id="managing-graph-access-with-client-awareness"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 graph access with client awareness</h3>



<p class="wp-block-paragraph">Client awareness has been so useful to us that we&#8217;re considering adopting an&nbsp;<a target="_blank" href="https://gist.github.com/zionts/dfbd24145d41ed751a6856401c6d59e1" rel="noreferrer noopener">Apollo Server plugin</a>&nbsp;to restrict all operations from unidentified clients. We&#8217;re thinking of doing this just to ensure we can track any operation sent to our servers to a specific use case and have a person at the other end of the &#8220;client&#8221; to talk to.&nbsp;</p>



<p class="wp-block-paragraph">With partner integrations, we&#8217;ve asked users to set their client names to an email address, and we&#8217;ve reached out via email whenever we want to make breaking changes. The ability to signal the&nbsp;<strong>exact right audience</strong>&nbsp;with the relevant changes has given our team incredible confidence to clean up pieces of our API without worrying about affecting customers.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="749" src="https://wp.apollographql.com/wp-content/uploads/2020/08/Frame-1-5-1024x749.png" alt="" class="wp-image-4363" srcset="https://wp.apollographql.com/wp-content/uploads/2020/08/Frame-1-5-1024x749.png 1024w, https://wp.apollographql.com/wp-content/uploads/2020/08/Frame-1-5-300x220.png 300w, https://wp.apollographql.com/wp-content/uploads/2020/08/Frame-1-5-768x562.png 768w, https://wp.apollographql.com/wp-content/uploads/2020/08/Frame-1-5.png 1055w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>When making changes to our <code class="" data-line="">AffectedQueryMetrics</code> type, we were able to broadcast these changes directly to partners before rolling them out!</figcaption></figure>



<h2 class="wp-block-heading"><a href="#getting-started-with-apollo-studio" aria-hidden="true" class="aal_anchor" id="getting-started-with-apollo-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>Getting started with Apollo Studio</h2>



<p class="wp-block-paragraph">If you’re not using client awareness in Apollo Studio today, it’s really simple to <a href="https://www.apollographql.com/docs/studio/client-awareness/">get set up</a> (and impeccably documented, thanks to our documentation lead, Stephen Barlow!):</p>



<ol class="wp-block-list"><li>Make sure your Apollo Server (v2+) is reporting usage metrics</li><li>Add the <code class="" data-line="">name</code> argument and an optional <code class="" data-line="">version</code> number to your Apollo Client instance.</li></ol>



<pre class="wp-block-prismatic-blocks"><code class="language-javascript" data-line="">const client = new ApolloClient({ 
  name: &quot;YOUR_NAME_HERE&quot;,
  // optionally, add a version number 
  version: &#039;YOUR_VERSION_HERE&#039;
})</code></pre>



<p class="wp-block-paragraph">(There <em>is</em> the ability to try to automatically deduce the client name/version, using the <a href="https://www.apollographql.com/docs/studio/client-awareness/#advanced-apollo-server-configuration"><code class="" data-line="">generateClientInfo</code> option</a> in Apollo Server, but we’ve found things usually end up a lot cleaner if you set the <code class="" data-line="">name</code> option directly)<br><br>If you’re not using Apollo Client, all you need to do is pass the <code class="" data-line="">apollographql-client-name</code> and <code class="" data-line="">apollographql-client-version</code> headers instead, which we’ve done for a number of different scripts.</p>



<h2 class="wp-block-heading"><a href="#wed-love-your-feedback" aria-hidden="true" class="aal_anchor" id="wed-love-your-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>We’d love your feedback</h2>



<p class="wp-block-paragraph">If you <strong>are using client awareness</strong> in Apollo Studio, we’d love to hear your story about how it’s changed the way you’ve worked, not to mention how we can improve the feature to make your lives better!<br><br>We’ve just started a new <a href="https://github.com/apollographql/apollo-studio-community">GitHub repo</a> to share a change log, expose preview documentation, and collect feedback, so please open an issue on that repo with any requests!<br><br>If you want to showcase how you’re using Apollo Studio on our blog, reach out to <a href="mailto:studio@apollographql.com">studio@apollographql.com</a>!</p>


Who’s Using My Graph?


<p class="wp-block-paragraph">Early this year, the Apollo team began development on a new tool for navigating your graph and building GraphQL queries. Unlike many tools that seem more focused on server developers, our goal was to create a powerful, accessible, and intuitive experience for <em>graph consumers</em>—the product engineering teams that spend their days working with a production data graph.</p>



<p class="wp-block-paragraph">Today, we&#8217;re beyond proud and excited to reveal the result of that work: the <strong>Apollo Explorer</strong>.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="800" height="443" src="https://wp.apollographql.com/wp-content/uploads/2020/06/Screen-Recording-2020-06-18-at-10.25-PM-1.gif" alt="" class="wp-image-3910"/></figure>



<p class="wp-block-paragraph">The Explorer is a full-featured query builder and runner that’s part of <strong>Apollo Studio</strong> (which we renamed from Graph Manager <a href="https://www.apollographql.com/blog/graph-manager-is-now-studio" target="_blank" rel="noreferrer noopener">just yesterday</a> 🙂). This is the first Studio feature that’s first and foremost built for graph consumers. You can use the Explorer with every graph that’s part of your Studio organization, and with every environment those graphs run in (staging, production, and so on). Powerful features like dynamic field selection, intelligent search, and built-in documentation help your team members compose exactly the query they need.</p>



<p class="wp-block-paragraph">From the outset, we wanted the Explorer to just “feel right” to use. It includes a ton of small design touches that someone might not consciously notice, but together they create a genuinely magical user experience. We’ll cover a few of those touches on our tour.</p>



<p class="wp-block-paragraph">Let me show you around!</p>



<h2 class="wp-block-heading"><a href="#the-operation-editor" aria-hidden="true" class="aal_anchor" id="the-operation-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>The operation editor</h2>



<p class="wp-block-paragraph">The Explorer’s operation editor is built on <a rel="noreferrer noopener" href="https://microsoft.github.io/monaco-editor/" target="_blank">Monaco</a>, so it’ll immediately feel familiar to anyone who’s used VS Code. Naturally, it includes all the features and conventions we’ve come to expect from query-building tools (such as <code class="" data-line="">⌘+Enter</code> to run, state persistence across sessions, and panels for providing headers and variables). The editor also provides full IntelliSense support for GraphQL, including query linting, autocomplete, peek definitions on hover, jump-to-definition with a command-click, and more.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="802" height="356" src="https://wp.apollographql.com/wp-content/uploads/2020/06/Screen-Recording-2020-06-18-at-10.18-PM.gif" alt="" class="wp-image-3913"/></figure>



<p class="wp-block-paragraph">And when you’re working with multiple operations, the editor follows along, shifting its focus to whichever operation you’re working on:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="801" height="472" src="https://wp.apollographql.com/wp-content/uploads/2020/06/Screen-Recording-2020-06-18-at-10.15-PM.gif" alt="" class="wp-image-3916"/></figure>



<p class="wp-block-paragraph">We built the operation editor with one goal in mind: zero frustration. After all, we’re GraphQL developers too, and we use the Explorer all the time! When something bugs us about the editor, we fix it. If something bugs <em>you</em>, please <a rel="noreferrer noopener" href="https://docs.google.com/forms/d/e/1FAIpQLSfy9sH9KN3eZZ2Z5yA9XvFq74ITbWOvrFB-iAeMRKf-nWWQeQ/viewform" target="_blank">let us know</a> so we can fix that too.</p>



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



<p class="wp-block-paragraph">GraphQL’s syntax is a big part of its learning curve. On top of learning a new mental model for requesting data, you need to learn a new language to actually execute a request! Well, we believe that syntax should <em>never</em> get in the way of exploring and querying your graph.</p>



<p class="wp-block-paragraph">One of the beautiful things about GraphQL is that a query is pretty much just a collection of the schema fields you want to fetch. So hypothetically, if you could <strong>just click the fields in your schema that you want</strong>, you could build a query without even typing. Speaking of which, the Explorer lets you do exactly that:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="800" height="436" src="https://wp.apollographql.com/wp-content/uploads/2020/06/Screen-Recording-2020-06-18-at-10.05-PM.gif" alt="" class="wp-image-3922"/></figure>



<p class="wp-block-paragraph">The Explorer enables you to “step into your schema.” As you step further, it keeps track of your current path. This path helps you navigate back up your schema via breadcrumbs, <em>and</em> it tells Explorer exactly how to reach your current location from the root. This means that at any point, you can click the <strong>(+)</strong> button next to a field, and the Explorer knows exactly how to add that field to your query. It also knows exactly which arguments the field requires, and it automatically creates variables so you can specify values for those arguments:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="800" height="657" src="https://wp.apollographql.com/wp-content/uploads/2020/06/Screen-Recording-2020-06-18-at-09.44-PM.gif" alt="" class="wp-image-3925"/></figure>



<p class="wp-block-paragraph">Variables are often scalar types like strings and numbers, but they can be just as complex as any other object. By automatically creating variables for you, the Explorer helps prevent common errors like JSON bracket mismatches.</p>



<p class="wp-block-paragraph">This query-building flow becomes more and more essential as your schema grows in size and complexity. In a graph that includes unions, interfaces, and a large variety of arguments, being able to abstract away the GraphQL and <em>just query your data</em> makes a huge difference. Once you get used to it, you’ll feel like you’re moving in slow motion without it.<br></p>



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



<p class="wp-block-paragraph">Have you ever been positive that a field is somewhere in your schema, but you just can’t remember where? And even if you <em>do</em> know where, a large schema might include thousands—or even <em>millions—</em>of different paths you could take to query that field. Manually identifying the ideal path from a schema’s root down to a field takes a <em>lot</em> of mental energy, and it really shouldn’t need to. This is what search algorithms are for!</p>



<p class="wp-block-paragraph">To help you save that mental energy, the Explorer comes with a two-step, Spotlight-style search. First, it helps you identify which field you’re looking for. Then, it helps you identify which path you want to use to add that field to your query.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="800" height="468" src="https://wp.apollographql.com/wp-content/uploads/2020/06/Screen-Recording-2020-06-18-at-10.01-PM.gif" alt="" class="wp-image-3928"/></figure>



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



<p class="wp-block-paragraph">It’s very common for multiple fields in a schema to have the same name, like <code class="" data-line="">id</code> or <code class="" data-line="">status</code>. This first step helps you identify exactly which type-field pairing you’re looking for.</p>



<p class="wp-block-paragraph">If you know you&#8217;re looking for a field named <code class="" data-line="">email</code>, the Explorer helps you identify whether you want <code class="" data-line="">User.email</code> or <code class="" data-line="">Organization.email</code>. And if you&#8217;re less sure about the field&#8217;s name, Explorer uses a fuzzy search, so you can get it a little wrong. You can also include a <code class="" data-line="">.</code> modifier to search both type and field names simultaneously, which can help you narrow in on the perfect match.</p>



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



<p class="wp-block-paragraph">After you identify which type-field pair you want, the Explorer runs a breadth-first search from your schema’s entry points (<code class="" data-line="">Query</code>, <code class="" data-line="">Mutation</code> and <code class="" data-line="">Subscription</code>) to the chosen field. It lists all of the paths it finds, ordered by length. After you select which path you want, the Explorer opens it for you in the Documentation panel, and you can add it to your query with a click.</p>



<p class="wp-block-paragraph">The Explorer’s search feature removes tons of time and context switching from the query-building experience, especially for larger schemas. Queries that previously took minutes to design now often take just a few seconds.</p>



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



<p class="wp-block-paragraph">The Explorer includes a history tab that allows you to view a previously executed query, including all of its variable values:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="800" height="659" src="https://wp.apollographql.com/wp-content/uploads/2020/06/Screen-Recording-2020-06-18-at-10.07-PM.gif" alt="" class="wp-image-3931"/></figure>



<p class="wp-block-paragraph">This comes in handy for all the usual reasons: it’s easy to recover previous work; it helps you keep your workspace clean while retaining operations that took a lot of time and care to craft; and it’s easy to experiment and iterate with different values for variables.</p>



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



<p class="wp-block-paragraph">Last but not least, the Explorer comes with both light and dark themes, because what developer tool is complete without both? We even defined a new Apollo brand color named “midnight” specifically for our dark theme. 🌙</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="800" height="436" src="https://wp.apollographql.com/wp-content/uploads/2020/06/Screen-Recording-2020-06-18-at-10.09-PM-1.gif" alt="" class="wp-image-3937"/></figure>



<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">The Explorer is available for <strong>free, unlimited use</strong> for every team using Apollo Studio. If you’re a Studio user, head on over to <a href="https://studio.apollographql.com/explorer" target="_blank" rel="noreferrer noopener">studio.apollographql.com/explorer</a>. And if you’re new to Studio, <a href="https://www.apollographql.com/docs/graph-manager/getting-started/" target="_blank" rel="noreferrer noopener">get started here</a>.</p>



<p class="wp-block-paragraph">You can also try out a demo of Explorer right now at <a href="https://demo.apollo.dev" target="_blank" rel="noreferrer noopener">demo.apollo.dev</a>. Just create your Studio account and open up the Explorer tab. You can explore both Apollo’s demo graph (named Acephei) and GitHub’s public GraphQL API. Note that to explore GitHub’s graph, you’ll also need to <a href="https://github.com/apollographql/apollo-studio-preview-docs#try-studio-with-the-github-graph" target="_blank" rel="noreferrer noopener">set up a personal auth token.</a></p>



<p class="wp-block-paragraph">Thanks so much for reading, for exploring, and for continuing on this journey with us. As you try things out, please know that we deeply value your feedback, and that we read and consider everything you share with us:</p>



<ul class="wp-block-list"><li><a rel="noreferrer noopener" href="https://forms.gle/hhfA72JPC3fw43Wx5" target="_blank">Please use this form</a> to share structured feedback on the Explorer, and</li><li>Submit open-ended suggestions and bug reports on our <a rel="noreferrer noopener" href="https://github.com/apollographql/apollo-studio-preview-docs#try-studio-with-the-github-graph" target="_blank">feedback repository</a>.</li></ul>



<p class="wp-block-paragraph">As ever, happy querying!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="600" height="310" src="https://wp.apollographql.com/wp-content/uploads/2020/06/cat-explosion.gif" alt="" class="wp-image-3940"/><figcaption>Magic shipping cat</figcaption></figure>


Introducing the Apollo Explorer


<p class="wp-block-paragraph">At first glance, it might seem like GraphQL is so different from REST and other HTTP API technologies that you have to rethink all of your infrastructure from scratch. But it turns out that it’s not hard to add GraphQL to your existing setup and start getting the benefits you want right away, without having to rebuild anything you already have.</p>



<ol class="wp-block-list"><li>You can keep your existing backends and business logic, since you can put GraphQL over REST APIs.</li><li>You can add GraphQL data loading to your existing React app, one component at a time.</li><li>You can easily integrate GraphQL tools into your existing application infrastructure, since they run anywhere your server code does.</li></ol>



<p class="wp-block-paragraph">In this case, we’ll talk about Content Delivery Networks — CDNs.&nbsp;At first, it might seem like GraphQL isn’t easy to use with your existing CDN setup like Fastly, CloudFlare, or Akamai, but it turns out you can get it running in just a few easy steps.</p>



<p class="wp-block-paragraph">I’m writing this post because we just launched a new feature in Engine that enables all of these things to work together more easily than ever before, and I’m really excited to tell you about it! To get started, make sure you’ve&nbsp;<a href="https://www.apollographql.com/docs/engine/setup-node.html" target="_blank" rel="noreferrer noopener">set up Apollo Engine</a>&nbsp;and head on over to the&nbsp;<a href="https://www.apollographql.com/docs/engine/cdn.html" target="_blank" rel="noreferrer noopener">Engine CDN integration docs</a>.</p>



<p class="wp-block-paragraph">If you’re looking to learn more about what CDNs do and what questions people usually have about using them with GraphQL, read on!</p>



<hr class="wp-block-separator"/>



<h3 class="wp-block-heading" id="a519"><a href="#how-does-a-cdn-help-your-api" aria-hidden="true" class="aal_anchor" id="how-does-a-cdn-help-your-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>How does a CDN help your API?</h3>



<p class="wp-block-paragraph">If your application has a lot of public data that doesn’t change very frequently, and it’s important for it to load quickly, you’ll probably benefit from using a CDN to cache your API results. This can be particularly important for media or content companies like news sites and blogs.</p>



<p class="wp-block-paragraph">A CDN will store your API result close to the “edge” of the network — that is, close to the region the user is in — and deliver a cached result much faster than it would have required to do a full roundtrip to your actual server. As an added benefit, you get to save on server load since that query doesn’t actually hit your API.</p>



<p class="wp-block-paragraph">Edge caching doesn’t help as much if your application has a lot of frequently-changing or private data, but it’s a must-have optimization for publishing or media applications with infrequently-changing, public data.</p>



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



<p class="wp-block-paragraph">One question we hear pretty frequently is whether this type of infrastructure can be used with a GraphQL API. On the surface, GraphQL might appear to make CDN caching harder, but it turns out that it’s not much more effort than with a REST API.</p>



<p class="wp-block-paragraph">Let’s go through some common misconceptions, and see how they are easily mitigated.</p>



<h3 class="wp-block-heading" id="60ad"><a href="#1-graphql-requests-are-too-diverse" aria-hidden="true" class="aal_anchor" id="1-graphql-requests-are-too-diverse"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. GraphQL requests are too diverse</h3>



<p class="wp-block-paragraph"><em>Answer: In most apps, they aren’t more diverse than hand-coded REST endpoints.</em></p>



<p class="wp-block-paragraph">Because GraphQL is a much more flexible query language than the URLs you use with REST, it might seem that whole query results would be harder to cache because there are so many different queries that could be sent to the server. Indeed, it is possible that some apps will have completely dynamic queries, but it turns out that when following modern GraphQL best practices, most frontends have a very finite set of queries they send to your server.</p>



<p class="wp-block-paragraph">Before GraphQL, people would often use a backend-for-frontend pattern that involved creating customized endpoints that matched the needs of a particular UI feature. This meant that you could end up with dozens or even hundreds of endpoints that served similar data in different ways, to optimize delivery for a particular part of the app.</p>



<p class="wp-block-paragraph">With GraphQL, you get those same efficiency benefits without having to write and maintain those endpoints. So at the end of the day, even though you didn’t handcode a set of URLs, your application makes a similar number of distinct API calls. So caching the entire GraphQL result for certain views based on the query and variables turns out to be just as reasonable as caching the entire REST API result was in the past.</p>



<p class="wp-block-paragraph">This is thanks to something that has been a best practice in GraphQL for a long time — writing&nbsp;<a href="https://dev-blog.apollodata.com/5-benefits-of-static-graphql-queries-b7fa90b0b69a" target="_blank" rel="noreferrer noopener">static queries in your UI code</a>&nbsp;with Apollo Client or Relay Modern rather than using a tool that automatically generates unpredictable queries, like Lokka or Relay Classic. Issues with how those older clients generated and sent queries are a big part of why that misconception exists today.</p>



<h3 class="wp-block-heading" id="543c"><a href="#2-graphql-requests-are-too-large-and-use-post-instead-of-get" aria-hidden="true" class="aal_anchor" id="2-graphql-requests-are-too-large-and-use-post-instead-of-get"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. GraphQL requests are too large, and use POST instead of GET</h3>



<p class="wp-block-paragraph"><em>Answer: You can easily switch to smaller requests and use GET by combining Apollo Link and Apollo Engine.</em></p>



<p class="wp-block-paragraph">A central principle of REST is that you use a URL to identify a piece of data, and use the&nbsp;<code class="" data-line="">GET</code>&nbsp;verb in your HTTP requests to indicate that you’re doing a data read and not a write. That tells a CDN that it’s OK to cache that result, since it’s not expecting to modify something on the backend.</p>



<p class="wp-block-paragraph">In contrast to that, historically, most GraphQL tools sent HTTP requests using POST, and instead of a URL they uses a complicated request body that contains a query and variables. As an added complication, in some browsers there’s a relatively small URL size limit that means you can’t fit the entire query and variables in the URL for the GET request.</p>



<p class="wp-block-paragraph">But by combining Apollo Link, our modular network interface for the client, and Apollo Engine’s “Automatic Persisted Queries” feature, we can address both concerns at once. After&nbsp;<a href="https://www.apollographql.com/docs/engine/setup-node.html" target="_blank" rel="noreferrer noopener">setting up Engine</a>, you can easily add&nbsp;<code class="" data-line="">apollo-link-persisted-queries</code>&nbsp;to your client code:</p>



<pre class="wp-block-preformatted">import { createPersistedQueryLink }<br>  from "apollo-link-persisted-queries";<br>import { createHttpLink } from "apollo-link-http";<br>import { InMemoryCache } from "apollo-cache-inmemory";<br>import ApolloClient from "apollo-client";<br><br>ApolloLink.from([<br>  createPersistedQueryLink({ useGETForHashedQueries: true }),<br>  createHttpLink({ uri: "/graphql" })<br>]);<br><br>const client = new ApolloClient({<br>  cache: new InMemoryCache(),<br>  link: link<br>});</pre>



<p class="wp-block-paragraph">This will do two things for you:</p>



<ol class="wp-block-list"><li>Send queries over HTTP GET instead of POST, while still using POST for mutations</li><li>Use a shortened persisted query ID in the GET URL, so that the cache key for CDNs is shorter and you don’t hit URL size limits</li></ol>



<p class="wp-block-paragraph">This brings GraphQL much closer to the regular HTTP GET requests that CDNs are designed to handle.&nbsp;<a href="https://www.apollographql.com/docs/engine/auto-persisted-queries.html" target="_blank" rel="noreferrer noopener">Read more about Automatic Persisted Queries in Engine in the docs.</a></p>



<h3 class="wp-block-heading" id="f63a"><a href="#3-its-harder-to-specify-cache-hints-for-a-graphql-query" aria-hidden="true" class="aal_anchor" id="3-its-harder-to-specify-cache-hints-for-a-graphql-query"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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. It’s harder to specify cache hints for a GraphQL query</h3>



<p class="wp-block-paragraph"><em>Answer: With Apollo Cache Control, you don’t have to specify hints for each query separately — you can do it based on GraphQL types and fields.</em></p>



<p class="wp-block-paragraph">With your REST API, you can simply return a&nbsp;<code class="" data-line="">Cache-Control</code>&nbsp;header from a specific endpoint, and until you write a new endpoint it will remain the same. But with GraphQL, you will constantly be improving the queries on the frontend, adding and removing fields based on what different versions of the UI need. So how do you make sure that your cache control hints stay up to date with the shape of the query, even as the data included in the result change over time?</p>



<p class="wp-block-paragraph">That’s exactly what&nbsp;<a href="https://github.com/apollographql/apollo-cache-control" target="_blank" rel="noreferrer noopener">Apollo Cache Control</a>&nbsp;is designed to solve. This is a spec for how a GraphQL server should return cache hints on a per-field level. It comes with a reference implementation for JavaScript that shows how you could specify cache hints with different levels of specificity:</p>



<p class="wp-block-paragraph"><em>For the entire schema:</em></p>



<pre class="wp-block-preformatted">app.use('/graphql', bodyParser.json(), graphqlExpress({<br>  schema,<br>  context: {},<br>  tracing: true,  // Set a max age of 5 seconds for the whole schema<br>  cacheControl: {<br>    defaultMaxAge: 5,<br>  },<br>}));</pre>



<p class="wp-block-paragraph"><em>For a GraphQL type or field:</em></p>



<pre class="wp-block-preformatted">type Post @cacheControl(maxAge: 240) {<br>  id: Int!<br>  title: String<br>  author: Author<br>  votes: Int @cacheControl(maxAge: 30)<br>  readByCurrentUser: Boolean! @cacheControl(scope: PRIVATE)<br>}</pre>



<p class="wp-block-paragraph"><em>Or even for a single execution of a resolver:</em></p>



<pre class="wp-block-preformatted">const resolvers = {<br>  Query: {<br>    post: (_, { id }, _, { cacheControl }) =&gt; {<br>      cacheControl.setCacheHint({ maxAge: 60 });<br>      return find(posts, { id });<br>    }<br>  }<br>}</pre>



<p class="wp-block-paragraph">This is important because this allows the API to specify the expiration of different pieces of data, while maintaining the freedom of the frontend code to specify whatever queries it needs.</p>



<p class="wp-block-paragraph">At the end of the day, Engine combines all of these hints into one convenient&nbsp;<code class="" data-line="">Cache-Control</code>&nbsp;header that your CDN can understand.</p>



<p class="wp-block-paragraph"><em>Note: If you’re not using a CDN, you can use cache control to power the caching feature of Apollo Engine.&nbsp;</em><a href="https://www.apollographql.com/docs/engine/caching.html" target="_blank" rel="noreferrer noopener"><em>Read the caching docs here.</em></a></p>



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



<p class="wp-block-paragraph">So, if you have some GraphQL data that you think would benefit from CDN caching at the edge, it’s actually really simple to get everything working well. This is a great example of the interplay between several tools we’ve been working on for a while:</p>



<ol class="wp-block-list"><li>Automatic Persisted Queries with Apollo Link lets queries use GET while mutations still use POST</li><li>Apollo Cache Control lets you specify cache control information in a fine-grained, schema oriented way</li><li>Apollo Engine generates small query IDs you can use in those GET requests to limit the cache key size, and sets the Cache-Control header for the CDN</li></ol>



<p class="wp-block-paragraph">Then, when you put it all together, you can see those results getting cached in your favorite CDN service:</p>



<figure class="wp-block-image alignfull size-large"><img loading="lazy" decoding="async" width="1024" height="523" src="https://apollographql.wpengine.com/wp-content/uploads/2020/03/1_gDXZPlE7OnCktrgMPILbmw-1024x523.png" alt="" class="wp-image-810" srcset="https://wp.apollographql.com/wp-content/uploads/2020/03/1_gDXZPlE7OnCktrgMPILbmw-1024x523.png 1024w, https://wp.apollographql.com/wp-content/uploads/2020/03/1_gDXZPlE7OnCktrgMPILbmw-300x153.png 300w, https://wp.apollographql.com/wp-content/uploads/2020/03/1_gDXZPlE7OnCktrgMPILbmw-768x392.png 768w, https://wp.apollographql.com/wp-content/uploads/2020/03/1_gDXZPlE7OnCktrgMPILbmw-1536x785.png 1536w, https://wp.apollographql.com/wp-content/uploads/2020/03/1_gDXZPlE7OnCktrgMPILbmw-2048x1047.png 2048w, https://wp.apollographql.com/wp-content/uploads/2020/03/1_gDXZPlE7OnCktrgMPILbmw-1200x613.png 1200w, https://wp.apollographql.com/wp-content/uploads/2020/03/1_gDXZPlE7OnCktrgMPILbmw-1980x1012.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>A screenshot of a demo app with the Fastly dashboard.</figcaption></figure>



<p class="wp-block-paragraph">Read all of the details for how to set it up yourself&nbsp;<a href="https://www.apollographql.com/docs/engine/cdn.html" target="_blank" rel="noreferrer noopener">in the Engine CDN docs</a>!</p>



<hr class="wp-block-separator"/>



<p class="wp-block-paragraph">Last year at GraphQL Summit, I gave a talk about how the power of GraphQL will become clearer as more and more tools work together across the stack — in the client, the API gateway, the server, and more. It’s really exciting to see these cooperating techniques combine to tell an even more compelling and coherent story, and we can’t wait to see what’s coming next!</p>


Caching GraphQL results in your CDN


<p class="wp-block-paragraph">So let’s say you and your team are hooked on GraphQL. You love the flexible API and reductions in roundtrips to the backend, and you’ve been adding new features at a breakneck pace. Amidst all the commotion, you might not have noticed something important: as your app has grown in complexity, your GraphQL query strings have been growing with it<em>,&nbsp;</em>resulting in request sizes that are now becoming a bit of “a problem”.<br><br>Don’t worry, you’re not alone. In some cases, we’ve seen GraphQL query sizes ranging well above 10 KB,&nbsp;<em>just for the query text</em>. This can be extra concerning since the uplink speed from the client is typically the most bandwidth-constrained part of the system. We continue to hear feedback in the GraphQL community that the size of individual queries is a major pain point, and in some cases a blocker to switching from REST. That’s why today we’re excited to introduce&nbsp;<strong>Automatic Persisted Queries</strong>&nbsp;— a tool to greatly improve network performance for GraphQL, now shipping with support in Apollo Server and Apollo Client.<br><br>The concept is simple: by sending a query ID or hash instead of an entire GraphQL query string, bandwidth utilization can be reduced, thus speeding up loading times for end-users. Previously, you would have needed some fairly sophisticated build steps in place in order to make this work (more on that below). Now there’s a solution that requires zero build-time configuration and is supported by Apollo Client + Apollo Server — simply add the&nbsp;<a href="https://github.com/apollographql/apollo-link-persisted-queries" target="_blank" rel="noreferrer noopener">Automatic Persisted Queries Link</a>&nbsp;to your client, upgrade to the latest version of&nbsp;<a href="https://www.apollographql.com/docs/apollo-server/" target="_blank" rel="noreferrer noopener">Apollo Server</a>, and you’re ready to go.</p>



<h2 class="wp-block-heading" id="4a2e"><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">The mechanism is based on a&nbsp;<a href="https://github.com/apollographql/apollo-link-persisted-queries#protocol" target="_blank" rel="noreferrer noopener">lightweight protocol extension</a>&nbsp;between Apollo Client and Apollo Server, which sits in front of your GraphQL server. It works as follows:</p>



<ul class="wp-block-list"><li>When the client makes a query, it will optimistically send a short (64-byte) cryptographic hash instead of the full query text.</li><li><strong>Optimized Path</strong>: Apollo Server observes the queries as they pass through to your resolvers. If a request containing a persisted query hash is detected, Apollo Server will look it up to find a corresponding query in its registry. Upon finding a match, Apollo Server will expand the request with the full text of the query and pass it to the resolvers for execution.</li><li><strong>New Query Path</strong>: In the unlikely event that the query is not already in the cached registry (this only happens the very first time that Apollo Server sees a query), it will ask the client to resend the request using the full text of the query. At that point Apollo Server will store the query / hash mapping in the registry for all subsequent requests to benefit from.</li></ul>



<p class="wp-block-paragraph"><strong>Automatic Persisted Queries: Optimized Path</strong></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="753" height="446" src="https://apollographql.wpengine.com/wp-content/uploads/2020/03/1_w5vsEwpB-Bx0ORZxqcWQdA.png" alt="" class="wp-image-891" srcset="https://wp.apollographql.com/wp-content/uploads/2020/03/1_w5vsEwpB-Bx0ORZxqcWQdA.png 753w, https://wp.apollographql.com/wp-content/uploads/2020/03/1_w5vsEwpB-Bx0ORZxqcWQdA-300x178.png 300w" sizes="auto, (max-width: 753px) 100vw, 753px" /></figure>



<p class="wp-block-paragraph"><strong>Automatic Persisted Queries: New Query Path</strong></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="753" height="538" src="https://apollographql.wpengine.com/wp-content/uploads/2020/03/1_7yEdVjVXcXcEeMEJF6CQGw.png" alt="" class="wp-image-892" srcset="https://wp.apollographql.com/wp-content/uploads/2020/03/1_7yEdVjVXcXcEeMEJF6CQGw.png 753w, https://wp.apollographql.com/wp-content/uploads/2020/03/1_7yEdVjVXcXcEeMEJF6CQGw-300x214.png 300w" sizes="auto, (max-width: 753px) 100vw, 753px" /></figure>



<p class="wp-block-paragraph">Inside Apollo Server, the query registry is stored in a user-configurable cache. This can either be an in-memory store on the same machine as your Apollo Server, or an external memcache store that you operate in your infrastructure. Read more here about&nbsp;<a href="https://www.apollographql.com/docs/apollo-server/features/apq" target="_blank" rel="noreferrer noopener">how to configure Apollo Server with APQs</a>.</p>



<h2 class="wp-block-heading" id="a809"><a href="#a-brief-history-of-build-time" aria-hidden="true" class="aal_anchor" id="a-brief-history-of-build-time"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 brief history of (build) time</h2>



<p class="wp-block-paragraph">This isn’t our first take on persisted queries —&nbsp;<a href="https://dev-blog.apollodata.com/persisted-graphql-queries-with-apollo-client-119fd7e6bba5" target="_blank" rel="noreferrer noopener">earlier this year</a>&nbsp;we published an alternative implementation in&nbsp;<a href="https://github.com/apollographql/persistgraphql" target="_blank" rel="noreferrer noopener">persist-graphql</a>. The persist-graphql solution (and others like it) is based on doing all of the work to generate the query map at&nbsp;<em>build-time</em>. Those solutions tend to rely on this kind of workflow:</p>



<ol class="wp-block-list"><li>Use static analysis to gather all of the queries from your client codebase (or codebases) and generate a mapping of queries to IDs.</li><li>Ensure that clients only send the IDs from this mapping instead of the raw queries.</li><li>Ship this mapping with your GraphQL server so it can translate the IDs back into queries.</li></ol>



<p class="wp-block-paragraph">While this “static” version of persisted queries solves some of the same performance problems, it makes different trade-offs that many organizations who absolutely need persisted queries are not able to make. Notably, it requires a build step that tightly couples your client code to your server in order to work. Any time a new query is added, it must be included in the server’s mapping well before it gets executed in production. This might not be so hard if your client and server are sharing a codebase, or even if they are owned by the same team. In practice, though, even in the best-case scenario this can mean a lot of added complexity. Managing all of this can certainly balloon from a small task to improve performance into a rigid process that slows everyone down.<br><br>In some cases, it’s not even possible to know ahead of time what queries the server will see in the wild. For those providing their GraphQL APIs to 3rd-party developers, part of the appeal is letting app developers come up with new and interesting ways to use their data. The same applies to larger organizations where the client and server teams operate mostly independently. Unless you can force all of the developers who use your API to also run a client-side build step whenever they ship their apps, build-time persisted queries are a complete non-starter.</p>



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



<p class="wp-block-paragraph">We’ve developed this new take on persisted queries to answer these frustrations. At its core, GraphQL was designed to improvedecoupling of clients and servers by empowering application developers to work with data in a more flexible way. With&nbsp;<strong>Automatic Persisted Queries</strong>, we fully embrace this decoupling: since the query-to-ID mappings are stored by the server at runtime,&nbsp;<em>any</em>&nbsp;query that passes through can automatically be turned into a persisted query. Client teams can ship new queries and features at will, and all of the complicated build-time machinery is eliminated. And everyone can stop worrying about how big their queries are getting.<br><br>Ready to give it a try? Check out&nbsp;<a href="https://www.apollographql.com/docs/apollo-server/features/apq" target="_blank" rel="noreferrer noopener">the documentation here</a>&nbsp;to get your app set up and running with Automatic Persisted Queries. Help us run some experiments and let us know what you learn about the performance impacts on your system!</p>


Improve GraphQL Performance with Automatic Persisted Queries


<p class="wp-block-paragraph">Today I’m excited to introduce you to&nbsp;<a href="https://github.com/apollographql/apollo-tracing" target="_blank" rel="noreferrer noopener">Apollo Tracing</a>, a GraphQL extension for performance monitoring that we’ve been working on for the last few months. Thanks to the community, Apollo Tracing already works with most popular GraphQL server libraries, including&nbsp;<a href="https://github.com/graphql/graphql-js" target="_blank" rel="noreferrer noopener">Node</a>,&nbsp;<a href="https://github.com/rmosolgo/graphql-ruby" target="_blank" rel="noreferrer noopener">Ruby</a>,&nbsp;<a href="https://github.com/sangria-graphql/sangria" target="_blank" rel="noreferrer noopener">Scala</a>,&nbsp;<a href="https://github.com/graphql-java/graphql-java" target="_blank" rel="noreferrer noopener">Java</a>, and&nbsp;<a href="https://github.com/absinthe-graphql/absinthe" target="_blank" rel="noreferrer noopener">Elixir</a>, and it enables you to easily get resolver-level performance information as part of a GraphQL response.</p>



<p class="wp-block-paragraph">Apollo Tracing works by including data in the&nbsp;<code class="" data-line="">extensions</code>&nbsp;field of the GraphQL response, which&nbsp;<a href="https://facebook.github.io/graphql/#sec-Response-Format" target="_blank" rel="noreferrer noopener">is reserved by the GraphQL spec for extra information that a server wants to return</a>. That way, you have access to performance traces alongside the data returned by your query. It’s already supported by Apollo Engine, the new version of Optics that&nbsp;<a href="https://dev-blog.apollodata.com/apollo-engine-and-graphql-error-tracking-e7dd3ce8b99d" target="_blank" rel="noreferrer noopener">entered preview recently</a>, and we’re excited to see what other kinds of integrations people can build on top of this format. For example, you could create a panel in Graph<em>i</em>QL that visualizes trace data on a per-response basis.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>We’d like to thank&nbsp;<a href="https://medium.com/u/93c50e4b5ebe?source=post_page-----97c5dd391385----------------------" target="_blank" rel="noreferrer noopener">Oleg Ilyenko</a>&nbsp;for adding support for Apollo Tracing to Sangria,&nbsp;<a href="https://github.com/RSuh" target="_blank" rel="noreferrer noopener">Reginald Suh</a>&nbsp;from Universe for the Ruby support,&nbsp;<a href="https://github.com/bbakerman" target="_blank" rel="noreferrer noopener">Brad Baker</a>&nbsp;from Atlassian for Java, and&nbsp;<a href="https://github.com/sikanhe" target="_blank" rel="noreferrer noopener">Sikan He</a>&nbsp;for Elixir.</p></blockquote>



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



<p class="wp-block-paragraph">Here’s an example of a response with trace data included:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-json" data-line="">{
  &quot;data&quot;: {
    &quot;hero&quot;: {
      &quot;name&quot;: &quot;Luke Skywalker&quot;,
      &quot;friends&quot;: [
        {
          &quot;name&quot;: &quot;Han Solo&quot;
        },
        {
          &quot;name&quot;: &quot;Leia Organa&quot;
        },
        {
          &quot;name&quot;: &quot;C-3PO&quot;
        },
        {
          &quot;name&quot;: &quot;R2-D2&quot;
        }
      ]
    }
  },
  &quot;extensions&quot;: {
    &quot;tracing&quot;: {
      &quot;version&quot;: 1,
      &quot;startTime&quot;: &quot;2017-10-16T18:58:06.797Z&quot;,
      &quot;endTime&quot;: &quot;2017-10-16T18:58:06.811Z&quot;,
      &quot;duration&quot;: 13962507,
      &quot;execution&quot;: {
        &quot;resolvers&quot;: [
          {
            &quot;path&quot;: [
              &quot;hero&quot;
            ],
            &quot;parentType&quot;: &quot;Query&quot;,
            &quot;fieldName&quot;: &quot;hero&quot;,
            &quot;returnType&quot;: &quot;Character&quot;,
            &quot;startOffset&quot;: 11089188,
            &quot;duration&quot;: 181335
          },
          {
            &quot;path&quot;: [
              &quot;hero&quot;,
              &quot;name&quot;
            ],
            &quot;parentType&quot;: &quot;Human&quot;,
            &quot;fieldName&quot;: &quot;name&quot;,
            &quot;returnType&quot;: &quot;String!&quot;,
            &quot;startOffset&quot;: 12304767,
            &quot;duration&quot;: 103632
          },
          {
            &quot;path&quot;: [
              &quot;hero&quot;,
              &quot;friends&quot;
            ],
            &quot;parentType&quot;: &quot;Human&quot;,
            &quot;fieldName&quot;: &quot;friends&quot;,
            &quot;returnType&quot;: &quot;[Character]&quot;,
            &quot;startOffset&quot;: 12588394,
            &quot;duration&quot;: 1106042
          },
          {
            &quot;path&quot;: [
              &quot;hero&quot;,
              &quot;friends&quot;,
              0,
              &quot;name&quot;
            ],
            &quot;parentType&quot;: &quot;Human&quot;,
            &quot;fieldName&quot;: &quot;name&quot;,
            &quot;returnType&quot;: &quot;String!&quot;,
            &quot;startOffset&quot;: 13583004,
            &quot;duration&quot;: 16006
          },
          ...,
          {
            &quot;path&quot;: [
              &quot;hero&quot;,
              &quot;friends&quot;,
              2,
              &quot;name&quot;
            ],
            &quot;parentType&quot;: &quot;Droid&quot;,
            &quot;fieldName&quot;: &quot;name&quot;,
            &quot;returnType&quot;: &quot;String!&quot;,
            &quot;startOffset&quot;: 13662093,
            &quot;duration&quot;: 1928
          },
          ...
        ]
      }
    }
  }
}</code></pre>



<p class="wp-block-paragraph">As you can see, the trace data includes the start and end time of the request, as well as detailed timings and type information for individual resolvers. Resolver-level data is organized by path, similar to the way error paths are handled in the GraphQL spec. The reason for including the type information is that we didn’t want interpretation of the results to require knowledge of the schema, especially because schemas may change, and because some resolvers depend on runtime type information.</p>



<p class="wp-block-paragraph">For a more detailed description of the format, see the&nbsp;<code class="" data-line="">&lt;a href=&quot;https://github.com/apollographql/apollo-tracing&quot; target=&quot;_blank&quot; rel=&quot;noreferrer noopener&quot;&gt;apollo-tracing&lt;/a&gt;</code><a href="https://github.com/apollographql/apollo-tracing" target="_blank" rel="noreferrer noopener">&nbsp;repo</a>.</p>



<h2 class="wp-block-heading" id="cdf2"><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">If you’re using Apollo Server, support for Apollo Tracing is built-in and you can try it out just by setting&nbsp;<code class="" data-line="">tracing</code>&nbsp;to&nbsp;<code class="" data-line="">true</code>:</p>



<pre class="wp-block-preformatted">app.use('/graphql', bodyParser.json(), graphqlExpress({<br>  schema,<br>  context: {},<br>  tracing: true,<br>}));</pre>



<p class="wp-block-paragraph">Since options passed to&nbsp;<code class="" data-line="">graphqlExpress</code>&nbsp;can be a function, you can turn tracing on and off on a per-request basis.</p>



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



<p class="wp-block-paragraph">For other servers, you can follow these instructions to enable tracing:</p>



<ul class="wp-block-list"><li><a href="https://github.com/apollographql/apollo-tracing-js" target="_blank" rel="noreferrer noopener">Node.js</a></li><li><a href="https://github.com/uniiverse/apollo-tracing-ruby" target="_blank" rel="noreferrer noopener">Ruby</a></li><li><a href="https://gist.github.com/OlegIlyenko/124b55e58609ad45fcec276f15158d16" target="_blank" rel="noreferrer noopener">Scala</a></li><li><a href="http://graphql-java.readthedocs.io/en/v4/instrumentation.html#apollo-tracing-instrumentation" target="_blank" rel="noreferrer noopener">Java</a></li><li><a href="https://github.com/sikanhe/apollo-tracing-elixir" target="_blank" rel="noreferrer noopener">Elixir</a></li></ul>



<h2 class="wp-block-heading" id="5cc0"><a href="#supporting-more-servers-and-tools" aria-hidden="true" class="aal_anchor" id="supporting-more-servers-and-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>Supporting more servers and tools</h2>



<p class="wp-block-paragraph">We think this format is broadly useful, and we’d love to work with you to add support for it to your tools of choice. If you’re looking for a first idea, we especially think it would be great to see support for Apollo Tracing in&nbsp;<a href="https://github.com/graphql/graphiql" target="_blank" rel="noreferrer noopener">GraphiQL</a>&nbsp;and the&nbsp;<a href="https://github.com/apollographql/apollo-client-devtools" target="_blank" rel="noreferrer noopener">Apollo Client developer tools</a>!</p>



<p class="wp-block-paragraph">If you’re interested in working on support for other GraphQL servers, or integrations with more tools, please get in touch on the&nbsp;<code class="" data-line="">#apollo-tracing</code>&nbsp;channel on the&nbsp;<a href="http://www.apollodata.com/#slack" target="_blank" rel="noreferrer noopener">Apollo Slack</a>.</p>


Announcement