A gate in front of dispatch
Fleet managers dispatch what they are told to dispatch. The runtime sits upstream and refuses work that fails policy — a low-confidence detection or an out-of-bounds payload never becomes an order, and no vehicle moves.
Solution · Fleet operations
Every order a robot receives was approved first.
The runtime does not have to live on the robot. In fleet mode it runs on a PC or edge server beside the fleet stack you already operate, and every transport request — from a vision system, a WMS, or an MES — is admitted or rejected against your policy before it becomes an order. We are not building a fleet manager. We are the gate in front of the one you have.
How it fits
Upstream of dispatch, not in place of it
The runtime is inserted ahead of the fleet manager. Everything downstream — assignment, routing, traffic control, the vehicles themselves — keeps working the way it already does.
Unvalidated — the requestGoverned — the fleet
A vision result, a WMS order, an MES signal. Probabilistic or unvalidated, and not yet trusted.
MQTTVQA / MES / WMS
Policy admission
Runs on a PC or edge server beside the fleet stack. Admits or rejects the request against your policy.
policy.jsonModel GatePC / edge
Receives only approved work, then does what it already does — assignment, routing, traffic.
VDA 5050existing stack
Vehicles receive standard orders from any vendor, and the trace id ties the movement back to the decision.
multi-brand AMR
One runtime product, three deployment solutions
On the machine, beside the stack, or above the fleet
Every solution is the same deterministic engine, deployed differently. Which one you need depends on what has to be governed — a single machine's actions, a robot's ROS stack, or the work handed to a whole fleet.
Deployment topology
Machine SafetyOn the target — embedded in the machine, dispatching over PLC / CAN
ROS 2Beside the robot stack — fed by ROS topics, decided off the executor path
Fleet modeOn a PC or edge device — supervising the fleet over VDA 5050, upstream of dispatch
What changesThe bundle and the boundary: events in, and where decisions are delivered
What does notThe engine, the gate, the recorded and replayable decision trail
What the runtime adds
The part your fleet stack doesn't do
Fleet managers are good at assignment, routing, and traffic. None of them were built to decide whether an AI-originated request should have been actioned at all — or to prove, afterwards, why it was.
One trace, request to wheels
A single trace id follows the chain from the originating request, through the runtime verdict, into the fleet task and the dispatched order — so any movement on the floor can be walked back to the decision that authorised it.
It connects, it does not replace
Your fleet manager, your AGV vendors, your WMS all stay exactly where they are. The runtime speaks VDA 5050 — the standard the industry already runs on — so it drops in beside the stack rather than through it.
Reference integration
Proven against a working VDA 5050 stack
We maintain an open reference fleet integration — a VDA 5050 fleet manager, mixed-brand vehicle adapters, and a live dashboard — purely to prove the pattern end to end. Scenarios publish real events and then check the actual message traffic, confirming a blocked request produces no fleet task and no vehicle order. The whole thing is public, so you can read exactly how the gate sits in front of dispatch.
scenario_runner — reference fleet integration
$ ros2 run edgeembed_vda5050 scenario_runner
[scenario] PASS allow_transport
runtime allow=True -> fleet task -> VDA 5050 order dispatched
[scenario] PASS block_low_confidence
runtime allow=False -> no fleet task, no VDA order
[scenario] PASS block_out_of_bounds
runtime allow=False -> no downstream device action
A reference integration for proving the pattern — not a fleet-management product, and not a certified VDA 5050 implementation.
Pilots
Running a mixed fleet?
If you operate AMRs from more than one vendor — or you're being asked to prove why a robot did what it did — we would love to talk.