Platform
Fleet Gateway
The permanently installed piece that makes the rest possible. Not a plug-in dongle — the truck’s connection to the platform, and the component every other feature depends on.
What it does, and what it refuses to do
- Hardwired to the terminal
- USB, not Bluetooth. No pairing, no reconnection failures, predictable latency and a physical trust boundary. This is a firm requirement, not a preference.
- One standard connector
- OBD-II 16-pin on the gateway itself. Trucks with 9-pin, 6-pin or RP1226 are handled with an adapter, so one gateway covers a mixed fleet.
- A connector is not a pinout
- A physical OBD-II socket on a heavy truck does not guarantee passenger-car wiring. The harness maps CAN high, CAN low, J1939, power, ground and ignition per vehicle.
- Buffered locally
- No signal is not the same as no data. The gateway keeps recording and the queue replays when the connection returns.
- Read-only by design
- The gateway reads the vehicle. It does not send commands to it. Any future control would require OEM-approved interfaces and a safety policy, never raw CAN writes.
Prototype development. No gateway hardware is confirmed, no vehicle is certified as compatible, and no supplier agreement is in place. Compatibility is established per make, model and year before installation is discussed — see the roadmap, milestone M3 and M8.