Built never to leave you stranded.
Vibration, voltage drops, the battery cut without warning, no network in the paddock. The display is built to survive all of that — and a botched update too.
Two systems.
One always good.
The update is written to the copy that isn't running. On reboot the display tries the new version: if it doesn't confirm it's healthy, it goes back to the previous one on its own. A rescue partition stays there for the worst case.
- Signed packages, verified on board before a single byte is written
- Streamed over an encrypted channel with the display's own certificate
- Never half-done: either everything installs, or nothing changes
The choices
you don't see
Read-only system
The system is never written during use: cutting the battery suddenly breaks nothing. Team data lives in a separate area.
Ready in 12 seconds
Boot optimised line by line: slim kernel, services off the critical path, animated team logo while it starts.
Watchdogs everywhere
Graphics, Bluetooth, radio, services: if something hangs, the display notices and recovers without the driver doing anything.
Works without internet
Fonts, graphics, configurator: all on board. On track internet often isn't there, and the display doesn't even notice.
Smart pit Wi-Fi
Several stored networks, Wi-Fi only if the cable has no internet, every network tested before it's kept.
No data lost
If the connection drops, telemetry points wait in a queue and leave as soon as it's back. Logs stay on board across reboots.
Your car answers
only to you
A display connected to the internet is a computer connected to the internet. We treat it that way.
Board identity
Every display has its own key, tied to the hardware. Reflash it and the Factory recognises it and re-onboards it.
mTLS everywhere
Updates, logs, race data: every connection authenticates both sides with a certificate.
Offline signing root
The key that authorises software is not on any reachable server.
No open ports
The car calls the Factory, not the other way round: no services exposed on the paddock network.
Every race
teaches us something
In a ten-hour race the tank float swung from empty to full in a few seconds. The old dash, trusting the sensor, showed zero litres for forty minutes with twenty litres on board.
We replayed the race on the bench with the recorded data and rewrote the estimator: today the injector model leads, the sensor only counts when it's credible, and the estimate always errs on the safe side. That's how we work on every feature.
Talk directly to the people who built it.
No call centre: you get the people who write the software and take it to the track.