About

Racers first. Software engineers second.

RaceDash is built by people who race. We know the cadence of a race weekend, the frustration of watching a lap back on a phone screen in the paddock, and the small joy of finally finding the corner you left time on.

The story

RaceDash started at Club100 in Buckmore Park. Between heats we'd sit in the paddock with a paper timing sheet and a phone, trying to find the lap we wanted to watch. We knew which lap was our fastest — the timing sheet said so — but the footage on our phones was 45 minutes of continuous recording with no markers, no context, and no way to jump to the one corner that mattered.

We tried Premiere Pro. It worked, just about, but by the time we'd finished exporting we'd already driven home. The whole point of watching the lap was to learn from it before the next session, and that window had closed.

So we built RaceDash. It knows what a lap is. It knows which one was your fastest. It pulls timing from whoever's running the event — Alpha, MyLaps, Daytona, TeamSport — or straight off the SD card in your MyChron. And it gets your video ready in the time it takes to grab a drink.

We're still racing. This is still the tool we want to use. That's the whole brief.

What we believe

Your footage stays yours

Everything renders locally by default. Cloud rendering is opt-in, and we don't keep your uploads longer than we have to.

Built for the paddock

RaceDash has to work on a laptop with patchy Wi-Fi, between sessions, on five hours' sleep. That's the real environment — so that's how we build it.

No unnecessary complexity

We don't add features because our competitors do. We add them because a racer told us they'd stopped watching their footage.

v1.0
2026
Early access

Be first on the grid.

Drop your email. We'll let you know the moment RaceDash is ready.