Computer vision for road evidence

A focused interface for traffic detection.

Upload a dashcam frame, run YOLOv8 inference, and review every detected object and traffic violation in one workspace.

Detection classes

23

vehicles, signs, signals, pedestrians

Validation mAP50

92.7%

on the 1,470-image validation split

Live simulationrealtime overlay
SIMULATED
YOLOv8s · 640×640
45km/h
5 objects · 2 violations1920×1080 · 30 FPS
2026-03-22 · 10:04:32

Detection vocabulary

0 classes · YOLOv8

personcartruckbusmotorcyclered lightgreen lightstop signno entryno overtakingspeed limit 20speed limit 30speed limit 40speed limit 50speed limit 60speed limit 70speed limit 80speed limit 100speed limit 120no left turnno right turnno stoppingno u-turnpersoncartruckbusmotorcyclered lightgreen lightstop signno entryno overtakingspeed limit 20speed limit 30speed limit 40speed limit 50speed limit 60speed limit 70speed limit 80speed limit 100speed limit 120no left turnno right turnno stoppingno u-turn

Real detection workspace

Upload a frame, run YOLOv8 inference, inspect every object, and export the annotated result without leaving the app.

Structured violation engine

Detections are cross-checked through rule logic so results read like an operational review, not a demo overlay.

Persistent review trail

Every run can be saved to local history, revisited in analytics, and exported for handoff or audit.

System framing

What it
does today.

A custom-trained YOLOv8s detector feeds a rule engine that flags likely violations, and every run can be saved for later review.

Detection classes

0

vehicles, signs, signals, pedestrians

Model inference

~0ms

per image on an Apple M3 Pro GPU; about 87 ms on CPU (the free live demo runs on CPU)

Dataset coverage

0,254

labeled training images

Workspace pages

0

detection, history, analytics, settings

Working flow
01

Upload

Drop a JPG, PNG, or WebP frame into the detection workspace.

02

Review

Inspect annotated output, confidence values, and rule-level findings.

03

Track

Saved analyses appear inside history and feed the analytics layer.

04

Tune

Preferences control autosave behavior and completion notifications.

Detector
Rule logic
Analytics
Preferences

Three parts: overview, system, workspace.

This page gives the overview, the system page explains the model and rule engine, and the workspace pages run detections and keep a history of past results.

Ready to use

Open the workspace.
Run a detection.

Built to be used, not just viewed. Open the detection workspace and run your first scan in under a minute.