DoorDash vertical integration threatens CloudKitchens
CloudKitchens
DoorDash is turning from a neutral traffic source into a vertically integrated operator that can own the customer, run the kitchen, and increasingly automate fulfillment. That matters because CloudKitchens mostly rents space and software to independent restaurant tenants, while DoorDash can decide which brands get featured in its app, staff the kitchen itself, and lower labor and delivery costs inside one managed system.
-
DoorDash Kitchens started as shared delivery real estate in Redwood City, then expanded into a full service model in which DoorDash handles hiring, prep, equipment, and ingredients for restaurant partners. That moves it much closer to operating the restaurant workflow, not just delivering the food.
-
The managed kitchen model is strongest where demand generation lives inside the same app that controls checkout and dispatch. A tenant in CloudKitchens still depends on DoorDash or Uber Eats for orders, but a DoorDash kitchen partner can be placed directly in front of DoorDash demand inside branded food hall locations in Brooklyn and the Bay Area.
-
Deliveroo offers a useful precedent. It built Editions to more than 300 kitchens globally, then pulled back when the economics got harder, including shutting its remaining Singapore cloud kitchens in 2024 and later exiting the market in March 2026. The lesson is that vertical control is powerful, but only in dense markets where order volume can cover rent and labor.
The next phase is tighter control over fulfillment economics. As DoorDash adds more merchant software and autonomous delivery tools like Dot, the advantage shifts toward platforms that can route an order from app discovery to kitchen production to doorstep delivery inside one stack. That raises the pressure on CloudKitchens to remain the best neutral infrastructure layer for brands that do not want platform dependence.