Our story

It started with a child's lunch.

Necessity often sparks innovation. For Kitchenoid, it began with something as simple, and as vital, as what kids were being handed to eat.

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. 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, on one dish, one format, a demo kitchen, then 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 through cut, cook and 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.

Founders

The people building it.

Portrait of Varesh Rangan

Varesh Rangan

Founder & CEO

The cook in the founding team is also the roboticist. Varesh spent two decades on automation at Amazon Robotics, Google X and Meta, where he took 70% of the cost out of one fulfilment programme and 90% of the chemicals out of an agricultural imaging line. He invented BotKitchen, and the recipes it ran first were the ones he had been cooking on Saturdays.

LinkedIn ↗
Portrait of Arun Chandrasekaran

Arun Chandrasekaran

Founder & CTO

Arun builds systems that are not allowed to fail. At NEC and JP Morgan he shipped national identity infrastructure clearing millions of biometric matches an hour, holds seven patents in vision and distributed systems, and has run engineering organisations of sixty and up. Kitchen OS is his architecture.

LinkedIn ↗
Portrait of Dr. Srikant Devaraj

Dr. Srikant Devaraj

Founder & CRO/CFO

Srikant's research on automation and employment was cited in presidential debates and became the basis of a Senate bill. A PhD economist, he went on to build a health-technology division from nothing to more than $20M in contracts. He is the one who asks whether the unit economics hold before anyone gets excited.

LinkedIn ↗

Come build the kitchen that runs itself.

That Saturday problem is still the one we are solving, now at commercial scale. If it is a problem you want to work on, or one you have in your own kitchens, we would like to hear from you.

Get in touch