Skip to main content

Goldsky vs The Graph

Last updated

A practical and comprehensive comparison of subgraph indexing, streaming, chain coverage, pricing, and production operations.

Goldsky vs The Graph: the verdict

Goldsky fits teams that want managed subgraph performance, 100% Graph-compatible migration, 150 chain coverage, and streaming into their own databases.⁠[7]⁠[6] The Graph fits teams where decentralization is the top priority.

Compare products, platform capabilities, and performance

At the subgraph layer, Goldsky and The Graph share the same foundation: the open-source Graph Node. Their streaming systems are distinct: The Graph has Substreams, while Goldsky has Turbo. Goldsky also includes Edge, a complete RPC product, and Compose, a framework for onchain automation.

Quick comparison of The Graph and Goldsky across key dimensions
FeatureThe GraphGoldsky
Platform
ArchitectureDecentralized Indexer protocol incentivized by GRT. Query access and Indexer payments go through the Edge & Node-operated gateway⁠[2]⁠[3]Advantage: Fully managed service with an autoscaling query layer⁠[7]
Subgraph compatibility100% Graph Protocol compatibleAdvantage: 100% Graph Protocol compatible, plus subgraph webhooks and Turbo data streams into your infrastructure⁠[7]⁠[8]
Supported chains57 chains⁠[1]Advantage: 150 chains⁠[6]
Performance
Subgraph indexing speedVaries by IndexerAdvantage: Up to 10x faster⁠[13]
Streaming to your infrastructureYes, Substreams lists 9 officially supported sink implementations⁠[9]Advantage: Yes, 11 managed sink types⁠[8]
Ownership & cost
Data ownershipData on decentralized Indexer nodes. A self-hosted option gives full ownershipData in Goldsky-managed infra, or streamed to your systems via Turbo
Pricing model100K queries/month free. Then $2 per 100K queries⁠[4]$100 Starter credit. Usage metered by active worker-hours, stored entities, and events written by pipelines⁠[14]

Migrate in 3 steps

Subgraph hosting and data streaming

Both platforms serve GraphQL APIs from subgraph deployments. The Graph is the canonical source. It defined the subgraph manifest, schema, and mapping format that has become the industry standard.

Goldsky Subgraphs is a fully managed service that extends the subgraph standard while remaining compatible with it. Existing subgraph.yaml, schema, and AssemblyScript mappings work without changes.

Where they diverge is in the developer experience and support for building and managing subgraphs. Goldsky Subgraphs provides a more streamlined developer experience with features like:

  • Instant subgraphs from ABI.
  • Tags for versioning.
  • Webhooks for real-time event notifications.
  • Detailed metrics including handler timing and eth_call counts.

For common dataset-to-database jobs, Turbo keeps sources, transforms, and sinks in one YAML definition.⁠[10] Substreams is typically a deeper engineering project. It requires:

  1. Defining Protobuf output types.
  2. Writing transformations in Rust.
  3. Configuring a manifest.
  4. Compiling to WASM.
  5. Bundling an .spkg package.⁠[11]

Even SQL output needs a dedicated Substreams SQL sink CLI or a provider to host it.⁠[12]

Beyond indexing

Goldsky extends beyond indexing and streaming into areas The Graph doesn’t cover: Edge RPC for low-latency multi-region read access, and Compose for onchain automation. Goldsky is the more complete platform for teams that write onchain data as well as read and stream it.

Boost automatically optimizes your existing RPC endpoints without changing providers, which lowers your billable RPC calls.⁠[15] Feeds returns a wallet’s balances or transfer history across supported EVM chains over a REST API, with no indexer to build.⁠[16]

Chain support

Using each platform’s production support catalog and excluding testnets, Goldsky supports 150 chains.⁠[6] The Graph supports 57 chains.⁠[1] Goldsky’s non-EVM coverage is stronger, including networks like HyperCore, Sui, and Canton.

Pricing

Pricing comparison between The Graph and Goldsky
FeatureThe GraphGoldsky
Subgraph queries$2 per 100,000 queries after the first 100,000 a month⁠[4]$0.05 per running subgraph-hour, about $36.50 a month. Query traffic itself isn’t metered⁠[14]
Substreams / streamingFirst 1 TB free, then $25 per TB⁠[5]Turbo pipeline workers cost $0.10 per hour, about $73 a month, plus $1.00 per 100,000 events written⁠[14]
Free tierFirst 100,000 queries a month free, plus the first 1 TB of Substreams free⁠[4]⁠[5]New accounts get $100 in free credit⁠[14]
Billing modelPay-per-query, plus Substreams data volume⁠[4]Usage-based, billed per subgraph-hour, per pipeline worker-hour, and per event written, or an enterprise contract⁠[14]

Goldsky doesn’t meter query traffic, so traffic spikes don’t directly increase the bill. Current Goldsky rates are on the pricing page.

When to choose Goldsky, and when to choose The Graph

Looking for an alternative to The Graph? Goldsky runs your existing subgraphs without code changes and adds streaming into your own database.

Choose The Graph if:

  • You need decentralized, token-incentivized subgraph queries
  • You want to use an existing Substreams package instead of writing your own
  • You want lower-level control over parallel streaming modules

Choose Goldsky if:

  • You want fully managed performance and reliability with human support
  • You need turnkey streaming into common databases and data platforms
  • You need RPC access and onchain automation, not just read-only data

Migrate from The Graph in three steps

If you have an existing subgraph deployed on The Graph, install and authenticate the CLI, then deploy the subgraph to Goldsky with one command.

  1. 1. Install the CLI

    $ curl https://goldsky.com | sh
  2. 2. Authenticate

    $ goldsky login
  3. 3. Migrate your subgraph from The Graph

    $ goldsky subgraph deploy my-subgraph/v1 --from-url <the-graph-subgraph-url>

Frequently asked questions

Goldsky fits teams that want managed subgraph performance, 100% Graph-compatible migration, 150 chain coverage, and streaming into their own databases. The Graph fits teams where decentralization is the top priority.
Yes. Teams combine The Graph’s decentralized network with Goldsky’s managed subgraphs and streaming. Goldsky also serves production subgraph queries on its own.
Yes. Goldsky is compatible with the Graph Protocol subgraph format. You can deploy your existing subgraph manifests, schemas, and mappings without changes.

The Graph shut down its hosted service as part of the Sunrise migration.⁠[17] Projects that used it can migrate to The Graph’s decentralized network, Goldsky, or another provider. See the sources below for The Graph’s official notice.

No. Goldsky Turbo takes a different approach. It uses managed pipelines with SQL and TypeScript transforms that push data into your own systems. It needs no Rust to write and no infrastructure to run.
It depends on whether you’re query-heavy or entity-heavy. The Graph prices queries, while Goldsky meters active workers and stored entities. If you also need data in Snowflake or Postgres, include the cost of separate streaming or ETL infrastructure in your comparison. See the current pricing sources below.

Sources

All sources were checked on October 26, 2026.

Show 17 sources

Ready to try Goldsky?

Start with the free tier to try subgraphs, data streaming, and multi-region RPC. No credit card needed.

© Endless Sky Inc. All rights reserved.

PrivacyTermsSecurity

System status