Skip to content

Technology

Built for continuous telemetry

From the tracker in the vehicle to the screen on your desk, every step is designed to keep the data complete, ordered and safe.

Teltonika devices, over TCP

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.

  • Device identification by IMEI
  • CRC-16 check on every packet
  • Codec 8 and Codec 8 Extended decoding
  • A packet is acknowledged only once its records are safely stored

Teltonika is supported out of the box. Any other tracker or device can be connected through a dedicated integration.

Not limited to one tracker brand

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.

  • Any tracker on the market

    If a device can send its data to a server, it can be connected to Pillaria through a dedicated integration developed for its protocol.

  • Any device, with custom development

    Sensors, readers and other connected devices are added the same way, scoped around the data you need from them.

  • The same platform for every device

    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 devices

What runs behind the screens

Real-time telemetry

Positions are pushed to your browser over WebSocket as they arrive, so the map follows the fleet without refreshing.

Data processing

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.

API

A REST API documented with OpenAPI covers units, drivers, devices, trips, alerts and reports.

Web access

Pillaria runs in any modern browser, on desktop and mobile screens, with a French and English interface.

Security and tenancy

Each organisation's data is isolated at the database level, access is role-based, and users can be limited to selected units.

Reliability

Records are stored durably before a device is acknowledged, so a device that did not get an acknowledgement simply sends the data again.

How the data flows

A simplified view of the path a position takes from the device to the dashboard.

  1. 01

    GPS devices

    Teltonika trackers report over TCP.

  2. 02

    TCP gateway

    Identifies the device, checks the CRC, decodes the packet and acknowledges it once it is stored in Kafka.

  3. 03

    Event streaming

    Kafka keeps every record durable and in order for each device.

  4. 04

    Processors

    Positions, trips, geofences and alerts are computed from the stream.

  5. 05

    Storage

    TimescaleDB holds history, PostgreSQL holds configuration and Redis holds the latest state.

  6. 06

    API and live updates

    A REST API and a WebSocket feed serve the applications.

  7. 07

    Web application

    Dashboard, maps, playback and reports in the browser.

Ready to Transform the Way You Manage Your Fleet?

See the platform on your own use case. We will walk you through it and answer your questions.