Skip to content
Traffica

Road intelligence from connected vehicles,for safer streets.

Traffica turns V2X, phone and telematics data into speeds, safety hot spots, signal performance, trips and driving scores for cities, insurers and fleets. One canonical pipeline, with privacy built in rather than bolted on.

Request a demoSee how it works

Midtown segment speeds

Median speed per segment · 15-minute cells · 8:30 am–8:45 am

Times SqHerald SqBryant ParkGrand Central

8:30 am: 45 segments stop-and-go, 98 slow, 86 moderate, 1 free flow, 0 not published. Slowest: W 50th St, 8th Ave – 7th Ave, 2 mph.

8:30 am
  • Free flow
  • Moderate
  • Slow
  • Stop-and-go
  • Under 5 vehicles · not published
  • Hard-braking hot spot

Who it’s for

One data platform, four kinds of customers

Public agencies get privacy-safe aggregates. Insurers and fleets get their own consented data, analyzed. Drivers stay in control. Every customer is strictly separated.

How it works

Every source, one canonical pipeline

Each source has an adapter that maps it to the same model, so adding a source never changes the core. Roadside units, phones and telematics units already flow through it; automaker and fleet platforms are next.

Platform details
Data flows from roadside units, driver phones, telematics units and (next) OEM and fleet platforms into Traffica. It is normalized into one canonical model, protected with pseudonyms, consent checks and k-anonymity rules, then analyzed into speeds, hot spots, signal performance, trips and scores, and delivered through the API, the dashboard and exports.

  1. Sources

    • Roadside unitsV2X · SAE J2735
    • Driver phonesInvited, consented
    • Telematics unitsAPI or device keys
    • OEM & fleet platformsISO 20078

  2. 01

    Normalize

    One canonical model · COVESA VSS · SI units · Deduplicated, time-fixed

  3. 02

    Protect

    Daily pseudonyms · Consent per category · k = 5 publication

  4. 03

    Analyze

    Speeds & hot spots · Signal performance · Trips & scores

  5. Delivered to

    REST API · Dashboard · Your systems

Proof, not promises

Every metric checked against ground truth

Every capability is benchmarked in controlled test scenarios where the right answer is known in advance, and the platform’s output is compared with it, metric by metric.

mean segment-speed error
0.44 m/s
94% of segment windows within ±1 m/s of ground truth
vehicle messages ingested
19,500/s
sustained on one developer laptop, nearly 4× the design target
intersection passages detected
97%
timed within 3 seconds of ground truth
trips reconstructed
250 / 250
start and end within 2 s, distance within 2%
raw vehicle IDs stored
0
checked by scanning every column of every table

Benchmarked against known ground truth in controlled test scenarios.See every validation result →

What you can measure

From raw messages to answers you can act on

Delivered as GeoJSON and CSV through the API, or in the dashboard. Shared V2X products are probe samples, labeled as such, never presented as traffic volume.

  • Segment speeds

    Median, 85th-percentile and mean speed per road segment and direction, every 15 minutes, matched to the road network.

  • Safety hot spots

    Hard braking reported by vehicles and detected from motion (≥ 0.4 g), counted per segment and per kilometre.

  • Intersection performance

    Arrivals on green, platoon ratio, stops, approach delay and red-light-running candidates, without new detectors.

  • Trips & journeys

    Trips detected from positions, chained into journeys, with distance, duration, speeds and events for each.

  • Origin–destination

    Where trips start and end, counted between H3 cells by local day, with small groups of people withheld.

  • Driving scores

    Events per 100 km, night driving and speeding against posted limits, combined with weights you set.

Privacy by design

Built for a world that is watching how driving data is shared

Regulators have made clear that location and driving data is sensitive. Traffica was designed around that from the first line of code: pseudonyms for shared data, consent for identified data, and limits that hold even inside a customer’s own account.

Privacy & TrustWhat drivers see
No cell is published unless at least five distinct vehicles or people contributed.
k = 5
Vehicle pseudonyms are keyed per day, and never linked across ID rotations.
24 h
Trip endpoints are trimmed unless the person consented to trip history.
200 m
Raw vehicle IDs stored anywhere. VINs and coordinates stay out of logs and audit trails.
0

Built on the standards your systems already speak

  • SAE J2735
  • SAE J2945/1
  • IEEE 1609.2
  • NTCIP 1218
  • COVESA VSS
  • ISO 24100
  • ISO/SAE 21434
  • CCPA/CPRA
  • OAuth 2.0 · OIDC · SAML

Put Traffica to work

Tell us what you want to measure, on your roads, your policies or your fleet, and we’ll show you how Traffica delivers it.

Request a demoSee the proof