iRacing first

An iRacing AI race engineer should feel like a calm voice in the car, not another dashboard fighting for attention.

That is the wedge for RACEngineer.ai. Not a generic chatbot next to telemetry. Not another tool that talks too much. The goal is an AI race engineer for iRacing that answers in race language, tracks the session properly, and knows when to wait until the debrief.

RADIO

Push-to-talk answers

Fuel, pit window, tyres, traffic context, and the short answer you need while driving.

STRATEGY

Session-aware judgement

Not just raw numbers. Stint shape, trend reading, undercut timing, and whether the call is worth making now.

DEBRIEF

Short post-race review

A few useful corrections for the next run, not a wall of charts after the flag.

Why iRacing is the right first surface

iRacing is where the value is easiest to feel. Drivers already care about fuel numbers, tyre life, traffic, multiclass context, safety rating pressure, endurance stints, and repeatable improvement. That makes it a better first home for an AI race engineer than a broad “supports every sim” pitch.

The hard part is not adding another voice. The hard part is building something that knows what should stay local and immediate, and what should wait for a more thoughtful answer. That is why the product is built around local urgency and cloud judgement.

What it should do better than current tools

Existing tools already do useful things. CrewChief is strong at deterministic spotter calls. Telemetry tools are strong at showing data. Setup products are strong at helping outside the car. The gap is the layer that connects those worlds in a way that still feels usable while you are driving.

·Answer a radio question without making you alt-tab.
·Track context across a stint instead of reacting to one isolated event.
·Remember recurring weaknesses across sessions.
·Respect attention instead of narrating constantly.

Who this is for

The best first users are likely iRacing drivers doing league races, endurance events, and deliberate practice. People who already care about radio discipline, session review, and shaving repeat mistakes. If someone mainly wants a novelty voice, this is probably the wrong product. If they want a better race loop, it starts to make sense.

FAQ

The iRacing angle, in short.

What would an iRacing AI race engineer actually do during a session?

It should answer push-to-talk questions, track fuel and tyre trends, manage pit-window context, stay quiet when nothing useful needs saying, and give you a short debrief after the run.

How is this different from CrewChief?

CrewChief is great at deterministic spotter and event calls. RACEngineer.ai is being built for the layer above that: natural-language radio, telemetry-aware strategy, post-session debriefs, and driver memory across sessions.

Why start with iRacing?

Because iRacing has the strongest mix of league racing, endurance use cases, telemetry-rich sessions, and drivers who already think in terms of race craft, strategy, and repeatable improvement.

Early access

Join the iRacing waitlist.

If this is the kind of engineer you want in the car, join the waitlist and I will send the first release notes, pilot openings, and build availability.

Join the waitlist Read the full explainer