Identifies
Locates where the lap was lost — corner entry, mid-corner, exit, or under braking — against the driver's own best reference and what that car has been shown to do at that track.
Racecraft Lab
Research · Software · Machine learning · Built for iRacing
Why was this lap faster
And what should happen next. Racecraft Lab builds the engineering intelligence that reads an iRacing session the way a race engineer reads one — then specifies what to change.
Scroll — one lap
0
Capabilities at first release
0
Engineering operations per session
0
Simulator supported at launch
0
Graphs you are asked to interpret
01 — Position
Information vs. decisions
Telemetry software already exists. The engineering labor to read it does not scale.
Existing tools
What
happened?
Channels, overlays, lap deltas. Accurate, complete, and inert. Interpretation is left to whoever has the time — which in sim racing means you, at midnight, between sessions.
Racecraft Lab
What should
happen next?
The same data, read by an engineering model. Deficiencies located, explained, ranked by projected lap time, and returned as specific changes to the car and to the driver.
The objective is not to replace telemetry software. It is to replace the engineering labor required to interpret it.
Professional teams employ data engineers, race engineers and setup specialists whose entire purpose is extracting hundredths from every lap. In iRacing you are all of them at once, usually after work. The platform is the engineer you were never going to hire.
02 — Sequence
Executed on every upload
Six operations. Performed automatically, in order, on every session.
Explains
Attributes the loss to a cause: driver input, mechanical balance, aerodynamic platform, tire state, or track evolution. Every attribution is traceable to the channels that produced it.
Ranks
Orders every finding by projected lap-time gain, so the first item on the list is the one worth the session. Engineering time is finite. Priority is the product.
Predicts
Estimates the effect of each correction before it is made, with a confidence interval. A recommendation without a projected outcome is an opinion.
Specifies
Returns actions in the units iRacing actually uses: clicks, turns, pressures, ride height, wing, diff, gear — delivered as a setup file you can load. Not adjectives.
Validates
Checks every recommendation against the next session. Predictions that fail are recorded as failures. The model is graded by results, not by output volume.
03 — Observation
Scored by projected gain
Telemetry processing extends well beyond graphing channels.
CH 01Trail braking efficiency
CH 02Throttle modulation
CH 03Brake application
CH 04Corner entry
CH 05Corner exit
CH 06Weight transfer
CH 07Suspension loading
CH 08Aerodynamic balance
CH 09Tire degradation
CH 10Driver confidence
CH 11Mechanical anomalies
CH 12Optimal driving line
CH 13Track evolution
CH 14Vehicle limitations
CH 15Driving inconsistency
CH 16Steering correction rate
Each observation is scored by projected lap-time gain — not by how unusual it looks on a graph.
04 — Data
Stated plainly
The largest asset within Racecraft Lab is not software. It is data.
One driver has
a season of data.
The platform
has all of them.
Every session that runs through the platform adds to a picture of how a given car behaves at a given track — under different conditions, in different hands, across a full season.
No individual competitor can assemble that. It is the difference between a recommendation drawn from your last three sessions and one drawn from every session ever run on the combination.
Sessions are stored and analysed on our servers and help improve the models. Full terms are set out before an account is connected.
05 — Program
Deliberately sequenced
The first release is intentionally focused. The destination is an engineering organization.
Version 1 — ships first
Upload your session.
Upload your session.
Receive engineering.
- Automatic telemetry upload
- Session parsing
- Driver performance report
- Lap comparison
- Corner-by-corner analysis
- AI-generated coaching
- Improvement priorities
- Performance history
- Setup file management
- Driver benchmarking
- Team dashboards
- Cloud telemetry storage
- Session summaries
- iRacing track database
- iRacing car database
- Discord integration
- Team management
- Driver profiles
- Secure cloud portal
Version 2 — in development
Engineering
Engineering
that anticipates.
- Automated setup recommendations
- Predictive lap simulation
- Mechanical anomaly detection
- Tire behavior modeling
- Driver confidence modeling
- AI setup assistant
- Engineering notebook
- Cross-session trend analysis
- Team engineering reports
- Remote engineer collaboration
Horizon
A digital race engineer,
A digital race engineer,
working the whole weekend.
- Live telemetry streaming
- Real-time coaching
- AI crew chief
- Pit strategy optimization
- Video synchronization
- Computer vision
- Vehicle digital twins
- Weather prediction
- Suspension simulation
- Dynamic setup generation
- Vehicle health prediction
- Voice engineering assistant
The engineering department you could never justify employing.
Racecraft Lab provides the intelligence. Vaquero Performance & Tuning delivers it to drivers. Access opens first to competitors already running serious iRacing schedules.
Request access