I built TuneWorks because my own performance car data was scattered everywhere: ECU logs in one place, setup changes in another, session notes in spreadsheets, and maintenance or feedback living mostly in memory. That made it hard to answer basic questions after a run or tuning session: what changed, what happened next, what should I check before the next event, and which issues are repeating? The first version focuses on the foundation: vehicles, setups, sessions, logs, maintenance, and notes all connected in one workflow. It started with my own Haltech-based RX-7, but the goal is broader than one ECU platform or one type of racing. I’d love feedback from tuners, racers, track day drivers, autocrossers, and anyone who has tried to manage performance car data across too many files and tools. AI-assisted log analysis and race-engineer style review are coming next, but I wanted the core workflow to be useful first: vehicles, setups, sessions, logs, maintenance, and notes connected in one place.

Tuneworks.ai 1.0

Your motorsports command center for faster lap times

Your motorsports command center for faster lap times