Nscale lines up $3.36B pre-IPO, and NVIDIA is both the anchor and the customer

Nscale lines up $3.36B pre-IPO, and NVIDIA is both the anchor and the customer

Good morning πŸ‘‹ NVIDIA just wrote a check to its own GPU customer, days before that customer starts its IPO roadshow. The filing explains why, and it isn't generosity.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


πŸ”­ THE ONE THING

πŸ—οΈ Nscale lines up $3.36B pre-IPO, and NVIDIA is both the anchor and the customer

Nscale just closed $2.36 billion of a $3.36 billion convertible note round, led by Third Point, with Apollo, Citadel, Hudson Bay, the Abu Dhabi Investment Council and 8090 Industries filling out the syndicate. NVIDIA is in for the other $1 billion, landing mid-November, and every note converts into equity the moment Nscale prices its IPO. That structure tells you what this really is: a bridge loan dressed as a funding round, priced to dodge setting a valuation until public markets do it instead. NVIDIA anchoring its own GPU customer's balance sheet ahead of an IPO is the part worth sitting with, not the topline number. If you're building on neocloud capacity, the takeaway is that the chips are still the scarce asset, and the people selling them are now also underwriting who gets to resell them.


πŸ”¬ RESEARCH HIGHLIGHTS


πŸš€ AI STARTUPS


πŸ› οΈ TRY THIS

Turn idle GPU cycles into batched robotics simulation with NVIDIA Warp

NVIDIA just anchored a $3.36B neocloud raise on the compute-supply side. On the demand side, its new MjWarp guide shows what you actually do with that GPU capacity: move a MuJoCo robotics task off single-world CPU execution onto thousands of parallel worlds. The code delta is smaller than you'd guess. Worth an afternoon if you're running RL rollouts or domain-randomization sweeps.

1. Get the task running clean in stock MuJoCo on CPU first. That's your ground truth for parity checks later.

2. Port to MjWarp as a single world (nworld=1) and diff the trajectory against the CPU run before touching batch size.

3. Tile your initial state with np.tile(), scale to hundreds or thousands of worlds, and size nconmax/njmax up front instead of debugging silent truncation after the fact.

4. Wrap the step loop in wp.ScopedCapture() for CUDA graph replay, and only start timing after a GPU sync plus a warmup pass. Skip that and you're benchmarking queue latency, not compute.

Prompt: I have a MuJoCo simulation running on CPU (paste my step loop and model-loading code). Help me port it to NVIDIA's MjWarp for batched GPU execution: show me the mjw.put_model/make_data calls, how to tile my initial state across N worlds, and how to wrap the step in a CUDA graph capture.

πŸ”— QUICK LINKS


That's the stack worth knowing today. Back tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.