Rydiq
How it worksChapter II · The pipeline

Upload a ride. Get a report. Download what you need.

Three steps for the cyclist. Seven steps for the pipeline. You only have to do the first one.

¶ 01What you do
01

Upload

Drag in a clip, or your whole SD card dump. Uploads resume if your wifi blips. Your card can be wiped the moment the upload finishes.

02

Auto-analyze

The pipeline finds every vehicle, measures every pass, identifies the close calls, and reads the plates. A notification lands when it's done.

03

Download

Open the ride, pick the incident, click Download. A police-ready PDF, annotated frame, distance, vehicle, plate, GPS, timestamp.

Ready to try it?

Free plan, 120 min/month, no card.

Join the beta
¶ 02Under the hood

The pipeline, step by step.

What “auto-analyze” actually does, in seven stages. No setup, no calibration, no manual review on your end.

i

Upload your ride

Drop in any clip from a forward, helmet, chest, or rear-facing camera. We probe the file, pick the right camera and mount preset automatically, and queue it for analysis.

ii

Find every vehicle

A computer-vision detector runs across the footage and tracks each vehicle through the frames it appears in. Cars, trucks, motorcycles, vans, anything that crossed your camera gets picked up and followed.

iii

Measure how close

For every tracked vehicle, we estimate the side gap to the rider in feet. The math uses the road surface as a reference and adapts to your camera and mount, so the same number means the same thing whether you ride with a handlebar GoPro or a seatpost cam.

iv

Filter the noise

Parked vehicles you rode past and oncoming traffic that wasn't actually close get classified out. What's left is the set of vehicles that genuinely passed you, bucketed by clearance into Severe, Near, Brush, and Safe.

v

Identify the vehicle

For every non-safe pass we run a vision model that returns make, model, year range, color, and body type. The model picks the best angle it has, not just the closest frame, so distant and side-on shots still get a clean read.

vi

Read the plate

Plate reading uses several candidate frames and takes the consensus, so a single blurry frame can't hallucinate characters. When the plate isn't legible from any angle, we say so, no guesses.

vii

Build the report

The ride lands as a timeline with a chapter for each pass. Click a chapter to seek the video; toggle the live distance HUD to see vehicle outlines and severity labels on top of the footage; open analytics for the totals. Every non-safe pass is one click from a downloadable incident PDF.

The pipeline does the calibration for you. You don’t measure anything, mark anything, or tell us where the road is.

, Why this works without setup
¶ 03On the map
Coming soonPhone-track sync

No GPS on your camera? Drop in your phone track.

Helmet cams, chest cams, dashcams — most don’t record GPS. Doesn’t matter. Drop in a Strava export or any GPX from your phone, and we line it up with the video timeline second-for-second.

Every incident gets pinned to the exact spot on a map. Every report gets an exact street address and the wall-clock time the pass happened. Officers don’t have to take your word for any of it.

How the sync works
i

Upload your phone track

Strava GPX, Apple Health route, Garmin Connect, or any standard GPX file.

ii

We align by timestamp

Your video’s recording time and the GPX track are matched to the second, no manual nudging.

iii

Map view + exact addresses

Every incident gets reverse-geocoded. The incident PDF gains a map, a pin, and a street address.

Want a heads-up when it ships?

Sign up free, phone-track sync rolls out to every account at launch, no plan change required.

Join the beta