At a community event, our founder Varesh was struck by how few healthy options there were for children. A passionate cook with deep roots in traditional culinary practice, he did the obvious thing: he started cooking. Every week he prepared wholesome meals from scratch, and before long other parents were doing the same.
It worked — and that was exactly the problem. Four hours in the kitchen every Saturday made the limits plain. Care doesn't scale. Every additional family meant another pair of hands, another weekend, another person who had to already know how to cook well. The robotics engineer in him couldn't leave the question alone: what if healthy cooking could be automated?
The bottleneck was never the recipe. It was the number of hands that could execute it.
That question became the seed of Kitchenoid. Varesh brought two decades of automation work from Amazon Robotics, GoogleX–Mineral.ai, and Meta; Srikant brought the discipline of a Ph.D. economist who had run multi-million-dollar programs and knew how to test whether an idea survives contact with real-world economics; Arun brought twenty years of building distributed, mission-critical systems for millions of daily users. A personal mission became a shared one.
The gap we kept finding
As the three of us went deeper, we kept running into the same wall. The products on the market didn't offer end-to-end autonomy across the spaces a real kitchen occupies. Most automated one station — a fryer, a wok, a single arm — and left the rest of the kitchen to people. Cleaning, prep, portioning, plating, and reset stayed manual, so the promised savings never materialized.
Just as importantly, almost none of them took on the hardest problems in the kitchen at scale. The systems that did solve something genuinely difficult solved it at an extremely small scale — one dish, one format, a demo kitchen — and fell apart when asked to run a full menu, through a dinner rush, every day, in more than one location.
We set out to address all of it in BotKitchen: the full kitchen journey — clean, cut, cook, serve — orchestrated as one continuous cycle by Kitchen OS, with robots of every kind working together under a single brain. We deliberately went after the hardest cases first — dishes from Japanese, Korean, Thai, Vietnamese, Chinese, Indian, Mediterranean, and Mexican kitchens, which demand precision, exact pan temperatures, and timing that leaves no room to fake it. Solve those, and the rest of the world's recipes come within reach.
That is still the standard we hold ourselves to — from a degree of pan temperature to an extra second of heat. It's what makes autonomy trustworthy, and it's why a recipe perfected once by one chef can be cooked with care for thousands.