Flux ingests events from any producer, derives canonical entity state, and pushes every change to every subscriber in real time. Build agents, dashboards, and automations on a world that never forgets.
Architecture
Any producer publishes events over HTTP. Events are immutable and append-only — the permanent record of everything that happened.
POST /api/events Authorization: Bearer <token> { "stream": "sensors", "source": "my-app", "timestamp": 1708694400000, "payload": { "entity_id": "myns/sensor-01", "properties": { "temp": 22.5 } } }
Flux processes events into live entity state. Properties merge on update. The engine owns and maintains the canonical world model.
# Live entity state { "id": "myns/sensor-01", "properties": { "temp": 22.5, "status": "active" }, "lastUpdated": "2026-02-23T..." }
WebSocket subscribers receive every state change in real time — sub-10ms end-to-end. Subscribe to one entity or everything at once.
# WebSocket push { "type": "state_update", "entity_id": "sensor-01", "property": "temp", "value": 22.5, "timestamp": "..." }
Use Cases
Flux has no built-in semantics. You bring the domain. The engine brings the state.
Multi-agent systems coordinate through shared world state. Agents publish observations and subscribe to peers — no message passing required.
OpenClaw skill available →Aggregate telemetry from thousands of devices. One WebSocket delivers every state change — no polling, no fan-out logic.
WebSocket subscriptions make dashboards trivially real-time. Subscribe once. Receive everything. No polling endpoints to build.
Trigger workflows from any state change. Subscribe to entities, react to property transitions, chain actions — all event-driven.
Equipment state, sensor readings, control loop feedback — all in one persistent, replayable world model.
Publish application events as Flux entities. Query and subscribe to service state without bolting on a separate metrics stack.
Pricing
Pay once. Your namespace on the public Flux instance is yours forever.
yourname/entity-id) No SLA · No refunds · Abuse = namespace banned · Terms of service
Read the docs, run the quickstart, or grab a namespace and start publishing in minutes.