What Is a Cloud Kitchen? Definition, Concept and Practical Guide

Cloud kitchen explained simply: what lies behind ghost kitchens and dark kitchens? Definition, differences, business model.

Cloud kitchen explained simply – in 3 points

  1. No dining area: A cloud kitchen produces exclusively for delivery and collection – no service, no tables, no walk-in customers.
  2. 100% digital: Orders come via delivery platforms (Lieferando, Uber Eats, Wolt) or a dedicated online shop.
  3. Low fixed costs: By eliminating a dining area, service staff and prime locations, both start-up investment and running costs fall considerably.

The delivery-only model is one of the fastest-growing trends in hospitality. But for whom does a restaurant without a dining area actually make sense? And what operational challenges await? This guide gives you a practical overview – from definition and business model through to the concrete steps for getting started.

1. Definition: what does cloud kitchen mean?

The term “cloud kitchen” describes a commercial kitchen that produces exclusively for the delivery and collection of food. There is no dining area, no tables, no service. All customer interaction runs digitally – via delivery platforms such as Lieferando, Uber Eats or Wolt, or via a dedicated online shop.

The name follows the logic of “cloud computing”: the infrastructure exists, but the end customer never sees it. Just as you do not visit a server room when you use an app, no guest enters a cloud kitchen either. Internationally, the terms ghost kitchen, dark kitchen, virtual kitchen and delivery-only kitchen are also common.

Simply explained: Imagine a restaurant that consists only of a kitchen. No entrance for guests, no waiter, no menu on the table. Instead: an efficient production facility that cooks, packages and delivers food to the customer via courier.

2. Ghost kitchen, dark kitchen, virtual kitchen – the differences

The terms are often used interchangeably in everyday language but differ in nuance:

TermFocus / NuanceTypical scenario
Cloud Kitchen Umbrella term for kitchen-based delivery-only concepts Provider supplies kitchen infrastructure (Kitchen as a Service); multiple brands produce there
Ghost Kitchen Emphasises invisibility – no signage, no public footfall Independent operation in a commercial estate, delivers under its own brand name
Dark Kitchen Mainly used in Europe and the UK; substantively identical to ghost kitchen Deliveroo Editions, former Gorillas kitchens
Virtual Kitchen Emphasises the brand: a virtual restaurant exists only as an online presence Existing restaurant kitchen operates a second brand solely for delivery
Virtual Brand Pure brand without its own kitchen – production by partners Food influencer launches burger brand; production in a rented kitchen

3. The cloud kitchen business model

The business model of a delivery-only restaurant differs fundamentally from the classic hospitality approach. Here are the central building blocks:

Revenue streams

  • Delivery platforms: Uber Eats, Lieferando, Wolt – reach in exchange for commission (typically 15–30%)
  • Own online shop: Higher margin, but requires building your own customer base
  • Catering & B2B: Lunch deliveries for offices, event catering as an additional revenue stream
  • Multi-brand strategy: One kitchen, multiple virtual brands – e.g. bowls, burgers and poke from the same production

Cost structure overview

Cost blockTraditional restaurantDelivery-only kitchen
Rent / Space Large (dining area + kitchen + storage) Small (kitchen + storage only)
Staff Kitchen + service + host Kitchen + packaging only
Start-up investment €80,000–500,000+ €20,000–80,000
Cost of goods 28–35% 26–33%
Platform commission 0% (direct business) 15–30% (primary channel)
Marketing Walk-ins + local 100% digital (SEO, paid, social)

Multi-brand: one kitchen, many brands

One of the most powerful concepts in the food delivery business is the multi-brand strategy. A single kitchen operates several virtual brands in parallel, sharing infrastructure, staff and storage. Each brand has its own branding, its own menu and its own platform profile.

The model is efficient – but places high demands on stock management. When three brands work from the same storeroom, consumption per brand must be clearly attributable. Otherwise, the multi-brand strategy quickly becomes a costing problem.

4. Delivery-only vs. traditional restaurant

Where delivery-only concepts excel

  • Faster launch: Operational in weeks rather than months – no elaborate dining-area fit-out required
  • Lower fixed costs: Less space, fewer staff, no prime location needed
  • Scalability: New locations or brands can be added comparatively quickly
  • Data-driven from day one: Every order is digital – analysis and optimisation are possible immediately

Where traditional restaurants are stronger

  • Guest experience: Atmosphere and personal contact cannot be replaced digitally
  • Brand loyalty: Regulars are easier to build through personal relationships
  • Higher margins: No commission deducted by delivery platforms; strong beverage revenue (often 70%+ margin)
  • Flexibility with shrinkage: Daily specials from leftover stock, spontaneous recommendations – hardly possible in delivery

Hybrid models as the future: Many successful businesses combine both worlds: a traditional restaurant with a dining area plus one or more virtual brands that generate additional revenue from the same kitchen – especially outside peak hours.

5. Advantages and disadvantages of a cloud kitchen

Advantages

  • Low start-up investment: €20,000–80,000 vs. €100,000–500,000+ for a restaurant without a dining area
  • Location flexibility: Commercial estates, backyard kitchens or kitchen-as-a-service spaces – no prime-location pressure
  • Rapid testing: New dishes, brands or concepts can be launched and validated in days
  • Production focus: No dining-area management, no service training – full focus on the kitchen and quality

Disadvantages

  • Platform dependency: Delivery platforms take 15–30% commission and control the customer relationship
  • No dining experience: Emotional customer loyalty is considerably harder without personal contact
  • Quality loss during transport: Not every dish survives 20–30 minutes of delivery time without deterioration
  • Packaging costs: Sustainable packaging is expensive but indispensable for brand perception
  • Precise stock management required: Without a dining area as a buffer (daily specials, spontaneous recommendations), stock must be exact

6. How to start a cloud kitchen: step by step

Step 1: Define your concept and target market

What do you want to offer? For whom? Delivery customers order differently from dine-in guests. Proven delivery concepts include bowls, burgers, wraps, curry and poke – dishes that package and transport well.

Step 2: Choose your kitchen model

  • Own kitchen: Rent and fit out a commercial space – full control, higher investment
  • Kitchen as a service: Shared kitchen with shared infrastructure – low entry costs, less flexibility
  • Repurpose an existing kitchen: Use your restaurant outside peak hours or a catering kitchen

Step 3: Permits and hygiene

Even a restaurant without a dining area is subject to the same food-hygiene regulations: HACCP concept, infection-protection briefing (§43), business registration and, where applicable, inspection by the health authority. Allow 4–8 weeks for this.

Step 4: Set up delivery platforms

Register with at least two platforms for reach. Invest in professional food photography – in delivery, customers buy with their eyes before they order.

Step 5: Optimise the menu for delivery

Test which dishes still look and taste good after 20–30 minutes of transport. Reduce to your strongest 15–20 items – less is almost always more in delivery.

Step 6: Set up stock management and processes

Before going live you need clear processes for purchasing, storage and inventory. This is the point where many delivery-only concepts fail: they launch on gut feeling rather than data. Set up structured stock management from the outset – whether via a specialist inventory tool, an inventory management system or at least a well-maintained spreadsheet.

Quick-start tip: Start lean: one brand, 15 dishes, one delivery partner. Only once kitchen, storage, ordering and fulfilment are running smoothly do you scale to additional brands and platforms.

7. Cost of goods and stock management: the decisive success factor

If there is one area that determines success or failure in delivery-only concepts, it is cost of goods. The reason: without beverage revenue and without the option to sell leftover stock spontaneously as a daily special, every lost euro in purchasing hits the margin directly.

The specific challenges

  • Multiple brands, one storeroom: Without clean allocation, costing per brand is impossible
  • Open containers everywhere: Opened sauces, half packs, open spice containers – not easily scannable
  • Time pressure: Between the lunch peak and evening production, often only 30–45 minutes remain for counting
  • Changing staff: The inventory system must be intuitive enough for anyone to operate
  • Multiple storage locations: Fridge, dry store, prep station, packaging store – everything must be mapped

Cost-of-goods formula for delivery-only businesses

Cost of goods (%) = (opening stock + purchases – closing stock) ÷ revenue × 100

Clean inventory data is the foundation for opening and closing stock – without it, the formula is worthless.

Typical delivery-only businesses target a cost of goods of 26–32%. Through standardisation of dishes, more precise control is possible than in traditional restaurants – but only with regular, reliable inventory.

Which tools help with stock management?

The market offers various approaches to food cost control and inventory in hospitality:

  • Specialist inventory tools: Focus on F&B reality: open containers, slider input, key-date workflows. Examples: BarBrain, Supy, Apicbase
  • Inventory management systems: More comprehensive solutions with purchasing, recipe management and costing. Examples: MarketMan, Lightspeed Restaurant
  • POS-integrated solutions: POS systems with an inventory module – often less deep, but seamlessly integrated
  • Excel / Google Sheets: Feasible for the absolute start, but barely maintainable beyond 50+ items
Common mistake: Many founders invest heavily in platform presence and marketing but economise on stock management. The result: revenue grows, margin does not – because nobody knows where the costs actually lie.

8. Market data: figures, growth and trends

The market for delivery-only concepts is growing rapidly – driven by changing consumer behaviour, rising delivery demand and the search for cost-efficient hospitality models.

Global market size

The global market was estimated at around USD 73–78 billion in 2024 and is expected to grow to over USD 140–190 billion by the early 2030s – depending on the source, with annual growth rates (CAGR) of 9.5–12%.

Sources: Grand View Research (USD 73.2 bn, 2024), IMARC Group (USD 78.1 bn, 2024), Market Data Forecast (USD 74.2 bn, 2024)

Market in Germany and Europe

Europe is a growing market with regional fragmentation. According to several analysts, Germany is the fastest-growing European market for delivery-only concepts, with a market volume of around USD 3.9 billion (2025) and a projected tripling to approx. USD 10.1 billion by 2034.

Sources: IMARC Group – Germany Cloud Kitchen Market (USD 3.9 bn, 2025); Virtue Market Research – Europe Cloud Kitchen Market (DE with 20% market share, fastest growth)

Trends shaping the market

  • Hybrid models: Restaurants supplement their offering with virtual brands from the existing kitchen
  • Kitchen pods: Modular kitchen units that can be set up quickly – the fastest-growing sub-segment
  • Sustainability: Packaging and delivery logistics are becoming a differentiating factor for brand perception
  • Data as a competitive advantage: Businesses that manage cost of goods, order patterns and food costs in a data-driven way scale more profitably

Consolidation: Major players such as Kitopi, Rebel Foods and CloudKitchens (Travis Kalanick) are increasingly dominating the infrastructure

Conclusion: cloud kitchens are more than a trend

The cloud kitchen concept goes far beyond a mere delivery kitchen. It is a fundamentally different business model for hospitality – leaner, more data-driven and more scalable than the traditional approach. But it comes with its own challenges: platform dependency, lack of customer contact and the need to manage cost of goods and stock precisely.

Anyone who wants to operate a cloud kitchen successfully needs, alongside a strong concept and good food, above all one thing: control over the numbers. And that starts with clean, regular inventory – the foundation for costing, purchasing and profitability.

Book your demo now!

Want to improve your inventory? Then it’s time to book a free demo.

Eine Linie im Hintergrund für einen Call-To-Action für die schnellste Inventur im Food & Beverage Bereich.

Wirf einen Blick auf unsere Artikel