Zephyr RTOS: 10 Years, 1000 Boards, so What's Next?

Ten years ago, Zephyr set out to solve a problem that many embedded teams quietly struggled with: how to build dependable real-time systems without being locked into a single vendor, toolchain, or proprietary stack. What followed was more than steady adoption. Zephyr introduced a new model built around portability, adoption of security best practices, modern tooling, and a shared ecosystem of drivers and middleware.

The combination of applying open source and security best practices and aiming to fill the gaps that embedded developers flagged in our initial research has helped steer Zephyr's development.  Following these practices has steadily resulted in more developers adopting it as an efficient and effective way to create products, which has led to over 1000 boards being upstreamed in the project.

As we look forward to the next 10 years, we again reached out to survey organizations that are using Zephyr, as well as those that are not, to identify what are the gaps, and what areas are important to developers.   This talk will go through some of the insights we've gained from that survey and provide a peek at the topics that the community will be addressing in the upcoming years.