Sample update
See how a page stays current.
A simple walkthrough. A restaurant changes an item, a promo, and today’s hours. Guests see the current page. The team gets a record.
Example request
Before
Mark the burger sold out. Add happy hour from 5 to 7. Close at 9 tonight.
Record
waiting
Click “Show the update.” The record appears here.
Harbour Deli
Guest page
Open today · 11–10
A current page guests can trust.
Published to
getkitch.app/r/harbour-deli
Menu
Smoked trout toast
Dill, pickled shallot
$18
Burger
Available
$22
Promo
Happy hour, 5–7.
Go deeper · the full product loop
Update the page. Run the night. Keep the record.
It’s 4:47 PM. You’re 86’d on burgers. A regular asks for happy hour. Tonight closes early. Tell Kitch in one line. The guest page is live in seconds, the team is told, the change is logged — and one tap rolls any of it back.
~45 sec
from prompt to live page
0%
take-rate on your orders, forever
Every change
versioned · undoable · yours
Kitch · brain ready
waiting on you
Click a scenario below. Watch the prompt type. Watch the page change. Watch the log fill.
- 01Run a Friday service update
- 02Push a staff training card
- 03Roll the first one back
Try a scenario
no runs yet
Harbour Deli
· Torontolive
Open today · 11–10
A page that keeps up with the kitchen.
Published to
getkitch.app/r/harbour-deli
+ harbourdeli.com · verified
Menu
Smoked trout toast
Dill, pickled shallot
$18
Burger
House grind, aged cheddar
$22
Latte
Espresso, whole milk
$6
Action log · version history
empty
Run a scenario. Every field-level change appears here, with what it was before, who changed it, and a one-tap rollback.
writes to your own database
your data · your call
What you just saw
One prompt walks three tiers — and writes a record on the way back.
Tier 1
The page
Your domain. Your brand. The link guests trust. Updated by chat, not by ticket.
Tier 2
The dashboard
Menu, hours, promos, knowledge cards, staff invites. Every mutation versioned with full history.
Tier 3
The brain
On-prem llama.cpp inference. Your prompts never train someone else’s model. Confidence scored, flaggable, undoable.
The same architecture runs in production today. The demo on this page is a faithful simulation — the prompts hit the same shape of API, the log writes the same records, and the rollback uses the same version history that lives behind your dashboard.
What ships in the demo
Live today. The next layers are on the way.
Live in this demo
Guest page
— menus, hours, promos, QR, contact, location
Chat updates
— type the change in the words you’d say it
Action log + rollback
— every field change recorded · one tap to revert
Staff knowledge
— training cards by role · allergen flags · attendance
Custom domain
— your URL, verified · we handle DNS
Building next
Team handoff
— line, floor, and owner working from one source
POS read-integration
— Kitch knows what’s selling and what’s running low
Wastage estimator
— a real number for what didn’t make it to the plate
Supplier flag
— the order goes out before you’re 86’d
Stop demoing. Start running it.
Your first page can be live by the next service.
— Live page on getkitch.app and your own domain
— Chat updates for menu, hours, promos, knowledge
— Action log + version history from day one
— First setup included · no take-rate, ever