The engine
Nexus — the data intelligence engine.
Ingest, process, store, query and stream on-chain data — in real time.
Pipeline
From validator edge to your stack — in five stages.
A single normalized path from raw Solana state to consumable APIs and live streams.
Ingestion
Yellowstone gRPC
Processing
Geyser plugins
Migrating
Storage
PostgreSQL + Redis
Migrating
Query
SQL / REST
Stream
WebSocket
Ingestion
Yellowstone gRPC
Processing
Geyser plugins
Migrating
Storage
PostgreSQL + Redis
Migrating
Query
SQL / REST
Stream
WebSocket
pipeline.nexus // last updated: active migration in progress
Capabilities
Six layers, one engine.
Real-time ingestion
Solana state is streamed through Yellowstone gRPC and geyser plugins, captured at the validator edge before any indexer hop.
Events are normalized into a consistent schema as they arrive — no batched ETL, no overnight delay.
// specs
In active migration- latency
- <100ms target
- chain
- solana mainnet
- status
- in active migration
Processing layer
Normalized events flow through processing workers that enrich, filter and route them — entity attribution, decoded instruction data, computed fields.
The layer is stateless and horizontally scalable; complexity is in the rules, not the runtime.
// specs
In active migration- throughput
- high / TBD
- framework
- custom
- language
- rust / go
Storage
PostgreSQL is the durable source of truth. Redis sits in front as a hot path for low-latency reads.
Retention is configurable per workload — recent state stays hot, history is tiered down. Long-term archives are owned by Ledger when it ships.
// specs
- primary
- postgres
- cache
- redis
- retention
- configurable
Query layer
SQL endpoints for analytical workloads, REST for everything else. Both speak the same normalized schema as the streaming layer.
Documentation is being assembled alongside the migration; SDK stubs are next.
// specs
- access
- sql / rest
- auth
- api keys
- rate-limit
- per-tier
Streaming
WebSocket channels deliver real-time feeds — per-chain, per-entity or per-program, with backpressure handling and resumable cursors.
Payloads are JSON by default, msgpack on request for high-volume consumers.
// specs
- protocol
- websocket
- format
- json / msgpack
- topics
- per-chain / per-entity
Observability & security
Audit logs are immutable and queryable. Access is gated by role-based controls scoped to tenants and datasets.
Security incidents have a coordinated disclosure path; the security page documents the process.
// specs
- logs
- immutable
- access
- rbac
- incidents
- disclosure@contact
In active migration. We're moving Nexus to more powerful infrastructure. Performance metrics, SLAs and public benchmarks will be published once migration completes.
Ready to stream on-chain data in real time?
We're onboarding a small group of design partners. Tell us about your workload and we'll get back to you.