Goldsky vs SubQuery
Last updated
A practical comparison of hosting, subgraph migration, chain support, and pricing, including how SubQuery’s managed hosting works through its partner OnFinality.
Goldsky vs SubQuery: the verdict
SubQuery is an open-source indexer with three hosting modes. A team can self-host the Indexer SDK, publish to the decentralized SubQuery Network, or use managed hosting now run by partner OnFinality.[1] Its own networks page lists 304 supported networks, more than Goldsky’s subgraph coverage.[7]
Goldsky runs Subgraphs as a single managed service. An existing subgraph deploys unchanged from its IPFS deployment hash, with no manifest or schema change.[11] Goldsky also ships managed streaming through Turbo and subgraph webhooks out of the box.[14][13]
SubQuery itself publishes no managed-hosting price and no uptime SLA. Every such figure traces back to OnFinality, the partner company that runs the hosting, not to SubQuery.[6]
SubQuery
Why SubQuery may be ideal for you:
- 304 supported networks, including non-EVM chains like Cosmos, Polkadot, Stellar, NEAR, Algorand, and Starknet[7]
- One project can index several layer-1 networks into one database and one GraphQL endpoint[2]
- Three hosting modes, including a decentralized network with no single managed-service vendor[1]
Why SubQuery may not be ideal:
Choose SubQuery if broad non-EVM chain coverage or multi-chain indexing in one project matters more than a single managed vendor.
Goldsky
Why Goldsky may be ideal for you:
Why Goldsky may not be ideal:
Choose Goldsky if a single managed vendor, built-in streaming, and unchanged subgraph migration matter more than chain breadth.
Compare products, pricing, and platform capabilities
SubQuery is an open-source indexer with three hosting modes. Goldsky answers with a single managed service: Subgraphs for GraphQL indexing, Turbo for streaming, and Edge RPC for JSON-RPC access.
| Feature | SubQuery | Goldsky |
|---|---|---|
| Architecture | ||
| Hosting modes | Advantage: Self-hosted Indexer SDK, the decentralized SubQuery Network, or managed hosting run by partner OnFinality[1] | Vendor-managed only. No self-hosted or decentralized deployment[10] |
| Data model | GraphQL schema plus TypeScript mapping functions over Postgres[3] | GraphQL schema plus mapping functions, the graph-node spec[10] |
| Multi-chain projects | Advantage: One project can index several layer-1 networks into one database and one GraphQL endpoint[2] | Single-chain per deployment[10] |
| Developer experience | ||
| Subgraph migration | subql migrate converts a subgraph project, then needs manual edits[3] | Advantage: Deploys an existing subgraph unchanged from its IPFS deployment hash[11] |
| Schema compatibility | Adds a JSON scalar and drops the Bytes, BigDecimal, and Timestamp scalars that subgraphs use[3] | Advantage: No manifest or schema change needed[11] |
| Streaming and data delivery | ||
| Managed streaming | None published, on any hosting mode. The customer connects to its own Postgres database[2] | Advantage: Turbo streams to 11 sink types, including PostgreSQL, ClickHouse, Kafka, S3, and webhook[14] |
| Webhooks | No webhook push published for any hosting mode | Advantage: Subgraph webhooks ship out of the box[13] |
| RPC services | ||
| RPC services | Decentralized RPC for Polkadot, Kusama, and Gnosis, paid in SQT. A separate OnFinality RPC plan runs free to $249 a month[5][6] | Edge RPC: JSON-RPC over HTTPS, EVM only, $5 per million requests[16] |
| Chain support | ||
| Supported networks | Advantage: 304 supported networks[7] | 106 chains show subgraph support[12] |
| Non-EVM coverage | Advantage: Cosmos, Polkadot and Substrate, Stellar, Concordium, NEAR, Solana, Algorand, and Starknet. Bitcoin is not supported[7][2] | No subgraph support for Solana, Bitcoin, Move, Arweave, NEAR, Starknet, Stellar, or TRON[12] |
Architecture
SubQuery offers three hosting modes. The Indexer SDK runs on infrastructure a customer owns. The SubQuery Network is a decentralized set of node operators paid in SQT. OnFinality, a separate partner company, runs managed hosting as the OnFinality Indexer Service.[1]
Goldsky Subgraphs is vendor-managed only. There is no self-hosted or decentralized deployment of any Goldsky product.[10]
- Data model: both platforms use a GraphQL schema plus TypeScript mapping functions, written over a Postgres-backed database.[3][10]
- Scalar types: SubQuery adds a JSON scalar and drops the Bytes, BigDecimal, and Timestamp scalars that subgraphs use.[3]
- Multi-chain projects: one SubQuery project can index several layer-1 networks into one database behind one GraphQL endpoint.[2] Goldsky Subgraphs index one chain per deployment.[10]
Developer experience: migrating a subgraph
The subql migrate CLI command converts an existing subgraph project from GitHub or a local path. It copies the schema and mapping file and turns on TypeScript strict mode.[3] SubQuery states the full migration “may take you an hour or two.”[3]
- Store calls: change from synchronous to asynchronous, so each one needs an added
await.[3] - Unsupported scalars: Bytes, BigDecimal, and Timestamp need manual conversion.[3]
- Query compatibility: a subgraph-compatible query service lets an existing client keep the old GraphQL query shape after migration.[3]
- Goldsky’s migration path: deploy an existing subgraph unchanged from its IPFS deployment hash, with no manifest or schema change.[11] The CLI also supports
graft-fromandremove-graftflags.[10]
Streaming and data delivery
SubQuery streaming and exports are self-run only, on all three hosting modes. A customer connects to the Postgres database the Indexer SDK writes to.[2] A --csv-out-dir flag writes CSV files a customer can load into BigQuery with its own tooling.[4]
No vendor, including OnFinality, publishes a streaming connector to Kafka or a webhook for any SubQuery hosting mode.[2]
- Goldsky Turbo: vendor-managed streaming to 11 sink types, including PostgreSQL, ClickHouse, MySQL, Kafka, S3, SQS, EventBridge, Google Cloud Pub/Sub, S2, and webhook.[14]
- Transforms: SQL through Apache DataFusion, TypeScript Script Transforms, Dynamic Tables, an HTTP handler transform, and a Throttle transform.[15]
- Webhooks: subgraph webhooks ship out of the box.[13]
RPC services
The SubQuery Network runs decentralized RPC endpoints for networks including Polkadot, Kusama, and Gnosis. Independent node operators serve these endpoints and get paid in SQT.[5]
OnFinality separately sells its own RPC plans, under the OnFinality name rather than the SubQuery name. The Developer plan is free, at 400,000 response units a day. Growth costs $49 a month. Accelerate costs $249 a month.[6]
Edge RPC serves JSON-RPC over HTTPS for EVM networks only, from 8 or more regions, with automatic failover.[16] It prices every method at $5 per million requests, with volume discounts above 500 million requests a month.[16]
Chain support
SubQuery’s own networks page states 304 supported networks.[7] The breakdown: EVM 196, Cosmos 48, Polkadot and Substrate 50, Stellar 3, Concordium 2, NEAR 2, Solana 1, Algorand 1, and Starknet 1.[7]
SubQuery’s own FAQ states Bitcoin is not supported.[2]
Goldsky’s own coverage matrix shows 106 chains with subgraph support.[12] The matrix lists no subgraph support for Solana, Bitcoin, Move, Arweave, NEAR, Starknet, Stellar, or TRON.[12]
SubQuery covers more non-EVM network families for subgraph-style indexing than Goldsky Subgraphs. One SubQuery project can also index several layer-1 networks into one database behind one GraphQL endpoint, while Goldsky Subgraphs index one chain per deployment.[2][10]
Pricing
Read the SubQuery column with one caveat. OnFinality, a separate partner company, runs the managed hosting and sets its price.[1]
| Feature | SubQuery | Goldsky |
|---|---|---|
| Managed hosting, free tier | Not published by SubQuery. OnFinality’s free Developer plan: 2 active projects, 500,000 stored entities, 1,000 deployment hours a month[6] | Starter plan draws down a one-time $100 signup credit, with no recurring monthly allowance[17] |
| Managed hosting, paid tier | OnFinality Growth: $0.50 per deployment hour, plus $3.50 per 100,000 entities a month above the first 500,000, falling to $1 per 100,000 above 10 million[8] | Scale: first 3 subgraphs free, then $0.05 per worker-hour. First 100,000 entities free, then about $3.89 per 100,000[17] |
| Decentralized network pricing | A default Flex rate of 1.0 SQT per 1,000 queries. A new EVM chain costs a one-time $2,000 fee[9][7] | No decentralized network product |
| Streaming pricing | Not published. No vendor-managed streaming connector exists[2] | Turbo: $0.10 per worker-hour plus $1.00 per 100,000 events written[17] |
| Uptime SLA | Not published by SubQuery. OnFinality states 99.9% uptime on its indexer pricing page, not tied to a named plan[1][8] | A general “99.9%+ uptime” figure, also not tied to a named plan[10] |
| Support | Community Discord. A paid Professional Services engagement covers migration and build work[2] | Scale targets 24 to 48 hours, best effort. Enterprise adds a named Customer Success Manager and a dedicated Slack channel[18] |
SubQuery itself publishes no managed-hosting price and no uptime SLA.[1] Every managed-hosting price and uptime figure above comes from OnFinality, the partner that runs the hosting, not from subquery.network.[6]
Goldsky publishes full pricing details, including volume discounts, on its pricing page.
When to choose Goldsky, and when to choose SubQuery
Choose SubQuery if:
- You want decentralized hosting with no single managed-service vendor
- You need non-EVM indexing across Cosmos, Polkadot, Stellar, NEAR, Algorand, or Starknet
- You want to index several layer-1 networks in one project and one GraphQL endpoint
- You accept sourcing managed hosting and its price from a separate partner, OnFinality
Choose Goldsky if:
- You run an existing subgraph and want to deploy it unchanged from its IPFS hash
- You want vendor-managed streaming into your own database, warehouse, or queue
- You want subgraph webhooks and pipeline transforms without building a separate stack
- You want one vendor to run and price your hosting, instead of two companies
Frequently asked questions
Who runs SubQuery’s managed hosting?
How much does SubQuery’s managed hosting cost?
Which networks does SubQuery support?
Does SubQuery support Bitcoin?
How does SubQuery store indexed data?
How does migrating a subgraph differ between SubQuery and Goldsky?
What is the main difference between Goldsky and SubQuery?
Sources
All sources were checked on October 28, 2026.
Show 18 sourcesHide 18 sources
- Run and publish a project. SubQuery Docs.abcde
- Indexer SDK FAQ. SubQuery Docs.abcdefg
- Migrate from The Graph. SubQuery Docs.abcd
- Query with BigQuery. SubQuery Docs.^
- SubQuery Network launches decentralised RPCs. SubQuery Blog.ab
- Pricing. OnFinality.abcde
- Supported networks. SubQuery.abcde
- Indexer pricing. OnFinality.ab
- Node operators: indexing a project. SubQuery Academy.^
- Index onchain data with Subgraphs. Goldsky Docs.abcdefg
- Migrate from The Graph. Goldsky Docs.abcd
- Supported networks. Goldsky Docs.abcd
- Subgraph webhooks. Goldsky Docs.abc
- Turbo - Supported sinks. Goldsky Docs.abc
- Turbo - Transforms overview. Goldsky Docs.^
- Edge RPC. Goldsky Docs.ab
- Pricing summary. Goldsky Docs.ab
- Getting support. Goldsky Docs.^
Ready to try Goldsky?
Start with the free tier to try subgraphs, data streaming, and multi-region RPC. No credit card needed.
Robinhood
HyperEVM
Arc
Solana
Ethereum
Polymarket
Base
Tempo
Bitcoin