Reliable control for cleaner, smarter kitchens.
Dependable equipment logic, repeatable cleaning cycles, clear operator controls, and service access built around the realities of working kitchens.
Consistent bottle sanitation, cycle after cycle.
A dedicated bottle-cleaning system with configurable sequencing, controlled injection, rinse discipline, safe stop behavior, and service visibility.
Disciplined cleaning control for fresh food.
The KitchenKontrol foundation adapted for vegetable and fruit cleaning applications, with profile-driven operation and serviceable machine logic.
One control foundation. Multiple machines.
Cycle sequencing, machine profiles, timing, relay assignments, diagnostics, event logs, notifications, and protected technician configuration in one structured platform.
Working-kitchen simplicity backed by professional control architecture.
KitchenKontrol separates daily operation from protected technical configuration. Clear controls stay visible at the machine. Deeper settings, diagnostics, and service records stay available where qualified work happens.
Small-business operators
Simple Start, Pause, and Stop controls. Visible cycle, step, status, and remaining time. No need to interpret controller logic during daily production.
Technicians
Timing profiles, diagnostic outputs, machine identity, service records, network status, clock status, and controlled test functions support faster problem isolation.
Equipment builders
Configurable profiles, output mapping, sequence modules, interface layers, and persistent settings support different machine designs without sacrificing control discipline.
Purpose-built applications on a shared automation foundation.
Each product carries a clear operational identity. Shared control architecture preserves service consistency, configuration discipline, and future expansion.
BottleMaster
Repeatable bottle-cleaning and sanitation cycles with configurable profiles, controlled injection, dedicated rinsing, safe drain behavior, and visible completion.
- Configurable cycle count
- Injection-cycle selection
- Sanitizer dwell support
- Service and event visibility
VeggieMaster
KitchenKontrol sequencing adapted to vegetable and fruit cleaning, with machine-specific timing, controlled fluid stages, operator clarity, and technician access.
- Fresh-food cleaning profiles
- Controlled stage timing
- Clear machine feedback
- Builder-configurable architecture
KitchenKontrol Software
The sequencing, configuration, diagnostics, logging, identity, clock, networking, and notification layer behind the product family.
- Operator and technician interfaces
- Protected persistent settings
- Event logging and notifications
- Reusable machine profiles
Dedicated sanitation control with configurable cycle discipline.
BottleMaster executes a defined cleaning sequence while preserving a clear separation between operator action and technician configuration.
Fresh-food cleaning without sacrificing operational clarity.
VeggieMaster extends the KitchenKontrol control model into vegetable and fruit cleaning applications. Machine behavior can be adapted around produce handling, cleaning stages, timing, and equipment design.
The shared control foundation behind every machine.
Current BottleMaster v1.10 architecture demonstrates the platform direction: machine sequencing, persistent profiles, local network interfaces, time-aware service records, and notification support.
OperatorMachine controlImmediate machine awareness
Mode, cycle, step, remaining time, total-left, network status, clock status, machine identity, and notification status stay visible alongside Start, Pause, and confirmed Stop controls.
Traceable operating history
RTC-stamped events can capture boot, run, pause, resume, stop, completion, web commands, and service configuration changes with mode, cycle, step, time, and machine identity.
Depth where qualified service needs it
Timing, profile rules, identity, software fields, clock, credentials, lifetime data, diagnostics, and notification settings remain separated from ordinary operation.
Cycle sequencing
Defined states, step transitions, pause/resume behavior, stop routines, completion logic, and optional dwell phases.
Machine profiles
Persistent cycle counts, injection masks, step timing, auxiliary timing, and machine identity values.
Output control
Relay and pin assignments, equipment outputs, step indicators, completion signals, and opposing-command interlocks.
Diagnostics
Runtime status, clock health, network status, service boundaries, output verification, and equipment troubleshooting support.
Event logging
Time-stamped machine and service events, newest-first history, paging, identity context, and controlled log clearing.
Notifications
Optional ntfy publishing with selectable alert categories, test notification, topic configuration, and queued events.
Safety behavior belongs inside the sequence—not in a note beside it.
KitchenKontrol architecture treats pause, stop, drain control, dosing, pump control, and completion as explicit machine states with defined output rules.
Pause means outputs off
Countdown freezes; active process outputs de-energize; Start resumes the same cycle and step.
Stop overrides normal logic
Run and pause logic yield immediately to a controlled stop-open and stop-rinse routine.
Drain commands interlock
Open and close commands cannot energize together.
No cleaner during stop-rinse
Dosing remains disabled while the drain stays open and rinse water clears the basin.
No pump during stop-rinse
Main circulation remains off during the stop routine.
Completion is unambiguous
The buzzer pattern belongs only to successful completion, never to stop or fault states.
BottleMaster v1.10 demonstrates a complete local control stack.
Specific hardware and assignments vary by machine. Current implementation establishes the reusable operating model behind KitchenKontrol.
A repeatable path from machine concept to supported operation.
Configuration depth stays structured around equipment needs, test stages, documented acceptance, and service continuity.
Define the machine
Lock operating purpose, loads, valves, pumps, actuators, indicators, stop behavior, and required operator feedback.
Build the profile
Assign cycle count, step timing, injection rules, dwell, output mapping, identity, clock, network, and notification preferences.
Validate in stages
Simulation, bench testing, low-voltage verification, valve and pump testing, stop-rinse acceptance, and final wet testing.
Support the field
Protected configuration, event history, diagnostic views, test functions, machine identity, and recorded final values.
Clear enough for daily operation. Structured enough for technical responsibility.
Platform clarity before deployment.
KitchenKontrol is a product-family control foundation, not a generic kitchen app and not a single hardcoded machine.
Open a project inquiryNo. KitchenKontrol is the shared automation platform. BottleMaster and VeggieMaster are application-specific products built on that foundation.
Yes. Machine profiles can carry cycle count, timing, injection rules, dwell, outputs, identity, and service settings while preserving a consistent control model.
Normal sequencing cancels. Process outputs shut down, the drain opens, a rinse occurs with the drain open, and the machine remains stopped.
No. Current v1.10 logic forces the final configured cycle to remain water-only.
Core sequencing and local machine control remain on the equipment. Local Ethernet interfaces support operation and service; optional notifications use the configured network path.
Daily controls remain simple. Protected service configuration is reserved for qualified technical access and machine commissioning.
Practical equipment meets professional automation.
Bottle cleaning, fresh-food cleaning, and future equipment profiles can share one disciplined control foundation without losing operational clarity.