Pathos co-development data conflict
Pathos
This is the core tradeoff in Pathos’s model, the same data engine that can make it a better asset picker can also make partners more cautious about what they hand over. Pathos is not just selling software or trial services. It is using Foundry and a growing clinical pipeline to choose, acquire, and advance oncology assets itself, including a majority stake in DeuterOncology, while also building a large oncology foundation model with Tempus and AstraZeneca. That makes every partnership discussion partly about collaboration and partly about information boundaries.
-
In practice, co-development means sharing the details that matter most, failed subgroups, biomarker patterns, site performance, dose logic, and why an earlier trial design broke. Those insights are valuable because they can improve Pathos’s own target selection and trial design engine, even if no formal IP is transferred.
-
Comparable AI biotechs have tried to balance both sides of the house. Recursion openly runs partnered programs with Roche, Genentech, and Sanofi while also advancing its own pipeline through Recursion OS. That model can work, but it requires unusually strong trust, deal structure, and data segregation because the platform owner is learning from both internal and external programs at once.
-
The tension rises as Pathos moves closer to owning more of the upside. A services or software vendor can promise neutrality. A company using its platform to source acquisitions and take majority stakes is economically closer to a biotech buyer, which narrows the set of pharma partners willing to open up their best internal program data.
Going forward, Pathos is likely to split into two lanes, a smaller set of deep partnerships where incentives are tightly aligned, and a larger push to compound advantage through owned assets. If its internal programs show better trial outcomes, the proprietary pipeline will become the stronger engine and partnership strategy will center on selective, high trust data relationships rather than broad platform licensing.