About
Rees Performance is a Formula 1 companion you open while watching — the schedule, the circuit, the stakes, the standings. Built by one engineer, in public.
I'm Alphonso Woodbury — a senior software and data engineer. This is where I point that at the sport I can't stop watching: a tool I actually use on race weekends, built to be fast, clear, and genuinely useful.
Rees is a family name — and, as it happens, one with a little F1 in it already. The site doubles as an open record of how I build: data engineering, AI, and design, all in one place.
How it's built · RPX
Data flows from source to screen. Each layer does one job and hands off cleanly.
Historical results, deep lap telemetry, and live session feeds — all from open F1 data.
Raw to clean to analysis-ready, in stages. Tested for freshness and integrity on every run.
Columnar parquet for scale, SQL for serving, time-series for telemetry, vectors for search.
A model for race forecasts, natural-language questions over the data, and a deterministic rules engine for answers that are exact and traceable.
Cached JSON at the edge for everything static; WebSockets for anything that moves during a session.
Static-fast by default, with interactivity and visualization layered in only where it earns its place.
Live today: the dataset, this companion, and the 3D Track Explorer. The rest is the build plan — shipped in tiers.
Sources
| Source | What it gives | Real-time |
|---|---|---|
| Jolpica | Results, qualifying, schedules — 1950 to now | Post-session |
| FastF1 | Lap data, car telemetry, tyres, stints | Post-session |
| OpenF1 | Live telemetry, positions, intervals, weather | Yes |
| Weather | Trackside conditions and forecasts | Yes |
Historical depth is solved. Real-time is an engineering problem, not an access one.
Real-time
A live feed fans out to every open browser through one stateful object per session. (On the roadmap.)
Scope
Each tier ships on its own and stands up the next.