Orbital Compute Continuity: Redmond/Woodinville, Kent & Launch-Cadence Risks

Pacific Northwest river valley industrial logistics corridor with freight rail and aerospace warehouses
BC ESG · Washington Space Cluster Segments (November 16, 2026)
Sourced Baseline: Cowboy Space (~290k sq ft Kent) sits in the Green River corridor; Starcloud sits in Redmond/Woodinville; all 3 depend on external launch cadence and radiation-tolerant supply.
TAKEAWAY BRIEF · PDF & MARKDOWN TWIN
Orbital Compute Continuity & Risks
Download the formatted 2-page briefing sheet (PDF) or read the single-source Markdown twin for Orbital Compute Continuity & Risks.
Orbital Compute Continuity: Ground & Orbital SPOFs

Ground Assembly Geography Meets Orbital Launch Dependency

Even though orbital compute aims to bypass terrestrial grid queues, its assembly lines remain exposed to Puget Sound corridors: Cowboy Space (~290,000 sq ft in Kent) sits in the Lower Green River valley, while Starcloud splits between Redmond and Woodinville in the Sammamish basin.

Beyond facility geography, the segment's defining single point of failure is launch cadence and radiation-tolerant GPU/radiator supply: hardware cannot be serviced easily on orbit, making launch delays or single-event-upset (SEU) failures irreversible without replacement launches.

Node / VectorOperator(s)Continuity RiskImpact
Kent Valley (~290k sq ft)Cowboy SpaceGreen River floodplain & liquefactionRocket & compute assembly pause
Redmond / WoodinvilleStarcloudSammamish corridor / I-405Starcloud-3/4 integration delay
Launch & Silicon SupplyAll 3 operatorsOut-of-state launch slots & GPU lead timesConstellation deployment slip

Related BC ESG Guides & Verified Primary Sources

BC ESG

ESG Strategy, Sustainability Intelligence, and Business Continuity for Forward-Thinking Organizations

© 2026 BC ESG — Business Continuity, ESG & Sustainability Intelligence