Restaurant

How to Start a Cloud Kitchen in India (2026): Licences, Costs and the First 90 Days

FSSAI and GST, kitchen setup costs, aggregator onboarding, menu engineering and the food-cost discipline that decides survival — a practical launch guide.

The cloud kitchen (or dark kitchen) model has exploded across India because it strips a restaurant down to its most profitable core: the food and the delivery, with none of the rent-heavy dine-in overhead. But “lower overhead” doesn't mean “easy money.” The margins are thin, the aggregator commissions are steep, and the first 90 days decide whether you build a sustainable brand or quietly shut down. Here's a practical 2026 guide to licences, costs and surviving the crucial launch window.

Why cloud kitchens work — and where they trap you

A cloud kitchen has no dining area, no front-of-house staff, and can run from a modest commercial space in a cheaper locality. That slashes your two biggest costs: rent and service staff. In return, you live and die by online orders — which means the delivery aggregators (Swiggy, Zomato) become both your lifeline and your biggest cost, taking a significant commission on every order. The whole game is engineering a menu and operation that stays profitable after those commissions.

The licences you need

A cloud kitchen still serves food to the public, so the compliance burden is real:

• FSSAI licence — mandatory; the aggregators will not list you without it.
• GST registration — required for listing on delivery platforms.
• Local municipal / trade licence — for operating the commercial kitchen.
• Fire safety NOC — depending on premises and local rules.
• Shop & Establishment registration — if you employ staff.

The good news: without dine-in, you skip the eating house and (usually) liquor licences, which are the most painful. Get FSSAI and GST sorted first, because your aggregator onboarding depends on them.

What it costs to launch

Cloud kitchens are far cheaper to start than dine-in restaurants, but the buckets still add up:

• Kitchen space deposit and rent — smaller and cheaper than a prime dine-in location.
• Equipment — commercial cooking, refrigeration and storage.
• Packaging — a real recurring cost that directly eats margin; design it lean.
• Initial inventory — raw materials for your menu.
• Aggregator onboarding and marketing — listing, photography, and the ad spend needed to gain early visibility.
• Working capital — to survive the ramp-up before order volume stabilises.

Surviving the first 90 days

The launch window is brutal because you start with zero ratings and zero visibility. What separates survivors:

Nail a tight, profitable menu

Fewer dishes, shared ingredients, and items that travel well. A sprawling menu kills your food cost and your kitchen speed.

Protect your ratings obsessively

Early reviews are everything on the aggregators. Consistent quality, correct orders and good packaging in month one compound into visibility for months after.

Know your true unit economics

For every dish, you must know its cost after ingredients, packaging and commission. If you don't, you can be “busy” and still losing money on every order. Recipe-based stock control and delivery reconciliation are essential — see our guide on cloud kitchen profitability.

Frequently asked questions

Is a cloud kitchen cheaper than a restaurant?

Yes, to start — no dine-in space or front-of-house staff means much lower rent and salaries. But aggregator commissions and packaging eat into the savings, so margins are thin.

Which licences does a cloud kitchen need in India?

At minimum an FSSAI licence and GST registration (both required for aggregator listing), plus local trade licence and fire NOC as applicable.

How do cloud kitchens make a profit with high commissions?

By engineering a menu with strong margins after commission, controlling food cost with recipe-based stock, minimising packaging cost, and driving repeat orders to reduce dependence on paid visibility.

Can I run multiple brands from one cloud kitchen?

Yes — many operators run several “virtual brands” from one kitchen to maximise orders per rupee of rent, as long as your system can keep each brand's menu, stock and reconciliation separate.

Launch lean, run tight

BecozAI's restaurant OS gives cloud kitchens POS and online-order management, recipe-based stock control with real food-cost margins, and Swiggy/Zomato reconciliation — so you always know your true profit per order. Read more on restaurant systems, then start free for six months and give your cloud kitchen the numbers it needs to survive.