134km
distance
2,140m
climbing
5:42
moving
231W
normalized
Time in zone
Z1Z6
Fueling target
78 g/h
[ N39.85° E2.80° · 1,340 m · SA CALOBRA ]
The ride. The lab. Side by side.
A power file shows what you rode; a lab test shows how your body works. rides.md reads them together, so each watt comes with the carbs and fat behind it.
◆ FIT files parse on your device.
The whole ride, in context.
Your rides, your planned week, and your lab numbers on one page, so the connections between them are something you can see, not piece together across three apps.
NP 245 Wlast ride
Every ride. Past and planned.
Connect Intervals.icu. See what you rode and what's next, in one timeline.
Open rides FatMax 218 Wfrom your CPETYour lab data, not assumptions.
Import a CPET. Substrate curve, thresholds, FatMax, the watts where fat oxidation tops out.
Open profile 86 g/hfueling targetFueling from your physiology.
Turn oxidation cost into fueling targets and per-ride feedback. Opt-in per ride, nothing stored.
Get feedbackThe instrument
See it on a real ride.
Every metric reads off your numbers: zones from your thresholds, fueling from your curve. Honest about what it knows.
Riding · Climbing · Fueling · Faffing
Your data stays yours.
Three kinds of data, and where each one actually goes.
- LocalFIT files parse in your browser. The file never leaves your device.
- DirectYour Intervals.icu key stays with you. The browser talks to their API; we never see it.
- Opt-inAI feedback is per ride. Only structured ride markdown and optional athlete notes are sent, never raw files or GPS.
Questions
What stays on your device, what you need to start, and how feedback works.
Where is my data stored?+
In your browser, on your device. FIT files stay local. Your saved profile data is included in the ride markdown that gets sent if you click Get feedback — it is never sent for any other reason.
Does rides.md upload my FIT files?+
No. FIT files are parsed entirely in your browser. The file never leaves your device.
What about the Intervals.icu connection?+
Your browser talks directly to the Intervals.icu API. Your API key stays in your browser. rides.md never sees it.
Will my data sync across devices?+
No. Each browser is independent. There is no account, no cloud, no sync. This is a trade-off: your data is yours, but you own the backup too.
Do I need a lab test?+
No. You get power zones, decoupling, hourly splits, and pacing analysis without one. A lab test adds substrate curves and shows what each ride costs in carbs and fat. Enter FTP and thresholds manually if you know them.
How does AI feedback work?+
Click Get feedback on any ride. Your ride summary, extracted lab values, selected substrate points, and optional athlete notes are sent to OpenAI for analysis. If Intervals.icu is connected, ride-day recovery data (resting HR, sleep score or duration, recovery %, form) is included too. Nothing is stored on our end. The response is cached locally so revisiting the same ride doesn't re-run the model. No raw files are sent, only the structured summary and notes you choose to add.
Drop a file. See the physiology.
No account. No tracking. No sync.