All reference builds
Reference buildDataIndexingSaaS

A cross-chain analytics platform indexing nine networks in real time.

Custom indexers, a query API and a dashboard product for funds, protocols and researchers.

On-chain analytics platform
TYPE
Reference build · concept work
BUILT FOR
Data companies, funds and protocol teams
TYPICAL TIMELINE
6–8 months, then a retainer
SERVICES
STACK
GoClickHouseKafkaPostgreSQLNext.jsKubernetes
The problem

Off-the-shelf indexers are slow to add chains, expensive to run and fall hours behind head during volume spikes. A data product needs sub-minute freshness across EVM and non-EVM chains, and something customers will pay for monthly.

How we build it

A Go-based indexing framework where a new chain is a config file plus a decoder, streaming into ClickHouse via Kafka. On top: a query API with per-key quotas and a dashboard with saved views, alerts and CSV/API export.

BUILT TO
9
Chains in the reference design, including Solana and Bitcoin
<60s
Target freshness from block to dashboard
Days
To add a chain — a fetcher and a decoder, everything else shared
Spikes
Absorbed — Kafka buffers and low-priority backfills keep the live tail current
01

One framework, many chains

Adding a chain is days, not months. The chain-specific work is limited to a block fetcher and a decoder; storage, backfill, reorg handling and the API are shared.

One framework, many chains
02

Built for spikes

Kafka buffers absorb volume bursts, ClickHouse ingests in batches, and backfills run as separate low-priority consumers so the live tail never falls behind.

Built for spikes
03

From internal tool to product

The dashboard, billing and API keys are designed as a product from the start: saved queries, alerting, team workspaces and a public API that can become a revenue line of its own.

From internal tool to product

Building something like this?

Tell us about it. A reference build is where we start — your product is where we end up. We reply within one business day.