Palo Alto Networks has agreed to acquire Applied Compute in an all-stock transaction valued at $4.5 billion, subject to adjustments. Applied Compute provides post-training and inference infrastructure for open-weight models. The buyer says the combination will support enterprise deployment across public and sovereign clouds while bringing Applied Compute's research team into its wider AI portfolio.

The transaction is subject to customary conditions, including regulatory clearance, and is expected to close in Palo Alto Networks' fiscal third quarter of 2027. Until then, it is an agreement rather than a completed acquisition. The filing says Applied Compute co-founder and chief executive Yash Patil would become a co-chief AI officer at Palo Alto Networks after closing.

Strategically, the deal links security with the model operations layer. Enterprises choosing open-weight systems often want greater control over data, tuning, cost and deployment location, but those choices also transfer more responsibility for model provenance, access, post-training integrity and runtime monitoring. Palo Alto Networks is arguing that these controls can become part of a security platform rather than a separate engineering stack. The valuation and product benefits are company claims, and integration risk remains. Even so, the scale of the proposed purchase shows that secure model adaptation and serving are becoming a material competitive market in their own right.


Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury's approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don't run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab's own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer's agents.
Share this post
The link has been copied!