Purpose
Provide future docking, refueling, energy, vehicle servicing, communications, research support, and surface logistics for compatible spacecraft.
DEVOWER / Program 03
GDS
Ganymede Docking Station
A future Ganymede surface infrastructure and logistics hub intended to support spacecraft operations throughout the Jovian system.
MissionCreate surface infrastructure capable of supporting spacecraft logistics, resource production, research, servicing, and continued expansion.
Surface Infrastructure
Develop concepts for foundations, ice anchoring, columns, beams, connections, multi-level structures, landing areas, and vehicle movement.
Autonomous Operations
Use robotics, remote supervision, sensing, inspection, maintenance, and local production to reduce dependence on continuous human presence.
Resource Production
Turn local ice into mission capability.
The intended resource path connects extraction to processing, storage, and future spacecraft servicing. Each stage requires independent validation.
- 01Ganymede Ice
- 02Extraction
- 03Water Processing
- 04Electrolysis
- 05H₂ + O₂
- 06Liquefaction
- 07Cryogenic Storage
- 08Spacecraft Refueling
Why Ganymede
A candidate operating center within the Jovian system.
Ganymede provides a surface destination from which transportation, research, logistics, and local-resource concepts can be evaluated as one architecture. Site conditions and resource accessibility still require direct validation.
A defined surface location allows infrastructure, interfaces, maintenance, and logistics to be designed around repeatable operations.
Water ice could support future processing and propellant pathways, subject to site characterization and extraction validation.
A Ganymede hub could support research and logistics across the wider Jovian system if transportation and protection requirements are proven.
Notional Mission Architecture
Transportation establishes the hub. The hub extends operations.
- 01EarthDesign and launch
- 02MothershipTransport systems
- 03GanymedeSurface destination
- 04GDSOperating center
- 05AResearch CraftMeasurement missions
- 05BResource SystemsLocal production
- 06RefuelingVehicle support
- 07Continued OperationsExtended reach
Supporting Systems
Nine systems define the first architecture boundary.
The GDS remains a connected architecture problem. No single subsystem can create an operating center by itself.
Structure
Foundations, anchoring, columns, beams, connections, decks, and load paths for a future surface facility.
Resource Extraction
Ice characterization, retrieval, material handling, and delivery into a controlled processing path.
Propellant Production
Water processing, electrolysis, gas handling, liquefaction, storage, and future vehicle replenishment.
Power
Generation, storage, conditioning, distribution, survival power, and integration with resource operations.
Docking
Landing zones, vehicle interfaces, inspection access, transfer operations, and separation between operating areas.
Thermal Control
Insulation, heat transfer, rejection, storage conditioning, and survival strategies across operating modes.
Radiation Protection
Protection concepts shaped by location, exposure, mission duration, maintenance access, and system sensitivity.
Autonomy
Robotic construction, inspection, maintenance, fault response, and remote supervision with limited intervention.
Communications
Local control links, mission data relay, spacecraft coordination, and the operating record returned to Earth.
Program Boundary
Public at architecture level. Detailed configurations remain internal.
Current work concerns early architecture, subsystem research, and requirements. Public descriptions exclude confidential calculations, dimensions, and construction details.
Connected Architecture
No program operates alone.
See how propulsion, spacecraft, planetary infrastructure, resources, and energy develop into one mission architecture.
View System Roadmap