SubQuery primary-source snapshot
Fetched: 2026-04-26 UTC
1) Official website
Source: https://subquery.network/
Selected excerpts from the official site:
SubQuery’s flexible DePIN infrastructure network powers the fastest data indexers. The most scalable RPCs, innovative Data Nodes, and leading open source AI models.
The SubQuery Network is open for business.
Additional signals from the site:
- The homepage no longer presents SubQuery as only an indexing SDK; it explicitly bundles indexing, RPC, and AI surfaces together
- The DePIN framing suggests the team wants to be understood as decentralized infrastructure, not just a SaaS data vendor
- The public network / delegation framing is a useful clue that operator economics matter to the product identity
2) Documentation portal
Source: https://subquery.network/doc/index.html
Selected excerpts from the docs:
SubQuery is a fast, flexible, and reliable open-source data decentralised infrastructure network, providing both RPC and indexed data to consumers around the world.
The SubQuery Data Indexer is a open-source data indexer that provides you with custom APIs for your web3 project across all of our supported chains.
SubQuery AI Apps framework makes building decentralised AI Applications fast and easy.
Additional signals from the docs:
- The docs compress the full product stack into three layers: indexed data, RPC, and AI apps
- The documentation is strong evidence that SubQuery’s current scope has expanded well beyond the original indexing-only narrative
- The docs are the clearest first-party source for how the team itself groups the product surfaces today
3) Main indexing framework README
Source: https://raw.githubusercontent.com/subquery/subql/master/README.md
Selected excerpts from the repo:
SubQuery is an Open, Flexible, Fast and Universal data indexing framework for web3.
Today, anyone can query and extract blockchain data from various supported networks in only minutes and at no cost.
You can also use SubQuery to index data from multiple networks in any combination of the above SDKs.
Additional signals from the repo:
- The README remains the strongest primary source for the project’s open-source indexing lineage
- The supported-chain list is a practical first-party source for the breadth of ecosystems SubQuery actively targets
- The README also exposes MCP integration, which is a notable sign that the project is leaning into AI-assisted developer workflows
4) GitHub organization
Source: https://github.com/subquery
Selected signals from the GitHub org:
- The verified org controls
subquery.network, which helps tie the code surface directly to the official project - Pinned repos include
subql,network-app,network-contracts, andnetwork-indexer-services, indicating that the public code surface spans both developer SDKs and network/operator infrastructure - Repository activity across contracts, app, and indexer-service components supports the claim that SubQuery is operating a real network stack rather than just publishing a query library
5) Indexer services README
Source: https://raw.githubusercontent.com/subquery/network-indexer-services/main/README.md
Selected excerpt from the repo:
Services that Indexers run to connect and serve data to the SubQuery Network
Additional signals from the repo:
- Even this short README is useful because it confirms the project has explicit software for indexer operators, not just for application developers
- The operator/service layer makes the DePIN/network framing more concrete
- This supports categorizing SubQuery as decentralized data infrastructure rather than only as a software framework
Notes
- This pass did not locate a classic standalone whitepaper or litepaper from official SubQuery sources.
- SubQuery appears best categorized as data indexing / RPC / decentralized data infrastructure / DePIN / AI app framework.
- The strongest primary materials were the official site, docs portal, GitHub organization, and first-party repo READMEs.