Product
Technical architecture
On-vehicle stack, yard graph, and what never leaves the site.
On the tractor
Two lidars, a forward camera, RTK GPS, and a safety PLC that can cut motion without asking the compute stack. Perception runs on an industrial GPU. The motion planner will not issue a command the PLC has not pre-cleared.
Yard graph
A surveyed map plus live occupancy. Dispatch assigns a tractor to a door only if the graph says the alley is clear and the WMS says the door will be free. The night-shift lead can override any assignment. Overrides are training data.
What stays on-prem
Raw sensor recordings do not leave a pharma or port site. We train on-site or on a customer-approved region. Model weights can leave; the bags do not. That is in the contract, not the pitch.
Integrations
Door events from the WMS. Gate appointments from the YMS if one exists. Trailer IDs from the yard camera when the WMS is silent. We will not replace a working WMS. We sit beside it.
What we will not build this year
Public-road autonomy. A consumer app. A second vehicle SKU under our own brand. A second continent.