Skip to main content
Goldsky provides a one-step migration for your subgraphs on TheGraph’s decentralized network. This is a drop-in replacement with the following benefits:
  • The same subgraph API that your apps already use, allowing for seamless, zero-downtime migration
  • A load-balanced network of third-party and on-prem RPC nodes to improve performance and reliability
  • Tagging and versioning to hotswap subgraphs, allowing for seamless updates on your frontend
  • Alerts and auto-recovery in case of subgraph data consistency issues due to corruption from re-orgs or other issues
  • A world-class team who monitors your subgraphs 24/7, with on-call engineering support to help troubleshoot any issues

Migrate subgraphs to Goldsky

  1. Install the Goldsky CLI: For macOS/Linux:
    For Windows:
    Windows users need to have Node.js and npm installed first. Download from nodejs.org if not already installed.
  2. Log into your Project by running:
    This opens your browser to sign in (Google, GitHub, SSO, or email). Once you authenticate, the CLI is logged in automatically — there’s no API key to copy or paste.
    On a headless or remote machine (or in CI), create an API key on your Project Settings page and pass it directly with goldsky login --token <API_KEY>. Use goldsky login --no-browser to print the login URL instead of opening a browser.
  3. Now that you are logged in, run goldsky to get started:
Use the following command to seamlessly migrate your subgraph to Goldsky via IPFS hash(visible on The Graph’s Explorer page for the specified subgraph):
You can alo get this IPFS deployment hash by querying any subgraph GraphQL endpoint with the following query:

Monitor indexing progress

Once you started the migration with the above command, you can monitor your subgraph’s indexing status with:
Alternatively, navigate to app.goldsky.com to see your subgraphs, their indexing progress, and more.