QWE AI Academy The Beth Kindig io-fund analysis that named this thing – Nvidia CoreWeave Nebius circular financing – is all over financial Twitter and r/WallStreetBets right now. Every take is written for investors: is CoreWeave a buy, is Nebius overvalued, is this 2008 again. That’s not your problem.
Your problem is the H100 invoice. The money loop between these three companies is quietly setting the price you pay per GPU-hour, shaping how hard your provider will push for a 12-month commitment, and – if it snaps – whether your training job has a home next quarter. This is the builder’s version: what the loop is, how to audit your own exposure, and where the hedges actually are.
What the loop is – one sentence, then the detail
Nvidia gives money to two GPU cloud companies. Those companies use it to buy Nvidia GPUs. Nvidia has promised to buy back whatever they can’t rent out. Dollars in a circle.
Per public filings and announcements: Nvidia put roughly $2 billion into additional CoreWeave shares in January 2026, then a parallel $2 billion into Nebius in March 2026. The backstop – the part that made analysts sit up – is a $6.3 billion agreement under which Nvidia is obligated to purchase CoreWeave’s residual unsold capacity through April 13, 2032, per the CoreWeave SEC filing reported by CNBC.
Turns out the agreement was signed in 2023. It only surfaced in an SEC filing in September 2025. The circle had been closed for two years before anyone outside the deal knew.
Which raises a question worth sitting with: if a $6.3 billion safety net can stay hidden in plain sight for two years, what else about your GPU provider’s financial structure are you not seeing? That’s not rhetorical – it’s the actual audit question below.
This hits your bill, not just the balance sheet
Two effects, both real. First: the loop keeps supply flowing even when unit economics don’t work – so hourly rates collapse. GPU rental rates have fallen 50-70% from peak (as of July 2026, per TechTimes). Good for your invoice this quarter. Bad for provider margins – CoreWeave’s adjusted EBITDA margin dropped from 62% to 56% in a year (Motley Fool, Q1 2026).
Second – and this one matters more – the backstop protects the provider, not you. If demand softens and CoreWeave restructures, your reserved-capacity contract is a creditor claim. The $6.3B flows to CoreWeave’s balance sheet. Not to keeping your training run alive.
Watch out: When a vendor cites their Nvidia relationship as a stability signal, ask what happens to your reserved instances in a bankruptcy scenario. If they can’t point to contract language, treat it as marketing.
4-step provider audit – do this before signing anything longer than 30 days
About 30 minutes. Worth it.
- Pull their most recent 10-Q or investor deck. Check debt-to-revenue. Reference point: CoreWeave’s total debt hit $24.9 billion in Q1 2026; it burned $4.71 billion in free cash flow that same quarter against $2.08 billion in revenue (Motley Fool / byteiota). If your provider’s numbers trend that direction, price them as high-risk regardless of the hourly rate.
- Check customer concentration. CoreWeave has a $21 billion commitment from Meta; Nebius landed up to $27 billion from Meta (Motley Fool, 2026). One customer walking equals crisis. Ask sales for top-3 customer revenue share before you commit.
- Normalize the price. Providers advertise per-node rates that obscure add-ons. CoreWeave’s H100 pricing works out to ~$2.70/GPU-hr when normalized from their $21.60/hr 8-GPU HGX node – then total hourly cost often exceeds $3 once mandatory CPU and RAM are added, per Thunder Compute’s pricing review. That’s a 10-30% gap versus the headline number.
- Run a community-cloud sanity check. As of June-July 2025 (this may have shifted since), RunPod H100 community rates were around $1.99/GPU-hr; Vast.ai ran as low as $1.49 in a promotional period (IntuitionLabs). If you’re paying enterprise rates for a workload that doesn’t need enterprise SLAs, you’re subsidizing the loop.
One freshness note on step 4: Nebius updated pricing for B300, B200, H200, and H100 VMs starting June 1, 2026. Any spreadsheet built before that date needs a refresh before you use it to make a decision.
Three things the press got wrong this month
“Nvidia is bailing them out.” Wrong framing. The backstop is a demand floor – Nvidia buys unsold capacity and finds another home for it. CoreWeave’s operating losses aren’t covered.
“Dark fiber all over again.” Half right, half lazy. The dark-fiber parallel assumes nobody’s using the capacity. CoreWeave’s disclosed backlog is $99.4 billion (TechTimes, July 2026). That’s not recognized revenue, but it’s not zero demand either.
“Nvidia can absorb any blowup.” Probably true in isolation – Nvidia’s LTM free cash flow was $119 billion as of 2026, second only to Apple (io-fund / Beth Kindig). The catch: if two or three neoclouds wobble simultaneously, writing more equity checks starts to look like a position Nvidia can’t exit cleanly.
CoreWeave vs Nebius vs community clouds – builder’s view
Skip the investor framing. Here’s what actually matters if you’re picking compute:
| Provider | H100 $/GPU-hr (approx., mid-2026) | Financial signal | Best for |
|---|---|---|---|
| CoreWeave | ~$2.70 (+ mandatory CPU/RAM, often $3+) | $24.9B debt, widening losses – offset by $99.4B backlog and Nvidia backstop | Long-committed enterprise training, InfiniBand-heavy multi-node workloads |
| Nebius | ~$2.00 on-demand | Q1 2026 revenue +684% YoY to $399M; annualized run rate $1.9B; less debt than CoreWeave | Cost-sensitive teams that still want a listed, audited provider |
| RunPod / Vast.ai | $1.49-$1.99 (as of mid-2025; may have shifted) | Private, no public financials; marketplace model | Bursty, fault-tolerant jobs where you can move workloads fast |
Nebius is the number worth staring at. Revenue up 684% in a single year – $399M in Q1 2026, annualized run rate jumping from $1.25B to $1.9B in one quarter. Its on-demand H100 rate (~$2.00) sits closer to community-cloud pricing than to CoreWeave’s normalized $2.70+. That gap is a signal, not a coincidence: it shows where enterprise GPU rates are being pulled.
The Reddit spike is a warning, not a green light
Reddit sentiment for Nebius hit 95 – very bullish – on a Friday morning in mid-2026, off a viral r/WallStreetBets post with 1,616 upvotes (Yahoo Finance). Two days later: CoreWeave down 13.9% to $85.68, Nebius down 17% to $229.18, both on Meta’s announcement that it would build its own compute.
Retail euphoria on your compute vendor’s stock isn’t a buy signal. It’s a concentration-risk signal. The same customers making the stock go up are probably also locking in long contracts – which means supply tightens, pricing flexibility shrinks, and your negotiating position weakens.
What to actually do tonight
Pull up your current GPU cloud invoice. Run the 4-step audit above: 10-Q check, customer concentration, normalized $/GPU-hr, community-cloud comparison. One flag = request a 30-day renewal instead of your usual term. Two flags = start a parallel test on a second provider this week. The loop spins either way. What you control is contract length and vendor concentration on your side.
FAQ
Is the Nvidia backstop actually being triggered right now?
Publicly, no – CoreWeave still reports more demand than capacity. But rental rates are down 50-70% from peak. The pressure is showing up in price, not unsold units, which is exactly what the backstop wasn’t designed to cover.
Should I avoid CoreWeave and Nebius entirely?
No. The loop cuts both ways. If you need 128 H100s for a two-month training run, CoreWeave’s InfiniBand fabric and multi-node tuning are genuinely better than most community clouds – and Nvidia’s financial entanglement means capacity is being over-built, which pushes prices down for buyers. The right move is shorter contracts and a documented Plan B provider. Not avoidance.
Does this affect OpenAI or Anthropic API prices?
Indirectly. The labs rent from these neoclouds. Cheaper GPU-hours mean cheaper inference upstream – eventually. Don’t expect API prices to drop next week.