Your AI race engineer
for iRacing.

Run laps. Tell Pace-ly how the car felt. Get back exact setup changes — spring rates, ARB clicks, tyre pressures — grounded in your actual telemetry, not a generic forum thread.

Get started How it works
AI race engineer Setup diffs Live overlays Per-corner analysis
SPA-FRANCORCHAMPS · STINT 3
L 11 / 14 · ON TRACK
Lap
1:47.382
Best
1:46.962
Δ Session
−0.213
Tire L/R
82° / 86°
BRAKE / THROTTLE TRACELAP 11
S1−0.142
S2+0.418
S3−0.073
PURPLE SECTOR
S3 · 0:34.812
−0.073 vs PB
P
Pace-ly
live
Loose on entry into Les Combes. Snapping on lap 7 and 11.
Confirmed. Your trail-brake is 0.42s longer on the snap laps. Rear inside wheel unloading early.
Rear ARBP5 → P4
Rear rebound+2 clicks
LAP1:47.382SECTOR 1-0.142SECTOR 2+0.418SECTOR 3-0.073THROTTLE94%BRAKE68%TIRE LF82°CTIRE RF86°CFUEL42.6LGEAR4RPM7820DELTA SESSION-0.213LAP1:47.382SECTOR 1-0.142SECTOR 2+0.418SECTOR 3-0.073THROTTLE94%BRAKE68%TIRE LF82°CTIRE RF86°CFUEL42.6LGEAR4RPM7820DELTA SESSION-0.213LAP1:47.382SECTOR 1-0.142SECTOR 2+0.418SECTOR 3-0.073THROTTLE94%BRAKE68%TIRE LF82°CTIRE RF86°CFUEL42.6LGEAR4RPM7820DELTA SESSION-0.213
The loop

The pit-wall workflow, automated.

Real engineers run a closed feedback loop with their drivers — test, talk, adjust, retest. Pace-ly runs that same loop, on your schedule.

STEP 01

Drive a session

Run laps in iRacing. The Pace-ly companion app reads telemetry in real time — throttle, brake, steering, tyre temps, suspension travel, all of it.

STEP 02

Describe how it felt

Plain language. "Loose on entry into T4." "Front pushing through the long right." No need to translate to engineering-speak.

STEP 03

Get an engineer's answer

Pace-ly cross-references your feedback with the telemetry trace and recommends exact changes — spring rates, ARB clicks, tyre pressures.

STEP 04

Apply, retest, iterate

Load the proposed setup, run another stint, and report back. The loop tightens as the AI learns the car, the track and your style.

Capabilities · with or without the AI

Engineering-grade tools, driver-friendly UI.

The AI is one way in — lap compare, per-corner analysis and the session library work on their own, no prompt required. Every feature answers one question: where is the lap time, and how do we go and get it?

Live telemetry capture

Reads iRacing's shared memory at 60 Hz. Throttle, brake, steering, slip, suspension travel — all logged, never lost.

AI race engineer chat

Conversational analysis tuned for motorsport. Ask for setup changes, driving cues, or a sanity check on a weird lap.

Setup diffs you can apply

Every recommendation comes as a concrete delta against your current setup. Copy values straight into the iRacing garage.

Session library

Every stint, every lap, indexed and searchable. Compare today's GT3 run at Spa to your PB from last month.

Per-corner analysis

Brake-zone segmentation, apex-speed deltas, trail-braking and exit-throttle fractions — corner by corner.

Lap & setup compare

Side-by-side delta charts between any two laps, plus full setup diffs across stints. See exactly where the time went.

And, since you're here · included

The usual overlay stack, in the box.

Nothing exotic — delta, fuel, standings, relatives, track map, inputs. The same HUDs every sim racer expects, included with the same plan. Drag anywhere, hide on a hotkey.

DELTA Live HUD
vs SESSION BEST
−0.213
Live gap to your reference lap. Green when you're up, red when you're losing — colour-coded by sector segment.
RELATIVES Live HUD
P3Verstappen, J.8.4k−2.1s
P4You5.2k—
P5Kowalski, M.4.8k+0.6s
P6Tanaka, R.4.1k+1.4s
Drivers around you on track with accurate gaps — even across laps and pit cycles.
FUEL · TYRES Live HUD
42.6L
12 laps
LF / RF82° / 86°
LR / RR74° / 78°
USE / LAP3.42 L
FINISH+1.2 L
Fuel burn rate, lap projection and tyre temps across all four corners — no maths between stints.
STANDINGS Live HUD
P1PLindqvist, A.1:43.214
P2PReyes, C.+1.142
P33Verstappen, J.+12.30
P43You+14.41
P53Kowalski, M.+15.02
Multi-class field with per-class positions and last-lap deltas. Stays out of the way when iRacing's UI shows it.
TRACK MAP Live HUD
SPA 7.004 kmSECT 2
Your position on track with sector-coloured trail — green where you're up on PB, red where you're losing time.
INPUTS Live HUD
Throttle
94%
Brake
12%
Clutch
0%
Pedal trace + steering angle. Stream it to coach a teammate, or record it to compare with your reference lap.
F9 toggles all overlays. Edit-mode unlocks them for repositioning per-track.
Inside the conversation

Real feedback. Real changes.

This is how a typical exchange runs — driver feedback, telemetry-grounded analysis, an applied setup diff.

Session · Spa-Francorchamps · Mercedes AMG GT3
14 LAPS · STINT 3
M
You · driver
Car feels loose on entry into Les Combes. I'm trail-braking and the rear just steps out — happened on lap 7 and lap 11. Mid-corner is fine but I'm losing the exit because I'm catching the slide.
P
Pace-ly · race engineer
Confirmed — your trail-brake into T8 is 0.42s longer than the laps that stuck. Telemetry shows the rear inside wheel unloading 18% earlier than the front, which lines up with the snap you're describing.

Two changes I'd run together:
· Soften the rear ARB by one click (P5 → P4) to keep the inside rear loaded under brakes.
· Add +2 clicks of low-speed rebound on the rear dampers to slow the weight transfer.

Driving-wise: ease off the brake about 20m earlier, carry the speed in. You're scrubbing on entry trying to recover from the snap — fix the car first, then re-set your reference.
M
You · driver
Apply the changes — let's run another stint.
Setup diff · proposed
3 changes
Rear ARBP5→P4
Rear low-speed rebound6→8
Rear tyre cold pressure26.5 psi→27.0 psi
Front spring rate120 Nm/mm·unchanged
Front camber-3.4°·unchanged
Tuned for the cars you actually drive
GT3GTP / LMDhLMP2MX-5 CupFormula VeeSuper FormulaNASCAR CupPorsche CupMazda Global MX-5F4F3Touring CariR-04
Questions

Things drivers ask first.

None. Pace-ly reads from iRacing's official shared-memory telemetry API — the same one the in-game black box uses. No DLL injection, no memory hacking, nothing that could affect your iRating or get you flagged. The companion app is sandboxed and runs alongside the sim.
Pace-ly works with every official iRacing car and track. The setup-coach has the most depth on the popular GT3, GTP, formula, and oval series, but the underlying telemetry analysis runs on anything in the service — if iRacing logs it, we read it.
They're grounded in your actual telemetry, not a generic forum thread. Pace-ly cross-references your feedback against brake-zone, corner-apex, and suspension data from your own laps. We're not promising you'll be Max Verstappen — we're promising the same kind of methodical, data-driven feedback a real engineer would give.
Yes. Drop in the HTML setup export from the iRacing garage and Pace-ly parses every section — suspension, dampers, aero, brakes, tyres — so the mechanic chat reasons about the exact car you're driving, not a stock baseline.
Yes. Pick any two laps from your session library and Pace-ly renders a side-by-side delta chart, sector splits and a track map of where the time went. Works for live laps and uploaded .ibt files the same way.

Go faster, in fewer laps.

Pace-ly is in early access right now. Sign in with Discord to join the queue — your session library starts the moment you're in.

Get started How it works