Silicon Valley’s AI wunderkind launches Underdog, the most private Instinct/Muse competitor yet
- ID
- 32481
- Status
- summarized
- Published
- 07 Oct 2026, 4:47 AM
- Fetched
- 07 Oct 2026, 5:59 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/10/06/silicon-valleys-ai-wunderkind-launches-underdog-the-most-private-instinct-muse-competitor-yet/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 4.0
- Created
- 07 Oct 2026, 6:00 AM
- Tags
- Audience
- developersai_ml_learnersai_agent_usersvibe_coders
What happened
Sigil Wen, described in the article as a self-taught coder and Thiel Fellow, launched an invite-only beta of Underdog on Monday — a fully on-device AI assistant that currently runs on Macs and Windows PCs, with Linux, iPhone, and Android versions stated as coming soon. It uses a custom inference engine called Husky that Wen says moves less data between the main chip and the graphics chip than other on-device engines, encrypts the keys to accounts like email that users authorise, and runs a 27-billion-parameter reasoning model fine-tuned from an unnamed base — considerably smaller than data-centre state-of-the-art models. The article reports no benchmarks, latency figures, model licence, pricing, or beta size.
Why it matters
The concrete trade-off is the 27B parameter ceiling plus no published benchmarks — so if you are considering on-device inference for privacy-sensitive workloads (for example, anything you would not want leaving a Malaysian-hosted app under PDPA obligations), you cannot yet compare Underdog against a cloud agent on quality or speed. The other practical blocker is platform: invite-only, Mac and Windows only, with Linux, iOS, and Android not yet shipped, so Linux-first or mobile-first teams cannot test it at all right now. Treat the 'most private' framing as an unverified claim until the encrypted-key design and Husky engine are independently examined.
Discussion angle
Underdog caps out at a 27B reasoning model with zero published benchmarks — what would an on-device assistant have to prove (tokens/sec, tool-calling reliability, context handling) before you would swap out a cloud agent for real work, and does the encrypted-key approach address the actual trust problem?