Should you build or buy Embedded & Real-Time Operating System (RTOS)?

An RTOS schedules tasks with deterministic, bounded response times for embedded devices, managing memory, interrupts and inter-task communication on hardware from microcontrollers to safety-critical systems. Device manufacturers select one as the foundation their application firmware runs on, choosing between free open-source kernels and commercially licensed, certified options.

Copy reviewed 2026-10-04 · Research revision 2026-09-25

Sources: nordicsemi.com; zephyrproject.org; threadxalliance.org; qnx.software; docs.zephyrproject.org

Default to Zephyr or FreeRTOS for products without a safety-certification mandate and put engineering into the firmware above the kernel; reserve VxWorks, QNX or ThreadX safety artifacts for programs where the certification evidence and a support counterparty are contractual requirements.

Build it, buy it, or bridge?

⚒ Build it
✓ Buy it
➔ Bridge
Cost shape
Zephyr and FreeRTOS are royalty-free; ThreadX Alliance access is EUR 5,000 or 25,000 a year, artifacts extra.
VxWorks and QNX are commercial licenses; the certified editions carry the safety evidence you pay for.
Run Zephyr or FreeRTOS free for the kernel; license certification evidence only where it is required.
Time to value
Nordic's Zephyr-based nRF Connect SDK is production-ready and used in hundreds of products already.
VxWorks and QNX come with vendor lifecycle support and pre-built certification packages.
Ship on Zephyr or FreeRTOS now; add a commercial certification package only when a regulator requires it.
Differentiation captured
The kernel confers no competitive edge; differentiation lives in the application firmware built on top of it.
Vendor owns certification evidence for DO-178C, ISO 26262 or IEC 61508 that a team cannot self-generate.
Own your firmware and product logic entirely; the RTOS underneath is not where the edge lives either way.
AI feasibility today
AI coding tools speed firmware work; 83.5% of embedded pros RunSafe surveyed shipped AI-generated code.
AI does not generate safety-certification evidence; that paper trail is what commercial vendors sell.
Use AI coding tools to build firmware on a free kernel; buy certification evidence only where mandated.
Who it fits
Products without a safety-certification mandate, where Zephyr or FreeRTOS is a proven production choice.
Programs requiring DO-178C, ISO 26262 or IEC 61508 certification evidence plus a support counterparty.
Products that run Zephyr day to day but need a certified option for one safety-critical subsystem.

When building makes sense

Zephyr and FreeRTOS are mainstream production choices, not experimental alternatives. Nordic Semiconductor's nRF Connect SDK is built on Zephyr and used in hundreds of products, the Lildog and Lilcat pet GPS trackers and Brilliant Labs' Halo smartglasses run on it, and Panic's Playdate handheld game device runs on FreeRTOS. AI coding tools are part of the work now too: a RunSafe survey found 83.5 percent of embedded professionals had already shipped AI-generated code to production. Both Zephyr and FreeRTOS are royalty-free, and the practical ceiling on this path is safety certification: Zephyr's own safety program is still working toward IEC 61508 SIL 3 certification, short of the ISO 26262 or IEC 62304 evidence commercial vendors already carry.

When buying makes sense

Buy certification evidence, not a kernel, when the product is regulated. VxWorks Cert Edition carries certification evidence for IEC 61508, ISO 26262 ASIL D and IEC 62304 Class C, and QNX OS for Safety is certified to ISO 26262 ASIL D, IEC 61508 SIL 3 and IEC 62304 Class C. That certification package, plus the vendor's lifecycle support, is what you are actually paying for. None of that certification evidence transfers from a free kernel. Zephyr's safety program hasn't finished its IEC 61508 SIL 3 certification, so an aviation, automotive or medical program can't use it off the shelf for that evidence today. Eclipse ThreadX sits in between: the code is free, and ThreadX Alliance members can license its safety artifacts for an additional fee. Paying commercial RTOS prices for a consumer product with no certification mandate spends money on evidence nobody will ever ask you to produce. Buy where a regulator, customer contract or safety standard requires the certification artifacts.

The desk read

Build-versus-buy analysis for Embedded & Real-Time Operating System (RTOS) is being written. In the meantime, the framework that drives every B4 call is on the B4 Index page.

Representative vendors BlackBerry QNXEclipse ThreadX + 4 more, listed in the full index

Frequently asked

What is a real-time operating system (RTOS)?

It is the scheduling layer under a device's firmware. It runs tasks with bounded response times and manages memory, interrupts and inter-task communication. The kernel itself confers no competitive edge; the value in a device sits in the firmware built on top of it, which is why free kernels like Zephyr and FreeRTOS ship in so many commercial products.

Is FreeRTOS or Zephyr good enough for production?

Yes, for most products without a safety-certification mandate. Nordic's Zephyr-based nRF Connect SDK is used in hundreds of products, and Panic's Playdate handheld runs on FreeRTOS.

When do you actually need a commercial RTOS like VxWorks or QNX?

When a regulator or customer contract requires certification evidence under DO-178C, ISO 26262, IEC 61508 or IEC 62304. That evidence and the multi-year support commitment behind it is what commercial vendors sell, not scheduling capability itself.

What are the main RTOS options?

Zephyr and FreeRTOS are the dominant free, open-source kernels; BlackBerry QNX and Wind River VxWorks are the commercial, certifiable options; Eclipse ThreadX offers free code with separately licensed safety artifacts.

The B4 Index scores every software category on two axes, strategic differentiation and AI feasibility, to classify it Build, Buy, Bridge, or Beware. See the full methodology.