Real-time telemetry
Positions are pushed to your browser over WebSocket as they arrive, so the map follows the fleet without refreshing.
Technology
From the tracker in the vehicle to the screen on your desk, every step is designed to keep the data complete, ordered and safe.
Trackers that report in Teltonika Codec 8 or Codec 8 Extended connect directly to the platform over TCP. The platform was developed against the FMB140 and FMC150 specifications.
Teltonika is supported out of the box. Any other tracker or device can be connected through a dedicated integration.
The platform is built around a common position format, not around one manufacturer. Each device family is read by its own protocol receiver, and everything after that point is shared.
If a device can send its data to a server, it can be connected to Pillaria through a dedicated integration developed for its protocol.
Sensors, readers and other connected devices are added the same way, scoped around the data you need from them.
Once a device is integrated, its data feeds the same maps, trips, alerts and reports as the rest of your fleet.
We start from the manufacturer's protocol documentation and a few test devices, and we agree the scope and timing with you before any work begins.
Discuss your devicesPositions are pushed to your browser over WebSocket as they arrive, so the map follows the fleet without refreshing.
Trips, engine hours, geofence events, road speed limits and fuel events are derived from the stream. Processing is at-least-once and idempotent, so a replay never duplicates results.
A REST API documented with OpenAPI covers units, drivers, devices, trips, alerts and reports.
Pillaria runs in any modern browser, on desktop and mobile screens, with a French and English interface.
Each organisation's data is isolated at the database level, access is role-based, and users can be limited to selected units.
Records are stored durably before a device is acknowledged, so a device that did not get an acknowledgement simply sends the data again.
A simplified view of the path a position takes from the device to the dashboard.
01
Teltonika trackers report over TCP.
02
Identifies the device, checks the CRC, decodes the packet and acknowledges it once it is stored in Kafka.
03
Kafka keeps every record durable and in order for each device.
04
Positions, trips, geofences and alerts are computed from the stream.
05
TimescaleDB holds history, PostgreSQL holds configuration and Redis holds the latest state.
06
A REST API and a WebSocket feed serve the applications.
07
Dashboard, maps, playback and reports in the browser.
See the platform on your own use case. We will walk you through it and answer your questions.