subquery/subql

SubQuery is an Open, Flexible, Fast and Universal data indexing framework for web3. Our mission is to help developers create the decentralised products of...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 3rd, 2026
Created on December 15th, 2020
Open Issues & Pull Requests: 102 (+0)
GitHub issues: Enabled
Number of forks: 396
Total Stargazers: 18,747 (+0)
Total Subscribers: 94 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

SubQuery is a data indexing framework for web3 that enables developers to process and query blockchain data across multiple networks.

The framework solves the problem of reliably extracting and consuming blockchain data by providing a unified indexing layer that works across different blockchain architectures. Rather than requiring developers to build custom indexing solutions for each network, SubQuery allows teams to define their data requirements once and deploy across supported chains. The tool processes blockchain data and exposes it through queryable APIs, eliminating the need for developers to manage the infrastructure or write low-level chain interaction code.

Teams building decentralized applications should consider SubQuery if they need to index data from Polkadot, Ethereum, Cosmos, Algorand, NEAR, Stellar, Solana, Starknet, Concordium, or combinations of these networks. The framework is particularly suited for projects that require reliable data access without managing their own indexing infrastructure, as it offers both a decentralized network option for hosting and managed hosting alternatives. The tool handles multi-chain indexing scenarios, allowing a single project to index data from multiple networks simultaneously.

The project shows moderate responsiveness to community engagement, with initial responses to issues and pull requests typically arriving within one to two weeks. Development activity concentrates on guild-related work, critical issues, and the Query Service component, indicating that infrastructure reliability and the query layer receive sustained attention from the maintainers.