What are the two main types of AI workloads CoreWeave addresses?

Training (the creation of model weights, done by companies like OpenAI, Anthropic, and Meta) and inference (the deployment and use of those models). Each requires different infrastructure.

Why can't companies just add GPUs to traditional cloud platforms?

Training workloads require large tranches of GPUs that are deeply interconnected and working together. Failures, storage bottlenecks, and job orchestration directly impact billion-dollar training runs, so generic cloud design—which deploys compute reactively as needs arise—is inefficient and costly for AI at scale.

What is Sanders' background and why is it relevant?

Sanders spent 20 years at Microsoft working on early Azure, then moved to industry solutions (financial services, retail). He was pulled into discussions on AI infrastructure optimization, which led him to CoreWeave to apply those learnings to a purpose-built AI platform.

AI Business & IndustryPractical AIJul 17, 2026Jul 17, 2026, 19:00 JST

CoreWeave's AI-native infrastructure challenge: why cloud needs reinvention

Send on LINE

3 Key Points

What happened
Corey Sanders, SVP of Product at CoreWeave (formerly 20 years at Microsoft Azure), discussed how AI infrastructure must fundamentally differ from traditional cloud computing. He identified two separate streams—training (model creation) and inference (deployment)—each with distinct infrastructure needs that generic cloud platforms cannot efficiently serve.
Why it matters
Training workloads require massive, deeply interconnected GPU deployments that are far more expensive and fragile than standard cloud compute. Failures, storage bottlenecks, and poor job orchestration directly impact billion-dollar training runs. Sanders' insight from his Microsoft years was that the legacy cloud strategy of deploying compute on-demand fails for AI because AI workloads demand purpose-built infrastructure, observability, and storage systems designed specifically for that use case—not bolted onto general-purpose platforms.
What to watch
Sanders framed a convergence between the training side (model creation by OpenAI, Anthropic, Meta) and a second half of the AI story (inference and application deployment) that he was about to detail. The distinction signals CoreWeave's positioning: infrastructure optimized end-to-end for AI workloads, from hardware layout and interconnect design through orchestration and observability, rather than generic rack-and-power cloud.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Get news like this every morning, free

Context & Analysis

Sanders' framing draws a direct parallel between cloud computing's transformation in the 2000s and the current AI infrastructure moment. Just as early Azure succeeded by designing systems around web-scale applications rather than retrofitting traditional data centers, CoreWeave positions itself around the observation that AI workloads—particularly massive training runs—have radically different hardware and orchestration requirements. The key insight is that GPU failures, storage performance, and job scheduling all have outsized impact on training economics because of the sheer cost per hour of running billions of operations across deeply interconnected hardware. Sanders' 20 years at Microsoft give him credibility to spot this parallel: he lived through the early cloud transition and recognizes that optimization at the infrastructure level (hardware interconnect design, observability, storage systems) is not a feature add-on but a foundational architectural decision. This explains why he pivoted from general-purpose cloud to an AI-native platform—the problems are structurally different, not just incremental. The mention of a "second half of the story" (inference and application deployment) signals that CoreWeave sees both training and deployment as parts of the same ecosystem, not separate vendors' problems.

FAQ

What are the two main types of AI workloads CoreWeave addresses?: Training (the creation of model weights, done by companies like OpenAI, Anthropic, and Meta) and inference (the deployment and use of those models). Each requires different infrastructure.
Why can't companies just add GPUs to traditional cloud platforms?: Training workloads require large tranches of GPUs that are deeply interconnected and working together. Failures, storage bottlenecks, and job orchestration directly impact billion-dollar training runs, so generic cloud design—which deploys compute reactively as needs arise—is inefficient and costly for AI at scale.
What is Sanders' background and why is it relevant?: Sanders spent 20 years at Microsoft working on early Azure, then moved to industry solutions (financial services, retail). He was pulled into discussions on AI infrastructure optimization, which led him to CoreWeave to apply those learnings to a purpose-built AI platform.

Practical AIRead Original Article

Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Get it free

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.