ChefOS

Order, kitchen and inventory state is pushed over Socket.io rather than polled, with clients subscribing only to the channels their role requires — the Kitchen Display System does not pay to receive billing traffic.

The server remains the single source of truth. Clients render what they are told rather than computing authoritative state locally, which is what keeps several simultaneously open screens from drifting apart during a rush.

Each table carries a QR code resolving to a mobile-first menu, so the diner's own device becomes the ordering terminal and no hardware has to be bought or maintained.

Dishes can carry interactive 3D previews rendered with React Three Fiber. It is the one piece of deliberate spectacle in the product, and it exists because a photograph cannot convey plating the way a rotatable model can.

Google's Generative AI SDK backs dish recommendations, using what is already in the cart and what is actually in stock rather than a static 'popular items' list.

Sessions are issued as JWTs, with Google OAuth through Passport.js as an alternative sign-in path for staff. Every protected route and socket event re-checks the role server-side; the interface hides what a role cannot do purely as a courtesy.

Redis absorbs the read-heavy paths — menu, stock levels, session lookups — so that a dinner rush does not translate directly into database load.

Stripe covers international cards; Safepay covers domestic Pakistani rails. Both sit behind one internal payments interface, so the ordering flow neither knows nor cares which processor settles a given transaction.

Subscription billing for the restaurants themselves runs through the same abstraction, which meant the recurring-revenue path did not require a second integration.