Launch GraphOS Studio

Migration considerations

Learn what to consider when migrating to a cloud graph

Cloud is currently in invite-only

. Don't hesitate to
get in touch
if you'd like to request access or have any questions or feedback.


, each recommended for different use cases. You may want to migrate to a cloud in these scenarios:

GraphOS offers two tiers of cloud routing: and Dedicated. This guide focuses on considerations when migrating to

. Refer to
this router comparison
to learn about the differences.


Dedicated currently support all

except for
safelisting with persisted queries
automatic persisted queries
, and
offline licenses
. Support for both features is on the roadmap.

Migrating from @apollo/gateway

use the same

that you can self-host. Therefore, migrating from
entails migrating to the Apollo Router. Refer to the
Gateway migration guide
for tips.

Router customizations

The Apollo Router supports a


  • Custom router binaries
  • Rhai scripting
  • External coprocessing

As a managed service, cloud routers don't support running custom binaries. Cloud routers don't currently support Rhai scripts, though support is on the roadmap. Therefore, you must migrate any customizations to

or built-in router features to use cloud routing.

Built-in router features that you may have previously supported with customizations include:

See the

for a full list of features.


Once your implementation is ready to run on the Apollo Router, including customizations, you can follow the

to get started.

Pricing considerations

Cloud Dedicated pricing depends on throughput instead of volume. Refer to the

to learn more.

When you no longer host your router, router-to- communication may be inter-region, inter-Availablity Zone (AZ), or egress traffic. Be aware of how your new network topology may affect your cloud costs.

AWS Lattice troubleshooting
Edit on GitHubEditForumsDiscord

© 2024 Apollo Graph Inc.

Privacy Policy