SATFORM

Sovereign Orbital AI inference

Compute that sits outside every national jurisdiction, sold to European buyers who cannot legally use a US hyperscaler. Each satellite earns on its own.

Orbit
550 KM SSO
Unit
1 satellite
Compute
8–16 GPU
Links
Relay + downlink
Milestone
1 sat, paid work
The thesis
01 / One-pager

European institutions need AI compute that no foreign government can compel, and orbit is the only place that exists. We are selling jurisdiction in the near-term, and cost competitive AI Inference compute in the long-run.

The problem
Europe has no compute outside someone else's jurisdiction

EU providers hold under 13% of their own cloud market. Three US hyperscalers control most of the rest. That drains an estimated €260B a year.[DIGITAL SME] Every one of those providers carries legal exposure to a foreign jurisdiction, the CLOUD Act included.

This has stopped being a talking point. The EU's Cloud and AI Development Act arrived in the June 2026 Tech Sovereignty Package.[EC, June 2026] It sets four tiers of sovereignty assurance.[CADA][EC] Public procurement will score vendors against them. Sovereignty is becoming a line item on a compliance form.

The architecture
One satellite is the compute unit

A single bus in the Starlink v2-mini class generates roughly 28 kW.[Google, Table 1] A Blackwell-class accelerator draws about a kilowatt.[NVIDIA] Allow for bus overhead and thermal margin and one satellite carries eight to sixteen GPUs.[own estimate] Those chips sit in one chassis and talk over copper and fibre at NVLink speeds, around 1.8 TB/s.[NVIDIA]

No laser link between two spacecraft will ever come close to that. So we do what terrestrial clusters already do. Tensor-parallel inside the box, where the fabric is fast. Anything slower gets the sparse traffic. This is the standard terrestrial pattern, stretched from a few metres of copper to a few hundred kilometres of vacuum.

Bigger satellites are also more mass-efficient. Shielding scales with surface area while compute scales with volume, so shielding per unit of compute falls as the satellite grows.[Starcloud WP] Better kilograms per kilowatt improves our economics no matter what launch prices do.

Architecture, at a glance
waste heat to deep space SAT-01 8× GPU, tensor-parallel internal fabric, no optics SAT-02 8× GPU, tensor-parallel internal fabric, no optics relay link ≈1000 km · coverage handoff no station in view optical downlink result only EU ground station PV face radiator optical link
ONE SATELLITE IS THE COMPUTE UNIT · GPUS RUN TENSOR-PARALLEL OVER INTERNAL FABRIC · OPTICAL LINKS CARRY COVERAGE HANDOFF AND DOWNLINK
Connectivity
Links exist to solve coverage

A satellite in low Earth orbit passes over a given ground station for a few minutes at a time. Without relay, a customer's job waits until the node flies overhead. Optical downlinks also lose to cloud, and Europe is cloudy. So we need links between satellites and several ground stations spread across different weather.

Relay is a well-served problem. It runs at hundreds of gigabits over thousands of kilometres.[STARCOM] Commercial terminals ship today. Splitting a model across spacecraft is a different regime entirely, needing roughly 10 Tbps at sub-kilometre range, which remains a research topic.[Google §2.1]

One option stays open. If a model outgrows a single chassis, pipeline parallelism across two satellites needs only a few gigabits per link and runs on the same commercial hardware.[own estimate] It is available when we need it.

Thermal, at our scale
Radiator area is a linear function of power

The 4 km² arrays in the press are a consequence of choosing 5 GW. Radiator area scales linearly with power, so the headline figure says nothing about a satellite four hundred thousand times smaller.

Run Stefan-Boltzmann with Starcloud's own emissivity of 0.92.[Starcloud WP] At their assumed 20°C a square metre nets about 630 W from both faces after solar and Earth absorption. We can run the radiator at 75°C, which is what an 85°C junction with a 10°C gradient allows, and the T⁴ term pushes that to roughly 1,400 W/m².[own estimate]

Eight GPUs at a kilowatt each[NVIDIA] is 8 kW of chip power. Add hosts, memory, networking and bus overhead and call it 12 kW. Every watt becomes heat. That needs about 9 m² of radiator, roughly three metres square. An ordinary deployable panel.[own estimate]

RADIATOR AREA AT 75°C, ≈1.4 kW/m² NET REFERENCE DESIGNS
1 10 100 1,000 10,000 0.1 km² 1 km² 10 km² 1 kW 10 kW 100 kW 1 MW 10 MW 100 MW 1 GW 10 GW SYSTEM ELECTRICAL POWER RADIATOR AREA (m²) Ours, 12 kW ≈9 m² Starcloud-3, 200 kW ≈143 m² Starcloud 5 GW ≈3.5 km²
ONE STRAIGHT LINE · NOTHING ABOUT THE PHYSICS CHANGES BETWEEN A 12 kW SATELLITE AND A 5 GW ONE, ONLY THE POWER BUDGET

The solar array is the larger structure. At 1,361 W/m², 22% efficiency and 90% packing, 12 kW needs roughly 45 m² of array, against 105 m² on a Starlink v2-mini.[Google, Table 1] Both fold and deploy routinely today.

Buildability
Every component of this exists today
  • Ordinary station-keeping. Sub-kilometre formation flight across many satellites remains unsolved at production scale. Our satellites fly at conventional constellation spacing.
  • Conventional collision avoidance. Google's reference design packs 81 satellites inside a one-kilometre radius.[Google §2.2] Ours spread across a normal orbital plane.
  • Commercial optical terminals. Relay and downlink hardware is available off the shelf from European vendors flying today.

The result is speed and low technical risk. The first satellite is a complete product on launch day, and revenue begins with a fleet of one.

Outside confirmation
The hardware data supports inference

Google put their own TPU in a proton beam simulating five years in sun-synchronous LEO. The chip survived the full mission dose with margin. Silent bit-flip errors during live workloads ran at roughly one in 3 million inferences at expected orbital dose rates.[Google §2.3] The same paper flags training as far more exposed and still unsolved.[Google §2.3] We picked the workload the hardware has been shown to handle.

Starcloud has already flown a GPU cluster on a smallsat carrying a Blackwell chip and an AWS server blade.[TechCrunch][Starcloud-2] The multi-GPU single-satellite configuration is proven in orbit.

First milestone
One satellite, running work someone paid for

A satellite carrying a GPU cluster, a purchased optical terminal, and a signed customer running real jobs. That proves the unit economics, the ground segment, and the sales motion at once. Everything after it is replication.

Sources
Constraints, told straight
02 / Read before Sunday

Every item below is a live problem with real consequences for the plan. They are stated plainly so they can be argued with.

The biggest one
Sovereignty carries the moat alone

The hardware is deliberately unexotic. A satellite carrying GPUs and a commercial optical terminal is a configuration a competitor could assemble, and Starcloud already flies something close to it.[Starcloud-2] Nothing in the bill of materials keeps anyone out.

Defensibility comes instead from jurisdiction, regulatory position, and the customer relationships that follow. That makes compliance and procurement work as load-bearing as the engineering, and it means execution speed matters more than technical secrecy.

Coverage
Duty cycle is the central engineering problem

A single satellite is over a given ground station for minutes a day.[arXiv 2604.27197] Academic work on orbital data centers is blunt about this. Geometry and weather set a hard ceiling on sustained space-to-ground throughput, and high availability forces a geographically spread ground segment whose cost scales with the bandwidth you need.[arXiv 2604.27197]

So availability is a function of how many satellites and how many ground stations we own. Both cost money. A customer who wants a defined turnaround window is buying our constellation size, and pricing has to reflect what a given fleet can actually deliver.

Unit economics
The industry disagrees on the one number we depend on

Reusable Falcon 9 runs about $3,600/kg to LEO today.[Google §4.4] Google treats $200/kg as the point where launch stops dominating cost.[Google §2.4] They model a learning curve of 20% per doubling that reaches under $200/kg by roughly 2035, needing about 1,800 cumulative Starship launches.[Google §4.4] Their aggressive reuse scenario reaches $15 to $38/kg on 100× component reuse that nobody has demonstrated.[Google §2.4]

Starcloud's whitepaper assumes $30 to $50/kg is achievable now and falling toward $10/kg.[Starcloud WP] That figure comes from their own marketing. Public sources spread across a factor of ten to a hundred on the single input our cost case rests on. We cannot move that number.

Attrition
Hardware failure in orbit is a one-way door

Google's radiation data is the best public evidence available and it is encouraging. Two caveats carry real weight. On-chip memory was the weak point, showing irregularities at only about 2.7× the required dose.[Google §2.3] And that is radiation alone. Nobody has published what five years of thermal cycling and mechanical stress does to a GPU in orbit.

Two disposal models are open. Dead hardware deorbits and burns up with nothing recovered, or modules are built for swap-out and partial salvage, which is the route Starcloud designs around.[Starcloud WP] The choice moves the economics materially and needs settling early in the design.

Sizing
There is an economic floor on satellite size

Small satellites are worse economically, and the effect is severe. Avionics, propulsion, comms and structure do not shrink with power, so fixed overhead dominates a small bus. Google's own comparison puts Starlink v2-mini at about 20.5 kg/kW, Starlink v1 at 37, OneWeb at 188 and Iridium NEXT at 430.[Google, Table 1] That is a factor of twenty between best and worst. Starcloud makes the same argument about shielding, which scales with surface area while compute scales with volume.[Starcloud WP]

The figure to minimise is kilograms per kilowatt. Below roughly 10 kW that diverges sharply from total mass, and fixed overhead starts eating the launch budget. This is what sets the eight to sixteen GPU range, and it is an economic constraint rather than a thermal one.[own estimate]

Thermal is a hard ceiling

There is no convection in vacuum. Heat leaves by radiation only. Junction limits of around 85°C[McCalip] cap how much compute a given radiator area can carry, and that cap is what sets our GPUs per satellite.[McCalip] Starcloud names the deployable radiator as one of two unsolved technical hurdles on their public roadmap.[SpaceNews] We face the same physics with a smaller team.

Vendor landscape
The comms layer can be bought in Europe

Mbryonics sits in Galway, Ireland. They sell to ESA, DARPA, Airbus Defence and Space, and the European Defence Agency.[Mbryonics] Their long-haul specifications suit relay and ground links directly.

  • STARCOM. Optical inter-satellite and Earth-link terminals. Up to 400 Gbps by 2027, link distances beyond 80,000 km. Sized for relay.[STARCOM]
  • STARLIGHT. Companion modem, amplifier, and antenna control unit. Full assembly under 14 kg.[STARLIGHT]
  • STARGATE. Their optical ground station, claiming roughly a thousand times the throughput of RF ground links. A direct candidate for our ground segment.[STARGATE]
  • TeraBIX. Radiation-hardened photonic transceiver for chip-to-chip links, under 5 mW/Gb/s. Useful inside the satellite.[TeraBIX]

One open question for them. Their forward error correction is tuned for 80,000 km range, and at relay distances the FEC delay could exceed the flight time.[STARCOM] That number is absent from the public spec sheet and is the first thing to ask.

Regulatory and insurance exposure is unmodelled
  • Launch licensing across EU and ESA bodies, plus any non-EU launch partner.
  • Ground station siting and licensing across several member states, which is a substantial part of the build.
  • Orbital slot coordination. Contested and worsening. Starcloud has filed for 88,000 satellites. SpaceX for up to a million.[GeekWire]
  • Insurance for launch and on-orbit hardware, which no public cost model in this field includes.

This is the full list. Any serious diligence process will surface the same items in the first ten minutes, so they are better addressed here than discovered later.

Sources
Where the opening is
03 / Market

The field is real, funded, and moving fast. Every serious player is chasing scale and raw cost. Jurisdiction is the open lane.

Primary angle
EU sovereignty is now a procurement criterion

The Tech Sovereignty Package and CADA stopped being proposals in June 2026.[EC] They are moving through Parliament now. The four-tier sovereignty framework will score vendors in public procurement.[CADA] An orbital node satisfies the hardest tier by construction. It sits beyond every national territory, which settles the question of applicable law in a way even EU-headquartered cloud providers still struggle to answer.

The argument runs into the supply chain too. Buying optical terminals and ground stations from an Irish vendor already trusted by ESA puts the sovereignty claim into the bill of materials, where a procurement officer can see it.

Who buys
  • Defense and ISR. Dual-use framing opens the EU Defence Fund and national innovation arms, which is non-dilutive capital.
  • Regulated finance. GDPR-bound inference, where sitting outside any jurisdiction is a novel legal position worth testing with counsel early.
  • Healthcare and pharma. Clinical and genomic inference. These sectors already pay a premium to OVHcloud and Scaleway for sovereign cloud.
  • Earth observation operators. They generate terabytes a day and downlink is their bottleneck.[Starcloud-2] Processing in orbit serves them at today's launch prices. Starcloud targets this market explicitly.[Starcloud-2]
Competitive field
PlayerPosition
StarcloudTargeting a $2.2B valuation. Over $200M raised.[SpaceNews] Filed for 88,000 satellites.[GeekWire] Building gigawatt training clusters with 4km arrays.[Starcloud WP] First to fly a GPU and train a model in orbit. Their cost story needs launch around $500/kg.[TechCrunch]
SpaceXFiled for up to a million satellites. Starcloud's CEO expects most of that capacity to serve internal xAI and Tesla workloads.[SpaceNews]
GooglePublished system-design research in November 2025 for TPU satellite swarms. 81 satellites, one-kilometre radius, free-space optics.[Google §2.2] The most rigorous public work in the field, currently a research programme.[arXiv]
Axiom, Kepler, Sophia SpaceEach working a different angle on orbital compute, all positioned on capability rather than jurisdiction.[Quartz]

All of them treat compute as the product and are building toward scale and eventual cost parity. Jurisdiction remains unclaimed, and the lane is narrow.

The first-mover argument

This market probably narrows to three to five players. Orbital slots, spectrum coordination, and launch manifest access are scarce and sequential. The scarcest resource is regulatory trust. CADA's sovereignty framework is not expected to be final before the end of 2027.[CADA] Vendors in the room now, with flying hardware, help define what sovereign assurance means for orbital infrastructure. Later entrants cannot buy that position with capital alone.

Sources
How this makes money
04 / Revenue

Two phases. Near-term revenue from a market that exists at today's launch prices. Long-term revenue from sovereignty contracts as CADA lands. The figures below are first-principles estimates, offered as a frame for the argument.

The number that matters
Break-even price per GPU-hour
~$21
GPU-hour needed to repay one satellite over 5 years at today's launch price
~$13
the same figure if launch reaches $200/kg
~1.3×
what AWS already charges per B200-hour today

The arithmetic.[own estimate] A Starlink v2-mini masses 575 kg for 28 kW.[Google, Table 1] We need about 12 kW, so a scaled bus plus GPU chassis and radiator plausibly lands between 350 and 450 kg. Take 400 kg. At $3,600/kg that is roughly $1.4M to launch. Call hardware and integration another $3M. Eight GPUs at 60% utilisation deliver roughly 42,000 GPU-hours a year. Five years against $4.4M of capex needs about $21 per GPU-hour before operating costs.

Mass is the most sensitive input in this calculation. It is scaled from a Starlink bus rather than costed from a detailed design, and every 50 kg moves the break-even by roughly a dollar. A bottoms-up mass budget is an early priority.

Now compare that to the market. Cross-provider median for a B200 sits around $6.25 per GPU-hour, but the spread is enormous, running from $3.75 at the cheapest neocloud to $16.11 on Google Cloud[GPU price index][28 providers] and past $27 on Azure managed instances. Hyperscaler rates already carry a large premium for SLAs, support, and integration.

That reframes the ask. The price sits at roughly 1.3 times what AWS charges a European buyer today, in exchange for a jurisdictional guarantee AWS cannot offer at any price. If launch reaches $200/kg our break-even lands at about $13, which is inside today's hyperscaler range. That is the single figure to validate with a customer before raising anything.

Phase one
On-orbit processing for satellite operators, 2027 to 2029

Earth observation operators generate terabytes of raw imagery a day and cannot get it down fast enough. Processing in orbit and downlinking only the result removes their bottleneck. Their reference point is the downlink capacity they lack, which makes this a capability sale rather than a price comparison.[Starcloud-2]

This market is live at today's launch prices and independent of CADA's timeline. It gives the first satellite paying work while the sovereignty motion matures, and it builds ground segment experience on a customer's schedule.

Phase two
Sovereign inference contracts, 2028 onward

As CADA's assurance tiers become procurement criteria, EU institutions and regulated sectors need vendors who can satisfy the top tier. We sell scheduled and batch inference under a jurisdictional guarantee nobody terrestrial can match.

Pricing here follows compliance rather than compute. A bank barred from running a workload on Azure measures our price against leaving the workload undone, which is where the premium comes from.

What we sell, precisely
  • Scheduled inference windows. Guaranteed GPU-hours in defined windows, priced per hour. Suits batch analysis, model serving on a cadence, periodic scoring.
  • Sovereign job execution. Data uplinked, processed, results downlinked, nothing retained. Sold on the compliance artefact as much as the compute.
  • On-orbit edge processing. Compute sold to other spacecraft operators who need results rather than raw data on the ground.

Every product above is scheduled or batch. Latency depends on when a satellite is overhead, which sets the boundary of what can be sold with a credible SLA.

Capital
Non-dilutive capital is available

Dual-use framing opens the EU Defence Fund and national defense innovation arms. Horizon Europe and the EIC fund sovereignty-aligned infrastructure. ESA runs technology development contracts. Every euro from those sources buys hardware without touching the cap table, and a first satellite funded partly by grant capital changes the shape of a seed round considerably.

The model rests on one unvalidated assumption. That a European buyer will pay a premium for jurisdiction. Getting one named customer to confirm that on the record is worth more than anything else in this document.

Sources