Idunn is a kitchen system for Indian households: what is in the pantry, what is about to go off, and — the question that actually matters — what can I cook right now with what is already here.

The gap it fills is not a missing feature, it is a missing corpus. Global pantry apps index a Western ingredient list, so aloo-gobi and bisi-bele-bath do not exist, and dhania is not coriander leaves is not kothmir. Nutrition data has the same problem: USDA-based databases miss home cooking, while the Indian Food Composition Tables exist and almost nothing consumer-facing uses them. Idunn treats both as first-class from the start, with a pantry that distinguishes staples from perishables and a recipe library that understands regional naming.

Retrieval is the technical core. Recipes and pantry state are indexed in MongoDB Atlas, and “what can I cook?” runs as hybrid search — vector and lexical results fused, then reordered by a cross-encoder reranker — with RAGAS-style evals to check that the answers stay useful as the recipe corpus grows. Receipt photos go through OCR into structured inventory rows, so restocking is a photo rather than twenty minutes of typing.

It is built in Python 3.13 with FastAPI, designed to hold up under real use in a real kitchen: multi-cook households, unit conversions between katori and grams, and recipes inherited on paper. Part of the same three-project portfolio as Frigg and Vanir. In progress, repository private.