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

  • Amber Hibberd (Intel)
  • Anas Nashif (Intel, TSC Chair)
  • Andrey Madan (Parasoft)
  • Asger Munk Nielsen (Oticon)
  • Carles Cufi (Nordic Semiconductor)
  • Chris Coleman (Memfault)
  • Danny Ørndrup (Oticon)
  • Danny Watson (Infineon Technologies AG)
  • David Brown (Linaro, Security Architect)
  • David Eriksson (teenage engineering)
  • David Leach (NXP)
  • Eugene Cohen (Qualcomm)
  • Flavio Ceolin (Intel)
  • Garrett LoVerde (Golioth)
  • Henrik Brix Andersen (Vestas, Community Representative)
  • Jimmy Johnson (T-Mobile USA)
  • John Lange (T-Mobile USA)
  • Karol Gugala (Antmicro)
  • Keith Short (Google)
  • Kevin Hilman (BayLibre)
  • Kumar Gala (Linaro)
  • Mahesh Mahadevan (NXP)
  • Marti Bolivar (Nordic Semiconductor)
  • Matt Gordon (Silicon Labs)
  • Michael Arnold (Baumer)
  • Michael Gielda (Antmicro)
  • Michael Scott (
  • Mieszko Mieruński (AVSystem)
  • Olof Johansson (Facebook)
  • Piotr Mienkowski (Independent, Community Representative)
  • Rasmus Abildgren (Bose Corporation)
  • Ric Wheeler (Facebook)
  • Rob Woolley (Wind River)
  • Roman Kellner (Baumer)
  • Ruud Derwig (Synopsys)
  • Ryan Erickson (Laird Connectivity)
  • Sam Grove (SiFive)
  • Scott Shawcroft (Adafruit)
  • Simon Glass (Google)
  • Stefan Mijovic (Sivantos)

Safety Committee

  • Alexey Brodkin (Synopsys)
  • Amber Hibberd (Safety Architect/WG Chair, Intel)
  • Anas Nashif (Intel)
  • Andrey Madan (Parasoft)
  • David Leach (NXP)
  • Egon Baumann (Baumer)
  • Flavio Ceolin (Intel)
  • Ioannis Glaropoulos (Nordic Semiconductor)
  • Jack Rosenthal (Google)
  • Kate Stewart (Linux Foundation)
  • Lauren Murphy (Intel)
  • Lukas Itin (Baumer)
  • Nicole Pappler (Functional Safety Manager, AlektoMetis)
  • Nikolay Anikeev (Synopsys)
  • Paul Fagerburg (Google)

Security Committee

  • Bekim Quela (Baumer)
  • David Brown (Linaro, Security Architect)
  • David Leach (NXP)
  • Denis Brockus (Google)
  • Flavio Ceolin (Intel, Security WG Chair)
  • Kate Stewart (Linux Foundation)
  • Ruud Derwig (Synopsys)

Marketing Committee

  • Alexander Gerstner (Baumer)
  • Anthony Nash (T-Mobile USA)
  • Barna Ibrahim (Google, Marketing WG Chair)
  • Bjarne Kielsholm-Ribalaygua (Oticon)
  • Chris Miller (Bose Corporation)
  • Chris Turner (Intel)
  • Colleen Harig (Memfault)
  • Cristina Brandtstetter (FIWARE Foundation)
  • Danny Watson (Infineon Technologies AG)
  • Daria Kolarczyk (AVSystem)
  • David Eriksson (teenage engineering)
  • Ebba Simpson (Linaro)
  • Frédéric Desbiens (Eclipse Foundation)
  • George Grey (
  • Jeff Mulhausen (SiFive)
  • John Ferguson (Wind River)
  • Jonathan Beri (Golioth)
  • Jonathan Kaye (Laird Connectivity)
  • Long Lu (Northeastern University)
  • Matt Fleming (BayLibre)
  • Matt Gordon (Silicon Labs)
  • Megan Hansen (NXP)
  • Michael Gielda (Antmicro)
  • Pål Kastnes (Nordic Semiconductor)
  • Phil Brownfield (Synopsys)
  • Phillip Torrone (Adafruit)
  • Ric Wheeler (Facebook)
  • Ricardo Camacho (Parasoft)
  • Uwe Rass (Sivantos)
  • 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.