Every other builder stops at the webhook
Arcflux turns real-time events — including live device streams — into governed, multi-step AI workflows. Visual to build, governed by default, wired to the physical world.
Built for the physical world
Subscribe to MQTT, NATS, and AMQP the way you'd add a webhook — with wildcards, QoS, and connector health. Sensors, vehicles, and machines trigger workflows directly, no bridge service to babysit.
Governance before spend
Every event passes a policy gate — dedupe, cooldown, throttle, condition, safety — before it runs, and risky steps pause for human approval. Noise drops before it spends a credit; nothing sends until someone clicks Approve.
A canvas, not a codebase
Model triggers, agents, tools, and approvals as one graph. Swap the model per step, watch every run stream token by token, and audit it end to end — no orchestration code to write or maintain.
Model your world, not just your webhooks
Events in and actions out are only half of a control plane. Arcflux is built to hold a live model of the things you operate — their states, how they relate, and the rules that move them. The nouns and verbs of your operation, in one place.
Same event. Different outcome.
- Device data needs a custom bridge service to become a webhook
- Every event spends compute — noisy sources burn budget
- Agents act with no approval step between draft and send
- Orchestration lives in code only its author understands
- Brokers are first-class triggers — subscribe like a webhook
- Policy gates drop duplicates and noise before a run starts
- Risky actions wait at an approval gate for a human
- The whole flow is a canvas anyone on the team can read
Turn your next event into a workflow
Model agentic workflows visually, trigger them from anywhere, and govern every run.