Every change is an event; the stream is the record.
- Surfaced in
- the console
- Shape
- family · ref · time
- Replay
- any state, reconstructed
- Delivery
- coming
- transfer.requested09:42:01
- appfee.assessed09:42:01
- debit_envelope.reserved09:42:01
- transfer.settled09:48:17
- appfee.collected09:48:17
delivery · coming
One ordered stream
Accounts opening, transfers crossing states, fees collected, keys created: every change surfaces as an event on a single stream, each with its family, its reference, and its time.
Read, and replay
The stream is not just a log to glance at. It can be read back and replayed, so any state in the system can be reconstructed and any movement reconciled to the unit.
Grouped by family
Events belong to families — the kind of change they record — so you can follow one transfer's whole life, or watch a single class of change across the whole book.
Delivery is coming
The stream is the record's source of truth. Console reading and outbound delivery — Alpine pushing events to your own endpoints, with retries — are being built. When delivery lands, your systems can react the moment something happens.
See events elsewhere