The US Department of War has set its sights on closed radio access network stacks, backing open source as the alternative, RCR Wireless reports. The move puts the Pentagon's weight behind a technical argument that the telecom industry has been fighting over for years.

The Department, renamed from its long-standing Defense Department designation, is now a visible player in the RAN software debate. Closed stacks — single-vendor bundles of radio hardware and network software from the likes of Ericsson, Nokia and Huawei — dominate deployed networks worldwide. Open source challenges that model by publishing the code, in principle letting any vendor or operator inspect, modify and substitute parts of the stack.

Why does a war department care about RAN software?

The answer runs through supply-chain security rather than spectrum policy. Radio access networks sit at the edge of national communications infrastructure, and closed proprietary stacks give operators limited visibility into what the software actually does. For an agency that depends on commercial networks for much of its connectivity, an auditable code base offers a form of assurance that vendor assurances cannot match.

The department's involvement also tracks with existing federal policy. Washington has already spent heavily to rip Chinese vendor equipment out of US networks, and it has promoted Open RAN interfaces as a way to widen the supplier pool beyond the three Nordic and Chinese incumbents that control most of the market. Open source RAN extends that logic from interfaces to the software itself.

How does this fit the wider Open RAN effort?

The industry's Open RAN push, led by the O-RAN Alliance and carriers such as Rakuten Mobile, AT&T and Vodafone, has focused on standardized interfaces that let radios from one vendor talk to software from another. Full open source stacks go further. Projects in this space aim to replace proprietary baseband and control software with code that anyone can read and build on.

Critics of that approach, including several major vendors, argue that open codebases are harder to harden, certify and support at carrier scale. Proponents counter that transparency shortens vulnerability discovery cycles and cuts costs. The Department of War's entry into the debate gives the proponents a powerful new patron with procurement budgets to match.

What happens next?

RCR Wireless's report signals intent rather than a finished program. The department has not, in this reporting, committed to a specific codebase, funding line or deployment schedule. Still, federal adoption of open RAN software would create a reference customer that smaller open source developers currently lack, and procurement requirements tend to ripple through defense contractor supply chains quickly.

For network operators and vendors, the immediate question is whether Pentagon backing shifts the economics of open source RAN from experiment to procurement option — a question that the coming budget and acquisition cycles should begin to answer.