Rennblock reads the car as you drive it and returns the one thing feel cannot: the exact corner where the tenth was found, or lost.
Chapter 01 — The premise
A brake released ten metres early. An apex a hand-width wide. A throttle that hesitated for a tenth. You cannot feel those — the car can, and Rennblock reads it two hundred times a second.
Chapter 02 — The pit-wall
Gear, revs, pedals, delta and the last ten seconds — updating twenty times a second while you drive. Private to you.
The pit-wall
Gear and revs, throttle and brake, four tyre and four brake temperatures, g-forces, fuel, delta and your lap history — one screen, refreshed twenty times a second. The wall a real team watches, yours alone.
Chapter 03 — How it works
Run the Rennblock client, paste your access key once, and race exactly as you always do.
The car is read two hundred times a second — laps, tyres, pedals, position. You never touch it.
Open the pit-wall in any browser: live data, your full archive, and the leaderboard for your circuit.
Under the hood
Every valid lap lands on a live board — your best time against the field, car by car, corner by corner, in real time.
Nothing is pruned. Come back a season later and the lap is exactly where you left it — the trace, the tyres, the tenth.
Two hundred hertz on the rig, twenty to the pit-wall, addressed to rooms so a packet only ever reaches the driver who asked for it.
The live path never touches a disk. State lives in memory under a short expiry; a lap is written once, when it is finished.
Access is granted, never taken. Every session is re-checked on each request, so an invitation can be withdrawn in a heartbeat.
Your telemetry is yours alone. Nobody sees your rig’s stream but you — not the field, not the next driver.
Chapter 04 — Performance
Invitation only
Rennblock is invite-only while we grow. Request a key and we’ll review it by hand — drivers first.