OSS + ELC EU 2026

Using Zephyr in space is not only a question of choosing an RTOS. A space computer is a system architecture: boot firmware, supervisor logic, watchdogs, safe mode, recovery paths, update policy, hardware monitoring, FPGA or SoC configuration, and the boundary between platform software and mission-specific applications all matter.

This talk looks at Zephyr from that system-architecture point of view. Based on Space Cubics’ OBC development experience and recent Space Grade Linux discussions, it explores where Zephyr can fit in future space systems: mission RTOS, payload-controller OS, supervisor/control-plane OS, or companion to Linux. Space already has credible RTOS options, but Zephyr can bring value if the ecosystem develops a clear architectural story around boot, recovery, observability, hardware control, and responsibility boundaries.

Attendees will leave with a practical checklist for evaluating Zephyr’s role in a space computer: what Zephyr should control, what should remain outside it, what must be recoverable after launch, and how to structure boot, update, monitoring, isolation, and fault-handling responsibilities.