Zephyr RTOS is one of the fastest-growing real-time operating systems for resource-constrained IoT devices. Developed under the Linux Foundation under an Apache 2.0 license, it combines a small memory footprint with a rich networking stack, support for hundreds of boards, and a modular architecture. In this guide we explain what Zephyr RTOS is, how its kernel works, when it is worth choosing over FreeRTOS, and how it supports security and OTA updates in production deployments.
In short: Zephyr RTOS is an open-source real-time operating system for microcontrollers that offers a kernel with a footprint from around 8 KB of RAM, a built-in networking stack (Bluetooth LE, Thread, MQTT, CoAP, LwM2M), and support for more than 750 boards across the Arm Cortex-M, RISC-V, Xtensa, and ARC architectures — so it scales from a battery-powered sensor to an edge gateway.
What is Zephyr RTOS?
Zephyr RTOS is a modular real-time operating system designed for resource-constrained embedded devices — from 8-bit sensors to 64-bit processors. The project is managed by the Linux Foundation and developed by more than 1,300 contributors and companies such as Nordic Semiconductor, Intel, and NXP.
Unlike monolithic Linux, Zephyr runs on microcontrollers with just a few kilobytes of memory. Configuration is based on the Kconfig system and Device Tree, which lets you select precisely the components a given application requires and keep the firmware image to a minimum.
How does the Zephyr RTOS kernel work?
The Zephyr RTOS kernel is a priority-based preemptive scheduler that supports both cooperative and preemptive threads. It delivers deterministic response times on the order of microseconds, which is essential in industrial control and real-time telemetry.
To manage concurrency, Zephyr provides threads, workqueues, semaphores, mutexes, and timers. A built-in power manager switches the core into sleep modes, which directly extends battery life — a topic we cover in more detail in our post on energy efficiency in IoT devices.
The most important kernel components are:
- Priority scheduler — cooperative and preemptive threads with a configurable number of priority levels.
- Memory management — static allocation, heaps, and memory pools that minimize fragmentation.
- Networking stack — native IPv6/IPv4, 6LoWPAN, Bluetooth LE and Thread, plus the MQTT, CoAP, and LwM2M protocols.
- Hardware layer — a unified driver API for GPIO, I2C, SPI, UART, and ADC, independent of the chip vendor.
Zephyr RTOS vs. FreeRTOS — which one to choose?
Zephyr RTOS is a complete platform with a built-in networking stack and driver model, whereas FreeRTOS is a lightweight kernel extended with separate libraries. The choice depends on the complexity of the project and the resources of your team.
FreeRTOS works well in simple applications and where a minimal footprint matters (the kernel takes about 6–12 KB) and a broad base of examples is valuable; we write more about this kernel on our FreeRTOS for IoT firmware page. Zephyr RTOS wins in projects that require wireless connectivity, multiple hardware architectures, and a long life cycle with remote updates.
In practice, it helps to consider a few criteria:
- Connectivity — if the device needs Bluetooth LE, Thread, or a native IP stack, Zephyr provides them out of the box.
- Portability — a single source base runs on many microcontroller families without rewriting the hardware layer.
- Simplicity — for a simple controller with no networking, FreeRTOS is often faster to deploy and lighter to maintain.
What hardware does Zephyr RTOS support?
Zephyr RTOS supports more than 750 development boards across several processor architectures: Arm Cortex-M and Cortex-A, RISC-V, x86, ARC, and Xtensa (including ESP32 chips). This makes it one of the most versatile RTOSes on the market.
Popular platforms include Nordic nRF52/nRF53 chips (Bluetooth LE), STM32, NXP i.MX RT, and Espressif ESP32. Selecting the right microcontroller and designing the board is a stage we handle as part of PCB design for IoT. Zephyr boots on a kernel that takes from around 8 KB of RAM and a few dozen KB of Flash.
How does Zephyr RTOS support security and OTA updates?
Zephyr RTOS integrates with the MCUboot bootloader, which provides secure boot, firmware signature verification, and a rollback mechanism if an update fails. This is the foundation of secure remote updates across an entire device fleet.
The system supports TLS 1.2/1.3, cryptographic libraries (mbedTLS, TinyCrypt), and hardware security elements. Combined with secure boot and a process of OTA updates at scale, it lets you build devices compliant with the requirements of the RED directive and the Cyber Resilience Act.
Where is Zephyr RTOS used in IoT projects?
Zephyr RTOS proves its worth wherever wireless connectivity, low power draw, and a long product life cycle are needed — from wearables to industrial sensor networks. The built-in networking stack shortens the time to deliver communication features by as much as several weeks, because the team does not have to integrate and test external libraries. It also makes certification and long-term code maintenance easier.
Typical deployments include Bluetooth LE and Thread sensors, edge gateways, metering, and devices with local AI inference. Zephyr works well with TinyML models on the ESP32-S3, and we deliver the finished device as custom IoT hardware together with firmware and cloud integration.
Frequently asked questions (FAQ)
Is Zephyr RTOS free?
Yes. Zephyr RTOS is fully open source and released under an Apache 2.0 license, which allows commercial use with no license fees. The project is developed by the Linux Foundation, and commercial support is offered by chip vendors such as Nordic Semiconductor.
How does Zephyr RTOS differ from FreeRTOS?
Zephyr is a complete platform with a built-in networking stack, driver model, and power manager, whereas FreeRTOS is a minimalist kernel extended with separate libraries. Zephyr is a better fit for complex, wireless devices, while FreeRTOS suits simple applications with a small footprint.
Does Zephyr RTOS run on the ESP32?
Yes. Zephyr RTOS officially supports Espressif ESP32 chips on the Xtensa core as well as ESP32-C variants on the RISC-V architecture. Wi-Fi, Bluetooth, and peripheral drivers are available, so you can build complete IoT devices on this popular platform.
Summary and key takeaways
Zephyr RTOS is a mature, open-source real-time operating system that combines a small footprint with a rich networking stack and support for hundreds of hardware platforms. For companies building IoT products, this means a shorter time to deployment, easier fleet scaling, and readiness for security requirements.
The FSS team designs hardware, writes firmware on Zephyr RTOS and FreeRTOS, and builds the cloud backend for complete IoT solutions. If you are planning a new device or a firmware migration, explore our custom IoT hardware offering and let's talk about your project.
{“@context”: “https://schema.org”, “@type”: “Article”, “headline”: “Zephyr RTOS for IoT: A Real-Time Operating System”, “description”: “Zephyr RTOS for IoT – a guide: what it is, how the kernel works, a comparison with FreeRTOS, supported hardware, security and OTA.”, “author”: {“@type”: “Organization”, “name”: “FSS Technology”}, “publisher”: {“@type”: “Organization”, “name”: “FSS Technology”}, “inLanguage”: “en”, “keywords”: “Zephyr RTOS, RTOS, IoT, firmware, FreeRTOS, ESP32, MCUboot”}
{“@context”: “https://schema.org”, “@type”: “FAQPage”, “mainEntity”: [{“@type”: “Question”, “name”: “Is Zephyr RTOS free?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Yes. Zephyr RTOS is fully open source and released under an Apache 2.0 license, which allows commercial use with no license fees. The project is developed by the Linux Foundation, and commercial support is offered by chip vendors such as Nordic Semiconductor.”}}, {“@type”: “Question”, “name”: “How does Zephyr RTOS differ from FreeRTOS?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Zephyr is a complete platform with a built-in networking stack, driver model, and power manager, whereas FreeRTOS is a minimalist kernel extended with separate libraries. Zephyr is a better fit for complex, wireless devices, while FreeRTOS suits simple applications with a small footprint.”}}, {“@type”: “Question”, “name”: “Does Zephyr RTOS run on the ESP32?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Yes. Zephyr RTOS officially supports Espressif ESP32 chips on the Xtensa core and ESP32-C variants on the RISC-V architecture. Wi-Fi, Bluetooth, and peripheral drivers are available, so you can build complete IoT devices on this popular platform.”}}]}