Policy Considerations for Orbital Data Centers

Downloads

Orbital data centers could complement terrestrial infrastructure by processing selected workloads in space, particularly where data is generated in orbit. Their value will depend on technical performance, life cycle economics, market demand, and a regulatory environment that does not hinder testing and deployment.

KEY TAKEAWAYS

Key Takeaways

Contents

Key Takeaways 1

Introduction. 2

Why Orbital Data Centers Are Gaining Relevance 3

Advantages of Orbital Computing. 3

Technical and Economic Challenges for Orbital Data Centers 4

Policy Challenges and Recommendations for Orbital Data Centers 6

Conclusion. 9

Endnotes 11

Introduction

Orbital data centers are specialized satellites that support computing functions by processing data in space.0F[1] This emerging technology is attracting growing attention amid both rising demand for computing capacity and advances in commercial space capabilities.1F[2] As the global space economy continues to grow and more digital services rely on space-based infrastructure, orbital computing may become useful for selected space-based workloads. Government assessments, technical research, and industry feasibility studies are currently examining whether selected computing functions could be performed in orbit for specialized applications, although significant engineering and economic questions remain.2F[3]

Today's orbital data center concepts should not be understood as near-term substitutes for terrestrial cloud infrastructure.3F[4] Data centers on Earth benefit from mature supply chains, easier repair and upgrade cycles, and lower operating complexity. Orbital systems, by contrast, must operate in a harsher environment that includes radiation exposure, thermal management challenges, communications constraints, and high deployment and replacement costs.4F[5] If orbital compute clears current technical and economic hurdles, then the central policy consideration is whether orbital systems can perform specialized computing functions well enough to justify their operational complexity rather than whether they can replace terrestrial hyperscale data centers.

The strongest near-term opportunity for orbital computing lies in workloads that benefit from processing data where it is generated in space. These include Earth observation, remote sensing, and onboard spacecraft autonomy.5F[6] Over a longer time horizon, onboard or distributed computing could also become useful for certain lunar and cislunar missions, particularly where communications architecture or operational requirements favor local processing. In such settings, orbital computing may reduce bandwidth demands and improve operational responsiveness, particularly where decisions must be made in orbit rather than on the ground.6F[7]

For that reason, orbital data centers are best treated as a complementary layer of digital infrastructure rather than a wholesale replacement for terrestrial systems.7F[8] Public policy should focus on ensuring that existing regulatory frameworks allow markets to identify and develop those applications for which orbital computing offers genuine comparative advantages, which could lead to orbital systems becoming a meaningful complement to the broader digital infrastructure ecosystem.

Why Orbital Data Centers Are Gaining Relevance

The simultaneous increase in demand for compute-intensive services alongside the improvement of commercial space capabilities is generating interest in orbital data centers. The Government Accountability Office's (GAO's) April 2026 "Science & Tech Spotlight" describes space-based data centers as "satellites that would house data processing and storage systems for AI and other computing needs," potentially reducing the land, electricity, and water required by terrestrial facilities.8F[9] This framing, in the context of resistance to expanding terrestrial data center infrastructure, helps explain why the concept is now receiving policy attention, even though the underlying technology remains in an early stage.9F[10]

Private-sector research has reinforced that interest. Google's Project Suncatcher is an exploratory initiative that examines the feasibility of scaling machine-learning compute in space using solar-powered satellite constellations, special processors, and free-space optical communications links.10F[11] Thales Alenia Space's ASCEND project likewise presents space-based data centers as a feasibility question, indicating that orbital computing has become the subject of structured technical and commercial investigation.11F[12]

The broader relevance is that orbital computing may become a useful layer of digital infrastructure for specific workloads before it becomes competitive with terrestrial cloud infrastructure.12F[13] A space-based architecture that is appropriate for one mission class may still be uneconomical for general-purpose computing, particularly where latency, maintenance, replacement, and scale economies continue to favor Earth-based facilities. Therefore, the current evidence supports measured attention rather than exaggerated expectations.

Orbital data centers may eventually complement terrestrial infrastructure in specialized use cases, but their near-term significance will depend on whether the technical and economic constraints can be managed at acceptable costs. The role for policymakers is to create a regulatory environment that minimizes unnecessary barriers to testing and deploying this new technology. The true value of orbital data centers will be easier to assess once these regulatory barriers are reduced.

Advantages of Orbital Computing

The most plausible near-term case for orbital computing is mission-specific data processing. When data is generated and processed in orbit, and only a subset is transmitted back to Earth, orbital data centers may reduce the volume of transmitted data and, in some missions, improve operational responsiveness.13F[14] That logic is especially relevant for Earth observation, remote sensing, spacecraft autonomy, and other space-native tasks.

A related but more contingent possibility is that orbital systems could reduce certain site-specific terrestrial infrastructure pressures in selected applications. GAO notes that space-based data centers could reduce the overall land, electricity, and water needs of data centers on Earth, while Google's Project Suncatcher similarly frames space-based compute as capable of lessening the strain on terrestrial resources.14F[15]

These potential benefits would materialize only in certain system configurations, and they are not evidence that orbital data centers will be cost competitive for general-purpose cloud computing workloads. Whether those advantages matter in practice will depend on the full life cycle economics of launch, servicing, communications, replacement, and orbital operations.15F[16] Thus, the relevant question is not whether orbital computing is superior in the abstract, but whether it offers a net advantage for certain operations once engineering constraints and life cycle costs are fully accounted for.16F[17]

For policy purposes, the key implication is that orbital data centers should be evaluated use case by use case rather than treated as a single integrated market. If regulatory compliance costs are minimized and equal across use cases, then the actual costs of each are limited to the technology itself, which provides clarity on which use cases genuinely benefit from orbital computing. Minimizing regulatory costs can be achieved through transparent compliance requirements and streamlined licensing procedures, as is discussed in more detail later in this report.

Technical and Economic Challenges for Orbital Data Centers

Orbital data centers face substantial engineering and economic constraints. Available technical studies identify radiation exposure, thermal management, communications capacity, limited servicing, cybersecurity, and system resilience as the recurring challenges in their design and operation.17F[18]

Thermal management is the most significant engineering constraint. Computing equipment generates substantial waste heat that must be removed to maintain acceptable operating temperatures. Terrestrial data centers can manage this heat through air- and liquid-based cooling systems that ultimately transfer waste heat to the surrounding environment.18F[19] In the vacuum of space, spacecraft cannot reject heat to the surrounding environment via convection and must reject internally generated waste heat through thermal radiation.19F[20] This engineering challenge creates trade-offs involving radiator area, spacecraft design, mass, and power density that can constrain system scale and performance.20F[21] Even where an orbital system can obtain substantial solar energy, heat rejection may remain a major design constraint.21F[22]

Radiation is another engineering challenge for orbital data centers. Depending on the orbit, shielding, component selection, and mission duration, exposure to ionizing radiation and energetic particles can increase fault risk, degrade component performance, and shorten hardware lifetimes.22F[23] Radiation-hardening and other mitigation techniques can improve tolerance and limit damage. Still, radiation hardening adds costs associated with a satellite's mass, power, performance, hardware resources, and engineering complexity.23F[24]

Maintenance and upgrade cycles in orbit differ substantially from those of terrestrial data centers. Terrestrial data centers can be serviced, expanded, and refreshed comparatively easily, but orbital systems face limited opportunities for repair and replacement.24F[25] Because physical servicing in orbit remains difficult, costly, and unavailable for many architectures, hardware failures may be substantially harder to repair than in terrestrial data centers. Furthermore, rapid changes in computing technologies in hyperscale data centers may lead to technological obsolescence if satellite deployment schedules are not aligned with hardware advances.25F[26] This dynamic effectively shortens the usable life cycle of orbital hardware relative to its terrestrial counterpart, which translates directly into higher life cycle costs than for a comparable terrestrial deployment.

These engineering and economic constraints are compounded by a set of cybersecurity and data governance concerns that have no straightforward terrestrial equivalent. Their attack surface may span spacecraft, communications links, ground infrastructure, and cloud management systems. Command channels and telemetry may be vulnerable to spoofing or unauthorized access; radio-frequency links may be subject to jamming; and supply-chain compromise, malicious firmware, or insider threats may affect both space and ground components.26F[27] Depending on the architecture, mission, data, technology, and jurisdictions involved, operators may also encounter export-control and government-access requirements, as well as privacy and data-governance considerations.27F[28]

For example, depending on the architecture and mission, U.S. operators may be subject to Federal Communications Commission (FCC) licensing requirements and, wherever a system operates regulated remote-sensing capabilities, National Oceanic and Atmospheric Administration (NOAA) licensing under 15 C.F.R. Part 960.28F[29] Depending on the technology, data, and other characteristics of the system, export-control restrictions or other sector-specific legal obligations may also apply.29F[30]

In addition, federal policy and guidance, such as Space Policy Directive-5 and National Institute of Standards and Technology (NIST) cybersecurity guidance, establish cybersecurity principles and recommended practices relevant to commercial space systems.30F[31] Collectively, these authorities address different aspects of space operations, communications, remote sensing, export controls, and cybersecurity, but no single generally applicable federal framework governs orbital computing as an integrated space-and-ground network architecture.

Because spacecraft are often difficult or impossible to repair once deployed, cybersecurity and resilience should be incorporated throughout system design, development, and operations. Relevant measures include strong encryption and authentication, resilience planning, and supply-chain risk management. Existing federal cybersecurity frameworks can provide a starting point for managing risks across the space and ground segments.31F[32]

Together, these operational, security, and governance burdens suggest that early orbital data center applications are more likely to involve specialized, mission-driven workloads than general cloud substitution. That overhead is easier to justify for workloads with distinct requirements than for commodity computing that terrestrial infrastructure already handles well. In-orbit processing may offer commercial value if it reduces downlink burdens, supports spacecraft autonomy, or handles workloads for which timeliness matters more than raw cost per unit of compute.32F[33] Terrestrial data centers are likely to remain the default platform for broad commercial computing because they benefit from mature infrastructure, established business models, and simpler maintenance and upgrade cycles.33F[34]

Figure 1: Comparison of terrestrial and orbital data centers

Policy Challenges and Recommendations for Orbital Data Centers

Policymakers should reduce unnecessary regulatory barriers to experimentation to effectively measure the benefits of orbital data centers. This reduction includes removing constraints on spectrum access, streamlining inefficient licensing, addressing launch-capacity constraints, and accounting for externalities such as orbital debris and cybersecurity risk.

These reforms are needed because spectrum is a necessary resource to enable the compute functions that may make orbital data centers useful. Slow licensing and launch capacity constraints prevent iterative testing capabilities by blocking orbital data centers from launching frequently enough to extract critical performance data. Insurmountable cyber vulnerabilities and an overly congested orbital environment risk making orbital data centers a nonstarter before they have been fully tested.

Orbital data centers will need reliable spectrum access for space-to-ground, ground-to-space, and space-to-space communications. The FCC's Spectrum Abundance for Weird Space Stuff proceeding is considering measures to clarify access to existing spectrum allocations and make additional spectrum available for telemetry, tracking, and command, and other emerging space operations.34F[35] More generally, uncertainty around spectrum rights and coordination procedures can increase transaction costs and deter investment. Clearer rules and more efficient licensing could reduce regulatory uncertainty and unnecessary administrative barriers. The FCC has adopted reforms to modernize its satellite and earth station licensing framework, and is investigating ways to create more spectrum for launch, reentry, and in-orbit activities.35F[36] As new satellite technology combines communications, computing, storage, and other functions, certain orbital data center architectures may nevertheless raise questions about how existing licensing and spectrum requirements will apply to emerging hybrid systems. Regulatory agencies should proactively determine how emerging technology such as orbital data centers will fit within current compliance regimes or begin developing new regulations that account for next-generation systems. Doing so will prevent regulatory drag on orbital data center testing and deployment.

The FCC, through its existing administrative authority, can ensure that regulation does not lag behind innovation-and it should proactively do so. Additionally, Congress could complement those efforts through legislation like the SAT Streamlining Act, which establishes additional statutory requirements intended to increase the predictability and timeliness of satellite licensing.36F[37]

Licensing reform alone will not be sufficient if launch capacity cannot support deployment, as some proposed large-scale architectures could depend on heavy-lift launch capabilities and a high launch cadence to deploy in orbit. Congress should evaluate spaceport modernization and launch-infrastructure investment in light of demonstrated capacity needs, broader government and commercial launch demand, and public benefits.37F[38] Where infrastructure constraints are demonstrated, policymakers should prioritize investments and regulatory reforms that expand launch capacity while accounting for budgetary trade-offs and preserving competition among commercial launch providers.

More launches also mean more satellites in orbit, raising separate sustainability concerns. As the space ecosystem continues to grow, orbital data centers would place additional satellites into increasingly congested orbital regimes, heightening the importance of debris mitigation, tracking, conjunction assessment, and space traffic coordination. Policies like the ORBITS Act would address active debris remediation and related sustainability practices. At the agency level, NOAA's Office of Space Commerce is deploying the Traffic Coordination System for Space to provide basic space situational awareness and spaceflight-safety services to civil and private operators.38F[39] Measures that improve debris mitigation, space traffic coordination, and conjunction awareness can improve the safety and predictability of the orbital environment for continued space operations.39F[40]

Finally, regulatory agencies should clarify how existing cybersecurity expectations apply to orbital compute architectures, including software assurance, encryption and authentication, identity management, supply-chain risk management, and incident response across the space and ground segments.40F[41] For government-facing systems, federal acquisition processes can provide a mechanism for incorporating cybersecurity and software supply chain risk management considerations into procurement decisions. For commercial systems, voluntary guidance and risk-based frameworks may help operators manage cybersecurity risks without prematurely locking in rigid technical mandates.41F[42] Cross-border coordination also matters because data routing, launch services, component sourcing, and ground-station access often span jurisdictions with different security, export-control, and data-governance rules.

These recommendations reflect a common principle: minimize unnecessary regulatory friction while preserving the safeguards necessary for safe experimentation. The goal is not to subsidize orbital data centers into existence or to presume that they will scale broadly; it is to ensure that the regulatory frameworks avoid unnecessary barriers to testing while preserving legitimate safeguards for spectrum, safety, cybersecurity, national security, and orbital sustainability.

Figure 2: Rendering of a potential orbital data center system

Conclusion

As orbital data center technologies evolve, policymakers should focus on reducing unnecessary regulatory uncertainty, improving the predictability of spectrum access and licensing, clarifying cybersecurity expectations, and improving the safety and predictability of an increasingly congested orbital environment. These measures can lower barriers to experimentation while preserving appropriate safeguards for competition, national security, orbital sustainability, and the reliable operation of critical communications infrastructure. Whether orbital data centers ultimately become a meaningful component of digital infrastructure should depend on demonstrated technical performance, life cycle economics, customer demand, and operational reliability-not on regulatory inertia or policy-driven preferences.

Endnotes