What do we actually have?
Pantries, fridges and cupboards are rarely tracked as one usable household state.
4DK. knows what you have, what needs using, what you can make, what to buy, and how it all fits together.
People buy food, forget what is already at home, lose track of freshness, repeat the same meals, and shop again without a clear picture of the household.
Pantries, fridges and cupboards are rarely tracked as one usable household state.
Food expires because useful freshness context is scattered or invisible until it is too late.
Meal discovery is usually disconnected from the ingredients, people and history inside the home.
Shopping starts from memory or a blank list instead of the real gap between pantry and plan.
See what you have. Know what matters. Decide what makes sense. Cook it. Remember what worked.
Pantry, quantities, freshness, people, preferences and recent context.
Ask 4DK, discover meals, rescue ingredients and adapt recipes to the real kitchen.
Plan meals, cook step by step and shop only what the household is missing.
What was eaten, what worked, what people prefer and what the kitchen should do next.
4DK. is built as a household system: each surface feeds the next instead of living as a disconnected tab.
Know what is at home and turn visible kitchen items into useful inventory context.
Understand what is fresh, what needs using soon, and where attention matters.
Get contextual answers from the real pantry, household and current food state.
Bring in recipes from links, images or text and adapt them to the kitchen you actually have.
One shared kitchen, different people — with personal preferences and boundaries preserved.
Turn ideas into a usable week of meals instead of starting from scratch every day.
Build the list from household state — buy the gap, not the whole kitchen again.
Keep useful history so meals, preferences and household decisions improve over time.
4DK. models the pantry, the people and the decisions around them — not just a catalogue of dishes.
The Food Library is structured around local ingredients, aliases, portions and everyday cooking patterns.
One kitchen can be shared while preferences, dietary needs, history and personal data remain scoped.
AI is used where it removes friction — capture, recognition, context and suggestions — with deliberate usage limits.
Inventory, meals, shopping, memory and nutrition reinforce one another instead of living in separate apps.
Status: advanced pre-launch, release hardening in progress. This is product evidence — not invented user traction.
“Food is culture. 4DK. turns that culture into usable household intelligence.”
Aliases, portions, meals and household food language become usable product data.
Cooking context becomes searchable, reusable and easier to carry across generations and formats.
A richer local food graph can support recipes, educators, cooks and food creators working from real context.
Better visibility can support nutrition awareness, lower waste and smarter local food commerce.