About

I’m Tom Pamminger. I started rides.md on a rest day in Mallorca, after juggling four different apps to plan routes, track rides, and figure out fueling. Each one held a piece of the answer. Each one wanted to own my data.

I started by checking what I could pull out of FIT files. Power, heart rate, cadence, altitude, timestamps. Then I moved to lab files, trying to understand where carb and fat oxidation showed up. First for myself. Then enough of it became useful to put online.

The boundaries matter as much as the features. FIT files stay in your browser. Profile data stays local. AI feedback only runs when you ask for it.

No account. No tracking. No cloud profile pretending to be inevitable.

I ride, and I’ve spent 25 years designing and building digital products. I’m not a coach or a sports scientist. I usually understand things by taking them apart and building around them.

rides.md is that habit applied to cycling data. Some assumptions may be wrong. I’m learning in public and shipping as I go.

If something looks wrong, or a ride file doesn’t make sense, send me a note. If you build tools like this, I’d like to talk too.