Features
Everything, with its real status
This is the whole list, including the parts that do not exist yet. A capability is only marked as available in the demo if you can go and touch it right now. Everything else says what it is — in development, planned, or still an open question we have not answered.
Nothing here is described as production, because nothing is. The page is written this way on purpose: a fleet that discovers the gap at installation is a fleet you never get back.
Status
Area
58 of 58 shown
Load workflow
Interactive demoAssigned through completed, one state at a time, with the next action on screen.
Every step the driver takes raises the same event the fleet side reads. Nothing is a screen-only transition.
Live fleet map
Interactive demoEvery truck, its route and its state, on one map.
Runs in the demo on invented trucks and a schematic map, not a real one.
Exception-first overview
Interactive demoWhat needs attention, ahead of what is merely happening.
Multiple demo scenarios
Interactive demoOrdinary day, hours running out, a truck breaking down, paperwork going missing — the same interface, four different situations.
Behaviour at fleet scale
Interactive demoThe same screen at 10 trucks and at 1,000 — the list of exceptions grows, the wall of trucks does not.
The counts come from declared rates, not from a fleet we have operated.
Truck detail on selection
Interactive demoDriver, trailer, load, position, hours and health for one vehicle.
Load lifecycle
In developmentAssigned through delivered, with the paperwork attached to each step.
Dispatch and assignment
PlannedWho is available, who is legal to run it, and what it does to the day.
Dwell and detention tracking
PlannedArrival, check-in, dock and departure, timed automatically.
Driver home
Interactive demoOne screen: current load, hours, truck, trailer, what is needed next.
Parked and moving modes
Interactive demoIn motion the terminal shows and stops asking.
Driver identity and truck assignment
In developmentIdentity follows the driver, not the device. Co-driver on one terminal.
Locked-down Driver OS
PlannedDevice-owner mode. No store, no browser, no launcher.
Offline operation
Interactive demoStore, queue, sync, verify. The truck keeps working without signal.
Demonstrated in the simulator; the real queue ships with the gateway.
Engine telemetry
In developmentLive vehicle data over J1939, read from the gateway.
Truck health
Interactive demoSystem-by-system state, with faults shown as faults.
No single health score. A number without a definition is an impression.
Fault codes with history
PlannedSPN and FMI, how often, and whether the frequency is rising.
Truck digital twin
PlannedThe permanent record of one vehicle — repairs, faults, costs, drivers.
Gateway keeps running without the terminal
In developmentCollection, buffering and ignition detection survive a terminal failure.
Axle weight reporting
Research requiredPer-axle and gross weight reported to the terminal.
Depends on trailer scale hardware that has not been selected.
Trailer status
Interactive demoWhich trailer, connected or not, and what it reports.
Automatic pairing
PlannedCoupling detected and confirmed against the load.
Detached trailer tracking
PlannedThe trailer stays visible when no truck is attached to it.
Driver issue reporting
PlannedReport from the cab with photos, severity and whether it can keep driving.
Maintenance cases
PlannedOpen through closed, with the evidence attached.
Preventive schedules
PlannedBy miles, engine hours, calendar or condition.
Failure prediction
Research requiredDeviation from a truck’s own baseline.
Deliberately not called predictive maintenance. Predicting a failure requires evidence we do not have yet, and claiming it early is how this category loses trust.
Hours of service view
Interactive demoDrive, shift and cycle remaining, and what they allow.
DEMONSTRATION ONLY. Not produced by a registered logging device and not a compliant record.
Pre-violation warning
Interactive demoSays the run cannot be completed legally before it is attempted.
Electronic logging
Research requiredEngine-synchronised duty records.
No registration has been obtained and none is claimed. The path — partner first, own engine later — is on the roadmap.
Immutable records with visible corrections
PlannedThe original is kept. Every permitted correction is marked and attributed.
Architectural rule: no administrator, owner, developer or automated process can perform an edit the regulator does not permit.
Roadside inspection mode
PlannedReachable in one action, not buried in menus.
Context-driven capture
Interactive demoPicked up asks for the BOL. Delivered asks for the POD. No hunting.
The demo runs the real sequence. The paper itself is simulated — capture from an in-cab scanner is separate and still being specified.
Classification and extraction
In developmentRecognises the document type and pulls the fields off it.
Extraction never overwrites the scan. The original stays authoritative. The demo shows fixed fields, not a working extraction model.
Missing document tracking
Interactive demoWhich loads are short a document, before invoicing finds out.
In-cab scanner
Research requiredA real scanner in the truck, not a photo of a crumpled page.
Driving events
PlannedHarsh braking, acceleration, cornering and speed, with context.
Built to explain, not to punish. Context ships with the event.
Incident package
PlannedVehicle, driver, position, speed, telemetry and video around an event.
No audio from inside the truck, ever
In developmentThe platform never records or stores sound from inside the vehicle.
Not a setting. An architectural rule with no override, enforced in hardware selection and reviewed in code.
Front camera
Research requiredWindshield-mounted, recording locally at full quality.
Event clip protection
PlannedA clip around an event is locked automatically instead of overwritten.
Authorised live view
PlannedViewing is possible, logged, and attributable to a person.
Side, rear and cargo cameras
Research requiredCoverage beyond the windshield.
Truck-safe routing
PlannedHeight, weight, axle and restriction aware. Not consumer navigation.
A routing provider will be used at first. No provider is selected.
Live position and ETA
Interactive demoWhere the truck is, how fast, and when it arrives.
Geofence arrival and departure
Interactive demoArrival recorded without anyone pressing anything.
Truck parking availability
Research requiredWhere a legal stop is actually possible.
Requires a data provider. None is contracted, and availability data without a source and a timestamp is worse than none.
Driver settlements
PlannedCompensation, reimbursements and deductions, from operational data.
Cost per mile
PlannedFuel, maintenance, driver, tolls and equipment against miles run.
Load and lane profitability
PlannedRevenue against the costs that can actually be attributed to it.
Operational economics, not accounting. It is not a general ledger.
Fuel and toll reconciliation
PlannedTransactions matched to truck, driver, trip and load.
Driver and dispatch messaging
PlannedIn the platform, with the load as context.
Maintenance call with context
PlannedThe mechanic gets the truck, faults and telemetry without being told.
Reduced interaction while moving
PlannedThe office cannot make the terminal demand attention at speed.
Shipper and receiver knowledge
PlannedWhich gate, whether you can park, how long they really take.
Built from a fleet’s own drivers. Private to that fleet by default.
Diagnostic assistance
PlannedCorrelates a fault with history, telemetry and the trip in progress.
Describes observations and suggests tests. It does not state a conclusion it cannot support, and it never replaces a mechanic.
Fleet questions in plain language
PlannedWhich trucks need attention, who is short on hours, what is late.
Compliance is never decided by a model
In developmentHours, permissions, safety and billing are deterministic.
Assistance explains. It cannot create, alter or erase a duty record.