3 quotes from 2 episodes on All-In Podcast, each with a timestamped link to the source.
3 quotes2 episodes
The short version
Nikesh Arora states that practical enterprise applications will eventually rely on open-source AI models. Modifying model weights allows organizations to validate outcomes and document exact computational processes.
Most interesting insights
Unvalidated AI creates direct liability when managers report unknown outcomes to executives or regulators.
“If I can't validate, it's not going to be okay to go to your boss to say, 'I don't know what happened, but the IT guys put an AI model in there, it did it,'”
Nikesh Arora, All-In Podcast · October 2026 · Watch at 9:31 ↗
Open architectures fit practical corporate workloads
Routine enterprise applications will likely settle on open-source AI. Palo Alto Networks already inspects endpoint traffic for $20 to $25 a year per machine using small local models.
“I think for most practical use cases in enterprises, we're going to end up training some version of an open-source model…”
Open architectures give engineering teams the direct ability to train and alter AI parameters. Routine production workloads demand this custom weight management to maintain data sovereignty.
“We preference open source open weight because it allows us to modify the weights and train them…”
Nikesh Arora, All-In Podcast · October 2026 · Watch at 9:13 ↗
Frontier cloud API calls cost $20 to $50 per million tokens, while running optimized open-weight models on private GPUs drops the bill to $1 to $2 per million tokens.
Routing raw operational data through proprietary APIs breaks enterprise unit economics; Palo Alto Networks inspects hundreds of megabytes of endpoint traffic for just $20 to $25 a year per machine by running small models on local hardware.
Regulated enterprises in finance and healthcare are abandoning closed frontier models because proprietary APIs block internal chain-of-thought auditing.
Palo Alto Networks CEO Nikesh Arora warns that telling a banking or medical regulator that "an IT model did it" creates immediate corporate liability.
How we attribute quotes. Every quote was matched against the episode transcript, so the words and the timestamp are real (we trim filler words like "um", nothing else). The name comes from our written summary of the episode, and we use it only when a separate check of the captions finds that person on the episode. YouTube gives us no voice-by-voice transcript, so open the timestamp to hear who is talking. See a wrong name? Tell us and we fix or remove it.