STELLAR / market
The orbital cloud is becoming an infrastructure category
Launch costs are falling. AI infrastructure demand is rising. Satellite data volumes are expanding. Optical relay networks are emerging. Together, these forces create the conditions for orbital data centers.
Early
Category
AI + space data
Demand driver
Power + downlink
Constraint
Infrastructure
Opportunity
Market/ visual
Orbital cloud emerging category
01 / market forces
Four forces are converging
Orbital data infrastructure becomes credible when space access, AI demand, data volume, and resilience needs all move in the same direction.
Force 1
Launch economics
Lower launch costs make orbital infrastructure deployment more plausible than it was a decade ago.
Force 2
AI infrastructure pressure
Power, cooling, land, and permitting constraints are turning data-center capacity into a strategic bottleneck.
Force 3
Space data growth
Satellites, stations, sensors, and defense systems are generating more data than traditional downlink patterns can comfortably absorb.
Force 4
Sovereign resilience
Governments and enterprises need infrastructure patterns that are secure, physically separated, and resilient by design.
02 / category map
The category is early, but no longer empty
Starcloud is proving AI compute in orbit. Axiom is building orbital data-center infrastructure. Other hosted payload and edge-compute models are emerging. STELLAR's opportunity is to build a staged, infrastructure-first roadmap.
STELLAR / MARKET / CATEGORY MAP
Orbital cloud · category positioning & capability map
Six players grouped by orbital proximity and infrastructure depth, with movement vectors and a capability coverage matrix. STELLAR is positioned as the staged infrastructure-first ladder.
Vintage · 2026-Q26 players · 6 capabilities
AQuadrant chart · orbital proximity × infrastructure depth
Trajectory · next 24 moSTELLAR vectorSTELLAR markerOther players
BPlayer profiles
Player Amature
Cloud providers
Earth-bound hyperscale extending toward space data
Focusground-side compute · ingest · analyticsModelsubscription compute + storage
Player Bscaling
Launch companies
Enabling layer adjacent to the category
Focusaccess · rideshare · mission integrationModellaunch services + mfg
Player Cestablished
Hosted payloads
Single-customer payloads on shared buses
Focusmission-specific instruments · ridesModelbespoke contracts · per-mission
Player Dpathfinder
Starcloud
Orbital AI compute pathfinder
Focusinference workloads in orbitModelAI compute as a service
Player Ein-build
Axiom ODC
Orbital data-center programs · station heritage
Focusorbital DC modules · sovereign customersModelstation + ODC modules
Player FGroundLab → Pathfinder
STELLAR
Staged orbital infrastructure ladder · Node-0 → Node-5
Focuscompute · storage · verified deliveryModelmission ladder + multi-tenant nodes
CCapability coverage matrix
●●● full · ●● partial · ● limited · — none| Capability | A Cloud providers | B Launch companies | C Hosted payloads | D Starcloud | E Axiom ODC | F STELLAR |
|---|---|---|---|---|---|---|
Compute inference + processing in orbit | — | |||||
Storage durable ECC mission store | — | |||||
Power continuous payload envelope | — | |||||
Downlink verified scheduled delivery | — | |||||
Multi-tenant shared infra · isolation | — | — | ||||
Sovereign jurisdiction · audit · control | — |
Earth-bound
cloud + ground analytics — outside category
Adjacent
launch + buses — enabling, not the category
Hosted
single-mission payloads on shared buses
Orbital infra
multi-tenant compute · storage · delivery
Compete through a stronger mission ladder
STELLAR should be judged by how clearly each mission advances the infrastructure layer: not by one claim, one payload, or one diagram.