I build and run F1 Intelligence, a site for following a Formula 1 weekend as it unfolds. It carries live timing and session coverage through practice, qualifying, sprints and the race. Between weekends, there are results, driver and team pages, standings and replay.
For Replay, I chose recorded session snapshots. Race order, gaps, tyres and battle cards all follow the same point in time, so jumping to a lap keeps the view tied to what was known then. That is the behaviour I wanted when someone returns to a race they missed.
During live sessions, I work on classification changes, the closest battles and the different qualifying phases. The Weekend page brings the session views and reporting together. I also run the ingestion jobs and production deployment, so a race weekend means operating the service as well as developing it.
I build the Next.js frontend and FastAPI data services, with PostgreSQL for session history and Redis for live updates. The captured 30-day Cloudflare view shows 9.61k visits and 468.3k HTTP requests. These are traffic totals; they do not establish a unique-user count or retention rate.
