Connectors
Any vendor. One layer.
Machines reach the behavior layer two ways: through the open standards the industry already agreed on, or through a connector we write against a manufacturer's own interface. Either way, a machine already on your floor joins the fleet without being replaced.
Open standard
VDA 5050
The interface most of intralogistics already speaks. Published by the VDA with VDMA, it defines how a master control sends transport orders to vehicles and how vehicles report state back, over MQTT with JSON payloads. Version 3.0 landed in March 2026, adding support for freely navigating robots and a formal zone concept.
Brings in AGVs, AMRs, tuggers and autonomous forklifts without a per-brand integration.
Open standard
Open-RMF
The building side of the problem. Born from getting cleaning, delivery and security robots from different vendors to share hospital corridors, it coordinates robots with each other and with lifts, doors and other bottlenecks. Managed by the Open Source Robotics Alliance.
Brings in service, cleaning and security fleets, plus the building infrastructure they have to negotiate.
Middleware
ROS 2
The framework a large share of modern autonomous machines are built on. Where a manufacturer exposes its ROS 2 graph, the machine can be brought under the behavior layer directly rather than through a vendor gateway.
Covers inspection quadrupeds, research platforms and most newer industrial autonomy.
Direct
Vendor API
Where a manufacturer publishes its own REST or SDK interface, we write a connector against it. One connector per vendor, maintained by us and shipped to every customer running the platform.
Covers the machines whose makers have not adopted a standard, which is still most of port and heavy equipment.