fluxrig
fluxrig is a connectivity and protocol orchestration platform for distributed mission-critical infrastructure.
It provides a unified control plane to route, transform, and monitor data streams across heterogeneous environments, from industrial IoT sensors to global payment networks. Declarative configuration defines the routing and transformation logic. This applies to a flow that engineers design now. It also applies to one in production for a decade.
A Rack is an edge node that runs a scenario: a YAML description of processing steps and how the scenario wires them. The Mixer enrolls Racks. It deploys scenarios to them. It collects their telemetry. A Rack keeps its identity and its last scenario in local state, and reconnects to the Mixer by itself after an outage.
TIP
Start with the 5-Minute Quickstart. For background, read the Architecture Overview and the use cases.
Why fluxrig?
fluxrig serves environments where data integrity and edge resilience are non-negotiable.
- One control plane for many edge nodes. Racks enroll themselves. They receive scenarios. They report telemetry to a single Mixer.
- Protocol agnostic. A native ISO 8583 codec reads its dialects from a spec, not from code. Generic TCP framing handles binary protocols. Bento mappings handle JSON and the rest.
- Configuration over code. Deploy complex routing and transformation logic with declarative YAML. Standard integrations need no custom code.
- Edge resilience. A Rack keeps its identity and last scenario in local state. It reconnects by itself after a backhaul outage. It keeps running the flows that stay inside it. It can start without the Mixer.
Design philosophy: the professional audio logic
We borrow our architectural nomenclature from professional audio engineering to describe complex data flows with both precision and scale:
- The Gear: A Gear is a modular unit of logic (an ISO 8583 codec, a Bloblang mapping, a Wasm module of your own).
- The Rack: A Rack is an edge node that hosts and executes multiple Gears (like a stage rack).
- The Mixer: The Mixer is the central Front of House (FOH) control plane that manages the fleet and aggregates telemetry.
Technical architecture
Core entities
| Entity | Technical Role | Analogy |
|---|---|---|
| Mixer | Central control plane and entity registry. | Mixing Console |
| Rack | Distributed edge node executing local logic. | Equipment Rack |
| Gear | Modular functional unit (Native or Wasm). | Effect Pedal |
| Wire | Persistent, ordered message queue (NATS). | Signal Path |
| Snake | Secure, multiplexed mTLS tunnel. | Audio Snake |
| fluxMsg | Standardized internal data structure (CBOR). | High-Fi Signal |
Choose your journey
For operators & SREs
Maintain uptime and operational visibility. fluxrig provides the tools to orchestrate distributed racks. It manages immutable snapshots. It analyzes telemetry in real time.
- Deployment architecture & binaries →
- Operations & CLI reference →
- Technical configuration (Mixer/Rack) →
- Telemetry & analytics guide →
For developers & SDK users
Build specialized processing logic. Use the Native Go SDK to create custom protocol drivers. Use the declarative Bento Gear for message transformation.
- Writing your first Native Gear →
- SDK reference & contract →
- Bento Gear declarative logic →
- Gears ecosystem reference →
For architects & security teams
Design resilient, sovereign data planes. With fluxrig, design complex, multi-actor topologies. They enforce strict data isolation. They enforce zero-trust connectivity. They enforce deterministic execution.
- System foundation & core principles →
- Security & identity architecture →
- Network & message flow integrity →
- Industry use case spectrums →
