STELLAR / company
Building compute infrastructure beyond Earth
STELLAR is a space infrastructure company developing orbital data-center nodes for compute, storage, and secure mission data processing.
Space infrastructure
Company type
Node-1
First program
Compute + storage
Core capability
Luxembourg
Base
STELLAR/ visual
Space infrastructure company / Luxembourg
01 / mission
Make orbital compute usable as infrastructure
The goal is not to make space sound futuristic. The goal is to make orbital compute technically credible, commercially accessible, and operationally dependable.
Model 1
Mission engineering
Define the flight gates, spacecraft interfaces, orbital assumptions, and verification plan.
Model 2
Payload systems
Design compute, storage, power, thermal, RF, and fault behavior as one payload.
Model 3
Software infrastructure
Make orbital capacity usable through APIs, scheduling, receipts, and customer delivery.
Model 4
Commercial partnerships
Connect spacecraft, launch, hardware, ground networks, cloud platforms, and early customers.
02 / company model
A company built around systems integration
Orbital data centers require spacecraft, software, thermal, storage, operations, and commercial infrastructure to come together as one service.
Spacecraft + software + thermal + ops one team
STELLAR / COMPANY / OPERATING MODEL
STELLAR operating model
Four engineering disciplines, five partner classes, one orbital service. Each discipline owns a slice; partners compound external leverage; integration is the actual product.
Vintage · 2026-Q24 disciplines · 5 partner tiers
AOperating engine · four disciplines, one service
D1discipline
Mission engineering
Mission gates · spacecraft I/F · orbit assumptions
Ownsflight gates · ICDs · V&V planI/Fspacecraft + launch partners · mission ops
D2discipline
Payload systems
Compute · storage · power · thermal · RF · faults
Ownspayload reference design · qualificationI/Fcompute + radiation hardware suppliers
D3discipline
Software infrastructure
APIs · scheduling · receipts · delivery
Ownsservice plane · audit · customer SDKI/Fground network · cloud platforms
D4discipline
Commercial partnerships
Spacecraft · launch · ground · cloud · customers
Ownspartner tiering · LOIs · contractsI/Fevery external partner class
↓ verified mission
↓ integrated mission
↓ usable orbital
↓ mission customer
Orbital service · compute + storage + verified delivery
One orbital service, four integrated disciplines
Mission baseline → integrated payload → usable capacity → customer pull. Integration is the deliverable.
BPartner ecosystem · five tiers
P1
Spacecraft + launch
Hosted-payload bus · launch service
Leverageflight access · ride shareExamplesbus integrators · launch providers
P2
Hardware suppliers
Compute · storage · power · radiation hardening
Leveragequalified parts · long-lead supplyExamplesradhard FPGA · GR740 · ECC memory
P3
Ground network
TT&C · X-band downlink · pass scheduling
Leverageglobal pass coverage · contact densityExamplesX-band networks · S-band stations
P4
Cloud platforms
Customer cloud handoff · analytics adjacency
Leveragewhere customer data already livesExampleshyperscaler regions · sovereign cloud
P5
Mission customers
Workload · pull · validation
Leveragefirst paid orbital workloadsExamplesEO ops · sovereign · AI research
CDecision rights · what each discipline owns and integrates
4 rows · clear ownership| Discipline | Owns | Integrates with | Cadence |
|---|---|---|---|
Mission engineering D1 / 04 | flight gates · ICDs · V&V plan | spacecraft · launch · ops | per mission gate |
Payload systems D2 / 04 | reference design · qualification | hardware suppliers | per build cycle |
Software infrastructure D3 / 04 | service plane · audit · SDK | ground · cloud | continuous |
Commercial partnerships D4 / 04 | partner tiers · contracts · LOIs | all external classes | rolling |
Operating cadence — rhythm of the model
Daily01 / 05
engineering standups · ops watch
Weekly02 / 05
cross-discipline integration sync
Monthly03 / 05
partner + customer review
Quarterly04 / 05
mission gate · risk burn-down
Per mission05 / 05
design baseline → flight → close-out
Start with Node-1, scale toward mesh
STELLAR begins with Node-1, a hosted payload program designed to validate the interfaces, software, thermal constraints, and operating model required for orbital data-center services.