01 / DEFINITION

Own the specialised payload, share the spacecraft services

A hosted payload is a secondary system integrated onto a spacecraft whose platform serves another mission or multiple customers. The host may provide structure, power, attitude control, thermal interfaces, communications, command routing and launch integration. The payload provides its own bounded compute, storage, security and mission functions.

Hosted does not mean software-only, free infrastructure or exemption from qualification.

The exact split belongs in an interface control document. Without it, cost, safety and schedule claims cannot be compared.

02 / INTERFACE CONTROL

Every shared service needs a declared limit

MASS + VOLUMEPhysical envelope

Launch loads, mounting, centre of mass, deployment clearance and debris containment.

POWERElectrical envelope

Peak, average, startup, eclipse, fault current, grounding and power-quality limits.

THERMALHeat-transfer envelope

Conductive paths, radiator access, allowable interface temperature and safe-mode load.

DATA + COMMANDAuthority envelope

Permitted messages, timing, bandwidth, authentication, update process and emergency shutdown.

Radiofrequency compatibility, electromagnetic emissions, contamination, cybersecurity, export controls, licensing, operations and end-of-life responsibilities must also be allocated.

03 / NON-INTERFERENCE

Isolation is demonstrated, not asserted

The payload should minimise trust and access across the host boundary. Command filtering, one-way or tightly bounded interfaces, separate memory, isolated power domains and rate limits can reduce propagation risk. The host still needs independent authority to protect its primary mission.

  • Define allowed commands and reject all unspecified states.
  • Prevent payload software from controlling host attitude or safety systems.
  • Test electrical, thermal, timing and network faults in both directions.
  • Provide authenticated update, rollback and safe-state mechanisms.
  • Log boundary events without exposing protected customer data.
04 / ECONOMIC BOUNDARY

Shared infrastructure can reduce scope—not erase lifecycle costs

A hosted approach may avoid development of a dedicated spacecraft bus and may use scheduled rideshare capacity. It still carries payload manufacturing, qualification, integration, host fees, launch, licensing, communications, insurance, operations, replacement and disposal costs.

Comparisons must use the same delivered workload and service level. Comparing a small hosted demonstrator with a complete independent constellation produces a scope difference, not a verified percentage saving.

05 / READINESS

Five gates before a hosted mission is credible

  • A frozen payload requirement and common workload definition.
  • A signed interface baseline with mass, power, thermal, data and command limits.
  • Bench and hardware-in-the-loop evidence for boundary and safe-state behaviour.
  • Environmental, electromagnetic and cybersecurity acceptance.
  • A contracted launch and operations path with regulatory responsibility assigned.

Proof of Pulse is evaluating hosted payloads as a capital-disciplined deployment pathway. Public material describes a proposed architecture and test sequence, not a completed flight integration.