Anduril was founded around the idea that defence procurement had become too slow for software-defined warfare. Arsenal-1 extended that critique from software into factories.
The planned Ohio campus was not simply additional capacity. It was an attempt to industrialise a different production model: fewer bespoke programmes, more reusable platforms and factories designed around rapid iteration.
The factory was part of the product
Traditional defence manufacturing often optimises for long programmes, specialised supply chains and low annual unit volumes. Anduril's autonomous systems thesis requires the opposite in several categories: systems that can be produced in larger numbers and updated quickly.
A five-million-square-foot campus therefore represented strategic intent. Anduril was preparing to carry more manufacturing risk internally rather than remain primarily a design and software company.
Scale creates credibility with the Pentagon and new execution risk
Winning a prototype competition is different from supplying at operational scale. Arsenal-1 was designed to close that gap and give the company a stronger answer to the question that follows every defence-tech demo: how many can you build?
The risk is that manufacturing campuses lock in cost before contracts materialise. Anduril's model depends on procurement reform moving quickly enough to reward companies that invest ahead of awarded programmes.
Ohio made Anduril an industrial-policy story
The project tied venture-funded defence technology to regional manufacturing, workforce development and supply-chain policy. That moved Anduril closer to the economic footprint of a traditional prime contractor even while it argued for a different operating model.
If Arsenal-1 achieves high utilisation, it could become one of the clearest examples of software-era defence companies becoming major manufacturers rather than acquisition targets for incumbents.