CoreWeave, Inc. 10-Qquarter ended 2026-06-30

MixedAccounting issue

Existing customers fuel AI cloud growth, but NVIDIA GPU capacity expansion and rising financing costs deepen losses.

Filed 2026-08-11 19:24 ET

Key figures · Q2 FY2026 · period ended 2026-06-30

  • Revenue$2.6BYoY +112.5%QoQ +23.9%
  • Operating income−$49.0MYear ago $19.0MQoQ +66.0%
  • Net income−$626.0MYoY −115.9%QoQ +15.4%
  • Total assets$77.1BQoQ +38.7%
  • Total debt
    How total debt adds up
    Recourse debt, current$6,235M
    + Non-recourse debt, current$1,278M
    + Recourse debt, non-current$25,170M
    + Non-recourse debt, non-current$2,385M
    + Finance lease liabilities, non-current$214M
    + Finance lease liabilities, current$7M
    Total debt$35,289M

    Lines as the filer presents them on its balance sheet.

    $35.3B1QoQ +40.6%
  • Shareholders' equity$5.0BYoY +89.0%QoQ +5.6%
  • Tangible book value$3.7BQoQ +7.1%
Notes (1)
  1. Total debt: Recourse and non-recourse debt plus finance lease liabilities.
Notes on other figures in this summary (1)
  • Cash and cash equivalents: Summary: $15.6B · Filing: $5.5B

    Comment from AI: The summary's $15.6B combines cash, marketable securities and available facilities; cash and cash equivalents of $5.52B excludes marketable securities and short-term investments.

How this filing reads

  • Health−0.5H1 free cash flow was $(10.5)B against $15.6B of cash, securities and available facilities, with $35.6B of debt principal payments.
  • Momentum+0.2Revenue grew 112%, while H1 net loss widened to $1.37B from $605M.
  • Outlook+0.3Remaining contractual obligations reached $103.7B, with 41% expected to convert within 24 months.
  • Accounting issue“Unresolved material weaknesses cover financial-system controls, segregation of duties and staffing”

Executive Summary

CoreWeave sells GPU-based cloud computing to AI developers and enterprises, earning revenue primarily through committed service contracts. It is expanding its integrated AI platform and data-center capacity to serve larger workloads from existing customers. Q2 revenue rose 112%, but infrastructure costs and financing expenses widened losses as the company built capacity ahead of future revenue. Its $103.7B of remaining contractual obligations offers substantial growth visibility, but investors must weigh that opportunity against heavy borrowing, delivery risk and customer concentration.

What's Happening in the Business

  • Customer expansion drove growth: Existing customers generated ≈93% of the revenue increase in both Q2 and H1. CoreWeave is combining GPU infrastructure, networking and storage with tools for model and agent development, seeking to serve more of customers’ AI workloads rather than computing capacity alone.
  • Large commitments are broadening the customer base: These include Meta’s initial commitment of up to $21.0B and Jane Street’s ≈$6.0B commitment announced in April. Customer A’s Q2 revenue share fell from 71% to 36%, while Customer B reached 26%; dependence has shifted toward several large accounts rather than disappeared.
  • Capacity expansion is accelerating: H1 capital spending supported GPUs, servers, networking and data centers, while net property and equipment rose 53% from year-end. Development joint ventures extend CoreWeave’s involvement into building facilities, increasing control over capacity but also construction and funding exposure.

Key Financial Highlights

Metric Q2 2026 H1 2026 Investor interpretation
Revenue $2.58B; +112% Y/Y $4.65B; +112% Y/Y Existing-customer expansion drove most growth.
Operating income / (loss) $(49)M vs $19M $(193)M vs $(8)M Infrastructure costs outpaced revenue growth.
Net interest expense $640M vs $267M $1.18B vs $531M Financing costs substantially exceeded operating losses.
Net loss $(626)M vs $(290)M $(1.37)B vs $(605)M Revenue growth has not translated into profitability.
Operating cash flow — $3.66B vs $(190)M Customer receipts and noncash depreciation explain the divergence from losses.
Capital expenditures / FCF — $14.1B / $(10.5)B Infrastructure spending far exceeded internally generated cash.
  • Cost pressure: Cost of revenue reached 34% of revenue from 26%, reflecting rent, power and depreciation; technology and infrastructure expense also grew faster than sales as capacity expanded.
  • Cash conversion: H1 operating cash flow benefited from $2.54B of depreciation and amortization and a $1.37B increase in deferred revenue. Customer prepayments help fund construction, but do not eliminate the investment shortfall.
  • Earnings quality: Unrealized strategic-investment gains contributed $109M in Q2 and $111M in H1, cushioning losses without representing cloud-service operating improvement.
  • Financing and dilution: H1 private placements raised $2.98B net, while common shares outstanding increased 9.8% to 551M. Stock-based compensation was $318M; expansion is being financed partly through shareholder dilution.
  • Liquidity: Cash, marketable securities and available facilities totaled $15.6B, up from $6.86B at year-end. Much of that capacity is borrowing availability rather than cash, tying continued expansion to access to financing.

Risk Assessment

  • Financial-reporting controls: Unresolved material weaknesses cover financial-system controls, segregation of duties and staffing; no material misstatement resulted, but remediation still requires implementation and testing.
  • Financing and fixed commitments: Debt principal payments total $35.6B, alongside $16.3B of operating lease liabilities and $35.5B of payments on leases not yet commenced, creating substantial obligations before new capacity earns revenue.
  • Customer and AI-demand concentration: The three largest customers supplied ≈72% of Q2 revenue, so a default, spending slowdown or reduced need for computing could leave infrastructure obligations unsupported despite take-or-pay contracts.
  • Delivery and power: Previously disclosed third-party data-center delays and a power shortfall that caused customer service credits demonstrate how construction or utility constraints can disrupt contracted deployments.
  • Supplier and technology dependence: All deployed GPUs are NVIDIA products, while larger cloud competitors can bundle or underprice services; supply disruption, faster hardware obsolescence or pricing pressure could weaken returns on expensive infrastructure.

What to Watch

  • Contract conversion: CoreWeave expects 41% of remaining performance obligations to become revenue within 24 months. Timely deployments and revenue recognition would validate the expansion; delays or contract changes would weaken that visibility.
  • Customer breadth: Existing accounts supplied ≈93% of revenue growth despite a less concentrated largest-customer share. Further growth across Meta, Jane Street and other customers would broaden the base; renewed concentration would preserve dependence on a few buyers.
  • Capacity delivery: Data-center expansion and development joint ventures are under way following earlier delivery delays. Facilities entering service without customer credits would support execution; further power or construction problems would undermine it.
  • Funding economics: H1 FCF was deeply negative and interest expense rose sharply. Improving operating profitability and a narrower cash shortfall would support the investment case; continued borrowing and share issuance without those improvements would weaken it.

Changes since the previous 10-Q

Since the Q1 FY2026 10-Q:

  1. Risk materialized New York development restrictions
    Power-use and construction regulation could limit data-center expansion. → July New York moratorium restricts development of data centers using at least 50 MW.
  2. Watch item worsened Infrastructure self-financing
    Q1 operating cash flow: $2.98B; capital spending: $7.70B; external funding remained necessary. → Q2 operating cash flow: $679M; capital spending: $6.42B; external funding dependence increased.
  3. Watch item improved NVIDIA Rubin readiness
    Second-half 2026 Rubin deployment was planned; availability and customer adoption were priorities. → Vera Rubin NVL72 completed bring-up and validation, an early step toward deployment.
  4. Risk materialized Power availability
    Power shortages could delay deployments or impair service. → A customer project's power shortfall caused service credits.

Was this summary useful?

Figures are computed from the filing's XBRL data; the summary and scores are written by an AI model reading the filing.

Model 006 · prompt v105 · 2026-10-26 11:33:40Z

Feedback