What Repast is, and what it refuses to be

The idea

Dinner comes around 365 times a year. Figuring out what to cook often falls to someone already hungry and tired, standing in front of a fridge. Nearly every tool aimed at that problem answers it with browsing — more recipes, better search, a nicer grid. Browsing is the same decision again, with more options.

Repast takes on the choosing. Describe your household and its AI selects the recipes, fits them to your cooking nights, and brings you a complete week to review. Keep the menu as it is or ask for a change. When you are ready to shop, build the grocery list from the dinners in your plan.

Four decisions that shaped the app

The planner selects. It never composes.

A model that can write a recipe can write one that does not work, with quantities nobody has cooked and a step that skips something. Repast’s planner can only choose from the catalog. That costs flexibility — it cannot invent a dish around what is in your fridge — and buys the guarantee that everything it proposes is real.

The arithmetic is separate from the model.

Grocery quantities are computed on the device by a deterministic engine against a table of 33 units. The model that picks the dishes has no part in it. A language model adding fractions is usually right, and the times it is not are the times you find out at the till.

Unknown stays unknown.

About 74% of the recipe-and-allergen pairs in the catalog carry no declaration at all. The app shows that as its own state and never rounds it up to safe. It is the single most consequential piece of restraint in the product, and it is why there is no green checkmark anywhere near an allergen row.

The week has to survive Wednesday.

Plans that only work when nothing changes are not plans. Checkmarks are stored as quantities so re-planning does not clear them, dishes drag between nights, every destructive edit has an undo, and an unfillable night stays visibly empty rather than being filled by quietly dropping one of your rules.

What leaves the phone, precisely

Two things. First, a planning request: the household size, your allergen and diet settings, your shopping day and cooking nights, the sentence you typed, and enough of the current plan to make the request coherent. The service answers and keeps nothing.

Second, product analytics and crash reports through Firebase, and subscription state through RevenueCat. Those carry a device identifier the app generates, not your name or your Apple Account. We would rather say this in plain words than let “no account” be read as “no data”. The full detail is in the privacy policy.

Your plans, grocery lists, journal and photographs are not in either list. They stay on the device and sync only through your own iCloud.

What we chose to leave out

No calorie targets, no macro tracking, no streaks and no notification telling you that you have broken a chain. A household that skipped three dinners does not need an app to be disappointed in it. What is left is the part that actually saves an evening: dinners chosen for you, a grocery list ready to shop, and recipe steps ready when you are.

Where the numbers come from

Every statistic on this site is computed from the export that becomes the app’s content pack, on August 28, 2026: 1,366 foods, 23,675 images and 259,064 ingredient lines. Wherever a figure is quoted as a share or a count, that pack is what it was measured across, and every page quoting one says so.

None of them is rounded up, and the ones that make the product look smaller are printed next to the ones that do not: 1,525 recipes left for a dairy-free household, 158 vegan recipes, and an oats column with nothing in it at all.

Contact

hello@eversight.io. Published by Eversight Studio. Repast is an independent product and is not affiliated with Apple Inc. or with any of the recipe publishers whose licensed content appears in the catalog.