yootri
A triathlon training planner that fits a season to the hours you actually have,
and keeps it in your own browser. It is free, open source, and has no server of
its own — no account is required, and nothing is uploaded unless you ask it to be.
Live at https://yootri.gzarruk.com
What it does
- Fits a season to a race date. Give it a race and a rough annual hour
budget and it lays out periodised blocks — base, build, peak, taper — landing
on the day you race.
- Turns hours into actual sessions. A deterministic engine decides session
lengths, disciplines and zones from the week's budget. It never invents time:
if the week does not fit, it says so rather than quietly padding.
- Works around your life. Availability per day, standing constraints ("the
pool is shut on Mondays", "no more than three swims a week") and per-block
discipline splits all feed the fit.
- Drag-and-drop rescheduling, add/edit/delete sessions, mark sessions done.
- Logs what actually happened — duration, RPE, a note — separately from what
was planned, and reports compliance against the plan.
- Training paces from a result you ran. Enter a race or time trial — or drop
in the activity CSV Garmin Connect exports, or a single TCX or GPX — and every
Run session shows the pace band it is asking for, in min/km and min/mile.
Nothing is measured: the numbers are arithmetic on the time you gave it, and
replacing the result updates the whole season at once.
- Charts the season's training load, weekly or cumulative, per discipline.
Hand-drawn SVG; no charting library.
- Multiple named plans: create, switch, rename, duplicate, delete, export,
import.
Nothing is edited in place. Any change — yours or the coach's — is built as a
draft, checked, shown to you as a diff, and only written when you apply it.
The AI coach
The coach is optional and stays off until you configure it. It can read your
plan and propose changes; it cannot write to one. Everything it does lands in
the same draft-and-review gate as everything else, so the worst it can produce
is a proposal you reject.
- Bring your own API key. yootri has no server and no API account of its own.
- Your key stays in your browser. It is held in
localStorage, is never
written into a plan, and is never exported or synced. Anything that can run
script on the page could read it, so use a key you are willing to rotate.
- You pay your provider directly. Conversations are billed to your own
account. The model list is ordered cheapest first, and the default is the
cheapest model that can reliably drive the tool loop.
- I never see your data or your key. Requests go from your browser straight
to the provider you picked.
- Coach conversations never leave your browser. They are not synced and are
not included in an exported plan.
Two providers are supported: Anthropic, and anything speaking the OpenAI
Chat Completions shape — OpenAI itself, OpenRouter, Groq, Together, LM Studio
or Ollama — through an editable base URL. A local endpoint works well here and
keeps everything on your own machine.
Responses are generated by an AI model, not a human coach, and can be wrong.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
