NEW HORIZON Act
- Sponsor
- Sen. Cruz, Ted [R-TX]
- Committees
- Armed Services Committee (primary)
- Last action
- Jun 4, 2026
Bottom line
The NEW HORIZON Act directs the Department of Defense to pilot commercial in-space data processing to enhance national security space operations and leverage private sector innovation.
What it actually does
This bill mandates the Secretary of Defense to establish a five-year operational pilot program under the Hybrid Space Architecture initiative. This program will evaluate commercially available orbital data center services and space-based cloud computing capabilities for national security and joint mission requirements. It also outlines stringent security, resilience, and interoperability requirements for these commercial services, aiming to reduce data latency, enhance resilience, and improve mission outcomes in contested space environments.
Proponents argue
Supporters argue that modern national security missions generate vast amounts of data, overwhelming terrestrial infrastructure and introducing vulnerabilities. Leveraging commercial orbital data centers can significantly reduce latency, enhance resilience, and improve the effectiveness of military and intelligence operations by processing data in space. This bill is seen as crucial for maintaining a technological edge, fostering a competitive domestic industrial base, and integrating cutting-edge commercial solutions into defense architectures.
Opponents contend
Critics might raise concerns about the potential costs of integrating novel commercial technologies, the inherent security risks of relying on non-governmental space infrastructure for classified data, and the challenges of ensuring robust cybersecurity and resilience in a contested space domain. Some may also question whether the benefits outweigh the risks or if resources could be better allocated to existing, proven defense programs.
The bill is concise and relatively straightforward, allowing an informed reader to grasp its core provisions and implications within a short timeframe.
Section 1
Short Title
This section establishes the official short title of the Act as the 'Nodes, Enterprise Workloads, and Hybrid Operations, Resilience, Integration, Zero-Trust, Orbital Networks Act' or the 'NEW HORIZON Act'. This provides a concise and memorable name for the legislation.
Supporters argue
Supporters argue that a clear and memorable short title facilitates public understanding and legislative reference, making the bill more accessible and identifiable.
Critics contend
No specific opposition is typically raised against this provision, as short titles are standard legislative practice.
Tradeoffs
None.
Section 2(a)
Congressional Findings on Space Data and Commercial Capabilities
This section outlines Congress's understanding and rationale for the bill. It highlights the increasing volume of data from national security space missions, the limitations and vulnerabilities of ground-based processing, the emergence of commercial orbital data centers, and the strategic need for hybrid architectures. It also emphasizes the importance of a competitive domestic industrial base for space infrastructure.
Section 2(b)(1)
Establishment of Orbital Data Center Pilot Program
This provision mandates the Secretary of Defense, acting through the Director of the Defense Innovation Unit (DIU), to establish an operational pilot program within one year of the Act's enactment. The program's purpose is to evaluate commercially available orbital data center services and space-based cloud computing capabilities for national security and joint mission requirements under the Hybrid Space Architecture initiative.
Section 2(b)(2)
Purposes of the Pilot Program
This section details the specific objectives of the pilot program, including assessing military utility, evaluating operational integration into existing DoD architectures, examining resilience and security benefits of in-space processing, informing potential transition to sustained programs, evaluating asset protection strategies against threats, and assessing the integration of multi-vendor commercial components.
Section 2(b)(5)
Security and Resilience Measures for Sensitive and Classified Information
This provision mandates that any orbital data center services used for sensitive or classified information must implement robust security measures. These include cybersecurity protections (zero-trust, encryption, continuous monitoring), risk management for supply chain and foreign influence, resilience capabilities (redundancy, failover), protections against various threats (cyber, electronic warfare, counterspace), secure command and control links, ground system protections, and safeguards for workload isolation and data sovereignty.
Section 2(b)(8) and 2(c)
Pilot Program Briefing and Termination
This provision requires the Secretary of Defense to provide a briefing to the congressional defense committees by December 31, 2028. The briefing must cover the program's execution, operational use cases, lessons learned, recommendations for future use, and assessments of various risks (cybersecurity, insider threat, counterspace, commercial provider risks). The authority to carry out the pilot program is set to terminate five years after the date of the Act's enactment.
This subsection directs the Secretary to encourage competitive participation from a diverse set of nontraditional defense contractors and commercial space providers.
Section 2(b)(4)
Why it matters:This is standard legislative practice for encouraging broad participation, but its importance for fostering innovation and a robust industrial base could be overlooked by a casual reader focusing on technical mandates.
Case for: Supporters argue that this provision is crucial for ensuring the DoD taps into the full breadth of commercial innovation, preventing vendor lock-in and promoting a dynamic industrial base.
Case against: No specific case against, but some might argue that prioritizing 'nontraditional' contractors could complicate procurement or introduce unproven entities into sensitive national security programs.
Estimated impact: Potentially broad impact on market access for new space companies and the overall competitiveness of the defense industrial base for space technologies.
This subsection requires the Secretary of Defense, acting through the Director of the Defense Innovation Unit, to consult with a wide range of entities, including the Assistant Secretary of Defense for Space Policy, service acquisition executives, the Space Force, other military departments, the National Reconnaissance Office, and the National Geospatial-Intelligence Agency.
Section 2(b)(7)
Why it matters:Consultation requirements are common in legislation. However, the breadth of agencies listed here is significant, indicating a strong intent for broad integration and buy-in across the national security enterprise, which is a key operational detail.
Case for: Proponents argue that extensive consultation ensures the pilot program is well-integrated, avoids duplication of effort, and garners necessary buy-in from key stakeholders across the defense and intelligence communities.
Case against: Some might argue that such extensive consultation could slow down the pilot program's execution due to bureaucratic complexities and differing agency priorities.
Estimated impact: Ensures comprehensive strategic alignment and operational integration of the pilot program across the national security space enterprise.
This subsection provides a precise definition of 'orbital data center' as a space-based computing, data storage, or networking capability, including spacecraft or hosted payloads, designed primarily to provide persistent, scalable, or shared in-orbit processing, analysis, storage, fusion, routing, or dissemination of data as a distinct operational capability, rather than ancillary to a primary mission.
Section 2(d)
Why it matters:Definitions are often placed at the end of bills. However, this specific definition is crucial for understanding the exact scope and intent of the entire pilot program, distinguishing it from general satellite computing capabilities.
Case for: Supporters argue that a clear and precise definition is essential to prevent ambiguity, ensure the pilot program focuses on the intended capabilities, and guide industry development towards specific DoD needs.
Case against: No specific case against, but an overly narrow definition could inadvertently exclude innovative solutions that don't perfectly fit the described parameters.
Estimated impact: Crucially defines the scope of the technology to be evaluated, shaping the entire pilot program and future acquisition strategies.