The parts you haven't noticed yet.
Hestia does a lot of things quietly. The leftover math. Who eats which serving. Why the score on your recipe changed after you shopped. This page explains what's actually happening, and why it's built that way.
The little icons aren't decoration.
Every recipe card in your plan shows which members of your household are eating that meal. Tap one and you'll see the assignment, who gets which servings, and how many.
Here's why it matters: a lasagna that feeds six doesn't disappear after dinner for a family of four. Two servings carry forward. The next day, the plan might assign those two leftovers to different people than the two who are getting something new. Hestia tracks planned portions across meals and days so the shopping list can account for expected leftovers. Actual results still depend on what gets cooked, eaten, and recorded.
This is the part that surprises people the most. Most meal planners plan recipes. Hestia plans what actually gets eaten.
Your recipe score isn't fixed. Your shopping changes it.
Every recipe in your plan starts with a baseline Ember Score, calculated using typical grocery store ingredients. That baseline is honest: it's what the meal looks like under average conditions.
When you shop and choose specific products, the score updates. Wild Planet tuna instead of generic. Avocado oil mayonnaise instead of standard. Those two swaps move the same tuna salad from a B toward an A. Same dish. Different choices. Different score.
This is why Hestia tracks product-level details. The recipe is the plan. What you actually bring home is the result. The Ember Score bridges both.
The plan isn't a weekly grid. It rolls.
Most meal planners give you a blank Monday-through-Sunday and ask you to fill it. Hestia generates a plan that rolls forward continuously, it knows what you've already eaten, what's carrying over as leftovers, and what's sitting in your pantry. The next plan builds on the current one. It works with your schedule.
That means if Thursday's chicken made extra, Hestia accounts for it on Friday instead of scheduling a second grocery run. If you didn't get around to the salmon, it doesn't disappear, it moves. The plan stays honest about what's actually happening in your kitchen, not what was supposed to happen on paper.
Hestia knows what's already in your kitchen. And under your sink.
When you finish a shop and check items off, they move into your pantry. Hestia tracks what you have, and the next plan accounts for it. If you bought olive oil two weeks ago and still have half a bottle, it doesn't show up on your shopping list again.
The pantry covers more than food. Dish soap, paper towels, laundry detergent, household products live here too. You do one shop. Hestia tracks it all.
It's not a perfect inventory system, you don't have to weigh everything or log every teaspoon. It's a practical one. Good enough to stop you buying a third jar of cumin.
You earn points for making Hestia more accurate.
Prices change. Sales end. Stores run out. No database stays current on its own, someone has to check.
Missions send you into stores with a specific task: confirm a price, flag a change, verify a product is still on the shelf. Complete the mission, earn points. Points unlock rewards.
It's not busywork. Every confirmed price makes the shopping list more accurate for every family using Hestia in that store. Your shop funds the next person's. That's how the data stays honest.
Here's what we do with your data. All of it.
Missions send you into stores to confirm prices. That price data gets aggregated and sold to food manufacturers and retailers, that's part of how Hestia funds the points you earn for doing it. You're contributing to a database that makes everyone's shopping list more accurate, and you're compensated for it. That's the first part of the deal.
The second part: your filter profile, allergen settings, Ember Score target, and budget range can be used to match you with product offers from manufacturers whose products meet those selected standards. They do not get your name or address. They see that an eligible household is shopping for products in that category and can offer a reason to compare one.
The offer has to pass your filters to reach you. If it doesn't meet your Ember Score threshold, it doesn't show up. The manufacturer has to earn the introduction.
The Ember Score itself is calculated from peer-reviewed science. It is not adjustable, not purchasable, and not influenced by any commercial relationship. A product scores what it scores.
We'd rather you know all of this than find it buried in a terms of service you never read.
The dish soap gets graded too.
When you scan a household product, cleaning spray, shampoo, laundry detergent, Hestia scores it the same way it scores food. A to F. But the mechanism is different.
Food scoring summarizes nutrition and processing. Household-product information is different: Hestia can display ingredient hazard classifications from identified reference data, including respiratory, skin-contact, acute-toxicity, endocrine, carcinogenicity, and environmental flags when available. A hazard flag is not a prediction of personal harm.
How a product is used affects exposure, so Hestia presents use context separately from ingredient hazards. It is general product information, not a toxicology assessment or safety guarantee.
One more thing: if a product lists "fragrance" or "parfum" instead of actual ingredients, it gets penalized. That word can hide dozens of undisclosed chemicals. Hestia doesn't reward opacity.
There are families who haven't thought about what's under their sink in years. Not because they stopped caring. Because the plan handles the food, the pantry handles the restock, and the score handles the judgment call. By week five, they're not tracking anything. The system took care of itself.
The products didn't change. The information did.
See how it works in practice
Every recipe. Every product. Graded before it reaches your plate.
See a sample plan