Skip to content

How Roudiy works

This section explains the ideas behind Roudiy: what the hardware does, how data becomes trips and events, and who on your team sees what. These pages do not walk you through screens; the guides do that. Read them when you want to understand why the dashboard shows what it shows.

  • TruckDriving, idling, parked
  • JC371 dashcamGPS, AI cameras CH1–CH3
  • KD032 gatewayEngine (ECM) data
  • RoudiyTrips, events, scores, alerts, IFTA
  • Fleet DashboardIn your browser
  • DispatcherMap, trips, video
  • Safety ManagerEvents, coaching, scores
  • Compliance ManagerIFTA, fuel
  • Company AdminSetup, users and all fleet work, company-wide
From the truck to your team: the kit records, Roudiy processes, the dashboard shows each role its part.
  1. The truck. A Roudiy technician installs the kit and pairs it with the vehicle. From then on, whatever the truck does is recorded.
  2. The kit. The JC371 dashcam knows where the truck is (GPS), watches the road and the driver with AI, and records video to its SD card. The KD032 gateway plugs into the engine port and reads engine data such as the odometer, RPM and fuel level.
  3. Roudiy. The data arrives over 4G. Roudiy builds trips and stops, creates safety events, calculates weekly safety scores, fires alerts and adds up miles per state for IFTA.
  4. The Fleet Dashboard. Your team opens it in a browser. The map and vehicle list refresh every 30 seconds.
  5. Your team, by role. A user’s role says what they may do; their group says which trucks and drivers they see. A dispatcher in Dallas North does not see Dallas South unless you give them access.