One driver.Every lane.

Why a truck needs its own driver.

Atruckisnotacarwithmoreaxles.Itiseightythousandpoundsathighwayspeed,fivehundredfeetofstoppingdistance,andonelaneithastohold.Sowewroteadriverforthetruckinstead.

Never off shift.

A human driver is capped at eleven hours behind the wheel. Ours takes the trailer from yard to yard, at night, in rain, and hands it over full.

See the run reports
01
02
03

How the driver works

  1. Sensors to steering in a single network. No stack of hand-tuned modules arguing with each other about the same object.

  2. Every mile is replayed with the weather changed, the cut-in earlier, the trailer heavier. Failures surface before the truck leaves.

  3. The stack ships to the tractor, runs the lane unattended, and returns every takeover to the simulator by morning.

The vehicle

Class 8

The route

Dark lanes

The proof

Safety case

Measured on the corridor

4.18M
Driverless miles on the corridor
9,380
Loads delivered with an empty cab
1.4B
Miles run in the simulator first
11h 40m
Longest run with no takeover

Carriers already hauling driverless.

These carriers put our driver on their own tractors, on their own lanes, and audit every takeover against their own safety policy.

  • Northline Haul
  • Basin Carriers
  • Ridgeway Freight
  • Anvil Logistics
  • Longbed Transit
  • Creekside Reefer
Night handover
We gave it our worst lane - night, no shoulder, sixty miles of construction. It ran forty-one times without a takeover.
Marisol ReyesVP, linehaul
Read their audits

Dispatches.

Every run leaves a report - what the driver saw, what it did, and what we changed in the simulator afterwards.

Start a lane
SafetyReport

Our third safety case

Read the case
SimulatorMethod

One cut-in, ten thousand ways

The method
CorridorOps

What a dark yard needs

Field note
HardwareSensors

Where the lidar goes

Teardown
FreightEconomics

The empty backhaul problem

The numbers

Corridor by corridor.

We open a lane when the simulator stops finding new failures on it, and not before.