Home Kitchen — Home‑Chef Marketplace
A marketplace connecting home chefs with customers: each chef runs their own menu, weekly schedule and offers, and the customer orders, rates and chats with them directly — across three separate API surfaces for chef, client and public.
Overview
Marketplace connecting home chefs with customers: kitchen profiles and menus, orders with delivery scheduling, ratings and payments.
01The challenge
A home chef is not a restaurant: they do not cook everything every day but plan a week ahead against a limited number of orders. A model of "a fixed menu, always available" would have promised the customer something that could not be delivered.
Onboarding a chef also needs vetting: questions and information that must be reviewed before they appear in the marketplace.
02What we built
We built a weekly meal schedule per chef: a dish is available on specific days, and the customer sees what can actually be cooked rather than the whole catalogue. Offers sit on top of dishes as time-bounded bundles.
Chef onboarding runs through recorded questions and answers that admin reviews before publishing, so marketplace quality is controlled at the gate rather than after a complaint.
The API is split into three groups — chef, client and public — each with its own authentication, so no permission leaks across. Chat and ratings are built into the system, keeping the conversation on the platform.
03The outcome
The customer sees what will actually be cooked on the day they order, and the chef plans their week and controls their capacity instead of being surprised by orders.
Conversation and ratings stay on the platform, so the marketplace keeps its quality record instead of losing it to private chats.
What the system does
The modules that were delivered and put into daily use.
-
01
A weekly meal schedule per chef: a dish is available on specific days, not permanently.
-
02
A chef onboarding path with questions and answers reviewed by admin before publishing.
-
03
Offers and bundles over dishes, coupons, a meal cart and orders.
-
04
Direct in-platform chat between customer and chef, plus ratings and notifications.
-
05
Three separate API surfaces (chef, client, public), each with its own JWT authentication.
-
06
A dish catalogue with categories and multiple images, country and city data, and bilingual content.
Technologies used
What this system is actually built on — not a generic list.