Etched leaves stealth with a working chip, $800M raised, $1B in orders

Etched leaves stealth with a working chip, $800M raised, $1B in orders

Good morning ๐Ÿ‘‹ A chip startup just did what a hundred pitch decks couldn't: shipped working silicon, not a roadmap.

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

โšก Etched leaves stealth with a working chip, $800M raised, $1B in orders

Etched came out of stealth today with the one thing most AI chip startups can't show you: first-pass (A0) silicon that actually works, built on TSMC's N4P process. The company has quietly raised $800M total, including a $500M round last December at a $5B valuation, from a backer list that reads like a prop-trading-desk reunion (Jane Street, Two Sigma, Hudson River Trading) plus a TSMC-linked fund, with Karpathy, Hinton, and Fei-Fei Li in as angels. Customer contracts are north of $1B, and rack-scale systems running DeepSeek, Qwen, Mamba, and Llama ship this summer. Worth separating what's confirmed from what isn't: the silicon success and the funding are independently verified, but that $1B order book has no named customer behind it, it's Etched's number alone. Still, a chip that works and a $5B check from people who trade for a living is more than most Nvidia challengers ever get to.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿ› ๏ธ TRY THIS

Instrument the agent before it fails quietly in prod

Etched's chip story is a bet that agents get cheap enough to run everywhere. Cheap agents in prod means more of them silently looping, misfiring on tool calls, or burning turns doing nothing useful. AWS just published the actual playbook for catching that with Bedrock AgentCore's built-in traces and metrics.

1. Turn on AgentCore Observability for one agent already live, not a demo.

2. Pull the trace on its worst run from this week and find the exact step it looped or called the wrong tool.

3. Set a metric alert on that specific failure (tool-call count, turn count, whatever broke).

4. Re-run the same task and check the trace actually looks different.

Prompt: Given this agent trace [paste], find the exact step where it looped or invoked the wrong tool, and propose one guardrail (prompt edit, tool schema fix, or turn limit) that would have stopped it there.

Worth a look: Amazon Bedrock AgentCore Observability, if you're running agents on Bedrock and flying blind on failures.


๐Ÿ”— QUICK LINKS


See you tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.