GATEWAY
Components · Data component

Gateway Indexer

A configurable indexing component that turns selected onchain events into structured, queryable data for applications, reporting, operations, and reconciliation.

Data componentAvailable for supported networks and events
Gateway Indexer component
Selected eventsDefined schemasQuery and delivery APIs
What it is
Data component
Current posture
Available for supported networks and events
What varies
Architecture, providers, operating scope, and commitments
Why it exists

Applications need meaning, not repeated RPC polling.

Teams otherwise rebuild event decoding, chain-state handling, schemas, retries, reorganisation logic, APIs, and reporting pipelines around every product. Indexer creates a defined data boundary for the events that matter.

What changes

Gateway Indexer changes the boundary, not the institution’s authority.

01

A product-specific data model

Select relevant events and map them into schemas designed for the application and reporting workflow.

02

Defined delivery behaviour

Choose supported query, webhook, stream, or export patterns with documented latency and finality assumptions.

03

One operational boundary

Scope replay, reorganisation, retention, monitoring, recovery, capacity, and support responsibilities.

Product boundary

What Gateway Indexer contributes. What still needs a decision.

01

Event selection

Define supported contracts, events, fields, networks, and finality requirements.

02

Schema design

Transform selected chain events into application, reporting, and reconciliation data models.

03

Delivery interfaces

Expose supported query, webhook, stream, or export interfaces for the target consumers.

04

Chain-state handling

Document confirmation, reorganisation, replay, correction, and recovery behaviour.

05

Capacity and retention

Scope workload, query profile, storage, retention, and scaling for the selected configuration.

06

Operations

Define telemetry, alerts, incidents, recovery, support, and service commitments contractually.

Related paths

Continue from Gateway Indexer into the operating model.

Scope Gateway Indexer

Bring the requirement. Define the Gateway Indexer boundary.

A focused workshop maps the target capability, existing systems, providers, controls, and deployment variables.