This page stays grounded in what ships today: the offline crew app, admin dashboards, builder, AI help desk, and optional telemetry. Use the answers below to understand how Kitchen Toolkit works in pilots and day-to-day operations.
Sales, pilots, and tenant access are handled for business, institutional, and professional kitchen operators. Current hardware deployments may include pilot, evaluation, or pre-certification units for supervised indoor use until released otherwise in writing.
It’s the all-in-one, hosted playbook for your kitchens: the crew app, manager dashboard, builder, AI helper, and optional sensors working together. Crews keep moving offline, chefs update menus without binders, managers can review completion history and exceptions, and alerts surface issues quickly.
See how it works →For the hosted offering, sign-up and rollout do not require a CLI, source repo access, or self-hosting. If you want your own email, push, or log-storage settings, you can configure them in the admin console with a few clicks.
Staff log tasks and temps without paper. Chefs update recipes once and everyone sees it. Managers spot gaps and export records quickly. Keeping allergens, expiry, and temperatures up to date can help teams reduce mistakes for guests.
Yes. The app caches each restaurant, saves everything locally, and automatically retries sync when connectivity returns. You can still download CSV to the device or email once you’re back online—built for basements and walk-ins.
Every log has a timestamp and device. Managers see missing temps and late tasks at a glance and can coach quickly. Push reminders and emails replace clipboard chasing, but customers decide whether those records are used only for workflow follow-up or for any person-specific accountability process.
Keep humans in the loop or let sensors handle temps. The system keeps checking fridge and freezer temperatures for you, queues readings during connection blips, and warns the right people if something gets too warm or cold, a battery is low, or a sensor stops checking in.
Kitchen Toolkit is designed to reduce paper, training friction, and avoidable spoilage risk. Crews use guided checklists and searchable recipes instead of binders, while waste and temperature charts help teams spot problems earlier. Optional hubs and nodes can reduce manual temperature rounds, and alerts call out drifting fridges/freezers sooner. Logs include timestamps and exportable device context so audits can move from manual fire drills to more structured review.
From the admin console, export temperature and waste logs as CSVs or email summaries in a few clicks. Each entry carries a timestamp and available device context for review, and retention can be tuned in settings so teams can assemble records faster when an audit or inspection asks for them.
You do. Kitchen Toolkit hosts the platform and isolates operational data by tenant. If you prefer, you can connect your own email or alert services for exports and notifications. Non-default tenant content requires admin or provisioned-device context, but Builder bundles are still Git-backed, so removing live content does not rewrite repository history.
The builder is an app that builds restaurant apps. Publish menus, recipes, allergens, and checklists in one click; the platform helps keep each location refreshed, including offline caches.
Kitchen Toolkit ships with a hosted assistant grounded in approved content and designed to guide onboarding, workflows, troubleshooting, and customer support. It uses the same account access controls as the rest of the platform, and an optional demo mode is available for pilots.
Yes. The builder lets you publish location-specific menus, checklists, and branding. Each restaurant’s bundle is cached separately for offline use so data stays scoped to that location.
Use the guided flasher to load firmware, mint secrets, and set the first network credentials. Once flashed and provisioned, the hub is typically ready for validation and handoff. If a Wi-Fi hub later loses Wi-Fi, or you clear saved credentials with a long BOOT hold, it comes back with its maintenance AP so you can join Hub-<device-id> and enter new Wi-Fi details at http://192.168.4.1 without reflashing. The admin console still shows heartbeats, labels, and secret state after that recovery step.
Open /admin and click 🛠 Manage Equipment. Use Heard But Unmapped for brand-new sensors, the hub-grouped smart sections for equipment that is already mapped, and Saved But Detached for equipment records you want to reattach later. Enter or update the equipment name and type, confirm the node and hub selection, then use the single Create & map or Save button for that row. Remove from this hub only removes one hub link, Detach node keeps the equipment record but unpairs the node, and the hub-local /nodes page is the same-LAN fallback when you need local recovery.
Step-by-step mapping guide →LoRa handles the local sensor-to-hub link through stainless and walls where Wi-Fi and BLE often drop. The hub can then use its own upstream path, including a dedicated LTE gateway when needed, so teams are not depending only on venue Wi-Fi for either in-kitchen coverage or cloud delivery. It still supports, rather than replaces, manual monitoring procedures.
Too-warm or too-cold equipment, additional escalated alerts for emergency fridge/freezer readings, low battery, and sensors that stop checking in can trigger push + email. Recipients come from the Alerts modal or your alert settings, and email may use your SMTP settings or a Kitchen Toolkit-managed pilot-stage outbound path depending on the feature and configuration. These are operational notifications, not a bulk marketing mailer, and alerts clear once readings recover.
No. Nodes use factory-calibrated probes and are meant to be set-and-forget in normal service. Kitchen Toolkit does not put them on a calendar schedule. If a node stays more than 0.7°C away from its rolling average for about 10 minutes, Node Status will flag it for verification so you can inspect placement and run the ice-bath routine only if needed. The normal field path is the PRG/BOOT menu: quick double-tap to open it, then select Calibration.
Verification steps →Quick double-tap the node’s PRG/BOOT button to open the on-device menu. A single tap cycles through the options and holding the button selects the highlighted item. That menu now includes Calibration, Turn off, and Exit. Turn off shuts down the OLED, radio, and scheduled transmissions until you press the RST button. If you only need an immediate reading for pairing, hold PRG/BOOT for about 800 ms outside the menu instead.
Node controls →Because those networks often depend on captive portals, expiring sessions, or IEEE 802.1X device authentication. Those controls assume a browser or managed-device enrollment step, which is a poor fit for unattended, headless monitoring hardware that needs to stay online continuously.
See the connectivity architecture →The preferred deployment uses a dedicated cellular gateway: a Teltonika RUT241 LTE router with a Hologram Hyper eUICC IoT SIM. The hub connects to that router over Ethernet, receives a private LAN address from DHCP, and sends telemetry to cloud endpoints over outbound HTTPS.
It removes login timeouts and network-policy surprises, while adding router-level watchdog and reconnect behavior. The multi-carrier IoT SIM can fall back to available networks when coverage varies, and the telemetry profile is lightweight enough that typical usage stays in the tens of MB per month.
No inbound ports are required. The router keeps the hub behind NAT, and the application model is outbound HTTPS to cloud services, so the device is not directly addressable from the public internet in the normal deployment model.
The Trust & Security overview provides a plain-language summary of data handling, risk considerations, and policy access without internal documentation.
Trust & security overview →We host Kitchen Toolkit for you. Your account’s data is isolated by default, and you can connect your own email or alert services if preferred so exports and notifications use your services. Admin access is intended to stay limited to users your organization authorizes, with session, CSRF, and tenant-scoping controls around the admin surfaces.
Retention timing is adjustable in the admin console. Export when auditors ask, or delete/shorten retention at any time—no CLI needed.
Current pilot hardware posture is supervised indoor evaluation, and some hardware may remain pre-certification or pre-production until explicitly released otherwise. Pricing, warranty scope, and liability terms are handled in the current legal docs and any signed pilot paperwork.
Kitchen Toolkit can record timestamps, device IDs, and related log metadata, so if you use it in a way that identifies workers or supports accountability reviews, your team may need its own employee notice or HR/labor process before rollout.
Employee monitoring guide →Terms of service, privacy, security, and data-handling policies are publicly available under the legal docs section, and the sign-up flow links to them directly. Security incidents are communicated to tenant contacts without undue delay and in line with applicable law, and the legal docs now include a standard DPA, transfer packet, and subprocessor schedule.
Legal docs →The user manual is a plain-language guide to the crew app, admin workflows, content updates, offline behavior, and telemetry options.
Open the user manual →Pricing is handled directly with the Kitchen Toolkit team. Quotes and pilots are scoped for business, institutional, and professional kitchen teams, with pilot hardware and rollout terms confirmed per deployment before expanding.
Support targets and escalation paths are shared during onboarding, with faster incident help during pilots.
Email liam@liambendix.com for onboarding, pilots, quotes, or urgent incidents tied to a business deployment. The FAQ and help desk stay open for frontline questions.