Flagship Engineering
Back to work
Alpha Prototype · Telemetry & coaching

LapSignal

A sim-racing telemetry and coaching platform that processes F1 2021 driving data into actionable analysis, combining deterministic analytics with optional, evidence-bounded AI coaching.

Flagship EngineeringFull-Stack & AI Engineering
View Live Showcase
Workflow stages
01
Capture
02
Measure
03
Explain

From telemetry to coaching

  1. 01 →F1 2021 → UDP

    Live driving telemetry or recorded replay

  2. 02 →Windows collector

    Normalize telemetry into a game-independent contract

  3. 03 →Python / FastAPI

    Zod and Pydantic validate data at the boundaries

  4. 04 →Deterministic analytics

    Session and lap metrics, comparison and verified findings

  5. 05 →Next.js interface

    Bounded WebSocket updates and circuit visualization

  6. 06 →Optional AI coaching

    Explain verified findings; retain rule-based coaching

The optional AI layer receives compact verified metrics, findings and evidence IDs. It does not calculate performance from raw telemetry; unsupported measurements are rejected. Rule-based coaching remains available without an API key.

Behind the system

01Overview
LapSignal is a local-first telemetry analysis platform for sim racers. It captures F1 2021 driving data, measures pace, braking, throttle, steering, stint behavior, and consistency, then turns those patterns into evidence-backed coaching. Every coaching claim should have a signal behind it.
02Problem
Sim-racing telemetry tools often overwhelm drivers with raw data or make vague coaching claims without showing the evidence behind them. LapSignal connects measured performance to a clear next action.
03Approach
Measurement comes before explanation. Telemetry is normalized, validated, stored locally, and analyzed deterministically before any coaching layer explains the findings. Pace, braking, throttle, steering, stint degradation, consistency, and theoretical best laps are calculated by the system.
04Engineering
F1 2021 telemetry enters through a native Windows UDP collector or replay, is normalized into a game-independent contract, and reaches a FastAPI backend. Zod and Pydantic validate both sides of the boundary. High-frequency telemetry is stored separately from relational metadata, and bounded, downsampled WebSocket updates feed the Next.js interface. Missing telemetry returns null rather than fabricated estimates.
05AI
AI is an optional explanation and prioritization layer, not the source of truth. It receives a compact bundle of verified metrics, findings, and evidence IDs; it does not analyze raw telemetry or calculate performance. Output that introduces unsupported measurements is rejected. Rule-based coaching remains available without an API key.
06Privacy
Local-first by default: raw telemetry stays on the driver's machine and no cloud account is required. Optional hosted AI through OpenRouter receives compact deterministic summaries rather than raw high-frequency telemetry.
07Outcome
An alpha prototype that brings recording and replay, session analysis, comparison, coaching, and progress tracking into an engineering-focused sim-racing workspace. LapSignal grew from my interest in applying software, data, and AI to motorsport-style performance analysis.

The web experience

Inside LapSignal

The public web demo is a read-only product preview with representative telemetry. It does not capture live F1 UDP data from your machine or connect to a physical collector, backend, database, or AI model. Live collection requires the local application.

LapSignal live-session web preview with circuit map, speed, throttle, brake, and steering values
Circuit visualization and recorded session playback · Representative preview data
LapSignal comparison workspace with distance-aligned speed, throttle, brake, and steering traces
Distance-aligned telemetry comparison · Representative preview data