Fixed-Scope Offer

RTOS Code & Architecture Review

"It runs" is not the same as testable, maintainable and defensible - especially in safety-critical products. In a fixed-scope review I examine your Zephyr or FreeRTOS firmware for architecture, determinism and testability - with a written, prioritized findings report you can use in release planning.

Where RTOS firmware gets caught out too late

These four issues block releases or bite you in audits

Determinism & Timing

Priority conflicts, long interrupt latencies, race conditions and unknown worst-case execution times usually surface in the field - not in the lab.

Test Gaps

Missing unit and integration tests, no hardware-in-the-loop regression, untestable task boundaries: "it runs" is not evidence - not for customers or auditors.

Safety-Critical Release Risk

Prototype-to-production breaks: memory handling, watchdogs, logging and error paths are taken seriously too late - exactly where safety-critical firmware fails silently.

CI/CD & Static Analysis

Builds on one machine only, no automated quality gates, warnings as noise - without a pipeline and static analysis, every fix becomes a manual leap in the dark.

What You Get

One to three weeks, fixed budget, written outcome

1

Code & Architecture Review

I review task architecture, task boundaries, memory and concurrency handling, watchdog and logging design of your Zephyr, FreeRTOS or custom-RTOS firmware.

Task DesignMemory HandlingInterrupt LatencyWatchdogsLogging
2

Test Architecture Assessment

Assessment of unit, integration and HIL tests, static analysis and CI/CD gates - including the gaps that actually endanger your release and your audits.

GoogleTestCppUTestHIL TestsStatic AnalysisCI/CD Gates
3

Prioritized Findings

A prioritized written report: what is mandatory before the next release, what can wait, what must not happen - plus a live debrief with your team and realistically estimated follow-up steps.

Findings ReportPrioritizationDebriefRecommendationsEffort Estimates

Four Steps to Release Transparency

1

Free Technical Review

15–20 minutes: you bring your specific question, we scope the review, access and goals.

2

Kickoff & Access

Fixed runtime (1–3 weeks), read access to repository and build environment, NDA on request. No write access, no production interference.

3

Review & Analysis

Architecture review, test-architecture assessment and timing-risk analysis on your actual code - including rebuilding and running the relevant test paths.

4

Report & Debrief

Written findings report with prioritized recommendations, joint walkthrough, optional implementation as a follow-up engagement.

Technologies in Scope

ZephyrFreeRTOSCustom RTOSC/C++GoogleTestCppUTestPytestHIL TestingStatic AnalysisCI/CDTask DesignInterrupt LatencyWatchdogsMCUbootTraceability

Frequently Asked Questions

How does the RTOS review work and what do you need for it?

After a free technical review we agree on a fixed scope with a one to three week runtime. You provide read access to the repository and build environment - there is no interference with productive systems, NDA on request.

What does the RTOS code & architecture review cost?

The scope is fixed, the price is an individual fixed price agreed after the review - it depends on system size and complexity and is confirmed in writing before the engagement starts. Inquiries are answered the same business day.

What is the outcome?

A written, prioritized findings report on architecture, determinism and timing, testability and CI/CD, plus a live debrief with your team. Optionally we outline realistic implementation paths as a follow-up engagement.

Is my firmware code kept confidential?

Yes. The review is confidential, access is limited to read-only, and results are not shared without your consent. On request we work anonymized - including any reference.

Clarify the release risk before the field does it for you

Start with a private technical review. Afterwards you know whether a firmware review makes sense for your system - and what it would cover.

Book Review