Table and online orders stay separate
Table service accumulates against one live session. Online orders remain individual bills and workflows.
BUILDS / Active build / Platform / 2026
Dwaar System
One operating layer for restaurants, cafés, and cloud kitchens.
Dwaar is being designed as an end-to-end operating layer for cafés, restaurants, and cloud kitchens. Instead of forcing teams to stitch together unrelated tools, it brings customer ordering, staff workflows, billing, delivery, and operational intelligence into one coherent system.
WHY THIS EXISTS
One operating layer for every restaurant workflow.
Dwaar System connects table service, kitchen operations, billing, delivery, staff responsibilities, and restaurant oversight inside one shared operational model. Instead of forcing each department to work through disconnected tools and conflicting order states, every role works from the same order lifecycle and source of truth.
PRODUCT AREAS
One system, several connected workspaces.
Move across the areas to inspect the part each one plays.
WHO MOVES THROUGH IT
Different roles. One operating layer.
The system changes what it shows and allows depending on the person using it.
KEY WORKFLOW
Table service
The handoffs matter more than any isolated screen.
PRODUCT DECISIONS
The operating rules beneath the interface.
Four product laws that keep the system coherent when the restaurant becomes busy.
Realtime does not depend on browser focus
Operational queues keep updating while teams move between tabs, devices, and workspaces.
Permissions follow role and plan
Visibility and actions stay scoped to restaurant, role, plan, and explicit owner permissions.
Delivery collections are their own operation
Settlement and collection reconciliation do not disappear inside the delivery task queue.
WHERE DWAAR SYSTEM IS NOW
Built in phases, without pretending unfinished work is finished.
Core architecture and workflow rules are defined. Current work is completing operational workspaces, production data, and live restaurant testing.
CURRENT PHASE
Live testing
Production Supabase, restaurant onboarding, plan controls, and operational trials.