Skip to main content


Find everything you need to get started with Zephyr below. Check out demos and our database of supported boards, or dive into the docs and the latest release. You can also find developer tools here, and learn how to contribute upstream. The community is here to help you learn, deploy, and master Zephyr. Engage with us if you need something that you don’t find here.

Org Chart

The  Zephyr Project source code is maintained in a Git repository. Zephyr is provided as source code and build scripts for different target architectures and configurations, and not as a binary image.

For releases 1.14 and after, multiple repositories are used, so the preferred method for downloading source code is by using a Zephyr Project tool called west.  While you can also download source code as a tar.gz file or use Git commands (see the bottom of the GitHub release notes pages), this requires additional manual steps (see Using Zephyr without west documentation for details).

Zephyr Project Organizational Chart

Governing Bodies

The project is composed of two governing groups: administrative and technical.

The administrative leaders meet in a Governing Board that approves the direction and initiatives for the project. The technical leadership is comprised of subsystem maintainers. The Technical Steering Committee (TSC) functions as a bridge between these groups. The TSC appoints a chair who represents the interests of the TSC on the Governing Board and also works with the TSC to find solutions per the direction of Governing Board.

Governing Board

  • Choose policies
  • Articulate strategy
  • Provide guidance to the TSC

Technical Steering Committee (TSC)

  • Serves as the highest technical decision body consisting of project maintainers
  • Sets technical direction for the project
  • Coordinates cross-community collaboration

Each member organization provides an administrative representative to the project’s Governing Board, and a technical representative to the Technical Steering Committee.

In choosing maintainers from the community of project developers, the TSC evaluates the needs of the project as a whole and the subsystem or component, taking into account the active participation of the individual. This results in a system of governance that relies on merit and trust as well as participation and transparency.

Committees & Working Groups

Technical Steering Committee

  • Anas Nashif (Intel, TSC Chair)
  • Andrey Madan (Parasoft)
  • Asger Munk Nielsen (Oticon)
  • Brandon Satrom (Blues)
  • Carles Cufi (Nordic Semiconductor)
  • Carlo Caione (BayLibre)
  • Chris Coleman (Memfault)
  • Chris Friedt (Meta)
  • Danny Ørndrup (Oticon)
  • David Leach (NXP)
  • Dennis Ruffer (T-Mobile USA)
  • Erik Tamlin (Percepio)
  • Eugene Cohen (Qualcomm Innovation Center)
  • Flavio Ceolin (Intel, Security Architect)
  • Henrik Brix Andersen (Vestas, Community Representative)
  • Ian Fyall (Infineon Technologies AG)
  • John Lange (T-Mobile USA)
  • Jonathan Beri (Golioth)
  • Karol Gugala (Antmicro)
  • Keith Short (Google)
  • Kevin Townsend (Linaro)
  • Luka Mustafa (IRNAS)
  • Mahesh Mahadevan (NXP)
  • Marti Bolivar (Nordic Semiconductor)
  • Marty Davis (Sternum)
  • Matt Gordon (Silicon Labs)
  • Maureen Helm (Intel)
  • Maxim Adelman (Meta)
  • Michael Arnold (Baumer)
  • Michael Gielda (Antmicro)
  • Mieszko Mieruński (AVSystem)
  • Piotr Mienkowski (Independent, Community Representative)
  • Rasmus Abildgren (Bose Corporation)
  • Rob Woolley (Wind River)
  • Roman Kellner (Baumer)
  • Ruud Derwig (Synopsys)
  • Ryan Erickson (Laird Connectivity)
  • Sam Grove (SiFive)
  • Simon Glass (Google)
  • Simon Hein (Baumer, Safety Architect)
  • Wonmoon Cheon (Qualcomm Innovation Center)

Safety Committee

  • Alexey Brodkin (Synopsys)
  • Amber Hibberd (Intel)
  • Anas Nashif (Intel)
  • Andrey Madan (Parasoft)
  • David Leach (NXP)
  • Flavio Ceolin (Intel)
  • Jack Rosenthal (Google)
  • Kate Stewart (Linux Foundation)
  • Lauren Murphy (Intel)
  • Nicole Pappler (Functional Safety Manager, AlektoMetis)
  • Nikolay Anikeev (Synopsys)
  • Paul Fagerburg (Google)
  • Simon Hein (Baumer, Safety Committee Chair + Architect)

Security Committee

  • David Brown (Linaro)
  • David Leach (NXP)
  • Denis Brockus (Google)
  • Dennis Huang (Qualcomm Innovation Center)
  • Flavio Ceolin (Intel, Security Committee Chair + Architect)
  • Kate Stewart (Linux Foundation)
  • Ruud Derwig (Synopsys)

Marketing Committee

  • Alexander Gerstner (Baumer)
  • Ali Aljaani (Nordic Semiconductor)
  • Anthony Nash (T-Mobile USA)
  • Bjarne Kielsholm-Ribalaygua (Oticon)
  • Chris Turner (Intel)
  • Colleen Harig (Memfault)
  • Cristina Brandtstetter (FIWARE Foundation)
  • Danny Watson (Infineon Technologies AG)
  • Daria Kolarczyk (AVSystem)
  • Debosmita Das (Google)
  • Ebba Simpson (Linaro)
  • Emma Wimberley (Blues)
  • Frédéric Desbiens (Eclipse Foundation)
  • Jeff Mulhausen (SiFive)
  • John Ferguson (Wind River)
  • Jonathan Beri (Golioth)
  • Jonathan Kaye (Laird Connectivity)
  • Kathleen Jachimiak (NXP)
  • Long Lu (Northeastern University)
  • Luka Mustafa (IRNAS)
  • Marty Davis (Sternum)
  • Matt Gordon (Silicon Labs)
  • Michael Gielda (Antmicro, Marketing Committee Chair)
  • Michael Turquette (BayLibre)
  • Mike Skrtic (Percepio)
  • Phil Brownfield (Synopsys)
  • Ric Wheeler (Meta)
  • Ricardo Camacho (Parasoft)
  • Yannis Damigos (ICCS)
  • Yonghua Li (Beijing University of Posts and Telecommunications)

The TSC meeting has an open attendance policy and publishes meeting minutes to the TSC mailing list: see the Group meetings wiki page for more information.

Administration & Leaders

Roles & Responsibilities

Administrative governance includes oversight as well as the provision of services to the project, usually in the form of sub-groups underneath the Governing Board. These can be created at any time and consist of member representatives designated for specific administrative tasks.

Administrative Leaders

Current administrative sub-groups and roles include: Members of these sub-groups direct activities within those categories, often with service providers. Linux Foundation currently provides some servers and systems administration advocacy and infrastructure to the Zephyr Project. Other roles are filled by members.

Technical Steering Committee

  • Organized intentionally with no single leader communications
  • Communications administered by the Community Manager


  • Administration of project finances
  • Headed by a Finance Administrator or Treasurer


  • Servers and systems administration
  • Headed by a Systems Administrator


  • Public relations, website, training and materials management & other outreach activities
  • Headed by a Lead Advocate


  • Management and coordination of community activities and forums, direct outreach, and liaison among other groups
  • Headed by Community Manager

Technical Leaders

Technical leadership also includes administrative roles defined by the needs of the project. Current technical roles include:

Chief Architect

  • Responsible for directing technical tasks within the project and managing the other roles


  • Responsible for bug triage and managing technical tasks related to specific components

Program/Project Manager

  • Responsible for schedules, chairing technical meetings, and resolving conflicts within the technical development of the project

Release Manager

  • Responsible for handling the release process

Copyright & Trademarks

The Zephyr Project is an open source project formed in 2015 to manage the Zephyr kernel, its subsystems and core components, and its tool chain and development tools. In reference to the project, it is preferred to use the entire name “Zephyr Project” to distinguish it from the Zephyr kernel. Derivative operating systems are expected to have their own names. Zephyr™ Project and the Zephyr Project logo are trademarks of the Linux Foundation. Other names and brands may be claimed as the property of others.