Nscale's S-1 shows a $44.6B bet from Anthropic and a $1B check from Nvidia

Nscale's S-1 shows a $44.6B bet from Anthropic and a $1B check from Nvidia

Good morning ๐Ÿ‘‹ Nvidia just wrote a $1 billion check into a company whose biggest contract is buying Nvidia chips. Nscale's S-1 makes that circularity official, and it isn't even the strangest number in the filing.

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's S-1 shows a $44.6B bet from Anthropic and a $1B check from Nvidia

Nscale filed to list on the NYSE as NSCL yesterday, and the numbers inside are wild: $140.6 million in first-half revenue, up 1,252% from a year ago, against a $1.02 billion net loss. The engine behind that growth is a GPU Services Agreement with Anthropic worth up to $44.6 billion, signed August 25 to build out the Monarch Compute Campus in West Virginia. Three days before filing, Nscale locked in $3.1 billion in convertible notes, a billion of it from Nvidia itself, the chip supplier effectively financing the customer that buys its own chips. Press pegs the IPO at a $30 billion valuation, which is the conversion cap on those notes, not a market test. One customer accounting for tens of billions in contracted revenue is either the best backlog in AI infrastructure or the single point of failure that sinks this stock the day Anthropic renegotiates.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿ›๏ธ POLICY & REGULATION


๐Ÿ› ๏ธ TRY THIS

Benchmark your vector store before you lock into one, using AWS's own numbers

1. Pull your Bedrock Knowledge Base's real query pattern (top-k, filter usage, docs ingested per day) from CloudWatch, not the sample workload in the blog post.

2. Run AWS's three benchmark scenarios against OpenSearch, Aurora PostgreSQL with pgvector, and S3 Vectors using that data.

3. Score by cost per million vectors at your current scale and at 10x. Latency numbers alone will steer you wrong once volume grows.

4. Pick S3 Vectors if you can tolerate slower recall for the discount. Pick OpenSearch if you need sub-100ms lookups under load.

Prompt: Given my RAG workload (doc count, queries/day, latency budget), compare Amazon OpenSearch, Aurora pgvector, and S3 Vectors using AWS's Bedrock Knowledge Bases benchmark framework. Show projected cost per million vectors at current scale and at 10x.

Worth a look


๐Ÿ”— QUICK LINKS


Watch what happens the day Nscale's biggest customer asks to renegotiate. That's the whole thesis in one clause.

Pradeep Perugu

Get inovAIte in your inbox.