Work through ambiguity
Interpret messy language and unstructured inputs in context.
The platform
One source of restaurant truth. Every output built from it.
One 8 Eats separates AI interpretation from approved operational truth, giving owners a structured foundation they can review, govern, and reuse.
Pre-BetaDesign-partner validation
How it works
From uncertain input to approved output.
1. ObserveWebsites, menu images, owner requests, and other restaurant inputs.
2. Interpret and proposeMia turns ambiguity into structured, reviewable proposals.
3. Review and commitThe owner approves what becomes canonical restaurant data.
4. Publish and extendApproved data supports current and future output channels.
Owner workspace
Restaurant operations organized around connected truth.
Items are not duplicated just because they appear in multiple menus. Locations can be assigned without automatically becoming public. Media, events, identity, and menu structure remain connected while preserving their distinct responsibilities.
Impact before commitment
Owners can see the consequence of a change.
A shared menu item may appear in many contexts. The platform models that relationship so bulk actions and contextual adjustments can be reviewed without pretending every menu entry is a separate product.
The AI boundary
Mia helps with interpretation. She does not get to redefine reality.
Create reviewable changes
Translate intent into explicit, structured proposals with visible scope.
Keep the owner in control
Deterministic services validate and commit only approved changes.
Capability map
What exists now—and what does not yet.
| Capability | Status | Plain-language meaning |
|---|---|---|
| Owner workspace and canonical restaurant data | Available in pre-Beta | Core restaurant structures and owner management flows are working. |
| Photo2Menu proposals | Available in pre-Beta | Menu images can become reviewable proposals; owner approval remains required. |
| Selected Mia workflows and design-partner deployment | Under controlled validation | Implemented work is being exercised in bounded real-world conditions. |
| Complete Beta onboarding and expanded website publication | In active development | These experiences are not yet presented as Beta-ready. |
| POS, digital menu, social, print, and contextual pricing outputs | Planned | These are target output channels, not currently shipped capabilities. |
Current restaurant website
Approved restaurant data can become a customer-facing site.
The current pre-Beta product can render a restaurant website from structured, owner-approved data. Additional composition and publication workflows remain in active development, so this is a current output—not a claim that the final Website Studio has shipped.
