Realtime delivery

Durable events delivered to live clients.

Consume broker events, match tenant-aware subscriptions, and deliver them through GraphQL or native WebSockets with replay support.

2durable brokers

2socket protocols

Cursorreplay contract

System boundary

A focused runtime between inputs and outcomes.

Broker inputs

NATS JetStreamACKED

Redis StreamsREPLAYABLE

Domain publishersJSON EVENTS

Realtime engine

Match · fan out · isolate · replay

● healthy

Deliver through

GraphQLSUBSCRIPTIONS

WebSocketNATIVE

Tenant clientsROUTED

Replay cursorsRESUMABLE

Built for operations

NATS JetStream and Redis Streams remain the source of replayable event history.

Use GraphQL subscriptions for typed operations or native WebSockets for direct event delivery.

Bounded queues keep one stalled client from blocking unrelated subscriptions.

Debug logging exposes broker consumption, matching, delivery, disconnect, and replay decisions.

Operating model

The runtime contract covers deployment, recovery, and administration rather than stopping at the happy-path data flow.

Clients own the cursor

Reconnect with the last successfully processed sequence to continue from the correct broker position.

Publish from many services

Existing systems publish domain events to the configured broker without routing through Fleet.

Scale the socket role

Run multiple realtime pods against durable broker state while preserving tenant boundaries.