Private beta
Your Race Engineer for iRacing, in Discord.
Learning a new track or getting ready for your next event? Run a prep and get back insights and a race plan. Debriefs after a session go deeper, based on your own numbers.
Race Engineer · corner note
Sector 4 · primary gain ≈0.3s
- Gap
- +0.555s
- Spread
- 1.127s
The loss is before the crest, not through the drop. Your turn-in varies lap to lap. Pick one fixed marker, commit, do not lift.
The difference
Honest feedback, not flattery.
Most tools show you data. This one reads it. It leads with where the lap time is, and it is straight about what you can take back versus what is the car's limit.
One lap, two kinds of gap
Yours to claim. You've hit these sectors faster, just not on the same lap.
The car and the line won't give more here. Not on the table.
How it works
Telemetry in. A plan out.
Three things go in: your telemetry export, track data, and your own driving history. Your engineer's read comes back to you in Discord.
Coaching is per driver, private by default. Your data stays yours.
Two commands
Plan a race. Run a debrief.
/prepThe race plan
Pick an upcoming event. Get a fuel plan, a tire plan, and a qualifying plan from your own consumption and wear, with realistic pace targets and the risks to watch.
/debriefThe post-session debrief
Attach a Garage 61 export. The biggest time gain is up top, then a session summary, a sector-by-sector breakdown mapped to named corners, and ranked findings. Every finding reads data, root cause, fix, lap-time target.
What you get back
A debrief, not a data dump.
Not a screenshot. A representation of the read you get after a session.
- Data
- Min speed 64 mph into the Corkscrew. 5 mph down on your best lap here.
- Root cause
- On the brakes 8 m early, then coasting before turn-in.
- Fix
- Brake to the 100 m board. Trail to the apex, back to power earlier.
- Target
- −1.0s in S5, lap after lap.
Grounded
Anchored to real track data.
Corner references come from verified circuit data, not a model's memory. When the engineer names a braking marker, it points at one that is actually there. It is the same circuit data behind our track guides.
See the circuits →It remembers
One brief that learns every session.
Each driver has a living brief: benchmarks, weak corners, focus areas ranked by time gain, and a session log. Coaching is cumulative. It remembers last time, flags the pattern, and tracks you against your targets.
Where it stands
Built by and for sim racers.
Pixelsonly Racing is a sim racing team with a methodical, data-first culture. Race Engineer is the coaching system we run on. It reads real telemetry and gives back findings named to the corner, honest about the car's limit versus the driver's. A private beta, proven on our own driver first.
iRacing to start
Optimized for its schedule, cars, and telemetry. Other platforms are being evaluated.
Sports cars and Formula today
For data-minded drivers who already run telemetry and want to improve methodically.
Multi-driver by design
Private per driver from the ground up. Drivers decide what gets shared with others.
Get in
Request beta access.
There are only a handful of seats. We would rather give them to the right drivers than the first to reply. Beta access requires a short NDA. If you are a fit, we will reach out.
- iRacing, intermediate to advanced.
- You already run telemetry and log laps.
- You want honest numbers over hype.
Request received.
Seats are limited and we read every one. If you're a fit, we'll reach out.
Race Engineer is in active development and currently in private beta. Features, functionality, and availability are subject to change, and may not reflect the current or final product.