HeilsaA household food workflow, not another recipe feed
Heilsa is built in the UK around one idea: the kitchen has a state, everyone in the house should be able to see it, and dinner should start from there.
The belief underneath it
Households do not need more food content. They need an accurate, shared answer to what is in the kitchen, because every other food decision depends on it and nobody has one. Get that right and dinner, shopping and waste all improve as a side effect.
Why it starts with the pantry
Pantry state is the context missing from every other tool. Recipe apps do not have it, shopping lists do not have it, and a chatbot has to be told it from scratch every time. It is also the hardest part to maintain, which is why it has to pay for itself immediately rather than eventually.
Opinionated about scope
Heilsa is not a nutrition tracker and not an AI assistant with a personality. Those are reasonable products; they are just not this one. It does plan meals and hold your recipes, but always downstream of the pantry — a feature earns its place by making the kitchen state more useful, not by being the sort of thing a food app has.
Where the product is now
Heilsa is in live testing with a small number of real households on TestFlight. The ingredient catalogue and the recipe set are still growing, and the coverage answer gets better as they do. We would rather test with a few households properly than open it to everybody early.
How decisions get made
Features get built when the data asks for them, and they arrive in the order the pantry makes them possible. Household dietary exclusions, freshness signals and the meal plan all landed that way — each one waited until the kitchen state underneath it was good enough to be worth acting on. The same test applies to whatever is next.
See whether it holds up in your kitchen
Live testing is how the product gets decided. If your household cooks at home and coordinates groceries, your friction is the useful kind.
iOS 17 or later. Free during the beta.