Request a firmware review
Menu
Teams choosing an operating system for a new microcontroller product

Compare Zephyr, FreeRTOS and bare metal for your product

Weight each criterion for your product, score each option and read the weighted totals. The weights and scores filled in are a fictional example for one product, not a ranking.

Key characteristics

Options
Zephyr, FreeRTOS and bare metal
Criteria
Seven to start; edit them or add your own
Default example
Fictional weights and scores for one product
Runs
In your browser with nothing sent

Selection worksheet: Compare Zephyr, FreeRTOS and bare metal for your product

The weights and scores are a fictional example for one product, not a ranking. Weight each criterion from 1 to 5 for your product, score each option from 1 (poor) to 5 (strong), and the weighted totals update. Nothing leaves your browser.

CriterionWeightZephyrFreeRTOSBare metalRemove

Weighted totals

Zephyr
113 of 125
FreeRTOS
93 of 125
Bare metal
75 of 125

Total = the sum of weight × score for each criterion. A close result means the criteria, not the totals, should decide; write down why.

The choice between Zephyr, FreeRTOS and plain bare-metal code shapes everything after it: which drivers you write yourself, which bootloader and update tools you get, how much memory is left for your application, and who fixes security bugs five years from now. It is also a choice teams often make out of habit. This worksheet makes the reasons explicit. You weight what matters for your product, score each option against it, and keep a record of why you chose.

The default weights and scores are a fictional example for one product. They are not a ranking of Zephyr, FreeRTOS or bare metal. A different product, team or microcontroller would produce different numbers and could reasonably reach the opposite answer.

How to use it

  1. Read the seven criteria, then edit, remove or add your own. Good criteria come from your firmware requirements.
  2. Weight each criterion from 1 (nice to have) to 5 (decides the product).
  3. Score each option from 1 (poor) to 5 (strong) for your hardware and your team.
  4. Read the totals, then read the rows again. Download the CSV as the record of the decision.

What the criteria ask

Criterion What to check
Fits the microcontroller and its vendor SDK Is the chip supported out of the box, and does the vendor SDK assume one option?
Bootloader and update support we can use as is Can you use a bootloader, signing tools and an update protocol without writing your own?
Bluetooth LE stack included and maintained Is a maintained stack part of the option, or do you integrate one yourself?
Team experience today What your engineers have shipped before, scored honestly
Long-term support and security fixes Who backports fixes, and for how long
Memory left for the application Flash and RAM left after the kernel and stacks
Licensing the company is comfortable with Whether your company and customers accept the license terms

Some criteria have checkable facts behind them. Zephyr’s stable releases are supported for about a year (two release cycles), and its long-term support releases are maintained for about five years. FreeRTOS LTS libraries get security updates and critical bug fixes for two years. Zephyr is licensed under Apache 2.0 and the FreeRTOS kernel under the MIT license. Bare-metal code is the code you write plus what the chip vendor supplies, so its support period is yours to plan. Other criteria, such as team experience, only you can score.

Reading the default example

Example (fictional). Loamwick scored the options for the LW-1 probe, which runs on a Bluetooth LE microcontroller with 1 MB of flash and has to accept signed updates. Weights: bootloader and update support 5; microcontroller fit, Bluetooth LE stack and long-term support 4 each; team experience and memory 3 each; licensing 2. Scores, in the order Zephyr, FreeRTOS, bare metal: microcontroller fit 5, 4, 5; update support 5, 3, 2; Bluetooth LE stack 5, 3, 1; team experience 3, 4, 4; long-term support 5, 4, 1; memory 3, 4, 5; licensing 5, 5, 5. Weighted totals: Zephyr 113, FreeRTOS 93 and bare metal 75, each of 125.

The totals are the least interesting part. In this example Zephyr came out ahead on the rows Loamwick weighted highest (update support, the Bluetooth LE stack and long-term support) and behind on team experience and memory, where it scored 3 against 4 or 5. That tells the team where to spend effort: learning Zephyr early, and watching flash use closely, which the flash budget calculator later showed was the right worry. Had Loamwick weighted team experience and memory higher, the gap would have been smaller.

How it calculates

For each option, the worksheet multiplies every score by its criterion’s weight and adds the results. The maximum is the sum of the weights times 5. In the example the weights add up to 25, so the maximum is 125. Zephyr’s 113 is 4 × 5 + 5 × 5 + 4 × 5 + 3 × 3 + 4 × 5 + 3 × 3 + 2 × 5.

Limits

  • Scores are opinions with numbers attached. The value is in writing down why each score is what it is. Keep a short note for each one with the CSV.
  • A close result should not be decided by the totals. If two options are within a few points, decide on the one or two criteria that matter most, and record why.
  • Three options only. The worksheet compares Zephyr, FreeRTOS and bare metal. Another RTOS your vendor supports, or Linux on a larger processor, needs its own comparison.
  • Facts change. The support periods and licenses above were checked in November 2026. Check the current release pages before you decide.

What to do next

Our firmware development work starts with this choice, made with you and written down, and sustaining releases keep track of the support clock afterwards. For processors that run Linux, see embedded Linux. More on architecture choices in the firmware architecture section of Field Update.

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.