Into tech, and into triathlon. I built Triday because I kept losing evenings preparing my own races.
By hand: open the athlete guide, list the aid stations one by one, break the course profile down segment by segment, work out carbs per hour in a spreadsheet. Several evenings per race. And on race day, my family still had no idea where to wait for me, or when.
Triday is that exact work, automated. You pick your race, set your paces across three scenarios, and everything else follows: your split times, a nutrition plan cross-referenced with the official aid stations, a checklist per transition bag, and a page you send to your family so they know where to stand.
A race plan is only worth the data behind it. If the app promises you Coke at kilometre 120 and there is none, you don't lose a feature — you lose your race.
So here is the rule I set for the catalogue: a course only enters it once it is sourced from the edition's official athlete guide, with its source and verification date on show. No automatic generation, no figure lifted from a forum. If I can't source an aid station, it doesn't appear.
It's slower. It's also the one thing a generic tool won't do in my place.
Application servers and the database are hosted in the European Union. Analytics run through a European instance and only start after you consent — the detail is in the cookie policy.
This gets built alongside the athletes who use it. If you're preparing a race, found a wrong data point, or just want to complain about a detail: write to me, I read everything.