LDC Build-Out -- Two Business Models -- March 27, 2026

AI Prompt: With regard to LDCs, there appear to be two business models. One, the large hyperscalers (AWS, META) buiild their own, top to bottom. Two, independent contrators (CoreWeave) finance, build, rent/sell to second tier LLMs -- sometimes to specification, sometimes not. At one time, Oracle was doing the same thing -- using something called the "cookie cutter" approach. Thoughts? Reply: You’re basically describing the vertical integration vs. capacity merchant split in AI infrastructure—and you’ve got it right. The interesting part is why both models exist simultaneously and why they may converge or clash over time. Let’s break it down cleanly. ⸻ 1) Hyperscaler Model: Full-Stack Ownership Examples: Amazon Web Services, Meta Platforms, Google Cloud What they do • Design chips (e.g., Trainium, TPUs) • Build data centers • Own networking + software stack • Run internal + external workloads Strategic logic This is control + optimization at scale: • Cost curve advantage If you’re deploying millions of GPUs/ASICs, shaving 10–20% matters enormously. • Workload-specific silicon Trainium / TPU = tuned for their own models + customer workloads. • Tight vertical integration Think Apple but for the cloud: • silicon → compiler → runtime → application • Guaranteed utilization They are the anchor tenant (internal AI demand + cloud customers) Weakness • Enormous capex risk • Can’t pivot quickly if architecture shifts (e.g., from training → inference-heavy world) ⸻ 2) “AI Infrastructure Merchant” Model Examples: CoreWeave, Oracle (to a degree), emerging GPU lessors What they do • Raise capital • Buy GPUs (mostly NVIDIA) • Build or lease data centers • Rent capacity to: • LLM startups • Enterprises • Even hyperscalers at times Strategic logic This is capital arbitrage + speed: • Faster deployment No legacy constraints → can spin up clusters quickly • Specialization Optimized for AI workloads only (not general cloud) • Financial engineering • Long-term contracts (like power purchase agreements) • Debt + structured financing backed by compute demand • Serving the “long tail” Not everyone can get capacity from AWS/Google during shortages ⸻ 3) The “Cookie Cutter” Concept (Oracle angle) Oracle’s “cookie cutter” approach was essentially: • Standardized data center modules • Repeatable deployment templates • Pre-configured hardware/software stacks Why that matters now This idea is suddenly very relevant again in AI: • AI factories are becoming modular • Think: • 50k GPU cluster • standardized power/cooling/network design • replicated globally CoreWeave and others are effectively doing a modernized cookie cutter, but: • financed externally • tied to specific GPU generations • often pre-sold before completion ⸻ 4) The Real Underlying Difference This isn’t just business models—it’s who bears risk. Hyperscalers • Bear: • Technology risk • Demand risk • Capex risk • In return: • Capture full margin stack CoreWeave-type players • Shift risk: • To lenders (debt) • To customers (long-term contracts) • Operate more like: • toll roads for compute ⸻ 5) Where It Gets Interesting (Your “Two-Tier” Insight) You previously mentioned: EDGE vs CLOUD This maps directly: EDGE (Apple-like world) • Apple • Own silicon + tightly integrated ecosystem • Optimized, private, efficient CLOUD (this discussion) Splits into: 1. Fully integrated hyperscalers 2. Merchant AI infrastructure providers ⸻ 6) Convergence Scenarios (This is the key forward-looking piece) Scenario A: Hyperscalers win • Custom silicon (Trainium/TPU) undercuts NVIDIA economics • Third-party GPU clouds get squeezed • CoreWeave becomes niche or acquisition target Scenario B: Merchant model explodes • AI demand >> hyperscaler capacity • Capital markets fund massive GPU fleets • CoreWeave-like firms become: • “ExxonMobil of compute” Scenario C (most likely): Hybrid equilibrium • Hyperscalers: • dominate baseline + integrated workloads • Merchants: • handle burst demand + frontier training + startups ⸻ 7) Subtle but Critical Point The real dividing line isn’t just “who builds the data center.” It’s: Who owns the customer relationship AND the software layer? • Hyperscalers → sticky, platform-driven • CoreWeave → more commoditized (unless they move up-stack) That’s why: • Everyone is racing up the stack (platforms, APIs, tooling) • Not just renting GPUs anymore ⸻ Bottom Line Your framing is right, but I’d refine it slightly: • It’s not just two business models • It’s two different economic philosophies of compute 1. Vertical integration (Apple/AWS-style) → optimize everything, own everything 2. Financialized infrastructure (CoreWeave-style) → standardize, scale, lease, securitize And Oracle’s “cookie cutter” idea is the quiet bridge between them—it’s the industrialization layer that both models now depend on. ⸻