For cyclists who cook for themselves
Food that keeps up
with your training.
Musette reads what you actually rode — measured work, training load, time in each zone — and sets that day's calories and carbohydrate against it. Then it writes the shopping list.
Two halves of the same number
A four-hour Saturday and a rest-day Monday are not the same eating problem. Most apps make you do that arithmetic yourself.
Read from your ride file, not estimated from a slider.
Every figure here is arithmetic done in code. Nothing is a language model's guess.
How it works
Connect your training
One link to intervals.icu, which already syncs from Garmin, Wahoo, Coros, Polar, Suunto, Zwift and the rest. Your rides arrive on their own.
Answer the intake once
Weight, height, the hours you ride, what you are training for, and what you will not eat. Ten minutes, and you can change any of it later.
Shop and cook
A month of dinners, portioned to your days, with the shopping list already split by store and priced. Tick items off in the aisle.
What it does not do
This is a list of absences, and it is deliberate.
- No feed, no streaks, no badges. Nothing here is trying to get you to open it more often.
- No ads, and your data is never sold or shared for marketing. There is no second business model hiding behind the first.
- Not a medical device. It will not diagnose, treat, or tell you what your body needs. It plans food around training.
- No calorie shaming, ever. It will not tell you to earn a meal or work one off.
- No public signup. Invite only, so the person who invited you can vouch for it.
What it holds about you
- Bodyweight, height, age and training load. Because the targets cannot be computed without them.
- What you ate, if you log it. Kept 90 days, then deleted automatically.
- Three processors: Cloudflare hosts it, intervals.icu supplies the rides, OpenAI writes the explanations.
- Export and delete yourself, at any time, without asking anyone.
This is health data
Training load and bodyweight are special-category data under GDPR Article 9. We treat them that way: explicit consent at signup, a named processor list, and a retention policy written down rather than implied. The full detail is on the privacy page, in plain language first.