Products
Data Access Portal API SQD Network Supported Chains
Development SDK SQD Cloud SQD 360
Solutions
By Use Case DeFi & Trading Analytics AI Agents Wallets & Payments Compliance All Solutions
By Industry Stablecoins RWA All Customers
Developers
Get Started Documentation Subsquid Subsquid Labs Dev Chat
Resources
Learn Guides Compare Blog Videos Changelog
Company About Ecosystem Brand Assets
Customers Pricing
Talk to us
Home / Solutions / Analytics
Analytics

2 petabytes of validated blockchain data, one API

Query full-history data from genesis across 225+ networks without running a single node. Backfill years of chain data in hours, stream new blocks in milliseconds, and pipe everything into the warehouse you already use.

Talk to us Try the Portal API
2 PB Data archived
30x Faster than RPC
225+ Networks
$0 Egress cost
Trusted by leading enterprises
Morpho
GMX
PancakeSwap
RAILGUN
Deutsche Telekom
Capabilities

Built for Analytics at scale

*

Single endpoint, 225+ networks

One POST to portal.sqd.dev returns decoded events, transactions, traces, and state diffs from any supported chain. No per-chain RPC setup, no endpoint management, no data reconciliation across providers.

|

Full archival depth from genesis

Every block, every transaction, every event log from block 0 to head, on every chain. Backfill a year of Ethereum data in hours, not the 3-5 days other indexers take on high-throughput chains like Monad.

>

Real-time NDJSON streaming

Stream new blocks, events, and state changes as NDJSON over HTTP. No WebSocket complexity, no polling intervals. Your dashboards update in real time with the same API you use for historical queries.

=

Direct warehouse integration

Pipe raw or transformed data directly into ClickHouse, BigQuery, Snowflake, or Postgres. The Pipes SDK outputs to Parquet/S3 for data lake architectures. No intermediate storage layer required.

The Architecture Difference

Why running your own nodes is a losing game

A full Ethereum archive node requires 15+ TB of storage and takes weeks to sync. Now multiply that by the 225+ networks your analytics platform needs to cover. Most teams give up after chain #3 and start making compromises, sampling data, caching stale results, or just ignoring chains that are "too hard."

SQD's network of 2,000+ worker nodes has already done the hard work. 2 petabytes of validated data stored in columnar Parquet format, optimized for the exact query patterns analytics platforms need. You get 30x faster data retrieval than direct RPC calls, with none of the infrastructure burden.

Direct RPC SQD Portal
Backfill time 3-5 days Minutes
RPC calls/day ~1M ~270K
Chain setup Per-chain One endpoint
Data validation None 6-step pipeline
Historical depth Varies Full genesis
Two paths, same data

Choose the SDK that matches your architecture

Squid SDK

Correctness-first ETL

Batch-oriented processing with automatic reorg handling, TypeORM schema migrations, and optional auto-generated GraphQL APIs. Built for dApp backends where data correctness is non-negotiable.

  • - PostgreSQL, BigQuery, S3 outputs
  • - Auto-generated GraphQL endpoint
  • - Reorg-aware by default
  • - Deploy to SQD Cloud or self-host
Pipes SDK

Throughput-first streaming

Composable streaming pipelines with materialized views and no ORM lock-in. Portal-native from day one, designed for data lake architectures and high-throughput analytics workloads.

  • - ClickHouse, S3/Parquet, any sink
  • - Materialized views built-in
  • - No ORM, flexible schema
  • - Lowest latency path to data
Playground

Try the Portal API

Live queries against real blockchain data. Pick a network, choose a query, hit run.

Public endpoint is free, no API key needed. See plans for dedicated portals and higher limits.

Network+200 more
Query
1curl --compressed -X POST \
2 'https://portal.sqd.dev/datasets/base-mainnet/stream' \
3 -H 'Content-Type: application/json' \
4 -d '{
5 "type": "evm",
6 "fromBlock": 23000000,
7 "toBlock": 23000010,
8 "fields": {
9 "block": {"number":true,"timestamp":true},
10 "transaction": {
11 "hash": true,
12 "from": true,
13 "to": true,
14 "value": true,
15 "sighash": true
16 }
17 },
18 "transactions": [
19 {
20 "to": [
21 "0xcF77a3Ba9A5CA399B7c97c74d54e5b1Beb874E43"
22 ]
23 }
24 ]
25 }'
Basebase-mainnet/stream
Transactions on Base's largest DEX
These are example queries, explore the full Playground →
Use Cases

What teams build with SQD

Ecosystem health dashboards with cross-chain comparisons
Whale & smart money tracking across DEXs and lending protocols
Gas price analytics and fee market modeling
Cross-chain activity benchmarking for L2 comparisons
Institutional research with validated historical datasets
Internal tooling powered by real-time onchain feeds
All solutions

Other ways teams use SQD

Each of these runs on the same SQD data layer.

DeFi & Trading

Index every swap, liquidation, and position change across 225+ networks.

AI Agents

LLMs can't parse raw hex calldata.

Wallets & Payments

Your users don't care which chain their tokens are on, they want to see everything in one feed.

Stablecoins

Stablecoin flows are the circulatory system of crypto.

RWA

Tokenized treasuries, real estate, and private credit need data infrastructure that meets institutional standards.

Compliance

Most indexers give you event logs.

See all solutions
Background reading
What is onchain analytics?

How blockchain history feeds analytics dashboards. The data pipeline, the common metrics, and how this is done in tools like Dune and in-house BI.

Frequently asked questions

How do I query SQD data from a dashboard?
SQD writes to standard databases and warehouses; dashboards then query those the same way they query any other data source. Squid SDK provides PostgreSQL persistence via TypeORM with an auto-generated GraphQL API for read access. Pipes SDK provides first-class outputs to PostgreSQL, ClickHouse, MongoDB, SQLite, and Parquet, plus a custom-target API for sinks like BigQuery, Snowflake, and Databricks. Connect Grafana, Metabase, Tableau, Hex, or any BI tool to the database, and SQL works as normal.
What's the difference between SQD and Dune?
Dune (and Flipside) is SQL-as-a-service on a curated, hosted blockchain dataset, optimized for ad-hoc exploration. SQD is the data layer underneath: raw, validated, cross-chain data delivered through a streaming API or SDK to your own warehouse. Use Dune or Flipside when you want fast SQL on someone else's hosted data; use SQD when you need your own data, your own warehouse, chains those services do not cover, or production-grade access without hosted-query rate limits.
Can I export to BigQuery or Snowflake?
Yes, via Pipes SDK. The framework includes a custom-target API that wraps a streaming pipeline into any destination, with BigQuery, Snowflake, and Databricks as documented patterns. First-class built-in targets are PostgreSQL, ClickHouse, MongoDB, SQLite, and Parquet on S3 (which BigQuery and Snowflake can read directly as external tables). See the SQD documentation for the Pipes target API.
Get started

Your blockchain data infrastructure, handled.

Private Portal. Dedicated. Validated. Managed. Tell us what you're building, we'll show you what it looks like on SQD.

Talk to Us Try the Public API