CoreWeave’s financed delivery promise

CoreWeave’s place in the compute market becomes clearer when its cloud contracts are read alongside its financing. Customers buy GPU-cluster access; lenders and shareholders finance much of the buildout. The business depends on making those two sets of promises fit. Our assessment is that its central competitive test is the interval between securing a customer commitment and delivering a productive cluster. Good execution can turn advance commitments into a funding advantage. Delays can leave the operator paying for infrastructure before the associated revenue arrives. cw-s1

The operating model is unusually explicit. CoreWeave’s 2025 annual report says infrastructure development is primarily financed with asset-level debt supported by take-or-pay customer contracts, supplemented by corporate debt and equity. Customers generally commit to specified capacity for multiple years and owe payment regardless of utilization under those arrangements. There is also pay-as-you-go access. This makes the company materially different from a market whose main service is matching buyers with spare GPU hours. CoreWeave is taking responsibility for the infrastructure and the financing that make a reservation deliverable, then operating the service over its contractual life. cw-s1

Software is part of that responsibility. Its SUNK product preserves researchers’ Slurm workflows while combining them with Kubernetes operations. The company describes topology-aware scheduling, job-level visibility and Mission Control monitoring for hardware faults and slow GPUs. Those are relevant capabilities because a cluster’s useful output depends on coordinated work, not simply installed chip count. But a feature list does not establish an achieved reliability rate. Buyers still need workload-specific evidence: time spent training successfully, recovery after failures, and the throughput delivered by the exact hardware, network and storage configuration in their contract. cw-s2

There is a revealing limit to the software portability story. The official SUNK Anywhere repository says its SUNK and Slurm Helm charts are proprietary and require a separate license. Public deployment documentation therefore does not mean the whole operational stack is freely reusable. For a customer planning to spread jobs across providers, technical compatibility and commercial rights are separate checks. A portable workflow can reduce migration work while still depending on vendor support, licensing and configuration knowledge. The sensible procurement question is what can actually move, under what agreement, and with which operational responsibilities left to the buyer. cw-s3

Named customers are more than logo evidence here. Microsoft accounted for approximately 67% of 2025 revenue, according to CoreWeave’s annual report. OpenAI provides a separate, customer-side check: its subprocessor list, updated October 14, identifies CoreWeave as a cloud-infrastructure provider for the API and several business ChatGPT products. That establishes a disclosed operating relationship from the buyer’s side. It does not disclose the amount paid, revenue recognized by CoreWeave, contract profitability or the share of OpenAI workloads served. Those limits matter when customer announcements are used to imply either diversification or financial strength. cw-s1, cw-s4

The second-quarter filing offers a more current concentration test. Customers A, B and C represented 36%, 26% and 10% of quarterly revenue respectively: 72% combined, by simple addition. The filing warns that letter labels may represent different customers from those in prior periods. We therefore do not map the letters to Microsoft, OpenAI or another named company. A lower largest-customer percentage can coexist with substantial dependence on a small group of buyers. The useful next disclosure would connect concentration with contract duration, payment timing and delivery obligations, rather than merely count newly announced customers. cw-s5

Backlog is the second important distinction. CoreWeave reported approximately $104 billion at June 30, defining the measure to include remaining performance obligations plus other estimated future revenue under committed contracts, subject to delivery and service availability. It is a measure of contracted future business, not cash already collected. The same release reported 1.5 GW of active power against approximately 3.7 GW contracted. These are different stages of supply development, not interchangeable descriptions of usable capacity. A large backlog creates work to deliver, and a large power pipeline creates work to commission. Neither number by itself establishes the return on that work. cw-s6

Core Scientific supplies a useful cross-check from the infrastructure side. Its July 28 presentation described approximately 590 MW leased to CoreWeave and more than 430 MW being billed as of mid-July, with full completion expected in early 2027. It also described a take-or-pay relationship with annual price escalation and customer-funded power, utilities and substantial buildout costs. This is counterparty evidence of real delivery and ongoing obligations, rather than a repeat of CoreWeave’s demand forecast. It remains a dated supplier report, not a November site inspection or proof that end-customer GPUs are fully utilized. Supplier billing and productive cloud output answer different questions. cw-s7

Financing scale gives those distinctions weight. In the first half of 2026, CoreWeave reported $3.663 billion of operating cash inflow, $14.874 billion of investing cash outflow and $13.985 billion of financing cash inflow. At June 30, it reported $35.6 billion of total indebtedness. The cash-flow pattern shows that expansion depended heavily on external financing. It does not, by itself, establish that the investment will lose money. The question is whether the eventual service cash flows and asset reuse justify the funding obligations. These are June snapshots, not an estimate of cash or debt outstanding on publication day. cw-s5

The second-quarter earnings release reported a 59% adjusted EBITDA margin alongside a $626 million net loss. Both figures belong in the picture. For a capital-intensive service, an earnings measure that excludes depreciation and financing costs cannot settle whether the overall buildout earns an adequate return. Conversely, a consolidated loss during rapid expansion does not prove that each operating cluster has poor economics. What is missing for that judgment is a consistent view of returns by deployment generation, including capital cost, useful service life, maintenance, power and financing. A headline margin is an incomplete answer to a lifetime investment question. cw-s6

September provides a concrete example of why financing headlines need reconciliation. The completed offering in CoreWeave’s September 22 filing was $4.2 billion of 2.875% convertible notes due April 2033, including the fully exercised $500 million purchaser option. Net proceeds were $4.137 billion before other offering expenses. Capped-call transactions cost approximately $566.2 million and were intended to limit certain conversion-related dilution or cash obligations, subject to a cap. Subtracting that cost leaves approximately $3.571 billion before those other expenses. The coupon is therefore not the full economic price of the financing, and the earlier $3.7 billion pricing headline understates the completed principal. cw-s8

NVIDIA is an important part of the system rather than a distant equipment supplier. In January, NVIDIA itself announced a $2 billion CoreWeave equity investment and a collaboration intended to accelerate more than 5 GW of AI factories by 2030. The plan included help with land, power and buildings, early adoption of successive NVIDIA platforms, and work toward broader use of CoreWeave software in reference architectures. Supplier alignment can support execution. It also makes the relationship worth analyzing across procurement, capital and software together. An investment and a development plan should not be read as an unconditional guarantee of CoreWeave’s obligations. cw-s9

There is also evidence of pricing opportunity. On September 17, CoreWeave said it had signed three-to-six-month contracts at approximately $40 million per MW, expressed as annualized revenue divided by power required for the relevant clusters. It reported 4.2 GW of contracted power as of August 11. The price measure is neither a standardized GPU-hour quote nor twelve months of secured revenue for a three-month contract. Shorter commitments may capture tight supply at attractive prices while bringing the next repricing decision closer. Without hardware mix, utilization, associated costs and renewal outcomes, the reported rate cannot establish a durable fleet-wide margin. cw-s10

PCT’s assessment is conditional: CoreWeave offers a substantive operating platform with demonstrated customer relationships and financed infrastructure delivery. Its risk is the coordination of those strengths over time. The decisive evidence would show customer payments, supplier milestones and debt service staying aligned across successive deployments, then show older equipment earning worthwhile renewal revenue. This review does not establish contract-level profitability, current project completion, future refinancing terms or realized resale values. CoreWeave has scheduled its next results discussion for November 10. Until then, treating announced commitments as delivered capacity would obscure precisely the execution the business must prove. cw-s11