Aegis Orbital Compute Node (AOCN)

A 1 MW batch-compute node in a dawn-dusk orbit: power without a grid, heat without water, and a break-even stated in the open

AOCN Rev B in a dawn-dusk orbit: a single sunlit solar array sheet with the compute vault and two edge-on radiator wings in its shadow on a truss behind it, Earth's terminator, city lights and aurora below
Rev B — September 2026. Rebuilt from the sizing up. The orbit moves to a 650 km dawn-dusk sun-synchronous orbit, which has no eclipse season and deletes the battery problem. The node is sized as 1 MW of accelerator load, not 200–500 kW inside a 1–2 MW bus. Solar area is stated end-of-life with the derates shown. Water shielding is replaced by an aluminium compute vault with a planned refresh cycle. The page now says what the node is for, what the data path is, and at what launch price it beats a building. Rev 1.1 thermal arithmetic is retained and checked; its dossier remains available below.

What It Is

The Aegis Orbital Compute Node (AOCN) is a free-flying compute unit: one megawatt of commercial accelerators in a shielded vault, a fixed solar sheet that faces the sun all year, and pumped-loop radiators that never see it. It runs batch work: model training, large-scale inference, simulation, and the processing of data that is already in orbit. It does not run a cloud. Nothing on it answers a request in milliseconds, and nothing on it needs to.

The node is the unit of scale. Capacity grows by flying more of them, not by making one bigger. Every node is sized, launched, and serviced the same way, and the compute inside is expected to be replaced every three to five years while the power and thermal plant stays.

Orbit650 km dawn-dusk sun-synchronous, ~98° inclination
No eclipse at any point in the year above ~620 km; the sun stays within 24° of the orbit normal
Accelerator load1.0 MW IT
1.2 MW electrical at end of life, with pumps, conversion, comms and attitude control inside the 20 % overhead
Solar array5,400 m², fixed, no gimbal
~223 W/m² end-of-life after the derates in the power section
Radiators2,000 m² two-sided, 315 K mean
~590 W/m² effective; edge-on to the sun and to the Earth limb
Node mass~65 t with 20 % growth
Bottom-up budget in the mass section
ServicingRobotic, EVA-compatible interfaces
Unpressurised vault; compute trays swap on rails, wings and array blankets are line-replaceable

Why Put Compute in Orbit

The honest case is narrower than the slogans and stronger than the sceptics allow. Three things are true at once.

1. The constraint on Earth is the grid, not the chip

Terrestrial AI capacity is gated by interconnect queues measured in years, by water for cooling, and by siting permits. In orbit none of those exist. Power is not free; it costs launched array mass. But a square metre of array in a dawn-dusk orbit produces about four and a half times the energy of the same square metre on the ground, because it is lit 100 % of the time at full solar constant and needs no storage. The question is whether that buys back the launch cost, and the economics section answers it with a number rather than a mood.

2. Batch work does not need a fast link to Earth

Training a large model is weeks of computation on a dataset that arrives once and a result that leaves once. That is the opposite of a cloud workload. The dataset goes up on launched storage: ten petabytes on enterprise SSDs is under 200 drives and well under half a tonne. Checkpoints and weights come down over optical crosslinks. A dawn-dusk orbit passes a polar ground station on nearly every revolution, so downlink capacity is not the limit. The data section sizes it.

3. Some customers are already in space

Earth-observation constellations downlink raw data they could process in orbit. Cislunar operations, when they exist, will want compute that is seconds away rather than a round trip through Earth. This is the only case with no terrestrial competitor. It is also the smallest market today, which is why AOCN is not designed around it. It is designed so that the same node serves it when it arrives.

What AOCN is not. It is not a cloud region, not an edge for latency-sensitive traffic, and not a claim that orbital compute is cheaper today. At current launch prices it is two to five times the cost of a terrestrial hall for the same accelerators. The page states where that crosses over.

Data Path

LegMethodCapacityNote
Dataset upLaunched solid-state storage, installed with each compute refresh10 PB ≈ 164 × 61 TB drives, < 0.5 tCheaper and faster than any uplink; refreshed with the trays it feeds
Results downOptical to polar ground stations, Ka-band RF fallback~110 TB/day at 100 Gb/s over ~150 min of contactA 1 TB checkpoint at 10 Gb/s takes ~13 min; weather handled by station diversity
Tasking and telemetryRF, continuous via relaykb/s to Mb/sAutonomous operation between contacts; ground plans, node executes
Node to nodeOptical crosslink within a plane10–100 Gb/sFor distributed training across nodes in the same orbit plane; not required for a single node

Dawn-dusk sun-synchronous orbits cross both poles every ~97 minutes. A single high-latitude optical terminal sees the node on most passes; two terminals on different continents cover weather.

Orbit Selection

Rev 1.1 assumed a generic 500–600 km orbit with a 35 % worst-case eclipse and either 2.6 t of battery per megawatt or a throttled duty cycle. The battery figure was cell-level; at a LEO-survivable depth of discharge and pack overhead it is closer to 12 t per node. That is a sizing problem, not a barrier; a node with a battery is buildable. Rev B chooses the orbit that does not need one, because everything downstream gets simpler: a fixed array, a constant sun, one radiator plane, and no charge cycle every orbit. Nothing moves and nothing cycles.

A dawn-dusk sun-synchronous orbit keeps its plane at the day-night terminator all year. The sun sits within about 24° of the orbit normal. Above roughly 620 km the Earth never gets between the node and the sun, at any season. AOCN Rev B baselines 650 km.

Arrangement

Blueprint-style illustration of the AOCN Rev B arrangement: sun's-eye view of the array sheet with the vault and edge-on wings at its centre, a view along the flight direction with sun rays stopping at the array, the vault on the truss and two radiator wings behind, and detail insets of the array edge, vault, truss joint, radiator ribs and thruster pod
AOCN Rev B arrangement drawing: sun's-eye view of the 90 by 60 metre array sheet with radiators edge-on behind it, and a view along the velocity vector showing the array edge-on, the compute vault on a truss, and two 50 by 20 metre radiator wings

Thermal: Radiator Sizing

At steady state every watt of electrical input becomes heat. Commercial accelerators hold junction temperatures below about 363 K; direct liquid cooling delivers coolant at 305–320 K and returns it 10–15 K warmer. The radiator therefore runs between roughly 330 K inlet and 305 K outlet, a 315 K mean radiating temperature. Rev 1.1 stated 290–330 K; the same range, now pinned to a sizing point.

Two-sided rejection follows the Stefan-Boltzmann law with an emissivity of 0.88. An effective factor of 0.6 covers Earth infrared on the oblique face, view-factor losses between wings, coating degradation, and fin efficiency. With the array shading the wings and no direct solar load, this factor is conservative.

Mean radiating temperatureTwo-sided, theoreticalEffective (× 0.6)Area per MW rejected
300 K808 W/m²485 W/m²2,060 m²
310 K922 W/m²553 W/m²1,810 m²
315 K (baseline)983 W/m²590 W/m²1,700 m²
320 K1,046 W/m²628 W/m²1,590 m²
330 K1,183 W/m²710 W/m²1,410 m²

The node rejects 1.2 MW, so the baseline radiator area is ~2,000 m² two-sided, carried as two 50 × 20 m wings on a pumped single-phase loop with redundant pumps and isolable sections. At 6 kg/m² for deployable pumped-loop panels the wings weigh about 12 t. If a future accelerator generation tolerates hotter coolant, the same wings reject more; the plant does not need to change when the trays do.

Power: Solar Array Sizing

Rev 1.1 sized the array at ~2,500 m² per MW from beginning-of-life cell efficiency at normal incidence. That is the number for a new panel pointed perfectly on the day it deploys. The array has to make 1.2 MW on its last day, at its worst sun angle, through a blanket that is not all cells.

StepFactorRunning value
Solar constant × 29 % triple-junction GaAs—395 W/m²
Blanket packing (cells, gaps, harness, hinges)0.85336 W/m²
Radiation degradation, 10 years in a polar orbit0.85285 W/m²
Operating temperature derate0.85243 W/m²
Worst-season sun angle, fixed array (cos 23.4°)0.92223 W/m² end-of-life
Area per MW electrical, EOL~4,500 m²
Rev 1.1 said ~2,500; the difference is the derates, not the physics
Node array5,400 m² for 1.2 MW
Carried as a 90 × 60 m sheet; deployable-blanket mass ~2.5 kg/m², ~13.5 t
Capacity factor~100 %
Against 20–25 % for ground solar; the array's only real advantage, and it is a large one
StorageSafe-mode pack only
No eclipse to bridge; sizing on the order of 50 kWh for attitude, comms and heaters through a fault

Compute Vault and Radiation

Rev 1.1 carried 15–50 t of water and structure as shielding for a compute payload. That is a crew figure applied to electronics. Silicon does not need a storm shelter; it needs a tolerable total dose, a handled upset rate, and a refresh plan.

Mass Budget, 1 MW IT Node

GroupBasisMass (t)
Solar array sheet5,400 m² at 2.5 kg/m² deployable blanket13.5
Radiator wings and loop2,000 m² at 6 kg/m² pumped-loop panel12.2
Compute trays and storage1 MW IT at ~12 kg/kW, liquid-cooled rack density12.0
Vault structure and shielding⌀4 × 10 m shell, 10–15 mm Al-equivalent, rails5.0
Power conversion, distribution, pumps, fluid, avionics, commsAllocation5.0
Truss, deployment mechanisms, attitude control, electric propulsion and propellantAllocation7.0
Subtotal54.7
Growth margin, 20 %10.9
Node mass~65

Rev 1.1 carried 40–80 t for 200–500 kW of accelerator. Rev B carries ~65 t for 1,000 kW. The change is not optimism; it is the removal of the water shield and the batteries, and the accounting of compute at the density liquid-cooled racks actually achieve. The refresh cycle relaunches only the 12 t of trays.

Economics: Where It Crosses Over

Both an orbital node and a terrestrial hall buy the same accelerators, and those dominate the bill either way: on the order of $40–50 M per megawatt of current-generation hardware. What differs is the plant around them. A terrestrial AI hall costs roughly $10–15 M per MW to build, plus around $0.6–0.9 M per MW-year in energy. Over a five-year hardware life that is about $15–20 M per MW of plant and power, before the years spent waiting for an interconnect.

The orbital node replaces all of that with launch mass. At 65 t per megawatt:

Launch priceLaunch cost per MW nodeAgainst $15–20 M terrestrial plant + power
$3,000 /kg$195 M10× worse
$1,500 /kg$98 M5× worse
$500 /kg$33 M~2× worse
$300 /kg$20 Mparity
$200 /kg$13 Mbetter
$100 /kg$7 M2–3× better

The crossover sits near $300 per kilogram to sun-synchronous orbit, before counting on-orbit assembly, qualification, and the operations team, which push it lower, and before counting the value of skipping a multi-year grid queue, which pushes it higher. That price does not exist today. It is the stated goal of fully reusable heavy launch, and the point of writing the number down is that it is a launch-price gate, not a technology gate. Everything else on this page is buildable now.

Refresh. Each accelerator generation relaunches ~12 t of trays and storage per node. At $500 /kg that is $6 M against $40 M or more of hardware inside them, so refresh cost is not what decides the case.

Scaling

Nothing in the node gets easier when it gets bigger. Deployed area, bending modes, pointing disturbance, fault-domain size, and the mass of any single failure all grow faster than the compute they carry. A 1 MW node is already a 90 m sheet with 50 m wings. The unit is fixed and the fleet grows.

Beyond Earth Orbit

The node does not care which body it orbits, but the case does. Around the Moon or Mars there is no advantage until there are customers there, and the Earth link gets worse. Where the case changes is the lunar surface, and only one part of it.

The lunar surface as a heat sink, with the caveat

The daytime surface is not a cold sink. At the equator it reaches ~390 K at noon for two weeks, and regolith is an insulator, so nothing conducts into the ground worth counting. A radiator on the day side of the Moon looks at hot ground and a hot sun for 14 days and then at nothing but darkness for 14 more, with no power.

The polar surface is different. Rim sites near the south pole are lit 80–90 % of the year at grazing angles, and next to them are permanently shadowed floors at 40–100 K. A vertical radiator on a rim, facing the shadowed floor and the cold sky, rejects about 490 W/m² one-sided at 315 K with no Earth infrared and no solar load. Per square metre that is comparable to the orbital wing. The difference is everything around it: no launch of the plant from Earth once regolith structure and local water are available, no deployment mechanisms, radiators that can be built as walls, and the program's own water on site for thermal storage across the short polar nights.

The LEO node is the near-term product and the testbed for the plant. The lunar polar node is where the plant stops being launched. That is the same gate the rest of the program is waiting on: a viable moonbase and industrial-scale lunar water.

What Changed From Rev 1.1

ItemRev 1.1Rev B
Orbit500–600 km, generic; 35 % eclipse650 km dawn-dusk sun-synchronous; no eclipse
Eclipse storage2.6 t/MW battery or throttlingSafe-mode pack only
Accelerator load200–500 kW in a 1–2 MW bus1.0 MW IT, 1.2 MW electrical
Radiator area1,800–3,300 m²/MW at 290–330 K~1,700 m²/MW at 315 K mean; 2,000 m² per node
Solar area~2,500 m²/MW, beginning of life~4,500 m²/MW end of life; 5,400 m² per node
Shielding15–50 t water and structure~5 t aluminium vault; 3–5 year tray refresh
Node mass40–80 t~65 t, bottom-up with 20 % growth
Use case"Power density, thermal isolation, space adjacency"Batch training and inference; space-native data second
Data pathNot statedLaunched storage up, optical down, budget stated
EconomicsNot statedBreak-even near $300/kg to SSO, shown as a table

Technical Reference

The Rev B architecture reference document carries the sizing set above with its bases, the mass budget, the economics table, and the lunar polar variant.

View / Technical Dossier (PDF) — Rev B
If the PDF doesn't open in your browser, right-click and choose "Save Link As…"
Rev 1.1 dossier (archived, February 2026)