Goldsky

• Name: Goldsky
• URL: https://goldsky.com/
• Category: managed blockchain-data backend / indexing-and-streaming vendor / RPC infrastructure
• Summary: Goldsky is a managed crypto data backend. It bundles Graph-compatible subgraphs, chain-data streaming into external databases, and performance-marketed RPC access under one operator surface. Useful vendor plumbing, not a canonical indexing primitive.
• What it does:
  • Provides Subgraphs for GraphQL-based indexing and query endpoints with historical and realtime support
  • Offers Mirror for streaming onchain data into external databases with backfills, reorg handling, and configuration-driven pipelines
  • Markets Turbo as a newer streaming-pipeline product with TypeScript transforms, snapshots, dynamic tables, and cross-chain aggregation
  • Runs Edge RPC for EVM-network access with caching, failover, hedging, and indexer-oriented behavior
  • Publishes a broad docs surface, including product intros and an llms.txt index, which makes the operator surface unusually legible for this kind of vendor
• Key claims:
  • The homepage calls Goldsky “the modern back-end for crypto-enabled products” and presents it as infrastructure for teams that need production-grade crypto data systems
  • Official materials claim 150+ chains at the site level, while Mirror docs mention 130+ chains; those numbers appear product-scope dependent and should not be treated as one clean metric
  • The site advertises scale claims such as $12B+ TVL powered, 4 PB+ of crypto data stored, and 500 TB+ of on-demand datasets; useful signals, still vendor claims
  • Edge RPC docs emphasize low latency, automatic failover, data cross-validation, and pricing aligned to production app and indexer workloads rather than hobbyist RPC use
  • The product mix makes the main point clear: Goldsky is selling an easier way to consume chain data without owning ingestion, normalization, replay, and serving yourself
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Goldsky’s official site and docs portal; see ../whitepapers/goldsky-primary-sources-2026-04-23.md.
• Sources:
  • https://goldsky.com/
  • https://docs.goldsky.com/introduction.md
  • https://docs.goldsky.com/llms.txt
  • https://docs.goldsky.com/mirror/introduction
  • https://docs.goldsky.com/edge-rpc/introduction

Internal linkages

• Best upward comparison points: the-graph, sqd, and firehose.

Governance / control risk

• The leverage sits in schema choices, backfill and reorg behavior, chain-support decisions, cache and failover policy, and how much of the data path stays inside Goldsky-managed infrastructure.

• Treat Goldsky as a vendor backend that makes chain data easier to consume, not as some neutral base layer for blockchain truth.

• Last reviewed: 2026-05-30 UTC