We got tired of filtering.
Eatvia started in a kitchen where three people could not eat the same dinner: one coeliac, one with a tree-nut allergy, one avoiding dairy. Every recipe app answered the same way — a shorter list of recipes. We wanted the opposite: keep the dish, change the ingredients.
What we build
Eatvia takes a recipe you already want to cook — pasted as a link or plain text — and rewrites it around your dietary profile. It swaps the parts that are unsafe or unavailable, explains why each swap works, and tells you what it does to the texture and flavour so nothing is a surprise at the table.
The second half of the product is your pantry. Eatvia knows what you already have, prioritises ingredients that are close to turning, and builds shopping lists that only contain what you are genuinely missing. Less waste is not a side effect for us; it is a feature we measure.
What we believe
- Explain every swap. An unexplained substitution is not trustworthy when an allergy is involved, so Eatvia always shows its reasoning.
- Safety over cleverness. When a substitution is uncertain, we say so plainly rather than guessing well.
- Cooking should still be fun. Dietary needs shouldn't flatten your food into the same five safe meals.
- Your data is yours. Your allergies and health goals are used to adapt recipes — never sold, never used for advertising.
Where we are
We are a small, remote, self-funded team of engineers and home cooks. There is no support call centre: the person who answers your message is usually the person who can fix the thing you found. If you want to know how the substitution engine actually decides, read the science behind Eatvia, or get in touch.