Your Chess Career

The problem

A rating is a snapshot; a career is the whole story. Players have no single place to follow ratings, openings, opponents and tournaments over time, or to review their games privately.

What it does

• Rating timelines by site and time control, openings, opponents and head-to-head records, tournaments and a world map.
• Drill down to any game, replay it, and export to CSV or PGN.
• Post-game review with the Stockfish engine running in the browser, resumable.
• A versioned 0–100 Game Score that shows its coverage and confidence.
• Accounts with passwordless sign-in, email reports, and an installable web app.

How it's built

• A Cloudflare Worker (Vinext with React server rendering and static assets) and a D1 database through Drizzle.
• Public Chess.com and Lichess APIs; Lichess through a fixed-host proxy that sends one request at a time.
• Engine analysis only in the browser; email through Resend with a durable outbox.

Engineering decisions

• Privacy by design: game files and engine output stay on the player's device, and the proxy stores nothing.
• No invented data: a position that couldn't be analyzed counts as missing, not as zero, and a Game Score needs real coverage before it appears.
• Chess-site data is cached for at least 12 hours and never served after 7 days, with coverage shown openly.
• A release guard: deploys must come from a clean tree that matches main, and production is checked against the local build.
• Layout checks across 10 device sizes on every release.