Use case
Blockchain data platform
Pipelines, schemas, and access control for chain data. The platform is a product. The chain is someone else's.
A company wants a maintained feed of public chain events for its own applications.
When shared machinery earns a place
Operating an indexer and an API is justified when more than one internal product needs the same data.
When it does not
You do not need to launch a network to sell or use a query.
Conventional-first
Node or RPC you trust, indexer, warehouse, API keys, retention.
Vendor and reorg risk, which you can name.
Hybrid
The platform plus a signed snapshot.
Support burden.
On-chain-native
Not generated here.
A token does not make the pipeline correct.
Patterns
Components
- PonderGreen — compatible use if you keep the notices
- Graph NodeGreen — compatible use if you keep the notices
- RethGreen — compatible use if you keep the notices
- LighthouseGreen — compatible use if you keep the notices
- viemGreen — compatible use if you keep the notices
Questions a person still has to answer
- Which networks are in scope?
- What is the freshness promise, in blocks, not in marketing?