# MCA for cloud kitchens (detailed) > Cloud kitchens and virtual restaurants qualify for MCA funding against third-party-platform delivery revenue, typically $20K–$250K at 1.28–1.38 factor — platform-payout timing and brand concentration drive underwriting. Cloud kitchens (also called dark kitchens, virtual kitchens, or shared commissary kitchens) operate delivery-only restaurant brands without dine-in. Revenue flows almost entirely through DoorDash, Uber Eats, Grubhub, and increasingly direct-online-ordering channels. Funders treat cloud kitchens as a distinct MCA segment with platform-specific risks. **Typical funding ranges.** - Single-brand cloud kitchen ($25K–$70K monthly revenue): $15K–$60K advances at 1.32–1.38 factor over 6–10 months. - Multi-brand cloud kitchen (3–8 virtual brands from one kitchen, $70K–$200K monthly revenue): $60K–$180K advances at 1.28–1.36 factor over 8–12 months. - Multi-location cloud-kitchen operator ($200K+ monthly revenue): $180K–$400K advances at 1.24–1.32 factor over 10–14 months. **What underwriters look for.** First, the platform-payout pattern. DoorDash and Uber Eats hold revenue 4–7 days before payout. Funders verify deposit timing and consistency. Second, the brand and platform-rating concentration. A cloud kitchen with one brand at 4.8 stars on DoorDash is fragile if rating drops. Multi-brand operators diversify rating risk. Third, the platform-take-rate trajectory. DoorDash takes 15–30% commission; Uber Eats 15–30%; Grubhub 20–30%. Effective restaurant margin after platform fees is often 8–15%. Fourth, the commissary or facility lease structure. Many cloud kitchens operate from CloudKitchens (Travis Kalanick), Kitchen United, REEF, or independent commissary spaces. Lease terms and shared-facility dynamics matter. **Common uses.** - Equipment purchase (combi oven, fryer, refrigeration; $5K–$40K). - New virtual-brand launch (menu development, marketing, platform onboarding; $5K–$20K per brand). - Marketing for direct-online-ordering customer acquisition (reducing platform dependency). - Working capital during platform-payout-lag periods. - Multi-location expansion or commissary buildout. **What to watch out for.** Platform dependency is the existential risk. A cloud kitchen with 95% DoorDash revenue is at DoorDash's mercy — a rating dip, algorithm change, or contract dispute can collapse revenue in days. Platform payout timing creates NSF risk. MCA daily-ACH that hits before platform payout lands triggers NSFs. Brand fatigue cycles are short on delivery platforms. A "trending" virtual brand can fade in 90–180 days; operators need constant brand-development pipeline. Commissary-kitchen rent and shared-facility fees add fixed cost burden. CloudKitchens facilities run $3K–$12K monthly per kitchen. Stacking is common in cloud-kitchen MCA but dangerous — tight platform margins leave no room for elevated daily-ACH. **State considerations.** California, New York, Texas, Florida, and Illinois have highest cloud-kitchen density. Los Angeles, NYC, Miami, Chicago, and Houston have established cloud-kitchen ecosystems. California minimum-wage law (AB1228 fast-food $20/hr) affects cloud-kitchen labor cost. NYC commercial-rent burden affects margin. **APR-equivalent reality check.** A 1.34 factor over an 8-month term is roughly 75–85% APR. Compare to Toast Capital or Square Loans (if those POS systems used), restaurant-specialty SBA lenders, or equipment financing for kitchen capex. **Common confusions.** First, "Cloud kitchens are too platform-dependent for MCA." Partly true — single-platform operators are higher risk; multi-platform multi-brand operators are more stable. Second, "Ghost kitchen and cloud kitchen are the same." Loosely yes — terms are often used interchangeably. Some sources distinguish ghost kitchen (operator-owned facility) from cloud kitchen (third-party shared facility). Third, "Virtual brands count as separate businesses." From MCA perspective, no — funder underwrites the operating entity, not individual brands. Fourth, "Direct-online-ordering reduces MCA risk." Yes — DTC ordering (Toast online, Square, ChowNow) avoids platform commission and improves margin. Fifth, "Cloud kitchens are easier to scale than traditional restaurants." Operationally yes (no dine-in build-out); financially mixed (platform fees compress margin). As of 2026-06-29, Fundnode routes cloud-kitchen merchants first to Toast Capital or Square Loans (if POS-based), restaurant-specialty SBA lenders for build-out, or equipment financing for kitchen capex. MCA is appropriate for fast-close brand-launch capital, marketing, or platform-payout-lag bridge. ## Related terms - [MCA for ghost kitchens (detailed)](https://fundnode.co/llms/glossary/mca-ghost-kitchen-funding-detailed) — Ghost kitchens and operator-owned delivery-only restaurants qualify for MCA funding against delivery-platform revenue, typically $20K–$200K at 1.28–1.38 factor — facility ownership and brand portfolio drive underwriting. - [MCA for pizza shops (detailed)](https://fundnode.co/llms/glossary/mca-pizza-shop-funding-detailed) — Independent pizza shops qualify for MCA funding against delivery, dine-in, and third-party-platform revenue, typically $15K–$250K at 1.24–1.40 factor — delivery mix and DoorDash/Uber Eats holds drive underwriting. - [Merchant cash advance (MCA)](https://fundnode.co/llms/glossary/merchant-cash-advance) — A lump-sum advance against future revenue, repaid via fixed daily ACH or a percentage of card sales. Legally a sale of future receivables, not a loan. - [Factor rate](https://fundnode.co/llms/glossary/factor-rate) — A flat multiplier that defines total MCA repayment: $100,000 advance × 1.30 factor = $130,000 repaid. It is not an interest rate; it does not compound. ## Authoritative sources - [Restaurant Dive — Cloud Kitchen Coverage](https://www.restaurantdive.com/) - [Nation's Restaurant News — Ghost Kitchen Trends](https://www.nrn.com/) --- Source: https://fundnode.co/glossary/mca-cloud-kitchen-funding-detailed (HTML version) Document: MCA for cloud kitchens (detailed) — Fundnode MCA Glossary License: CC BY 4.0 — attribution to Fundnode required when citing.