nutritionOS

You want to eat everything. And still hit your goals. No moral lecture. No health-food-store gray bread. No bullshit. nutritionOS does exactly that: it builds from your pantry, your day, your actual life. Restaurant punch. Zero junk. Clean numbers. Don’t ask “What am I allowed?” Ask: “What do I cook today — and how do I make it really good?”

Calories & Macros

Click to read

Pantry → Recipe

Click to read

Eat everything

Click to read

Short & clear:
Files instead of an app · No server · No gamification · Free for private use

Good food is easy. I avoided it in an unnecessarily complicated way for years

Nutrition doesn’t fit modern life anymore. We know pretty well that food matters: health, energy, training, mood. Good food flips your whole mode. Bad food does too. We just… often don’t want to know. We eat things that obviously don’t do us any favors, because life is fast, because it’s “just something on the side,” because between deadlines, distraction, exhaustion, stress — convenience wins. And while social media keeps yelling what we “should” eat, what we actually eat keeps getting cheaper, simpler, more processed.

The annoying part: eating well is easy. Normal supermarket food. No sermons. No purity contests. The first “oh wow” insight is boring: once you drop the heavily processed stuff, everything suddenly tastes like something again. Your body reacts. Energy comes back. And contrary to the popular myth, this doesn’t automatically cost more time or money. What’s missing is rarely knowledge. Most of the time it’s the unromantic thing: structure.

I know all that. Still, for years — decades — I ate like trash. No need to sugarcoat it. Barely fruit, little veg, basically no protein (sometimes for weeks). Plenty of sugar. The rest: carbs and fat. No meat, sure — but peak picky-eater behavior: skip things, puree things, never try things. My culinary universe was tiny and very “spaghetti with tomato sauce”-shaped, plus a few standards: homemade pizza, bolognese, risotto, fried potatoes. Most of the time I didn’t even cook them. Most of the time I just couldn’t be bothered. So: convenience. Jar pesto. Some random shelf tomato sauce. Lots of pre-made stuff. I knew it wasn’t great. I ate it anyway.

Early September 2025 I built nutritionOS — and according to my log, the last time I cooked spaghetti with tomato sauce was September 18. Sounds small. For my life it was a pretty spectacular turn 😀 And it didn’t come from a “big decision.” Not even a small one. I didn’t ban anything. I didn’t even set a goal. I was bored and asked nutritionOS what you can do with peanuts in a kitchen. That’s how it started. Then my food palette expanded, step by step: peanut butter. soy sauce. other nut butters. soy yogurt. lentils. chickpeas… No plan. No pressure. I didn’t stop eating things. I started eating more. Eating better. Eating wider. Suddenly cooking wasn’t a “task” anymore. It just worked. It tasted great. It actually filled me up. Sugar stopped being interesting.

I’m not telling you this to convince you. Eat what you want. Seriously. And feel free to use nutritionOS for it. If you want, you can set it up as a ridiculous fast-food configurator. Feed it garbage so it feeds you garbage right back. The point is: if you actually use the system, you notice very quickly that the best meals don’t come from restriction. You just have to cook them 😀

What is nutritionOS?

nutritionOS turns your AI into a personal nutrition assistant — and a cooking assistant.

You store:

• basic physiological data (for daily energy needs)
• goals (maintenance, deficit, gain, recovery, performance)
• rules & constraints (vegetarian/vegan, intolerances, everyday life, ethics, time)
• and most importantly: your real ingredients (pantry)

With that, nutritionOS becomes an assistant that:

• calculates your needs transparently
• balances macros, micros, and calories
• derives what you can cook from what you actually have
• designs recipes systematically (not just “ideas”)
• enriches, scales, and balances dishes on purpose
• keeps everything in long-term logs, so nutrition stops being episodic

If you want it really exact: let trainingOS calculate your daily burn. trainingOS takes your body data, baseline activity, and sport and shows what you actually spent that day. You pass that (like in the screenshot above) straight into nutritionOS.

Don’t want to store body data in an AI? Totally fair. You can use rough estimates — or let nutritionOS work with averages.

Important: nutritionOS does not replace medical care. It provides structure, continuity, and memory for eating, cooking, and goals — across weeks, months, and years.

What you use nutritionOS for

nutritionOS is for anyone who wants to organize nutrition with an AI — but in a calm, stable way.

Losing weight (without hunger drama)

• a deficit you can actually live with
• satiety through recipe architecture, not discipline myths
• trend over time, not daily scoring

Gaining weight / building muscle

• higher energy needs, distributed cleanly
• protein + micronutrients without “bro logic”
• planable, without turning food into a second job

Everyday stability

• “What do I eat today?” becomes a simple system question
• pantry prevents fantasy cooking
• routine without boredom (small variation, not chaos)

Learning to cook (for real)

• techniques, timing, order of steps, heat control
• equipment is taken into account (gas stove, oven, pans — just ask)
• flavor gets built: layering, acid, sweetness, umami, texture

nutritionOS doesn’t just tell you what you can eat. It teaches you how to cook — at restaurant level.

Click to read

Constraints & special cases

• vegetarian/vegan, allergies, intolerances, other restrictions
• reflux days / “my body can’t handle anything today” days
• low time, low energy, low motivation

nutritionOS doesn’t moralize food. It organizes, calculates cleanly, and suggests — you decide.

What you can actually do with nutritionOS

nutritionOS runs on memory. It stores goals, rules, pantry, recipes, and what you actually ate. You don’t have to re-explain your life every time. And you can always ask into your history: “What actually worked?”, “Why was I so full last week?”, “Where did my protein vanish?”

Calculate needs & set targets

• BMR based on stored data
• TDEE in combination with trainingOS
• deficit / maintenance / gain set transparently
• macro/micro targets derived in a way you can follow

Set up your pantry

• enter what’s really there (including nutrition values)
• use presets if you want to save time
• add things anytime

You set the pantry up once — and you’ve got a private food database. Nothing disappears into an app.

Designing recipes (from ingredients, not imagination)

• “What can I cook from what I have?”
• “I still need ~900 kcal / X g protein today”
• “Reflux-friendly, no garlic please”
• “Make it simple, I’m done today”
• “Make it good, I want restaurant quality”
• “Friends are coming later and I only have ketchup. What now?”

Click to read

“Only ketchup” becomes a plan. No drama.

nutritionOS builds dishes so they’re all true at once:

• they taste good
• they fit your targets
• they’re anchored in what you actually have

Logging & long-term review

• meals + daily totals in logs
• patterns and routines become visible
• analysis on demand (because it’s structured and persistent)

Once your AI remembers, you can ask questions apps can’t even form 🙂

Monthly review

Click to read

What worked

Click to read

Where it breaks

Click to read

Concrete next steps

Click to read

What changes for you

You set up your pantry once (or tweak a free preset) and start logging. The change shows up fast:

• nutritionOS organizes your nutrition. You just say what you feel like.
• you cook more often because decisions get easier. No energy to cook? nutritionOS still has an idea 🙂
• food stops feeling like control, obligation, a burden… and becomes a stable part of everyday life
• a “bad day” doesn’t explode. It’s just part of the timeline
• you see patterns without tearing yourself apart

nutritionOS doesn’t judge. It remembers.

How nutritionOS works

1. You store basic data and targets.
2. You set up your pantry (manual or preset).
3. nutritionOS suggests meals, scales, balances.
4. You log food — and nutritionOS reads history, not just the moment.
5. adjustments come from what actually happens.

Setup

Setup takes about 3–5 minutes:

1. download the ZIP
2. unzip
3. create a new project in your LLM
4. upload the files
5. EAT EVERYTHING 😀

Important: setup and personal customization happens after that. No panic. It happens in conversation with the AI.

Tested with ChatGPT.

Download nutritionOS

What’s inside

The ZIP contains files only. Specifically:

• nutritionOS Engine
  Core engine definition (nutritionOS_engine_v0.9.0.json).
  Defines how needs are calculated, how decisions are derived, and how state (logs, targets, history) is continued.

• Routing / Templates / References
  System logic and structure (nutritionOS_routing_de_v0.9.0.json, nutritionOS_templates_de_v0.9.0.json, nutritionOS_referenzen_de_v0.9.0.json).
  Defines inputs/outputs, intent routing, normalization, and internal relations.

• User Template & Glossary
  User state + shared system language (nutritionOS_user_template_de_v0.9.0.json, nutritionOS_glossar_de_v0.9.0.json).
  Contains goals, preferences, constraints, and definitions.

• Start guide
  Guided setup and recommended workflows (nutritionOS_startguide_de_v0.9.0.md).

• Presets/
  Prebuilt starting inventories (pantry variants) — starting points, not commandments.

• Food/ / Lebensmittel/
  Food + nutrition definitions, expandable with what you actually eat.

• Recipes/
  Reusable, scalable recipe building blocks you can iterate over time.

• Supplements/
  Supplement definitions, optional but integrated systematically.

• Log/ / Ernaehrungslog/
  Structured nutrition logs (append-only) showing development over time.

• legal/
  License terms and legal notes.

Where nutritionOS sits compared to classic nutrition apps

There are plenty of very mature nutrition apps: giant food databases, barcode scanners, colorful buttons, quick wins. You log what you eat, get numbers, see deficits, get reminders, somehow keep going. Many bundle gamification, streaks, ratings, pseudo-coaching. Especially early on, that can help a lot. The usual loop: track days, “fix” deviations, restart. Again. Again. Again. Food becomes something you manage, control, judge. Over time you get this weird mix of discipline, frustration, and fatigue. Each day stands alone. Each slip-up feels like a setback. Sure, there’s “history” — but it doesn’t feel alive.

Now imagine your nutrition system actually remembered. Not just calories. You. Your preferences, your day-to-day reality, your pantry. Your phases and goals. The days that felt easy — and the days where nothing worked. Imagine food didn’t have to justify itself every morning. Imagine: food can still taste good. Still be satisfying. Still be fun. 🙂 That’s the point of nutritionOS.

nutritionOS isn’t a classic nutrition app. It’s a persistent nutrition + cooking system that treats nutrition as a connected process over time, not a chain of isolated days. It doesn’t primarily run on “databases.” It runs on your life: your pantry, your needs, your history. It calculates, analyzes, and suggests — but always anchored in what’s actually there and what actually happened. A bad day isn’t a rupture. A deficit isn’t a drama. A detour isn’t a mistake. Nutrition stops being episodic.

What changes:

While many apps lean on control, nutritionOS runs on memory.
While others moralize food, nutritionOS contextualizes it.
While adjustments often stay abstract, here they’re concrete and explained, because they come from your real history.
And yes: nutritionOS helps avoid bad days — because it doesn’t just “propose meals,” it designs satiety architectures 🙂

nutritionOS doesn’t just organize nutrition. It holds it together — not only what you eat, but how eating feels over time: in everyday life, in training, in real life.

nutritionOS doesn’t have flashy buttons and it doesn’t drive you insane with gamification. It just remembers. And lets you live. Free for private use. Have fun 🙂 If you want to save setup time, you can buy presets further down. That’s convenience. No new features. You can build them yourself if you want.

Downloads

Extended Presets (optional)

License (short)

• Private use: free
• Commercial / institutional use: requires a license

Details: → View license terms

Support

nutritionOS is a public good.

If nutritionOS helps you and you want to support continued development:

Food doesn’t have to be a fight anymore. It can just be good. Every day. Every day restaurant quality — if you feel like it 🙂