The clock keeps running when the signal doesn't.
Every Hours of Service calculation happens on the device, from an append-only event log. No bars on the interstate, no dead zone in the Thar Desert, no ferry crossing stops a driver knowing exactly how much drive time is left.
Drag to run a shift. The rings fill clockwise as hours are used, exactly as they do in the app.
One engine. Six regulators. Zero forked code.
Each jurisdiction is a plug-in rule set implemented against the same interface — in Dart on the device and in Python on the server, cross-validated so both produce identical output for identical input. Pick one to see what it enforces, and watch the dials above reconfigure.
Built for the cab, not the conference room.
A driver has one hand free and eight seconds of attention. Everything below is designed around that constraint — and around the fact that a logbook is a legal record before it is a screen.
Four steps, and the log defends itself.
Know who's about to run out of hours — before dispatch does.
The carrier portal reads the same authoritative logbook the roadside inspector would. No reconciliation, no nightly export, no spreadsheet of truth.
Drivers and dispatchers, in their words.
Per driver. Cancel any time.
Every plan runs the full offline engine and a 14-day trial. You are billed for seats you actually dispatch.
Put it in the cab tonight.
Installs in under two minutes. Face enrolment takes three selfies and a licence photo, and the driver's clocks start the moment they go on duty.