Understand the project
Practical overview
When it fits
Use Graph Node when an application or development workflow needs self-hosted, queryable blockchain data organized through subgraphs, particularly for Ethereum-oriented indexing.
Who it is for
- Subgraph developers running a local indexing environment
- Contributors developing Graph Node itself
- Developers building applications that need structured indexed blockchain data
Documented uses
- Index supported blockchain data
- Organize application-specific data through subgraphs
- Serve indexed results through a GraphQL API
- Provide a self-hosted data layer for blockchain applications
- Store and query subgraph logs through supported backends
Before you choose
Requirements & limits
The cited repository is public, active, and open source under the Apache-2.0 license.
- Source-based operation requires Rust, PostgreSQL, IPFS, and the Protobuf compiler.
- Ethereum indexing requires an Ethereum node or provider, with the RPC argument including network and provider capabilities.
- Prebuilt Docker images are recommended for subgraph developers, while source builds are generally described for contributors.
- Graph Node supports local file logs as well as Elasticsearch and Loki backends, with backend choice affecting the operating setup.
- Advanced configurations can address multiple chains or separate indexing and querying across databases.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 1 October 2026
- Original website title
- graphprotocol/graph-node · Official homepage title · retained in its source language