01 / DEFINITION

Compute infrastructure governed by spacecraft constraints

An orbital data centre is a spacecraft, hosted payload or coordinated constellation designed to perform meaningful compute, storage or data-processing work beyond Earth’s surface. The word data centre describes the workload and service objective; orbital changes the engineering boundary.

A credible definition must include the spacecraft bus, power generation and storage, thermal transport and radiators, radiation-aware hardware, communications, navigation and timing, autonomous fault handling, ground operations, cybersecurity, launch integration, insurance, replacement and disposal. Leaving those layers outside the system may produce an attractive server specification, but it does not produce an orbital service.

02 / COMPLETE ARCHITECTURE

Eight layers that must close together

01Compute & storage

Processors, memory, storage, secure elements and workload scheduling sized for power, radiation and thermal limits.

02Power

Solar arrays, batteries, conversion losses, eclipse operation, degradation and safe power states.

03Thermal rejection

Cold plates, heat pipes, spreaders, phase-change buffering and radiators. Vacuum removes convection; it does not remove waste heat.

04Radiation tolerance

Shielding, component selection, error correction, redundancy, scrubbing and recovery from single-event effects.

05Communications

Ground links and cross-links with realistic contact windows, pointing, Doppler, weather, bandwidth and latency.

06Autonomy

Fault detection, isolation, recovery, workload degradation and safe-mode decisions when Earth is unavailable.

07Ground & security

Mission control, key custody, software supply chain, identity, command authority, observability and incident response.

08Lifecycle

Launch, commissioning, insurance, servicing assumptions, replacement cadence, debris mitigation and end-of-life disposal.

03 / ORBITAL REALITY

Orbit creates opportunities and constraints at the same time

Some orbital profiles can provide extended solar exposure, physical separation from terrestrial hazards, proximity to space-generated data and new sovereign-custody options. Those possibilities are real research motivations. They are not automatic economic advantages.

Every benefit carries a counterweight. Solar availability must be reduced by conversion, pointing, eclipse, storage and degradation losses. Physical isolation makes unauthorised physical access harder but also makes repair harder. Proximity to sensors may reduce raw-data downlink for some workloads, while increasing the importance of model updates, result delivery and cross-link availability. Sovereignty may improve only if jurisdiction, keys, command authority and operational control are designed coherently.

Orbital value is workload-specific. The right question is not “Is space better?” but “For which workload does the complete orbital system outperform the strongest terrestrial alternative?”
04 / PROOF OF PULSE POSITION

A staged path from model to hosted payload

Proof of Pulse Technologies is developing a modular orbital data-centre architecture intended to begin with ground simulation and engineering models, proceed through qualification, and then move toward a hosted-payload pilot before any larger constellation commitment.

The public architecture combines orbital compute and storage with hardware-rooted identity, policy-aware data custody, the Wave Synchronization Network and a purpose-built Layer-1 for provenance and infrastructure coordination. These are design components under development. The public site does not represent them as a flight-proven service.

The programme is led through the intended India and Goa product lane described in the group-structure map. Blockchain launch activity remains assigned to Estonia; the physical orbital programme remains assigned to India, subject to all applicable authorisations.

05 / EVIDENCE GATES

What must be demonstrated before the category claim becomes a service claim

  • A repeatable workload benchmark with declared inputs, outputs and service level.
  • Measured processor-to-radiator performance across representative thermal cycles.
  • Radiation testing, memory-integrity results and fault-recovery evidence.
  • End-to-end RF or optical link budgets verified against geometry and operations.
  • Hardware-in-the-loop autonomy exercises, including loss of communications.
  • Complete lifecycle cost, reliability, insurance, replacement and disposal models.
  • Independent security review and documented command/key governance.
  • Launch, spectrum, mission and jurisdictional approvals appropriate to the final design.

Until those gates are passed, Proof of Pulse uses the terms research, architecture, modelled, supplier specification and target to keep evidence maturity visible.