IOSG argues that private AI is moving from a niche concern to a practical deployment choice for both enterprises and consumers. The report says the core issue is no longer abstract model safety, but where plaintext prompts, internal data, and company-specific judgment end up once they leave a user’s device. It reviews the current privacy stack, from contractual zero-data-retention and anonymous relays to trusted execution environments, end-to-end encrypted inference, fully homomorphic encryption, and local inference, and finds that costs and performance penalties are falling for several of these approaches. A central example comes from a June 30 case study by Bridgewater’s AIA Labs and Thinking Machines. In that work, an expert-tuned open model based on Qwen3-235B outperformed frontier models in both accuracy and inference cost on investment-related tasks, scoring 84.7% versus 78.2% for the best frontier setup using expert prompts, while cutting inference cost by 13.8x. IOSG’s argument is not that privacy AI is solved. Tool calls in agent workflows, encrypted search, and private post-training remain major gaps. But the report says the infrastructure needed to train and run open models inside controlled, attestable environments is arriving piece by piece, giving companies a clearer path to keep their own alpha inside their own boundary.

IOSG argues that private AI is moving from a niche concern to a practical choice for both enterprises and consumers, as companies grow more wary of sending sensitive data and proprietary knowledge into closed-model systems. In a long-form analysis by Jeff @IOSG, the firm lays out the tradeoff now facing the market: frontier labs still lead in general capability, but open models are improving quickly and, in some specialized domains, already outperform frontier systems on both accuracy and cost. The report traces several privacy approaches, from contractual zero-data-retention and Oblivious HTTP to trusted execution environments, end-to-end encryption, fully homomorphic encryption, and local inference. It argues that only some of these offer verifiable privacy, and those routes largely depend on open models rather than proprietary ones. IOSG also points to a recent case from Bridgewater-backed AIA Labs and Thinking Machines, where a fine-tuned Qwen3-235B model beat frontier models on expert financial tasks. Even so, the report says major gaps remain. Tool use in agent workflows, private post-training, and encrypted search are still hard to deliver at scale. IOSG’s conclusion is that privacy inference is becoming cheaper and more deployable, but the most defensible opportunities lie in the unsolved layers around training loops, tool execution, and search infrastructure.

IOSG argues that private AI is no longer a niche technical preference but an emerging requirement for enterprises and power users that do not want proprietary data, internal workflows, or high-value judgment calls exposed to model providers. In its report, the firm lays out how the privacy problem starts the moment a prompt leaves a user’s device and reaches a server in plaintext, and why contractual protections such as zero-data-retention terms can only go so far. The piece links that risk to corporate restrictions on ChatGPT, shadow AI leaks, and a series of legal cases in which user chats became discoverable evidence. The report also maps the trade-offs across today’s privacy stack, from contract-based retention promises and OHTTP relays to trusted execution environments, end-to-end encryption, fully homomorphic encryption, and local inference. Its central case study comes from Bridgewater’s AIA Labs and Thinking Machines, which showed that a fine-tuned open model, Qwen3-235B, beat frontier models on both accuracy and cost in financial judgment tasks. IOSG’s conclusion is narrow but clear: for execution-heavy agent workflows, trust-based setups still dominate because tool calls expose plaintext to downstream services; for high-value strategic reasoning and domain-specific alpha, verified private infrastructure around open models is becoming a practical path.

A new report from IOSG argues that the core debate in AI is shifting from model capability alone to a harder question: who gets to see the data, and whether privacy claims can actually be verified. The piece points to a string of examples showing why that matters. Palantir CEO Alex Karp said companies are paying a token premium to frontier labs while letting proprietary knowledge leak out through plaintext requests. Wall Street banks restricted ChatGPT use within months of its launch, Samsung banned generative AI across its network after engineers exposed chip source code, and court orders later forced OpenAI to retain and disclose consumer chat records in litigation. The report maps the current privacy stack, from contractual zero-data-retention and anonymous relays to trusted execution environments, end-to-end encryption, fully homomorphic encryption and local inference. It argues that verifiable privacy is still mostly limited to open models, because frontier labs have little incentive to expose model weights or serving code. At the same time, the economics are changing: enclave-based inference is getting cheaper, and in some cases can match or undercut plaintext API pricing. IOSG also highlights a June 30 case from Bridgewater-backed AIA Labs and Thinking Machines, where a fine-tuned open model beat frontier systems on both accuracy and cost in financial tasks. The report’s broader point is that private AI remains incomplete, especially for agentic workflows and tool use, but it is no longer hypothetical.