The Navy has locked in three more years of Lockheed Martin support for Radiant Mercury, the cross-domain system that moves data between classified and less-classified networks, and it did so without a competition. The Oct. 26, 2026 Pentagon contract announcement, mirrored by GlobalSecurity, lists an $88,560,319 cost-plus-fixed-fee, indefinite-delivery/indefinite-quantity contract to Lockheed Martin Corp., Rotary and Mission Systems, of Littleton, Colorado. Naval Information Warfare Center Pacific in San Diego is the contracting activity, and the ordering period runs from Oct. 20, 2026, through Oct. 19, 2029.
For companies working in cross-domain security, the award signals that the Navy intends to keep its fielded Radiant Mercury General Service Cross Domain Solution systems in place and modernize them, rather than open the work to rival products during this window. For agencies outside the Navy, the vehicle offers a ready path to buy the same capability through task orders.
What Radiant Mercury Does for the Navy
Military users routinely need to pass information between networks that run at different classification levels. Those networks cannot simply be wired together, so a cross-domain solution sits between them and enforces rules about what can cross. The announcement describes the system's role plainly: "Radiant Mercury enables the secure transfer of information across different security domains, supporting operational information-sharing requirements for the Department of Defense and other government agencies."
TheDefenseWatch, which also reported the award, notes that the Navy's Program Executive Office for Command, Control, Communications, Computers and Intelligence lists Radiant Mercury, also called RADMERC, among its cross-domain solutions for multi-level security. The outlet also points to Navy budget documentation describing the system as a trusted information system that moves intelligence and operational data between security enclaves and supports coordination with authorized coalition partners.
What the $88.6M Ceiling Buys
The scope is broad. According to the announcement, the contract covers production, installation, program management, maintenance, modernization and sustainment of Radiant Mercury General Service systems, plus system security authorization support, logistics and training for the Department of the Navy and other government requirements.
The dollar figure is a ceiling, not an obligation. The contract carries a minimum ordering guarantee of $50,000 and a maximum value of $88,560,319. The announcement states that "Specific requirements, places of performance, periods of performance, and funding will be established through individual task orders issued under the contract." Each requesting activity will fund its own orders from its own appropriations.
TheDefenseWatch stresses the same point: "The award establishes a maximum contract ceiling of $88.56 million, but it does not mean the government will immediately spend that entire amount." The announcement does not say how many systems Lockheed Martin will produce or install, which organizations will place orders, or how much money was obligated at award.
The cost-plus-fixed-fee structure also matters. The government reimburses allowable costs and pays a fixed fee, which suits work such as modernization and security authorization support, where the effort required can shift as threats, software baselines and accreditation rules change.
Why the Navy Skipped Competition on Radiant Mercury
The Navy cited the Only One Responsible Source exception to competition. In the announcement's words, "This contract was not competitively procured pursuant to 10 U.S. Code 3204(a)(1), as implemented by Federal Acquisition Regulation 6.302-1, Only One Responsible Source."
That authority applies when only one responsible source can meet the government's need. The announcement gives no further public rationale, but TheDefenseWatch supplies history: in 2018, the Navy pursued a follow-on sole-source IDIQ for Radiant Mercury support, and that procurement's documentation pointed to the system's dependence on proprietary software and the incumbent's ability to meet established technical and security requirements. The outlet cautions that the earlier record does not by itself explain every provision of the 2026 award.
The logic is familiar to anyone who has worked on accredited systems. Replacing a fielded cross-domain solution means more than swapping hardware. A new product would need software integration, testing and a fresh security authorization, and the networks that depend on the existing system would face disruption during the transition. Those switching costs tend to favor the incumbent each time a support vehicle comes up for renewal.
What Remains Unknown About the Task Orders
Because the IDIQ sets only a framework, the real shape of the work will emerge order by order. The announcement identifies no new system variant, no specific modernization milestones and no installation schedule. It also does not name the non-Navy agencies that may use the contract.
Watch for task orders that reveal where the systems go and what modernization includes. Large modernization orders could point to software baseline updates or new authorization packages, while a steady stream of small sustainment orders would suggest the Navy is mainly keeping the current fleet of systems running through 2029.
What It Means for Contractors
Firms hoping to compete directly for Radiant Mercury production and sustainment work should not expect an opening before the ordering period ends on Oct. 19, 2029. The Only One Responsible Source justification means competing cross-domain products will not get a head-to-head evaluation on this requirement during that time.
Subcontracting is the more realistic route. The scope includes installation, logistics, training and security authorization support, all areas where a prime often brings in specialized partners. Companies with experience in Risk Management Framework packages, cross-domain accreditation or Navy shipboard and shore installation work should approach Lockheed Martin's Rotary and Mission Systems business about teaming on task orders.
Cross-domain vendors should also read the award as a market signal. Sole-source follow-ons for accredited systems tend to repeat when the government documents proprietary dependencies, so a vendor that wants a shot at the next cycle needs to build its case early. That means getting products onto approved baselines, briefing program offices and responding to sources-sought notices well before 2029, when the next follow-on decision is likely to come due.
Finally, agencies outside the Navy now have a vehicle for buying Radiant Mercury capability. Integrators supporting those customers should track which activities place orders, since those orders can reveal new programs that need cross-domain support around the core system.
