Local-first personal AI, architecture, and the industry moves that keep confirming the bet. Written in Hong Kong.
Two independent pieces, one from a creator-economy newsletter and one from a developer publication, land on the same diagnosis. Nobody has won the personal AI agent race. The bottleneck is not the model and it is not the hardware; it is whether the agent has access to the operator’s actual data. That is the problem Ostler is built around.
“Local-first” has become a polite lie in personal AI. Most products marketed as local actually keep the heavy lifting in the cloud, with the cache on your device. Ostler runs every component on a single Mac, the one the customer already owns. This is what local-first looks like when you build it honestly.
Kenan Saleh of a16z Speedrun sketches the next wave of AI: agents that continuously monitor context, predict what matters, and take action before being asked. He names two products doing it; both are cloud. Here is what observe-to-act looks like when the data never leaves the customer’s machine.
The New York Times reports corporate lawyers turning into bouncers at virtual meetings, kicking out cloud AI note-takers. The privilege risk is architectural, not editorial. Here is what changes when the note-taker runs on the customer’s own machine, with WhisperKit on-device transcription and a tamper-evident consent log.
Apple’s App Store privacy nutrition label is the only privacy disclosure surface in tech with structural enforcement. The Ostler iOS app declares zero tracking and no linked data, because there is no Ostler server to link data to. The architecture writes the label, not the lawyer.
A class action filed in California this month alleges that chatbot conversations have been routed through advertising trackers. The argument lands because chatbots are now the most intimate technology many people use. Privacy by policy cannot prevent this kind of leak. Only architecture can.
Three completely different vantage points have converged on the same architecture for personal AI over the past six months. Singapore's Foreign Minister using it daily on a Raspberry Pi. Andrej Karpathy describing it on stage. A founder shipping it to customers. They had no reason to agree. They did anyway.
Apple is about to concede the category. The fact that the most privacy-obsessed consumer-tech company on the planet cannot build a personal AI locally tells you exactly how large the market is, and why the local-first bet is the contrarian trade now being demanded.
On 21 April 2026, OpenAI released Privacy Filter as open weights under Apache 2.0. It runs locally, detects eight categories of PII, and slots directly into Ostler's ingest, diagnostic, and pre-flight pipeline. Here is why, and what the release signals.
On Dwarkesh Patel's podcast on 17 October 2025, Andrej Karpathy argued that a small reasoner with external memory beats a 1.8-trillion-parameter monolith. That is the architecture Ostler has been running since late 2025. Here is what it means for local-first personal AI.
After twenty years of giving my data to tech companies, I built a personal knowledge graph that runs entirely on a Mac Mini. This is the story of how it got here, and why it matters that nothing leaves the house.