The Xen Project has launched a safety committee to share reusable engineering artefacts for functional-safety certification, aiming to cut duplicated work, costs, and development time for open-source systems.
The Xen Project has launched the Xen Safety Committee to extend the open-source model beyond source code into shared functional-safety engineering. The initiative will develop and maintain reusable safety requirements, architecture specifications, testing frameworks, tooling, documentation, and other engineering evidence that organisations can use for their own certification programmes.
By sharing this foundation, the initiative aims to reduce duplicated engineering effort and certification costs while accelerating downstream certification of systems built on open-source software.
AMD, EPAM, and Renesas are founding contributors and have already developed safety-related material covering software safety requirements, architecture specifications, MISRA-related engineering, DFMEA analysis, testing frameworks, tooling, code coverage, and process documentation. The committee combines dedicated safety governance with Xen’s upstream, community-led development and review model.
“Safety engineering has traditionally required every organization to recreate much of the same foundational work. We believe open source can change that,” said Cody Zuschlag, Community Manager, Xen Project.
Xen releases now receive five years of support, comprising three years of regular support and two years of security support, providing a longer-term foundation for development, certification, and deployment.
The initiative targets safety-critical software-defined systems across automotive, avionics, industrial automation, robotics, and mixed-criticality environments. It also introduces Premier Plus membership for organisations pursuing functional-safety certification, providing access to committee-managed engineering artefacts and a role in programme priorities.
Xen supports x86 and Arm architectures, isolation and partitioning, MISRA C compliance work, and static analysis for mixed-criticality workloads.
