Reference Concept • Orbital Logistics Capability
Lunar Orbital Propellant Depot (LOPD)
A requirements-style definition of an orbital propellant depot capability class supplied by lunar-sourced water — the demand-side infrastructure node that converts a surface resource into an orbital economy, and pulls surface production forward by existing.
What this page is
This page defines a neutral capability class for receiving lunar-derived water in orbit, converting it to propellant, storing cryogens, and dispensing them to visiting vehicles. It is not a product announcement, not a mission design, and not a solicitation.
Core idea: a depot gated on lunar water is not a passive consumer of surface resource production — it is the demand signal that justifies it. Depot hardware can precede the resource: its commissioning date is set by first surface water delivery, and its existence in orbit is what makes that date matter.
The sequencing question
Every architecture that uses lunar water in orbit faces the same chicken-and-egg problem: surface extraction is hard to justify without an orbital customer, and orbital infrastructure is hard to justify without a proven resource. The conventional resolution — wait for extraction to mature before building anything in orbit — serializes the two developments and pushes the payoff of each behind the full schedule of the other.
The depot resolves the deadlock structurally. Among orbital infrastructure nodes it is the earliest useful thing to build: the first consumer of surface water, the first concrete demand signal that justifies scaling production, and the first operational target that gives extraction a near-term reason to exist. Because routine depot operations are autonomous and the hardware tolerates dormant standby, the depot can be emplaced before the resource flows — a forcing function, not a waiting room.
Once supplied, a depot breaks two standing constraints of cislunar logistics: transit vehicles no longer carry their return propellant outbound, and surface-ascent vehicles top off in orbit rather than lifting full reserves on every flight. The depot also absorbs variability in surface production and smooths it into supply available on demand.
Scope of application
LOPD-class capability applies to:
- Cislunar transport architectures whose return-leg economics depend on refueling at the destination
- Surface-ascent logistics fleets operating on repeated orbit–surface cycles
- Staging of propellant ahead of demand — buffering surface production variability
- Any program seeking to convert lunar water claims into a priced, deliverable orbital commodity
LOPD-class capability sits downstream of resource assessment and extraction in the water supply chain, and upstream of every propellant-consuming element of a cislunar architecture. It complements, and does not replace, surface propellant production concepts.
Functional objectives
Primary objectives
- Accept lunar-sourced water delivered by surface-ascent vehicles in standardized transfer units
- Convert water to propellant — at minimum LOX via electrolysis — at a rate matched to demand cadence
- Store cryogenic products with managed boil-off and fault isolation between storage banks
- Dispense metered propellant to more than one visiting vehicle class through standardized interfaces
- Operate routinely without crew: reception, production, storage, dispensing, and safing
Recommended (architecture-dependent)
- Accept, condition, and store imported fuel components not yet producible in situ (e.g. methane for methalox architectures), with an explicit substitution path to in-situ production
- Retain electrolysis hydrogen for future use (fuel-cell reserve, surface delivery, or propellant) rather than venting by default
- Provide a short-stay habitable maintenance node as a growth option — the seed of a permanent orbital logistics presence
Success criterion: a visiting vehicle can plan a mission against depot-supplied propellant with quantified availability — not against a promise that supply will exist by the time it arrives.
Functional requirements (requirements-style)
| ID | Function | Requirement |
|---|---|---|
| LOPD-F-001 | Feedstock acceptance | The capability shall receive lunar-sourced water delivered in standardized transfer
units, and shall offload, inventory, and buffer it between delivery cycles and continuous
production demand.
Standardized transfer unitSupply buffering |
| LOPD-F-002 | Propellant production | The capability shall convert water to at least liquid oxygen via electrolysis and
liquefaction, at a production rate that — not delivery hardware — sets the
water delivery cadence requirement for the supplying fleet.
Water → LOX baselineRate-limiting step declared |
| LOPD-F-003 | Cryogenic storage | The capability shall store cryogenic products with boil-off management approaching
zero-boil-off targets, and with fault isolation such that a single storage-bank failure
does not compromise total inventory.
ZBO targetFault isolation |
| LOPD-F-004 | Vehicle-agnostic transfer | The capability shall dispense metered propellant through standardized ports
accommodating more than one visiting vehicle class, with custody-transfer-grade metering
and inventory reconciliation.
Standardized portsCustody metering |
| LOPD-F-005 | Autonomous operation | Routine operations — reception, production, storage management, dispensing,
leak detection, and safing — shall not require crew presence. Crew visitability is
an optional tier, not an operating dependency.
Uncrewed baselineAutonomous safing |
| LOPD-F-006 | Dormancy tolerance | Because commissioning is gated on surface water supply rather than on depot hardware
delivery, the capability shall tolerate extended dormant standby on orbit and shall
commission upon first supply arrival without hardware revisit from Earth.
Forcing functionStandby → first light |
| LOPD-F-007 | Import substitution path | Where the served propellant combination includes components not yet producible in
situ, the capability shall accept them as imported cargo, shall track the import
dependency as a declared programmatic risk, and shall preserve an interface path to
substitute in-situ production without depot redesign.
Declared dependencySubstitution-ready |
Note: quantitative thresholds (production rates, storage capacities, boil-off allowances, port standards) are architecture-dependent and should be set by the demand cadence of the vehicles the depot serves.
Graduated capability tiers
A distinguishing property of this capability class is that it scales in place. A credible development path proceeds in tiers, each retiring risk for the next:
- Demonstration-class — single transfer-unit reception, a small electrolysis string, LOX-only production, one vehicle interface. Proves the orbital water-to-propellant chain end to end at minimum capital exposure.
- Operational-class — continuous production, dual-cryogen storage, multiple vehicle classes served, autonomous cadence matched to a working supply fleet. This is the tier at which return-leg and top-off economics actually change.
- Hub-class — adds expanded storage, maintenance access, and a short-stay habitable node: the first shirt-sleeve presence in lunar orbit, emplaced before any larger habitat exists. The depot becomes the beachhead for everything after it.
Each tier reuses the interfaces, accounting standards, and operating discipline of the tier before it. Nothing in the demonstration tier is discarded on the way up.
Interface and accounting standards
Minimum
- Standardized water transfer unit: a fixed hardware unit serving as both transport vessel and depot storage element, common across surface, ascent, and depot segments
- Standardized cryogenic transfer ports with published mechanical, fluid, and data interfaces
- Custody-transfer metering: reconciled inventory across reception, production, storage, and dispensing, auditable by supplier and customer
- Telemetry sufficient for independent verification of stored and dispensed quantities
Optional / architecture-dependent
- Published berthing/docking envelopes enabling third-party vehicle compatibility
- Hydrogen inventory accounting where the byproduct stream is retained
- Scheduling and reservation protocols for multi-customer dispensing
Usability requirement: interface and accounting standards should be legible to any qualified vehicle developer — a depot that only its builder can dock with is a fuel tank, not infrastructure.
Ballpark cost (ROM)
Order-of-magnitude cost for flight-qualified LOPD-class capability (excluding launch and the supplying surface/ascent segments), planning-grade only:
- Demonstration-class node: low hundreds of $M — dominated by cryogenic fluid management and autonomous rendezvous/berthing qualification rather than electrolysis hardware
- Operational-class depot: high hundreds of $M to $B-class, scaling with storage capacity and the number of vehicle classes served
These ranges are intended for early architecture budgeting and discussion, not vendor quotes. The economics comparison that matters: every ton of propellant sourced from lunar water displaces a ton lifted from Earth's surface at cislunar delivery prices — the depot is amortized against that spread.
Relationship to program risk
Absence of LOPD-class capability leaves a lunar water program without a customer: surface extraction matures into a resource with nowhere to go, and its scaling case collapses into speculation. Conversely, orbital vehicles designed without a depot assumption carry their full round-trip propellant forever, locking in the mass fractions the architecture was meant to escape.
The depot's own dominant risks are declared rather than hidden: the import dependency for any not-yet-in-situ fuel component (LOPD-F-007), and the dormancy period between hardware emplacement and first surface supply (LOPD-F-006). Both are schedule and economics risks, not feasibility risks — every constituent technology (orbital electrolysis, cryogenic fluid management, autonomous rendezvous and fluid transfer) has flight heritage or active flight demonstration programs.
LOPD-class capability reduces structural risk in both directions of the supply chain; it does not eliminate demand risk and does not replace staged investment discipline.
Standardization potential
A depot is infrastructure exactly to the degree that its interfaces are standards. Published transfer-unit, port, and custody-accounting standards allow surface producers, ascent fleets, and visiting vehicles to be developed independently by different parties against a common contract — the condition under which an orbital propellant market, rather than a single program's fuel tank, can exist.