What two years of running Red Lantern actually taught me
Everyone assumes a cloud kitchen is the easy version of a restaurant — no dining room, no front-of-house, no one to impress in real time. What nobody tells you is that you lose the thing that usually saves a bad night: the chance to charm someone through it. In a dining room, a slow ticket becomes a story the server tells. In a cloud kitchen, a slow ticket is just a cold plate and a one-star review.
Running Red Lantern for two years rewired how I think about a dish before it even hits the pan. Every recipe had to survive a second life — a box, a scooter ride, twenty minutes of steam trapped under a lid — and still taste like it was meant to be eaten that way. Momos, it turns out, are forgiving. Fried rice is not. I learned this the hard way, more than once.
The other thing nobody warns you about is how much of "cooking" is actually logistics. Vendor calls at 7am. Knowing exactly how much coriander survives a Kalimpong monsoon before it turns to soup. Costing a dish down to the gram because margins on delivery food are thinner than anyone wants to admit. I came out the other side a better cook, but an even better operator — and I don't think you get that second part without running the whole thing yourself, badly, for a while first.
— Prajwal