The Rise of Cloud Kitchens in the UK Curry Sector

A cloud kitchen has no dining room, no front-of-house team and often no sign on the street. It exists to cook food for delivery, and nothing else. For the curry sector this model has grown quickly, because curry travels well, delivery demand is deep, and the cost of running a traditional restaurant has become punishing. But the economics only work if you understand exactly where the money leaks out.

Why curry suits the delivery-only model

Curry is close to the ideal delivery food. A sauce-based dish holds its temperature in a sealed container, survives twenty minutes in a rider's bag without collapsing, and often tastes as good, or better, reheated the next day. There is no delicate plating to ruin and no soufflé to sink. That resilience is why curry houses were doing a brisk delivery trade long before apps existed, and why they adapted to the cloud-kitchen format faster than many other cuisines.

The economics: what you save and what you spend

The appeal is obvious on the cost side. A cloud kitchen strips out the most expensive parts of a restaurant: prime high-street rent, the fit-out of a dining room, and the wage bill of waiting staff. A unit on a cheaper industrial estate or in a shared commissary building costs a fraction of a town-centre restaurant, and the whole operation can run with a small kitchen brigade.

But the savings are offset by a new set of costs that a dine-in restaurant never faces at the same scale:

• Aggregator commission, the percentage taken by delivery platforms on every order, which can consume a large slice of the headline price
• Packaging, which for curry is significant: leak-proof containers, separate pots for rice, breads and sauces, and secure sealing all add up per order
• Marketing spend inside the apps to stay visible in a crowded listing where you have no passing footfall to fall back on

The uncomfortable truth is that a delivery-only kitchen can be busy and still lose money if commission and packaging are not controlled. Profitability lives in the detail of the per-order maths, not in the volume alone.

Running several brands from one kitchen

The most distinctive feature of the cloud model is the virtual brand. A single kitchen can list on delivery apps under several different names, each targeting a different customer: a traditional curry house, a biryani specialist, a street-food snack brand, a healthy grilled-protein concept. They share the same tandoor, the same base gravies and the same team, but present as entirely separate businesses to the diner scrolling the app.

This lets an operator capture demand they would otherwise miss. Someone searching for biryani may never click a general curry house, but will order from a brand that appears to do nothing else. The kitchen behind both is identical. Done carefully, this multiplies revenue from the same fixed cost. Done carelessly, it confuses the kitchen, muddles food quality across too many menus, and produces inconsistent orders that sink all the brands at once.

Packaging is a make-or-break detail

For curry, packaging is not an afterthought; it is central to the product. A gravy that leaks in transit turns a good meal into a refund and a one-star review. Rice that steams itself soggy in a sealed hot container arrives ruined. The operators who succeed invest in ventilated containers where needed, keep wet and dry elements separate, pack breads so they do not sweat, and seal everything so the customer can see it has not been tampered with. Sustainable packaging is increasingly expected too, and it is a visible signal of quality that customers notice.

The dependence problem

The strategic risk of the cloud model is dependence on the platforms. With no dining room and no direct footfall, the aggregator sits between the kitchen and its customers, owns the relationship, sets the commission and controls the ranking. If a platform raises its rates or changes its algorithm, the kitchen has little leverage. The strongest cloud operators actively build a direct channel alongside the apps: their own ordering website, a loyalty scheme, and repeat customers who order direct at a lower commission. That direct relationship is what turns a fragile app-dependent kitchen into a durable business.

Is it right for every operator?

A cloud kitchen is not a cheaper version of a restaurant; it is a different business with a different skill set. It rewards operators who are disciplined about per-order costs, comfortable with data and app marketing, and willing to obsess over packaging and consistency. It suits those testing a new concept without the risk of a full restaurant lease, and established restaurants wanting to serve delivery demand without clogging their dining-room kitchen. It does not suit anyone hoping delivery volume alone will paper over thin margins. For the curry sector, where the food is made for travel and demand runs deep, the cloud kitchen is a genuine opportunity, but only for those who treat the economics with the same seriousness as the cooking.