← All threads
POSITIONING

Space-data / multi-mission platform

3-yearlast moved 2026-08-29

PROMOTED [retro 07-28]: re-rate trigger fired — Shanghai's Xingshu Plan LAUNCHED (not merely unveiled) Jul 18, selling hourly on-orbit compute; >=2-actors/>=2-blocs bar met (US: Starcloud/"Orbital"; China: Three-Body/Xingshu). Next re-rate: a 2nd operator's commercial contract. SES's OWN DoD-program-lead sub-strand (distinct revenue logic, genuinely SES's, unlike the compute strand above) now 2 items in 3 days: Starlab O3b mPOWER relay [07-29] + K2 Space/PTS-G [NEW retro 07-31 — SES Space & Defense leads the K2 team on Space Force's Protected Tactical Satcom-Global; SpaceNews, medium confidence, single-sourced]. A 3rd instance should trigger considering a dedicated entry. WATCH [08-09, reader-flagged, UNCONFIRMED]: Intel reportedly patent-filed for orbital data centers — if confirmed, a 3rd distinct actor (Starcloud/US, Three-Body-Xingshu/China, Intel) that would itself clear the re-rate bar; verify via a primary patent-database check before treating as real. 2ND INTEL SIGNAL [08-10]: SpaceX-Tesla's Terafab chip-fab JV (announced Aug 6, pushed [S1] briefs/2026-08-10T0344Z.md), whose chips are earmarked partly for SpaceX orbital-AI data centers, names an undisclosed Intel "contribution" — a second, independent, still-uncorroborated Intel-into-orbital-compute signal alongside the patent note; a confirmed instance clears the re-rate bar (3rd distinct actor). Terafab is itself a concrete US industrial proof-point for the orbital-compute strand SES's space-data adjacency must compete against. NEW [08-14, Telesat CEO Q2 call primary]: Telesat is positioning Lightspeed's optical ISLs as an SDA-standard cross-operator relay network and named orbital data centres, unprompted, as a customer class ("when you hear others talk about data centers in space, that's another opportunity... it needs to be connected back to the earth") — a 2nd Western MEO/LEO operator (after SES's own Starlab/K2-PTS-G sub-strand) treating orbital-compute relay as a demand-side revenue line SES's space-data adjacency must compete in. RE-RATE CRITERION MET [retro 08-22]: NVIDIA's confirmed $250M Starcloud investment + dedicated "Space-1 Vera Rubin Module" hardware (Aug 21, 4-outlet corroboration incl. SpaceNews/Via Satellite) is a 3rd distinct major actor in orbital compute (after US Starcloud/Orbital, China Three-Body/Xingshu) — CLARIFIES the bar to include a major backer/technology-supplier committing dedicated hardware, not only a new operator; supersedes the unconfirmed Intel patent/Terafab-contribution placeholder as the operative 3rd-actor signal. Original 2nd-operator-commercial-contract trigger stays open, watch separately. GAP FOUND, SCOPE WIDENED [08-25, reader-flagged ZERO MISS]: Kepler Communications' commercial optical data-relay constellation (see STANDING ENTITY WATCHLIST) went live/commercial Aug 24 — a direct analog to the Telesat/SES optical-ISL-as-relay-infrastructure angle already tracked here, not just orbital compute — sat unswept despite being carried same-day in an already-healthy, already-mirrored source (payloadspace-rss, http 200); this thread's SCOPE now explicitly includes commercial optical/data-relay-as-a-service operators, not only orbital-compute providers. Same species as the 08-17 AST/Lynk and 08-24 Arianespace MISSes — 3rd instance, see SIGNAL TYPOLOGY THREAD-SCOPE ENTITY AUDIT note. PUSHED [08-25, 2152Z brief S2]: first tranche live/commercial, SDA-compatible 100Gbps optical links, 10+ ground stations, 2028 expansion tranche booked incl. a dedicated Rocket Lab launch — gap closed on its first test cycle. NEW [08-29, this session]: the FCC orbital-data-center (ODC) filing wave is now a REGULATORY contest, not only a commercial one — SpaceX (up to ~1M sats, "Orbital Data Center system," DA-26-113 accepted 02-04), Starcloud (88k), Blue Origin (51k), Cowboy Space "Stampede" (20k), Orbital (100k) all request FCC WAIVERS to run primarily on optical (OISL) links instead of licensed RF, and Earthjustice's 07-08 NEPA petition already seeks a processing pause (SpaceNews/Secure World Foundation, secondary; DA-26-113 primary via fcc.gov). UNCONFIRMED [08-29, @FreeSpeech101 via tripwire, partisan lead — verify to ICFS, never cite as source]: the FCC reportedly sent the ODC applicants a clarification note on OISL usage — plausible given the optical-waiver reliance, but NO primary FCC doc or secondary outlet found this cycle; next check the ODC dockets in ICFS (this is exactly a docs.fcc.gov path the sandbox can't reach — needs the routine-env/Action). SES READ-ACROSS [opportunity-framing, not an SES move on record]: if OISL-only scrutiny slows the pure-optical players and surfaces the inter-orbit/downlink interconnect gap (an ODC still has to move data across orbits and to ground, and RF downlink is what's under waiver review), that is a lane for a licensed, coordinated MEO backbone — SES O3b mPOWER/meoSphere as the "carrier's carrier" for orbital-compute traffic; same demand-side logic as the Telesat 08-14 and Kepler 08-25 optical-relay entries above, and the TerraWave/compute-backbone read in non-western-sovereign-constellations. Full detail (orbital-compute strand only — SES-DoD-lead sub-strand is UNPOINTED, watch for growth): dossiers/spacex-financial-architecture.md

EUUSCapital & survival