Skip to content
Traffica

For fleets

Every trip, every vehicle, one clean feed

Send telematics or phone data from your own systems or straight from devices. Traffica turns it into trips, journeys, daily usage and driver behavior, and keeps it yours.

Get startedSee the API

What you get

From GPS points to operational answers

Your fleet’s data is visible only to your organization. It is never mixed into shared products or another customer’s results.

  • Ingest your way

    Upload from your own backend in batches of up to 1,000 records, or let devices upload directly with their own keys.

    • Devices can buffer offline for up to 7 days
    • A result for every record, never a failed batch

  • Trips & journeys

    Trips end at a stop of five minutes or a ten-minute gap. Trips with short stops between them chain into journeys, like a delivery round.

    • Distance, durations, speeds, event counts
    • Deterministic, even with late or reordered data

  • Daily usage

    Trips, kilometres, driving and moving time and events per local day, per vehicle or per driver, for up to 92 days at a time.

  • Origin–destination

    Where trips start and end, counted between H3 cells at the resolution you choose, by local day in your time zone.

  • Driver behavior

    Hard braking, acceleration and cornering per 100 km, night driving, and speeding against the posted limit of each road.

  • Vehicle signals

    Signals named and unit-checked with COVESA VSS, stored when your consent records cover vehicle signals.

  • Retention you choose

    Keep positions and signals 14–90 days, events 30–365 days and trips 30–365 days. Trips can outlive their raw positions.

  • Your team, your rules

    Org admins, analysts and viewers; API clients; single sign-on with your identity provider; an optional MFA requirement; a full audit trail.

  • Next

    Telematics platforms

    Adapters for telematics platforms and automaker data (ISO 20078), so vehicles you already track flow in without new hardware.

Simple to integrate

One upload contract for phones and telematics units

Records carry a sequence number and device time, plus whatever the device knows: position, speed, heading, acceleration, events and vehicle signals.

  • Idempotent by designResend a batch after a timeout and nothing is stored twice: each record answers STORED, DUPLICATE, SAMPLED_OUT or REJECTED.
  • Signed devicesDevices authenticate with a key you enroll, either a short-lived signed token or a client certificate. Traffica never holds a device secret.
  • Consent-awareLocation, driving events and vehicle signals are each stored only when consent covers them; the answer tells you what was withheld.
Upload body (simplified)
{
  "devices": [
    {
      "deviceRef": "van-0142",
      "records": [
        {
          "seq": 18231,
          "t": "2026-10-12T14:03:07Z",
          "timeSource": "GNSS",
          "lat": 40.75271, "lon": -73.98931,
          "speedMps": 8.4, "headingDeg": 29.5,
          "events": [{ "type": "HARD_BRAKING", "peakMps2": -4.6 }],
          "signals": { "Vehicle.Speed": 30.2 }
        }
      ]
    }
  ]
}

Validated

Trips you can trust

Benchmarked with 316 test devices across two organizations, including delivery rounds and drivers with and without trip-history consent.

trips matched to ground truth, start and end within 2 s
250/250
record outcomes differing from an independent prediction
0
from a trip ending to it showing up, typically
≈90 s

Put your fleet’s data to work

Tell us how your vehicles report today. We’ll show you what Traffica produces from it.

Request a demoSee the proof