Software-defined defence
Software-defined defence describes military capability that is defined, updated and extended mainly through software on shared hardware rather than fixed at delivery.
Software-defined defence is a descriptive term, not a formal standard. It refers to military systems whose behaviour, features and interoperability are determined mainly by software that can be changed after the hardware is fielded. The idea borrows from software-defined networking and the software-defined vehicle: the platform provides general-purpose compute, sensors and interfaces, and capability is added or altered by releasing new code. No single government definition exists, and the phrase is used differently by armed forces, ministries and suppliers.
How it works
Three technical ideas recur. The first is separation of software from hardware, so that applications can be developed, tested and replaced without redesigning the platform beneath them. The second is a modular architecture with defined interfaces, the subject of the modular open systems approach. The third is a delivery pipeline that builds, tests and releases software frequently, usually through automated tooling often called a software factory.
The US Department of Defense framed this in its Software Modernization Strategy, published in February 2022. The document describes a department-wide software factory ecosystem, a multi-vendor enterprise cloud environment and continuous delivery supported by modern infrastructure, modular design and automation. It also treats the security approval step as a bottleneck to be redesigned, a theme covered under authority to operate.
Origins
The concept grew from commercial practice, where smartphones, cloud services and connected cars showed that products could improve after sale. Defence procurement has traditionally been organised around hardware platforms with long refresh cycles. Policy documents such as the 2022 US strategy set out the case for delivering software on a faster, more continuous basis. Related phrases, including software-defined warfare, circulate in policy debate, though usage is not uniform.
Who uses it
Defence ministries, programme offices and prime contractors all use the vocabulary, as do new entrants that sell software products rather than platforms. Alliances also frame infrastructure this way. NATO describes its Digital Backbone as the technical means for connectivity and data transport across all domains of operations, supporting data sharing across the Alliance and cloud and edge services. Such infrastructure is a precondition for software that moves between nations and platforms.
Why it matters
The approach changes how capability is bought and sustained. Contracts shift toward continuing development and sustainment rather than a one-time delivery. Intellectual property and data rights become central, because the ability to modify or replace software depends on who holds the interfaces and source. Security assurance moves from a single approval before fielding toward continuous evidence. Software also becomes a factor in interoperability and in the dependence of a force on particular suppliers.
There are limits. Safety-critical and weapons-related software needs rigorous verification that does not suit unrestricted release cadences. Legacy platforms may lack the compute or interfaces to accept frequent change. The term can also be applied loosely to products that are merely software-heavy.
What to watch
Observers follow whether acquisition rules, data-rights terms and approval processes change enough to make frequent releases routine, whether open interface standards are adopted across suppliers, and how allies align their architectures so that software can be shared and fielded across national boundaries.
Sources
Related: Authority to operate (ATO) · Command and control (C2) · Modular open systems approach (MOSA)