A look at real time OSes for spacecrafts, like VxWorks, preferred by NASA, and open source RTEMS, preferred by ESA, amid a new contender SpaceChain OS
The updates don't come every spring and fall, but space operating systems keep evolving. — The ESA's recently launched Solar Orbiter … Tweets: @astrogrant Tweets: Grant Tremblay / @astrogrant : ESA's Solar Orbiter RTOS flight software allows for ... a maximum of 50 seconds to respond to a pointing anomaly. 🥴 https://arstechnica.com/...
Context & Ripple Effects
ESA's Solar Orbiter illustrates what rides on this choice: its flight software allows a maximum of 50 seconds to respond to a pointing anomaly, so the real-time operating system is not infrastructure anyone swaps casually. The field has long split along agency lines — VxWorks is NASA's pick, while ESA flies the open-source RTEMS — and that split now has a security dimension, since researchers found Wind River's VxWorks had carried serious flaws for 13 years before patches landed.
The article also flags SpaceChain OS as a new contender entering a two-horse market, arriving just as embedded-OS security scrutiny has intensified across the board — the same wave that surfaced 13 vulnerabilities in FreeRTOS and Amazon's AWS connectivity modules two years earlier.
First-order effects
- NASA missions running VxWorks carry the audit-and-patch burden of a proprietary kernel with a documented multi-year flaw history, while ESA's RTEMS fleet gets a fresh validation point from Solar Orbiter's demanding pointing-anomaly budget.
- SpaceChain OS enters as a third option against two entrenched incumbents, competing for mindshare at exactly the moment agencies are re-examining RTOS trust.
Second-order effects
- Successive vulnerability disclosures in embedded real-time kernels (VxWorks, FreeRTOS) push space agencies and satellite builders toward open-source code they can inspect themselves, strengthening RTEMS's position inside ESA and pressuring Wind River's value proposition beyond raw reliability.
- European players planning constellations — the Airbus, Eutelsat, SES, and Thales group bidding for IRIS² against Starlink — inherit this software decision at fleet scale, where per-spacecraft licensing and auditability compound across hundreds of units.
Third-order effects
- If the pattern holds, spacecraft operating systems follow the broader embedded-software arc from proprietary incumbency toward inspectable open source, with agency preference (NASA/proprietary, ESA/open) hardening into de facto procurement standards that new entrants like SpaceChain OS must route around.
- As commercial constellations multiply the number of flying computers, RTOS selection shifts from a bespoke engineering choice per mission to a supply-chain security question regulators and insurers may eventually weigh.
The trend: Spacecraft flight software is splitting between proprietary incumbents and inspectable open source, with security disclosures and constellation-scale deployments forcing the choice into the open.