Nutrition trackers count calories and never see your pantry. Pantry managers see your pantry and never count a nutrient. Pantensa does both the moment you cook or log a meal — one entry, not two — and it's priced like a real product from day one.
Get notified when it's readyThe gap
MyFitnessPal and Cronometer count nutrients flawlessly — and have no idea what's on your shelf. Grocy knows your pantry — and doesn't count a single nutrient. Want both, and you're keeping two accounts, typing every product in twice. The niche exists precisely because big players won't touch it.
Nutrition trackers
$9–20/mo, per person
Pantry managers
free, self-hosted
The idea
Pantensa counts what you ate and, at the same time, knows what's left in your pantry — so you never type the same thing twice.
The usual fear with any tracker: "this is going to eat my evenings." Pantensa has two honest speeds, and you never get pushed into the slower one.
Just counting calories and macros. Log what you ate, see the day against your target and the weekly trend. The pantry doesn't exist at all — no screen even hints at it.
Also tracking what's at home. Everything above, plus the app knows what you have, what's about to spoil, what to buy — and logs what you ate against real stock automatically.
The mode is a household setting, not a pricing tier or a separate product.
Where the design came from
"When I have time, I add food to the meal plan throughout the day. Sometimes after the fact with real amounts, sometimes ahead with rough ones, then I fix it to the real amount right before 'consume.' Then in the evening, or the next day depending on mood, I hit 'consume.'"
— a description of an ordinary day, the source of the whole "a day is a draft" rule
Not the other way around: the code wasn't written first and behavior forced to fit it after. The model got rewritten once it became clear that closing the day in the evening is bookkeeping, not compliance with a plan.
What it does
One screen answers three questions: who you are and where you're headed, how today looks against your target, and your 7-day average.
A drawer where you throw in as many items as you want at once: products, recipes, or a freehand entry (name + calories, that's enough).
Don't know the calories in a product — don't enter them. Pantensa pulls the data from open databases (OpenFoodFacts, USDA) in the background.
The evening ritual subtracts what you ate from the pantry. A mismatch gives three doors: log a purchase, it was a different product, or there was less than logged.
One screen where stock moves both ways: ingredients disappear, finished dishes appear — sometimes several from one recipe (broth → liquid + chicken).
A smoothie with "Berry" instead of a hard-coded cherry or blueberry — the recipe has a flexible slot with options, the app suggests last time's pick, you always choose. No more cloning recipes every season.
What you have, what's spoiling soon, price per unit. A finished dish sits in the same list as raw ingredients.
A week of days ahead. A "what's missing" button checks the plan against your pantry and drops the gap straight into the shopping list.
Days, trends over time, and spending — including a chart: "milk is up 18% over six months."
The body belongs to the person, not the household. One calculator sets calorie and macro targets with the Mifflin–St Jeor formula, with room to adjust by hand.
Invite by link, roles, a shared pantry. Paid features are billed to the household, not to each person separately.
Your own API key connects Pantensa to Claude or another assistant — it can see your plan, pantry, what's about to spoil, and can add meals to the plan itself.
Installs like a normal app — an icon on your home screen, works without a browser address bar.
Design principles
Most inventory apps feel like a discipline system: miss one log and the numbers drift, the streak breaks, you're "behind." Pantensa is built the other way — imperfect data is the expected, normal state, not a failure to fix immediately.
Logged "oatmeal, ~60g" in the morning, weighed it in the evening and corrected it to 75 — that's a normal update, not a mistake to fix.
Didn't log the protein in a café coffee — the day quietly marks itself "incomplete," instead of showing a lower number that looks like a fact.
Cook and log a purchase both add to the pantry. Close the day is the only thing that subtracts. Everything used to be called "consume" — which is why nobody understood the model.
Protein and carbs are goals to hit. Sugar and salt are ceilings, where 100% isn't a win. Fiber is a floor.
Short on yogurt for a recipe because you forgot to log a purchase? The app offers to top up the amount from what it already knows, or drop the gap into the shopping list — instead of forcing you to stop and fill out a full purchase form just to make dinner.
Trust & privacy
Even inside a shared household, nobody sees what someone else ate — not even a spouse. The pantry and recipes are shared; the diary is yours.
Hosted in the EU region, with a named data controller and a real contact in the privacy policy — not an anonymous company.
Full export and account deletion on request. Nothing auto-deletes without a reason — a year of food history is exactly what people come back to after a break.
Just hosting and email. Any future AI provider is a new, separate consent question — not a silent config change.
Pricing
nutrients, no pantry
verified nutrients, no pantry
pantry, no nutrients, your own server
nutrients + pantry, whole family
Early users lock in this price for as long as they stay subscribed — even after it goes up for everyone else.
Honestly
Not live yet — still figuring out if this itch is mine alone or a shared one. If the two-apps-that-don't-talk problem sounds familiar, or you've solved it differently, I'd genuinely like to hear it.
Get notified when it's ready