MoonCloud™ unifies distributed compute, storage, synchronization and mission continuity across Earth, orbit and the lunar surface. CAIRN™ provides the orchestration logic. VirtualMoon™ makes the operating picture visible.
Compute, storage, cache and sync across mission nodes.
Place workloads, prioritize data and coordinate changing contacts.
Show terrain, assets, network state and mission events together.
A cislunar network connecting Earth, orbit and lunar surface operations.
Distributed nodes, CAIRN orchestration and reproducible mission scenarios.
Mission design, simulation, hosted-payload software and edge-compute integration.
Start with the first useful node and grow toward a shared cislunar compute fabric.
MoonCloud is the umbrella product. CAIRN is the orchestration engine underneath it. VirtualMoon is the operational environment that makes the system legible to engineers, partners and mission operators.
Future lunar missions will generate more local data, more autonomous decisions and more cross-provider coordination than a downlink-first model alone can serve well. The missing layer is the operating logic that decides where computation should occur, what evidence should be preserved, what state should be replicated and how missions continue seamlessly across changing links.
Push workloads toward the place where mission value is highest instead of defaulting to Earth.
Retain and replicate critical state without assuming infinite bandwidth or continuous contact.
Use future windows deliberately, prioritizing value, safety evidence and mission continuity.
Disconnection is treated as a normal operating state with planned continuity.
MoonCloud is the platform and service layer. CAIRN coordinates compute, storage and data movement above transport. VirtualMoon provides the shared mission operating picture.
Mission twin, common operating picture, demo environment and technical storytelling layer.
Dashboards, event review, scenario management and workflow visibility.
Resource recovery, logistics, science, infrastructure and rehearsal use cases.
Conference and partner-facing guided view of the same system logic.
Distributed compute, storage, cache, synchronization and hosted-node deployment path.
Compute placement, data prioritization, replication, contact use and degraded modes.
Mission-planning and node-local control roles interfacing with the platform.
Explainable, auditable system behavior with recoverable operational state.
Local command, telemetry and bounded coordination.
Store-carry-forward delivery across intermittent contacts.
Interoperable service baseline for communications and PNT.
Provider-diverse lunar and Earth connectivity.
Sensing, mobility and local computation.
WATERIG · OASIS · FIRN/TARN · EMBER and related infrastructure.
FLARE and future lunar logistics assets.
Surface hubs, orbital hosts, archive sinks and future service nodes.
One aerospace platform with clear technical roles and a shared mission purpose.
The compute and storage utility expression of the stack. MoonCloud packages distributed execution, replication, caching, synchronization and hosted-node services into one cislunar infrastructure story.
The policy core that decides what should be computed, what should be stored, what should move, what can wait and how operations continue under constrained power, storage and communications.
A presentation-grade lunar operations environment that connects terrain, assets, event logs, mission clock and CAIRN network health into one common operating picture.
MoonCloud serves agency missions, lunar infrastructure operators, payload and prime teams, and relay or hosted-compute providers through architecture, integration and deployment services.
Programs that need mission resilience, high-value data handling and operations continuity across distributed surface and orbital assets.
Commercial or mixed-use operators building the first persistent logistics, resource or communications infrastructure beyond Earth.
Mission builders who need a flexible compute, storage and orchestration layer without developing the full stack from scratch.
Orbital hosts and network providers seeking a useful application layer that creates demand for hosted compute and storage services.
“Compute where useful.CAIRN operating principle
Store where necessary.
Transmit what matters.”
Eight mission operations primitives define how MoonCloud executes, retains, prioritizes and reconciles distributed state across cislunar nodes.
Run the workload where it creates the most mission value.
Preserve raw, derived or critical mission state locally when needed.
Classify data and events by urgency, value and mission consequence.
Protect continuity by copying ledgers, logs and important state.
Use the right contact opportunity and align transfers with mission value.
Merge state correctly when isolated nodes rejoin the network.
Expose node status, contact condition and workflow state to operators.
Record decision receipts and mission evidence for later review and trust.
One lunar mission appears through three connected layers: physical infrastructure, distributed-system decisions and the operator view.
Where mission compute, storage, network interfaces and retained state physically live.
What the distributed system decides when power, storage, links and future contacts change.
How operators see terrain, asset state, network condition and mission events in one environment.
Science, resource or infrastructure data is created locally.
MoonCloud runs useful local workloads and retains state.
Prioritize, replicate, defer or transmit based on constraints.
Move the highest-value data when connectivity is available.
Receive mission products, receipts and synchronized state.
Present the same mission state as a coherent operating picture.
The clearest public explanation is a mission workflow: assets create data, CAIRN classifies and schedules it, MoonCloud preserves state and VirtualMoon shows the operational picture.
A rover acquires sensor data near an extraction site. CAIRN decides which products stay local, which move to a gateway and which are deferred until a future relay contact. MoonCloud preserves the mission ledger, local cache and synchronization history.
A sealed structural enclosure, passive thermal rejection surfaces, thermally managed mounts, recessed power/data ports, low-profile RF hardware and modular compute/storage define the external architecture.
A compact physical deployment layer for local mission compute, storage, state retention and network gateway functions, with structural fasteners, radiator surfaces, connector bays and mounting feet integrated into the product architecture.
The engineering model is organized around six core functions that remain common as processor, storage, radio and power configurations evolve.
Containerized workloads, local analytics and CAIRN agent execution.
Local cache, logs, ledgers, raw data and replication targets.
Local asset links, relay-facing interfaces and DTN-aware transfer.
Health monitoring, decision receipts, integrity and degraded-mode recovery.
Mission power interface, telemetry and policy-aware workload throttling.
Conduction paths, radiator surfaces and installation-specific thermal coupling.
COTS compute + NVMe + CAIRN + DTN testbed interfaces.
→Constrained processor, power and recovery behavior with flight-like interfaces.
→Containerized workload running on a hosted compute or relay platform.
→Local compute, cache, storage and gateway services under real lunar constraints.
This interactive panel shows the unified story: assets generate state, CAIRN adapts policy, MoonCloud retains continuity and VirtualMoon exposes the changing mission condition.
Compute placement and contact policy optimize delivery while preserving local mission continuity.
MoonCloud preserves mission continuity as relay windows change and surface assets partition and reconnect, with local state, decision receipts and data priorities retained across the network.
The near-term business starts with architecture, simulation, integration and demonstrator capability — then progresses toward deployment and hosted-node services.
Define the compute / storage / communications split for robotic, resource, logistics and science missions. Output: workload map, node roles, contact strategy and degraded-mode logic.
Compare transmit-all, DTN-only, fixed-edge and adaptive policies under power, outage and storage constraints. Output: reproducible scenarios, traces and mission-centric benchmark data.
Turn terrestrial computers and MoonCloud Nodes into a distributed lunar-compute demonstrator with injected partitions and resource limits.
Package edge applications and orchestration logic for embedded or hosted orbital environments. Output: containerized workload, interface package and recovery model.
Build a common operating picture around a site, asset set and network model for design reviews, rehearsals, technical presentations and partner alignment.
Compute, cache, storage and replication services exposed through shared cislunar infrastructure when hosted nodes and lunar service points become available.
CAIRN Mission Operations brings scenario control, network topology, asset state, resource telemetry, mission logs and decision receipts into one live orchestration environment.
VirtualMoon combines terrain intelligence, mission planning, CAIRN network state, asset health and Water Bank operations in one Shackleton mission environment.
Orbit, descent, surface views, site pack context and camera presets.
Site suitability, slope, uncertainty, routing, CAIRN line-of-sight and measurement tools.
CAIRN, WATERIG/OASIS, FIRN/TARN, FLARE, asset state, mission clock and Water Bank ledger.
IAC, IEEE, AIAA and SpaceCom presets with guided chapters, clean frame and presentation controls.
Working software, active integration environments and the deployment stages of the MoonCloud platform.
Live deterministic mission-operations demo with policy, network, event and autonomy views.
Offline Shackleton digital twin with Explore, Analyse, Operate and Present modes.
Distributed terrestrial nodes, fault injection, DTN integration and benchmark traces.
Physical compute/storage demonstrator with power, thermal and network telemetry.
Progress from embedded/HIL to orbital hosting and eventually a lunar surface service node.
The first useful form of the lunar cloud is a distributed computing utility proven step by step and expanded across terrestrial, orbital and lunar operations.
CAIRN simulator + MoonCloud nodes, real DTN where practical, workload placement, fault injection and benchmark traces.
Flight-like interfaces, constrained compute/power budgets and deterministic recovery behavior.
Remote update/recovery, DTN integration and real operations exposure in a hosted compute environment.
Local compute, storage, cache and autonomous continuity under lunar contact opportunities.
Cross-provider placement, replication, shared interfaces and persistent lunar edge-cloud utility services.
Start with the first useful node. Build outward into a persistent cislunar compute and storage fabric.