A dinner marketplace built
around trust at home.

The household is the venue, which makes trust the system. A marketplace for dinners in real homes has to design a warm consumer experience on top of a rigorous approval, privacy, booking, incident, and operating model — without exposing the household behind the table.

Connect public discovery to host, guest, and operator workflows while deliberately separating public presentation from exact household and safety data.

• The managed marketplace model: application, approval, scheduling, booking, oversight
• Public table discovery and guest journeys
• Host application and managed approval lifecycle
• Operator, booking, pricing, and incident surfaces
• Explicit public/private data projections
• A bilingual (English and Turkish) product architecture in one application

• A managed marketplace lifecycle: hosts apply, the platform approves, tables are scheduled, guests book, operators oversee — completion and reviews are explicit states
• A household privacy boundary: public projections show approximate area and product context while exact addresses, coordinates, dietary details, assessments, and safety data remain private
• One bilingual product system: EN and TR journeys share the same application, navigation, messages, host tools, guest account, and operator surfaces
• Demo-safe infrastructure: repository adapters and seeded journeys make the product testable without pretending production services, real payments, or real customers exist

The captures below come from the fictional local demo: read-only journeys over seeded records, contacting no remote production service. They are product evidence, not evidence of real people or transactions. A deeper walkthrough is available in conversation.

Private Phase 1 in active development. No public launch, real booking volume, host network, or commercial outcome is claimed, and payments are not connected to real production processing.

A MaydaLabs-owned lab product. Mehmet owns the product architecture and implementation, keeping demo evidence strictly separate from launch, payment, and customer claims.

• No public launch, real booking volume, host network, or commercial outcome is claimed.
• Payments are not connected to real production processing.
• Demo records are product evidence, not evidence of real people or transactions.
• Brand, photography, policies, and operating choices remain open to iteration.