breweryfood.fyiCULINARY PARENT · PROTOTYPE
NO KITCHEN REQUIRED

A taproom with no kitchenstill has a kitchen nearby.

Most breweries cannot cook and most good food is three minutes away. This closes that gap with a card on the table instead of a build-out. People who eat stay for another beer, which is the only argument the taproom actually needs.

What works today

The table layerOne hostname per taproom, one address per table. Scanned from a card, never typed. Free certificate, one level deep, noindexLive
OfflineThe menu survives the tower. Loaded once it keeps working, which matters more here than any feature on the listLive
The orderHanded to the shop on the phone or POS it already answers. No account for the shop, no app for the guest, and no money moving through usSoon
Menu intakeA shop sends a photo of a menu or a text and it becomes rows. This is the part that makes small rooms worth serving at allSoon
PaymentDeliberately not built. Taking a slice of a thin pizza margin makes us the thing shops already resent. The room pays, the kitchen does notSoon

TRY IT

Scan a table, or just tap

This is a working demo of the table layer — a fictional taproom, a real menu structure, a real order path. Load it once, then put your phone in airplane mode and keep using it. That is the entire product at a venue where four thousand people are on one tower.

Open table 12 →

Nothing is charged and no order is placed. The demo stops at the point where a real order would be handed to the shop.

Back of house

Back of houseRooms, kitchens, menus and what each table pulled. Members only.
Not yet
Workboardthe live estate boardNot yet Arcsession record + handoffNot yet The Buscadre comms boardNot yet Membershiproster + accessNot yet

The rest of the works