Built by a cyclist,
for cyclists who train seriously.

I'm an engineer and an amateur cyclist, based in Barcelona. I train consistently and take my performance seriously, with the hours a full-time job leaves me and without the budget of a professional. I live cycling; I don't live off it.

I trained for La Traka 360 — 360 km of gravel in a single day — across four separate apps: one read my recovery, one prescribed the sessions, one held the fitness curve, one handled nutrition. Each was right about its own slice, and not one of them handed anything to the next. I copied numbers between them by hand, paid four subscriptions, and at the end of every week I had data everywhere and clarity nowhere.

The ride went well: I got fit, I rode it, I finished it. What stayed with me was what it had cost — and the realisation underneath it. I had paid four times over, and the part that made the stack work was me, joining the dots every Sunday night.

So I built the joining. I had written some Python at engineering school and nothing since, so I learned what a backend was and what a frontend was — and, in the part I am least proud of and that taught me most, I let code pile up that I did not understand, until the periodisation engine had to be thrown out and written again from zero. That rewrite is the engine Summit runs on today. It is also the platform I prepared my whole Gran Diagonal on, and the one I wish I'd had when I was staring at a TSB chart I couldn't act on.