Cloud routing for supergraphs

When you create a cloud supergraph with GraphOS Studio, GraphOS automatically provisions and manages a router that acts as an entry point to your GraphQL APIs. In this architecture, individual GraphQL APIs are called subgraphs. Clients send operations to your router's public endpoint, instead of sending them directly to your subgraphs.

Initializing your router

Your router is provisioned automatically whenever you create a cloud supergraph in GraphOS Studio, or whenever you create a new variant for an existing cloud supergraph. Each variant has its own distinct router.

When you first create a variant, the router provisioning process can take a few minutes. If this process hasn't completed yet for a particular variant, an INITIATING ENDPOINT label is shown at the top of the variant's page in Studio:

Configuring your router

See Configuring cloud routing.

Cloud launches

Publishing a new subgraph schema or editing a cloud router's configuration triggers a new launch. Every launch automatically deploys new router instances for your supergraph.

Automatic deletion of unused routers

Apollo automatically deletes variants of Serverless cloud supergraphs that receive zero operations for 60 consecutive days. This deletes the router, along with all of the variant's historical metrics.

• Apollo will notify you via email whenever a Serverless variant is approaching this 60-day limit.
• To prevent deletion, execute at least one GraphQL operation on the variant's router before the 60-day limit.

Cloud routing FAQ

What happens if my cloud router goes down?

If your supergraph's cloud router goes down, queries sent to it will fail until service is restored. However, every cloud router has redundant machines in place to help prevent this.

How is my data protected with cloud routing?

The entire GraphOS platform (including its cloud routing infrastructure) is SOC 2 Type 2 certified. Secrets are encrypted both in transit and at rest, and they are available only inside the runtime environment where users have total control over when those secrets are resolved in configuration.

The Apollo Router (the underlying technology for cloud routing) has been tested and audited by Doyensec, with no issues.

How are cloud routers hosted?

Apollo works with major public cloud providers to deliver GraphOS cloud routing.

Which regions are available for cloud routers?

Cloud routing for Serverless plans is only available in Chicago, USA. Our infrastructure has interconnects with major public cloud providers, so latency is minimal. For example, latency between Chicago and AWS in Virginia is approximately 10ms. If there's a specific region you'd like us to support please request a region.

Cloud routing on the Dedicated plan has a wider variety of options. Get in touch to learn more.

Can I choose my cloud router's region?

Choice of region for cloud routers is only available on the Dedicated plan.

Does GraphOS also host my individual subgraphs?

No. GraphOS only hosts the runtime for your supergraph's cloud router. GraphQL servers for your individual subgraphs are still hosted in your infrastructure.

Which GraphQL server libraries are compatible with cloud routers?

Cloud supergraphs use Apollo Federation 2 for their core architecture. Many GraphQL server libraries support Federation 2.

Your GraphQL API does not already need to be using Apollo Federation to add it to a cloud supergraph.