Connect
The desktop app attaches to iRacing and uploads every session on its own. The setup that was on the car, the track state, and the conditions attach to the run, so the analysis has context and not just channels.
Upload your session. Receive engineering.
The first release solves one problem exceptionally well. A session goes in. A ranked, explained, and quantified engineering report comes back — without a race engineer on the payroll.
01 — Flow
Session to action
Four steps between the checkered flag and a decision.
Parse
Laps are segmented, corners identified, references selected, and channels aligned against the iRacing car and track databases. Bad data is flagged before it becomes bad advice.
Interpret
Corner-by-corner analysis against the driver's own best reference and what that car has been shown to do at that track. Every deficiency is attributed, ranked, and quantified in lap time.
Act
A driver report, a car report, and a prioritised list of changes — delivered as a setup you can load. Then it checks itself against your next session.
02 — Output
Produced automatically
A completed session produces a full engineering record. No manual intervention required.
Driver reportWhere time was found and lost, corner by corner, with the inputs that produced each result.
Vehicle reportBalance, platform behavior, and mechanical response across the session and across conditions.
Car health summaryPatterns that point at the car rather than the driver — damage, a setup that has gone away, or a tire falling off a cliff mid-stint.
Recommended setup revisionsSpecific changes with direction and magnitude, ordered by projected gain, exported as an iRacing setup file.
Driving prioritiesThe two or three things worth working on next session, and the ones not worth your practice time.
Projected gainsAn estimate in tenths for every recommendation, so the list can be triaged against track time.
Confidence intervalsHow certain the platform is, and why. Low confidence is reported as low confidence.
Recommended testing sequenceThe order to make changes in, so that each one remains measurable.
Development prioritiesWhat the program should pursue over a season rather than over a session.
03 — Driver
An evolving profile, not a lap time
The platform does not evaluate laps. It builds a model of the driver.
D 01Learning speed
D 02Consistency
D 03Aggression
D 04Adaptability
D 05Performance under pressure
D 06Setup sensitivity
D 07Mechanical sympathy
D 08Preferred balance
D 09Strengths
D 10Weaknesses
D 11Coaching priorities
D 12Historical progression
Training becomes individualized. Two drivers in the same car at the same track do not receive the same report.
04 — Contrast
Where the platform sits
Not better graphs. Better decisions.
Subject
Telemetry software & coaching tools
Racecraft Lab
The question answered
What happened during the session.
What should happen next, and what it is worth.
Who interprets
The customer, or an engineer they employ.
The platform, with the engineer reviewing.
Output
Channels, overlays, and reports to be read.
Ranked actions with projected gain and confidence.
Improvement over time
Features improve. Interpretation does not.
Every validated session improves the model.
Cost structure
Software licence plus engineering labor.
Subscription, with engineering services when a program needs them.
Compared against iRacing's own telemetry output, Garage 61, VRS, Track Titan, setup shops, and paid driver coaches. Telemetry is not the competition — it is the input.
Bring a session. We will show you what is in it.
Access opens first to drivers running serious iRacing schedules — road, oval, dirt, and endurance.
Request access