Docs
Launch GraphOS Studio

Cloud routing for supergraphs

Learn about Apollo-managed cloud routers


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

Your infrastructure
GraphOS Cloud
Subgraph A
Subgraph B
Cloud router
Clients

only hosts the runtime for your supergraph's . for your individual subgraphs are still hosted in your infrastructure.

Create your first cloud supergraph

NOTE

Cloud are only available to organizations with and . They aren't available with an or a legacy Free or Team plan.

Federation and subgraph compatibility

Cloud supergraphs use

for their core architecture.
Many GraphQL server libraries
support Federation 2. Your GraphQL API doesn't already need to be using to add it to a cloud supergraph.

Initializing your router

Your router is provisioned automatically whenever you create a cloud supergraph in GraphOS Studio, or whenever you create a new 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:

Label in Studio indicating a router hasn't finished provisioning

Once initialized, you can

.

Cloud router regions

Cloud routing for is only available in Chicago, USA. Apollo's infrastructure has interconnects with major public cloud providers, so latency is minimal. For example, latency between Chicago and AWS in Virginia is approximately 10 ms.

have a wider

. Region selection for cloud routers is only available on the .
Contact Sales
to learn more.

Cloud launches

Publishing a new or editing a cloud router's configuration triggers a new

. Every automatically deploys new router instances for your supergraph.

NOTE

A router deployment might fail due to a platform incident or schema issues. To resolve this, try republishing your subgraph schema.

Router version updates

With cloud routing, GraphOS runs a fully managed fleet of for you. Apollo manages the version of Apollo Router that is deployed and ensures that newly released versions are deployed to cloud routers within 30 days of release. Some minor and patch versions may be skipped.

releases go through rigorous testing before deployment on . During the deployment of new versions, an Apollo engineer actively oversees the process and rolls back any cloud routers that fail to boot up. While some edge cases may arise—for example, a update could result in slightly degraded performance—router updates should not disrupt your supergraphs.

NOTE

Opting out of router updates to cloud routers isn't currently supported. Advanced version management will be available in Dedicated in 2024.

Automatic deletion of unused routers

NOTE

Only cloud routers on the are automatically deleted. This doesn't apply cloud routers on the Dedicated plan.

Apollo automatically deletes of Serverless cloud supergraphs that receive zero operations for 60 consecutive days. This deletes the router, along with all 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 on the variant's router before the 60-day limit.

Limited compute on Serverless

Serverless has limited underlying compute resources, so certain types of workloads might require you to upgrade to Dedicated. Serverless capacity can be exhausted in the following circumstances:

  • Complex schemas can exceed available machine memory for Serverless cloud routers. For example, Serverless cloud routers don't support schemas with over 1,000 input types.
  • Too many simultaneous requests can cause your Serverless cloud router to return 429 errors to your clients.

You can upgrade to Dedicated for control over scaling and performance.

for a free trial.

Security and compliance

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

The (the underlying technology for cloud routing) has been

.

GraphOS Cloud on AWS

GraphOS Cloud on AWS is a managed API solution. It runs the Apollo Router on AWS infrastructure to provide a high-performance, configurable GraphQL router. All Dedicated cloud routers run on AWS.

. For more information on Apollo's compliance and security measures, visit the
Trust Center
.

Next
Configuration
Edit on GitHubEditForumsDiscord

© 2024 Apollo Graph Inc.

Privacy Policy

Company