Western Orbital Compute, Under Review: Starcloud Moves Fastest, Google Reasons Best
A layered review of Starcloud, Google Suncatcher, Axiom, Kepler, NVIDIA and Cowboy Space - and of the thermal, bandwidth, radiation and capital-sovereignty constraints that will determine whether orbital compute becomes infrastructure or remains narrative.
Author
Dylan
Singapore Space Agency
Published
27 May 2026
Last updated
27 May 2026
40 min read · 5,428 words · Market Intelligence

Quick summary
What this article answers
- Western orbital compute is a four-layer ecosystem spanning compute nodes, optical networks, payload platforms, and component infrastructure; ranking every participant together obscures more than it reveals.
- Starcloud has moved fastest in hardware, while Google Suncatcher has published the strongest system-level engineering case and radiation evidence.
- Thermal rejection and useful space-to-ground bandwidth, not headline accelerator performance, are the constraints most likely to govern commercial scale.
- For Asia-Pacific, the strongest openings are thermal systems, optical components, orbital runtimes, and neutral governance rather than another undifferentiated GPU satellite.
The real bottlenecks are thermal control, bandwidth, and the nationality of capital - a layered map from Starcloud to Google Suncatcher, two deep technical dissections, and structural implications for Asia-Pacific founders.
Report date: May 27, 2026 Author: Dylan | Singapore Space Agency
This is the mirror report to “China's Orbital Compute Reality Check.” The methodology is identical; the two pieces are designed to be read together.
Disclaimer: The progress scores in this report measure publicly verifiable progress, not investment value or the probability of future returns. Every numbered factual citation maps to the source list below. Claims that could not be independently verified are labelled accordingly. Nothing in this report constitutes an endorsement of any orbital-compute company.
Methodology: As in the China report, the score weights verifiable in-orbit facts at 35%, regulatory and official documents at 20%, commercial customers and revenue validation at 20%, the scaling engineering path at 15%, and financing and capital signals at 10%.
1. The 90-Second Summary
Western orbital compute is not one market. It is four overlapping layers: compute-node operators such as Starcloud and Axiom; optical-network providers such as Kepler; payload-platform companies such as Loft Orbital; and infrastructure suppliers such as Spacebilt and Sophia Space. Ranking all four on one progress table produces a false comparison.
Starcloud: the first high-performance GPU validation in orbit. The business model is not yet closed, and thermal management is its most important genuine differentiator.
Google Suncatcher: the most complete technical argument in the field. Its Trillium TPU radiation test is the strongest public hardware-reliability dataset so far. Yet its 1.6 Tbps inter-satellite link is constrained by a much narrower atmospheric downlink. That gap is the sector's most underappreciated technical limitation.
Axiom Space: the largest number of operational ODC nodes in orbit, at two. Its route is space-station infrastructure, not a general-purpose AI cloud.
NVIDIA Space-1, built around the Vera Rubin Module: no delivered hardware yet, but NVIDIA has already pulled almost every leading Western participant into CUDA. It is conducting a preventive ecosystem capture before a neutral “Space Android” can form.
Cowboy Space: a $2 billion valuation with no orbital compute and no demonstrated power-beaming system. At roughly 5-8% end-to-end efficiency, the energy-transfer proposition is close to absurd on ordinary commercial economics.
The Asia-Pacific opportunity: not another Starcloud clone, but thermal subsystems, laser-communications components, orbital inference software, and a neutral compute platform that is not constrained by U.S. sovereign capital such as In-Q-Tel.
2. Methodology and Fact Status
This report gives the highest weight to demonstrated in-orbit facts and the lowest weight to financing announcements and future plans.
- Confirmed: official announcements, academic papers, Axiom and Google pages, and YC company materials.
- Media reported: TechCrunch, SiliconAngle, SpaceNews, IEEE Spectrum, and comparable publications. Credible, but their framing still matters.
- Author inference: independent analysis derived from public facts and clearly identified as such.
3. Why Orbital Compute Became a Capital Story in 2025-2026
Before comparing companies, the underlying drivers need to be sized honestly.
Terrestrial data centers are running into a historic convergence of constraints. The International Energy Agency estimates that global data centers consumed about 415 TWh in 2024, or 1.5% of worldwide electricity, and projects roughly 945 TWh by 2030.^[1] In Northern Virginia, California, Germany, and other core markets, grid-connection queues have become materially longer. This is no longer only a capital problem; it is a physical-infrastructure problem.
Jensen Huang's directional point is more important than the disputed number. Huang has described agentic AI as much more compute-intensive than conversational generation. Some reports rendered the increase as “1,000 times,” others as “1,000%,” or roughly ten times.^[2] The multiple is debatable. The direction of travel is not.
The physical advantage is real, but conditional. In a sun-synchronous dawn-dusk orbit, satellites can remain illuminated for most of each orbit. They avoid terrestrial weather, night, and atmospheric losses. Some studies estimate an energy-yield advantage near five times, depending on system boundaries. Vacuum also permits heat rejection through radiation. But “space is cold” is not an engineering solution; the radiator problem becomes harder as power density grows.
The cost threshold is unforgiving. Google's internal work suggests launch prices need to fall toward roughly $200/kg before orbital data centers can compete economically on energy.^[3] Starship might approach that range in the mid-2030s if commercialization and reuse work as intended.
4. The Layered Ecosystem: Not a Single Progress Ranking
Kepler Communications and Starcloud are not direct comparables. Kepler is building an optical relay network; Starcloud is operating GPU spacecraft. A useful map separates the layers first.
4.1 Four Layers
| Layer | Core role | Representative participants | What it contributes |
|---|---|---|---|
| 1. Compute nodes | Operate orbital compute assets | Starcloud, Axiom Space ODC, Google Suncatcher | Put GPUs, TPUs, and data-center nodes into orbit |
| 2. Optical network | Connect nodes and ground | Kepler Communications, Skyloom | Inter-satellite and space-to-ground optical relay |
| 3. Payload platform and interfaces | Standardize deployment and control | Loft Orbital, Sophia Space | Mission control, payload interfaces, modular compute tiles |
| 4. Components and infrastructure | Supply the underlying system | Spacebilt, OrbitsEdge, NVIDIA Space-1 | Storage, thermal systems, compute modules, and chip ecosystems |
SpaceX+xAI may eventually span all four layers if the reported corporate integration and orbital-data-center plans mature. Today, however, it is still more strategic intent than operational compute hardware.

4.2 Compute-Node Progress
SpaceX is used as a 100% benchmark for integrated control capacity, not as a claim that it has already commercialized orbital compute.
| Company | Position | In-orbit state | Progress range | Core fact |
|---|---|---|---|---|
| SpaceX+xAI | Integrated-control benchmark | 10,000+ Starlink communications satellites; AI data centers still planned | 60-70% | Reported FCC application near one million AI satellites; Terafab plan announced by Musk |
| Starcloud | Dedicated GPU satellite | H100-class LLM work in orbit | 45-55% | First high-performance GPU validation in orbit, November 2025 |
| Google Suncatcher | TPU plus formation flight | None; prototype planned for 2027 | 35-45% | Most complete public radiation dataset; 1.6 Tbps laboratory optical link |
| Axiom Space ODC | Space-station infrastructure | Two ODC nodes in orbit, January 11, 2026 | 30-38% | Largest number of operational orbital data-center nodes |
| Cowboy Space | Power beaming plus compute | No orbital compute | 10-20% | $275 million round, $2 billion valuation, estimated 5-8% transfer efficiency |
4.3 Network, Platform, and Component Players
| Company | Layer | Core capability | Current state |
|---|---|---|---|
| Kepler Communications | Optical network | Inter-satellite and space-to-ground relay | Nine relay satellites in orbit by Q4 2025; 2.5 Gbps commercial service |
| Loft Orbital | Payload platform | Standardized payload interface and mission control | Hub Compute demonstration in orbit; €170 million financing |
| Sophia Space | Payload and compute tile | Modular compute tile | NVIDIA partnership; small-scale testing on Kepler spacecraft |
| Spacebilt | Components and infrastructure | Storage and compute infrastructure | ISS node planned; Axiom partnership; petabyte-scale orbital-storage ambition |
| OrbitsEdge | Thermal and components | Liquid-cooled SatFrame | Patented liquid-cooling approach; ground validation |
| NVIDIA Space-1 | Chip ecosystem | Vera Rubin Module, claimed at 25x H100 | Product announcement 70%; delivered hardware 0% |
5. Starcloud: A 17-Month Unicorn and the H100-First Bet
5.1 History: Recognizing a Convergence
Starcloud did not begin with a singular technical breakthrough. It began with a timing thesis: around 2024, the launch-cost curve and the AI-compute-demand curve were starting to intersect.
Philip Johnston identified the opportunity while advising government space organizations at McKinsey. His logic was straightforward: if terrestrial data centers are constrained by electricity and heat rejection, and orbit offers structural advantages in both, then falling launch costs make the economics worth calculating for the first time.
The founding team combines three deliberately complementary backgrounds:
| Role | Person | Background | Likely contribution |
|---|---|---|---|
| CEO | Philip Johnston | McKinsey space consulting; Harvard MPA; Wharton MBA; Columbia applied mathematics; CFA | Strategy, financing, customer development |
| CTO | Ezra Feilden | Ten years at Airbus Defence and Space; large deployable structures | Radiator and thermal-system architecture |
| Chief Engineer | Adi Oltean | Twenty years in Microsoft Azure GPU clusters; SpaceX Starlink beam tracking | Orbital GPU workloads and network integration |
These role descriptions are external inferences from public biographies, not internal company definitions.
| Date | Milestone |
|---|---|
| January 2024 | Founded in El Segundo as Lumen Orbit |
| February 2024 | Moved to Redmond, near Starlink, AWS, and Azure talent |
| Summer 2024 | Joined YC S24 |
| Early 2025 | Renamed Starcloud, shifting the frame from “orbit” to “cloud” |
| Early-mid 2025 | Raised about $21 million from NFX, YC, In-Q-Tel and others; joined NVIDIA Inception |
| November 2025 | Launched Starcloud-1 with an H100 pathway; a separate A6000 payload was damaged during launch |
| December 2025 | Trained NanoGPT in orbit and ran Gemma-related workloads |
| March 2026 | Raised $170 million led by Benchmark and EQT Ventures at a $1.1 billion valuation; total funding about $200 million |
| October 2026, planned | Starcloud-2 with H100, Blackwell B200, and a large deployable radiator |
In-Q-Tel is not a footnote. As the U.S. intelligence community's venture investor, its participation signals that orbital compute has sovereign value: sensitive data can be processed on nationally controlled spacecraft without passing through foreign-influenced ground infrastructure.
5.2 Six Subsystems
Thermal Management
Thermal control is the hardest physical constraint and Starcloud's most credible differentiator. In vacuum, waste heat cannot leave through atmospheric convection. It must be radiated.
Stefan-Boltzmann relation:
P = ε × σ × A × T⁴, whereεis emissivity,σ = 5.67 × 10⁻⁸ W/(m²·K⁴),Ais radiator area, andTis temperature in kelvin. Atε = 0.9andT = 350K, ideal heat rejection is about766 W/m².
| Heat load | Ideal radiator area | Practical implication |
|---|---|---|
| 40 kW, estimated Starcloud-2 scale | ~52 m² | Real area may be 2-3x after view factors, sunlight, Earth IR, and structural efficiency |
| 1 MW | ~1,307 m² | Large deployable structure |
| 100 MW | ~130,700 m² | Roughly 18 football pitches |
| 5 GW hypercluster vision | ~6.53 km² | Roughly 900 football pitches |
Starcloud-1's roughly 400 W H100-class load could use body conduction and passive surface radiation. Starcloud-2 claims the largest commercial deployable radiator attempted in this category.^[4] The hundred-fold increase in power generation requires a qualitatively different thermal system. That challenge maps directly to Feilden's Airbus experience in large deployable structures.
The inferred architecture uses heat pipes from processors to radiator panels, high-emissivity coatings around ε = 0.85-0.92, anti-solar radiator orientation, and eventually multi-square-kilometer structures for hyperclusters. Passive heat pipes and radiators have decades of space heritage. Active liquid cooling is denser, but pumps, seals, and leakage introduce reliability risks that have not been validated for this use at scale.
Compute Hardware
Starcloud chose not to design a dedicated space chip. It put leading terrestrial accelerators into space. Johnston summarized the bet plainly: the H100 may not be the ideal space chip, but the company wanted to prove that state-of-the-art terrestrial hardware could operate there.^[5]
The benefits are immediate CUDA compatibility, genuine data-center performance, and a shorter development cycle. The costs are radiation exposure, thermal shock, single-event upsets, and a heavier dependence on software ECC and fault recovery.
The separate A6000 damaged during launch is an important negative data point.^[5] Launch vibration and shock, roughly 20-100g in relevant events, make mechanical hardening and isolation first-order design requirements.
Starcloud-2 is described as carrying H100 and Blackwell B200 accelerators, plus Bitcoin ASICs to monetize otherwise idle power. A lower-grade report says AWS, Google Cloud, NVIDIA, and Crusoe delivered hardware to the Redmond integration facility; that detail remains unconfirmed.^[6]
Satellite Platform
Starcloud builds its own bus rather than purchasing a standard GomSpace- or EnduroSat-class platform. Conventional commercial buses are designed for much lower thermal loads. The Redmond payload-manufacturing facility gives the company tighter control over quality and iteration.
The likely orbit is a 500-600 km sun-synchronous orbit, chosen for high illumination, a stable radiator view to deep space, roughly 5 ms propagation latency, and a manageable lifetime.
Software and Operations
Oltean's Azure and Starlink background appears in three architectural choices: containerized deployment for minimally modified CUDA workloads; disconnected operation because ground-station windows are intermittent; and a software fault-tolerance layer to detect and recover from radiation-induced errors.
Communications
This is the least disclosed subsystem. Four commercial customers need meaningful uplink and downlink capacity. Plausible paths include mature but narrower Ka/Ku-band radio, higher-capacity laser links, and third-party networks such as AWS Ground Station.
The unresolved question is simple: what sustained downlink can Starcloud-2 deliver? The answer determines which AI workloads make economic sense.
Launch
SpaceX Transporter rideshare, around $6,000/kg to SSO, is the most economical reliable option currently available. It also creates strategic dependence on a supplier that is planning its own orbital data centers. If SpaceX prioritizes Starship capacity for internal AI spacecraft, the impact on Starcloud would be direct.
5.3 What the Business Can Sell Now
| Customer group | Current state | Why it may pay a premium |
|---|---|---|
| In-orbit processing for other satellites | Nearest-term; Capella SAR processing under validation | Less downlink demand and faster remote-sensing output |
| Sovereign-sensitive compute | In-Q-Tel signal indicates real demand | Data does not pass through foreign ground stations |
| AI workloads cheaper than terrestrial compute | Long-term; depends on launch near $200/kg | Energy economics, probably after 2030 |
Bitcoin ASICs are cash-flow engineering, not merely compromise. A 10%-utilized H100 costs the same to orbit as a 90%-utilized one but can produce one-ninth of the revenue. Mining can absorb unused electrical output while the AI customer base develops.
5.4 Real Moats and Questionable Ones
| Claim | Assessment | Durability |
|---|---|---|
| First H100-class orbital validation | Real and completed | Medium; Google can narrow the gap |
| Large deployable radiator capability | Real engineering capability | High |
| Low-friction CUDA migration | Real software capability | High |
| First-mover commercial customers | Media reported; still to verify | Medium |
| YC and Benchmark endorsement | Real recruiting and financing advantage | High |
6. Google Project Suncatcher: System Engineering Before Spectacle
6.1 Starcloud Proves It Can Fly; Google Models the Whole System
Google is not proving that an accelerator can run in orbit; Starcloud already did that. Google is testing whether self-designed TPUs, formation flying, optical networking, radiation reliability, and launch economics can form one coherent system.
The DeepMind and Google Research paper makes Suncatcher the most technically transparent project in the sector and gives its published parameters unusually high credibility.^[7]
6.2 Four Critical Design Decisions
Trillium TPU v6e Instead of a Commodity GPU
Google owns the TPU stack. That offers better AI performance per watt, the possibility of radiation-aware design, and native integration with JAX and TensorFlow.
Its radiation test is the strongest public hardware-reliability result in the field.^[7]
| Test dimension | Result |
|---|---|
| Environment | 67 MeV proton beam simulating a 650 km LEO environment |
| Expected five-year dose | About 750 rad(Si) |
| HBM irregularities begin | 2 krad(Si), about 2.7x the expected five-year dose |
| No hard HBM failure | Through 15 krad(Si), about 20x the expected dose |
| Compute core | Continued operating correctly at 15 krad(Si) |
| Conclusion | Unhardened commercial AI silicon can plausibly support a five-year mainstream-LEO mission without severe reliability failure |
This result benefits the entire sector, including H100-based systems.
An 81-Satellite Distributed Compute Unit
A single spacecraft is constrained by mass and dimensions. Google's answer is an 81-satellite cluster flying hundreds of meters apart and connected by lasers.
| Design parameter | Research configuration |
|---|---|
| Orbit | About 650 km, sun-synchronous dawn-dusk |
| Example cluster | 81 satellites within a radius near 1 km |
| Separation | Hundreds of meters |
| Formation | Rotating ellipse with two shape cycles per orbit |
| Disturbances | J2 oblateness, residual drag, solar-radiation pressure |
| Control | Backpropagation-trained ML model predicts disturbances |
| Propulsion | Described as modest and within an acceptable propellant budget |
If demonstrated, the satellites could operate like servers in a rack while remaining independently flying vehicles.

1.6 Tbps Between Satellites, Then a Narrow Exit to Earth
Google demonstrated a 1.6 Tbps free-space optical link between a transmitter and receiver in the laboratory.^[7] The widely quoted number is inter-satellite bandwidth. Results still need to cross the atmosphere.
| Space-to-ground constraint | Operational effect |
|---|---|
| Clouds | Tropical annual cloud cover can reach 60-80%; an optical link is unavailable when blocked |
| Atmospheric turbulence | Scintillation and random signal variation reduce effective throughput |
| Rain | Scattering can interrupt or severely degrade the link |
| Pointing | Milliradian-class accuracy over hundreds of kilometers becomes harder through turbulence |
Commercial optical downlinks can reach tens of Gbps in clear weather, but average usable throughput after weather and availability may be closer to 1-10 Gbps, particularly in tropical regions. That is one to three orders of magnitude below the internal cluster link.
| Near-term fit | Workload | Why |
|---|---|---|
| High | In-orbit remote-sensing processing | A 10 GB SAR image can become a 1 MB anomaly report before downlink |
| High | Autonomous decisions and sensor fusion | Compute stays in orbit; only key results return |
| Medium | Long-running batch work | Low real-time requirement; uses ground-pass windows |
| Low | Large-scale AI training | Requires continuous, high-bandwidth interaction |
| Low | Interactive inference | Users expect millisecond responses; access windows are limited |
| Low | High-throughput generic processing | Downlink becomes the system bottleneck |
Google's response is in-space reduction: do most processing in orbit and downlink the result rather than the raw data, potentially reducing traffic by 85-95%. That is sensible, but it also means orbital compute is a specialized tool before it becomes a general-purpose cloud.
Sundar Pichai has been unusually direct that the project still requires solving many complex engineering problems.^[8]
A Precise Economic Condition
Google's analysis places competitiveness near $200/kg launch.^[3] Historical learning curves suggest the mid-2030s as a plausible window only if Starship commercialization proceeds well.
6.3 Google's Moats
| Advantage | Nature | Durability |
|---|---|---|
| Complete Trillium radiation dataset | Industry-grade technical evidence | Very high |
| TPU performance per watt | Chip-design capability | Very high |
| ML formation-flight control | Proprietary orbital knowledge | High |
| Planet partnership | Manufacturing execution | Medium |
| Balance-sheet depth | No dependence on venture rounds | Very high |
| TPU-to-JAX application stack | Vertical software integration | Very high |
Google's weakness is speed. Starcloud moved from formation to launch in 22 months; Google announced in 2025 and targets two prototypes in 2027. That is not a moral judgment. It is a structural difference in learning cadence.
7. Three Technical Walls: Heat, Radiation, Bandwidth
7.1 Thermal Wall
| Approach | Representative company | State | Advantage | Risk |
|---|---|---|---|---|
| Passive radiation and deployable panels | Starcloud-2, Suncatcher | Starcloud-2 planned for Q4 2026 validation | Long heritage; no pump required | Large area and complex deployment |
| Thermal tiles | Axiom and Spacebilt | Two ODC nodes in orbit; validation pending | Integrated with structure | Limited surface area |
| Dual-sided modular tile | Sophia Space | Design and early test phase | Whole surface participates | Orientation complexity |
| Active liquid cooling | OrbitsEdge | Ground validation | More compact | Pump, pipe, seal, and leakage risk |
| Scale | Heat and area | Engineering meaning |
|---|---|---|
| Current, Starcloud-2 class | ~40 kW; ~52-156 m² including margin | Feasible deployable structure, now awaiting validation |
| Mid-term, 1-10 MW | ~1,300-13,000 m² | Tens-to-hundreds-of-meters structures; stiffness, deployment, and thermal fatigue dominate |
| Far-term, 100 kW × one million | ~130 m² each; ~1,300 km² total | Enters the territory of science-fiction-scale orbital construction |
Passive radiation is the most mature route today. Its area requirement makes scale equivalent to constructing progressively larger structures in orbit. Active liquid cooling may matter for dense systems later, but long-duration reliability is unproven.
7.2 Radiation Wall
Google's Trillium test and Starcloud's H100 operation together show that commercial AI chips can work in mainstream LEO for a reasonable mission duration without traditional radiation hardening.
Unresolved questions remain: degradation beyond five years; altitude and inclination differences; shielding mass versus dose; and chip-to-chip manufacturing variation. A true radiation-engineered Vera Rubin Space Module could industrialize the answer, but delivery remains “at a later date.”
7.3 Bandwidth Wall
| Link | Peak | Practical throughput after availability | Commercial state |
|---|---|---|---|
| Ka-band RF | Hundreds of Mbps to ~1 Gbps | Relatively stable; rain affected | Mature |
| Ku-band RF | Tens of Mbps to ~500 Mbps | Relatively stable | Mature |
| Commercial optical downlink | 1-100 Gbps in clear weather | Roughly 1-10 Gbps after cloud effects | Operating through Kepler, Tesat, and others |
| Google inter-satellite optical | 1.6 Tbps in laboratory | Not yet validated in orbit | Prototype target 2027 |
The critical number for commercial orbital compute today is not 1.6 Tbps. It is roughly 1-10 Gbps of useful space-to-ground capacity.
8. NVIDIA's Strategic Board: Capturing the Ecosystem Before Space Android Exists
8.1 The Partner List Matters More Than the Ship Date
At GTC 2026, NVIDIA announced the Space-1 Vera Rubin Module, claimed 25x H100 performance, and gave availability as “at a later date.”^[9]
Its partners include Cowboy Space, Axiom Space, Kepler Communications, Planet Labs, Sophia Space, and Starcloud - almost the entire leading Western field.
8.2 Preventive Ecosystem Capture
Before the commercial orbital-compute market exists, NVIDIA is making CUDA the default:
- Partner software is written for CUDA.
- Engineers optimize for NVIDIA hardware.
- Customer workloads arrive as CUDA-native code.
- Switching to AMD, a custom ASIC, or photonics requires expensive rewrites.
When the Vera Rubin module ships, these firms will be the natural first customers because their stacks are already aligned.

8.3 What This Does to Space Android
The emerging Western structure looks less like Android and more like Wintel: operators manufacture spacecraft around a chip and software ecosystem they do not control.
China is excluded from that stack by U.S. export controls. The forced separation is also an opening for Cambricon-class domestic chips and photonic-compute routes. A neutral Asia-Pacific platform would need a non-CUDA compatibility layer, multi-chip hardware support, and governance independent of U.S. sovereign capital. Satisfying all three is difficult, but that is what a genuine Space Android would require.
9. Capital Geopolitics: Compute Has a Nationality
| Company | Important capital source | Sovereignty implication |
|---|---|---|
| Starcloud | In-Q-Tel, Benchmark, EQT | Intelligence-linked capital sends a clear sovereignty signal |
| Cowboy Space | Mainstream U.S. venture and climate capital | U.S.-aligned, without an obvious intelligence investor |
| Google Suncatcher | Internally funded | U.S.-based company subject to U.S. legal frameworks including FISA 702 |
| Axiom Space | Private rounds plus government contracts | Material dependence on NASA and defense relationships |
In-Q-Tel was created by the CIA in 1999 to invest in strategically useful technology. Its investments commonly bring close engagement with the U.S. intelligence community, ITAR/EAR compliance, and sometimes limits on foreign participation. For Starcloud, the investment validates defense relevance and may constrain service to some foreign customers.
| System | Priority customers and governance | Technical and capital constraints | Asia-Pacific implication |
|---|---|---|---|
| U.S. sovereign compute | U.S. government, Five Eyes, NATO allies | CUDA; ITAR/EAR | Non-allied customers may face service restrictions |
| Chinese sovereign compute | Chinese government and Belt and Road projects | Domestic chips and Chinese regulatory architecture | Political barriers for neutral customers |
| Neutral APAC compute | Customers seeking data sovereignty outside either bloc | Standards and capital structure do not yet exist | Potential demand in the GCC, non-aligned ASEAN, and sovereign-sensitive workloads |
For a company selling “neutral” compute, capital cannot be treated as cosmetic. U.S. sovereign-linked money and Chinese state capital both define customer boundaries. Potential alternatives include Singaporean, Gulf, Japanese, or Korean institutional capital, with careful governance design.
10. Cowboy Space: The Power-Beaming Problem Behind a $2 Billion Valuation
Cowboy Space, formerly Aetherflux, raised $275 million at a $2 billion valuation in May 2026.^[10] Its concept combines orbital solar generation, laser power beaming, and in-orbit compute.
10.1 The Physics Bill
| Conversion stage | Estimated efficiency |
|---|---|
| Orbital solar energy to electricity | 28-32% |
| Electricity to high-power laser | 40-50% |
| Laser through atmosphere in clear weather | 60-70% reaches the ground; less after weather availability |
| Ground photovoltaic receiver | 40-50% |
| Estimated end-to-end efficiency | 0.30 × 0.45 × 0.70 × 0.45 ≈ 4.3% |
Only about 4-5 W of 100 W collected in orbit may reappear as electricity on the ground. Using the same power for compute in orbit and sending down a small result is energetically far more attractive.
That does not invalidate every Cowboy use case. Power beaming may serve defense bases or disaster zones; compute may generate most revenue; and external observers cannot know how much of the valuation is assigned to each component. But if power beaming is the primary commercial thesis, the efficiency is a fundamental obstacle.
The company has no orbital compute demonstration, no power-beaming demonstration, and targets a first internally built rocket flight in 2028. The valuation-to-hardware ratio is the most aggressive in the sector.
11. Axiom Space ODC: The Underestimated Operational Route
Axiom deployed two ODC nodes on January 11, 2026.^[11] That makes it a real orbital-compute event alongside Starcloud and ahead of Google's prototype.

| Dimension | Axiom ODC | Starcloud |
|---|---|---|
| Positioning | Space-station infrastructure | Dedicated compute-satellite operator |
| Nodes in orbit | Two, January 2026 | One, November 2025 |
| Architecture | Distributed ODC nodes | High-density GPU spacecraft |
| Partners | Kepler, Spacebilt, Skyloom, Phison, Microchip | AWS, Google Cloud, NVIDIA, Crusoe |
| Scaling path | Satellite nodes to ISS to commercial station | Satellite to hypercluster |
| Thermal route | Thermal tiles with Spacebilt | Large deployable radiator |
Axiom's advantage is orbital real estate. A station offers more volume, power, and thermal infrastructure than a small satellite. A planned optical ODC node on the ISS in 2027 could use existing station systems.
Its limitation is equally clear: this is not a general AI cloud. It serves companies processing space-generated data, and its scale depends on station construction.

12. What Would Falsify This Report
| Scenario | Judgment affected |
|---|---|
| Starcloud-2 launches successfully but customer utilization stays below 20% | Commercialization moves later; Bitcoin mining becomes the primary bridge revenue |
| Google's 2027 prototype achieves 1.6 Tbps in orbit and solves downlink through site diversity | Google's route moves materially faster |
| SMR nuclear, subsea, or polar terrestrial data centers ease power and heat constraints | Orbital compute loses relative advantage |
| Launch remains above $2,000/kg through 2030 | Economic feasibility moves later |
| Customers reject sensitive workloads in orbit because of insurance, regulation, or sovereignty | Sovereign-compute demand is weaker than expected |
| Vera Rubin Space ships before 2027 | Existing chip comparisons become obsolete |
| Large neutral capital outside In-Q-Tel/CIA-linked structures enters Asia-Pacific | The neutral Space Android route becomes more credible |
13. Asia-Pacific Founders: Four Traps and Four Structural Openings
13.1 Trap: Repeating Starcloud's Milestone
Putting an H100 in orbit was valuable when Starcloud did it in November 2025. Being second has little incremental value unless the new system is cheaper, denser, better cooled, regionally differentiated, or built for a different sovereignty regime.
13.2 Trap: Taking Sovereign U.S. Capital While Claiming Neutrality
Capital nationality defines compliance boundaries. A company funded by intelligence- or defense-linked capital cannot credibly promise unrestricted neutrality to every market.
13.3 Trap: Treating 1.6 Tbps Inter-Satellite Bandwidth as Service Capacity
The service bottleneck is downlink, not an internal laboratory link. A business model must be designed around useful space-to-ground throughput.
13.4 Trap: Entering CUDA and Expecting to Own the Standard
A fully CUDA-dependent company can be successful, but it is an NVIDIA hardware contractor, not the owner of a neutral platform standard.
13.5 Opportunity: Specialized Thermal Engineering
Every winner will need better cooling. Japan, Korea, and Singapore have relevant precision-manufacturing capability in high-emissivity coatings, space-grade heat pipes, large deployable structures, and in-orbit thermal-testing services.
13.6 Opportunity: In-Orbit Processing of Asia-Pacific Data
The region produces dense remote-sensing demand: South China Sea vessel monitoring, tropical forest change, typhoon tracking, and ocean-temperature observation. Local data partnerships, regional regulatory knowledge, and Asia-Pacific service windows can become genuine advantages.
13.7 Opportunity: Neutral Compute Governance
Singapore's strongest role may not be building satellites. It may be the legal and governance home for a platform serving non-aligned Southeast Asian, GCC, and South Asian customers: a trusted intermediary rather than the asset owner.
That requires a credible multi-party governance architecture under which governments with different political alignments are willing to place sensitive data.
13.8 Opportunity: A Non-NVIDIA Orbital Runtime
A multi-chip runtime supporting ARM, AMD, Cambricon-class hardware, and photonic accelerators could become the real orbital Android. ROCm and OpenCL exist on the ground, but no mature layer is optimized for intermittent links, radiation faults, orbital autonomy, and heterogeneous space hardware.
The work is software-heavy rather than launch-heavy. It requires the unusual combination of orbital dynamics, GPU programming, and fault-tolerant systems engineering.
13.9 Timing
The direction is established, but the true commercial window is more likely 2027-2030, after Starship economics and Vera Rubin delivery become clearer. The rational strategy is to build thermal, optical, and inference capabilities now, then enter the market in 2027-2028.
14. The Data Points That Matter Over the Next 12 Months
| Indicator | Timing | Why it matters | Effect on the thesis |
|---|---|---|---|
| Starcloud-2 launch and orbital performance | October 2026 | First major deployable-radiator test and real customer workloads | Tests the thermal route and business model |
| Actual utilization from four customers | Q4 2026-Q1 2027 | Shows whether customers pay to use orbital GPUs | Most important commercialization signal |
| Google and Planet two-satellite prototype | Early 2027 | First formation-flight, Trillium, and downlink measurements | Major validation of Google's architecture |
| Axiom ISS ODC node | 2027 | Tests station-based compute and petabyte storage | Compares station infrastructure with free-flying satellites |
| Commercial Starship price | Unknown | Largest external variable for the sector | Changes feasibility for every participant |
| Vera Rubin Space delivery | “At a later date” | Makes current performance comparisons obsolete | Resets chips and accelerates CUDA lock-in |
| Further U.S. sovereign-capital penetration into European players | Ongoing | Defines how much neutral capital space remains | Determines the scale of the APAC-neutral opportunity |
This report is based on public information available through May 20, 2026. Every progress score is a directional author assessment, not an engineering measurement or investment recommendation.
Sources
- 1.IEA — Energy and AI(iea.org)
- 2.ServiceNow Knowledge 2026 Conference; Glitchwire, May 2026. Jensen Huang's directional statement on agentic-AI compute, with inconsistent multiples across reports. B-grade source.
- 3.Google Research — Project Suncatcher: An AI Research Moonshot(research.google)
- 4.SiliconAngle, Starcloud Series A report, March 30, 2026. “Largest commercial deployable radiator” claim. B-grade source.
- 5.TechCrunch interview with Philip Johnston, March 2026. H100 rationale and A6000 launch damage. B-grade source.
- 6.Tech-Insider report on Starcloud-2 hardware deliveries from AWS, Google Cloud, NVIDIA, and Crusoe. Not independently confirmed. C-grade source.
- 7.Google Research — Project Suncatcher(research.google)
- 8.Google — Project Suncatcher(blog.google)
- 9.NVIDIA — NVIDIA Launches Space Computing Platform(nvidianews.nvidia.com)
- 10.TechCrunch — Cowboy Space raised $275M to build rockets for space data centers(techcrunch.com)
- 11.Axiom Space — Orbital Data Center(axiomspace.com)
- 12.Y Combinator — Starcloud(ycombinator.com)
- 13.SpaceNews, Axiom and Kepler partnership coverage, April 2025. ODC technical details. B-grade source.
- 14.Data Center Dynamics, Google and Planet partnership coverage, December 2025. Prototype details. B-grade source.
- 15.IEEE Spectrum, Nvidia H100 in Space, November 2025. Starcloud-1 orbital validation. B-grade source.
- 16.SatNews, The Physics Wall, March 17, 2026. Thermal architectures and Stefan-Boltzmann constraints. B-grade source.
- 17.Leviathan Encyclopedia, Starcloud entry. Company history, architecture, and WEF Technology Pioneer information. B-grade source.
Continue reading

6 Jun 2026 · 31 min read
Orbit Is Architecture: Why Orbital Compute Is First an Orbit-Design Problem
From LEO, MEO and GEO to sun-synchronous and dawn-dusk orbits, this technical brief shows how illumination, heat rejection, radiation, downlink, lifetime and regulation jointly define the engineering limits of orbital compute.

20 May 2026 · 38 min read
China's Orbital Compute Reality Check: Who Is Actually in Orbit?
A rebuilt native-English assessment of China's orbital compute sector, from the Three-Body Computing Constellation and Orbital Chenguang to Starcloud, Google Suncatcher, NVIDIA Space-1, and Dongfang Tiansuan.

20 May 2026 · 42 min read
SpaceX Is Apple. Now Someone Needs to Build Android.
SpaceX has achieved something Apple took decades to build: a vertically integrated ecosystem so complete that every competitor is either copying it or losing. The orbital compute inflection changes the calculation. Here is the case for Space Android — and a reference architecture for how to build it.