Live Tracking: how it works
Every vehicle, live, from any tracker
Live Tracking is the path from a device's raw bytes to a dot on your map. A protocol bridge decodes each tracker's protocol into one canonical telemetry record; the enricher turns a device into a vehicle you recognise, derives its status, and keeps the latest state hot for the console and the mobile app. Nothing here is specific to a tracker brand, which is the point.
The parts
1. Tracker
gt06 · teltonika · h02 · osmand
Any GPS device or a driver's phone connects over its own protocol to a public port. Concox, Teltonika, SinoTrack and phones have an open port today; other models are tested and opened on request.
2. Canonical telemetry
telemetry.decoded
Every fix becomes the same record: IMEI, time, position, speed in km/h, heading, fix validity, ignition, and the protocol's extra attributes.
3. Enricher
events.domain
IMEI to device to vehicle to tenant. Status derived from movement and ignition: moving, idling, stopped, no fix.
4. Live state
valkey · ttl 2 min
The latest position per vehicle is kept hot; a vehicle that stops reporting fades from the map instead of lying.
5. Live push
ws /ws/live
The console and the app hold one connection; a snapshot on connect, then every new position as it happens.
6. Storage
timescaledb · positions
Every position is also written to the time-series store, history, replay and trips read from here.
Build on it
The same data is available over the API and the live socket.