Request a firmware review
Menu
Startups with devices in the field and no full-time firmware team yet

Maintenance releases on a schedule you can plan around

After launch, firmware needs a steady rhythm of small, signed, staged releases. We run that rhythm with one named technical lead and a plain-English report after every release.

Key characteristics

Rhythm
Scheduled maintenance releases plus urgent fixes
Account lead
One named technical lead for every release
Every release
Release notes, SBOM, staged rollout, release report
You provide
Priorities, release approvals, fleet telemetry access

The first release is a project. Every release after it is a habit, and habits are where small teams slip. A library ships a security fix and nobody notices for months. The RTOS release you built on reaches the end of its support. A small fix waits for a big feature, and the devices in the field wait with it. Sustaining releases is an ongoing arrangement in which we keep your firmware current and ship scheduled maintenance releases through your update pipeline, with one technical lead accountable for each release.

What the arrangement covers

  • Scheduled maintenance releases at a cadence we agree with you, carrying bug fixes, small improvements and dependency updates. An urgent security fix can go out between scheduled releases when it needs to.
  • Dependency and security updates. We check each release’s SBOM against new vulnerability reports, record in a triage log whether each one affects your product and why, and update the RTOS, stacks and libraries you ship. Security fixes are kept separate from feature changes where that is technically feasible, which the EU Cyber Resilience Act will expect of products in its scope from December 11, 2027.
  • Long-term support tracking. Zephyr’s long-term support releases are maintained for about five years (the current one, 3.7, until July 27, 2029), and its regular releases for about a year. FreeRTOS LTS libraries get two years: the 202406 LTS ended on June 30, 2026, and the 202604 LTS runs to April 30, 2028. A Yocto Project LTS release is supported for four years. We keep a dated plan for moving before your release stops receiving security fixes.
  • Staged rollouts. Every release goes out in waves, with a soak period between them and a halt rule written down before the first wave starts. The staged rollout planner and the update policy worksheet set out the numbers and the rules.
  • Release records. Release notes, an updated SBOM, a test report and a release report for every release.

The technical account lead

Every client has one named technical lead. In a sustaining arrangement that person keeps the release calendar, agrees with you what goes into each release, runs or supervises each rollout, and writes two things:

  • A weekly status in plain English: what was done, what was measured, what is blocked and what is next.
  • A release report after every release, described below.

You always know who to ask, and the answer is in writing. More on this in how we work.

What a release report contains

The release report is one page, written for founders, board members, investors and support staff as well as engineers.

Section What it says
What changed The fixes and improvements in plain language, with a link to the full release notes
Who got it, and when Each wave: how many devices, when it started, how long it soaked
What went wrong Update failures, rollbacks and devices that went silent, with the cause where known
Field signals Battery, crash and reconnect figures compared with the previous version, where your devices report them
Security Vulnerabilities fixed, those assessed as not affecting you, and the SBOM version
Open risks and next steps What is still being watched and what the next release will carry

Example (fictional). Loamwick’s LW-1 firmware 1.1.0, released 2026-11-20, replaces 1.0.2. The report’s first section says moisture readings no longer drift upward after 30 days in wet clay, the gateway now sets the sensor wake-up interval, every report includes battery voltage, and probes refuse images signed with the retired development key. The waves are Loamwick’s own 4 bench probes, then 12 trial probes, then the remaining 24, with 48 hours between waves and a halt rule for any probe that rolls back or goes silent. The report carries forward one known issue: Rev C probes read temperature 0.5 °C high above 40 °C. The release notes builder produces the matching notes, and the example project tells the whole story.

How the arrangement is reviewed

A sustaining arrangement should keep earning its place. At an interval set in the agreement, we review it with you, using the records above:

  • Releases shipped against the calendar, with rollbacks and halts and their causes.
  • The vulnerability triage log, and anything still open.
  • RTOS, library and platform support dates falling in the coming year.
  • Whether the cadence and scope still fit the product and the budget.
  • Whether your own team is ready to take releases over.

A review can change the cadence or the scope, or end the arrangement with a planned handover. When you hire firmware engineers, documentation and onboarding is how the work moves to them, ending with a release your team ships while we watch. Terms are set out in each agreement.

Why a support period needs a plan

Regulation is turning release discipline into an obligation. Under the EU Cyber Resilience Act, from December 11, 2027, products in its scope need a support period of at least five years (or the expected time in use, if shorter), and security updates during it must be provided free of charge, with a narrow exception for tailor-made business products. The UK’s product security regime has required manufacturers of consumer connectable products to publish their minimum security update period since April 29, 2024. A support period is a promise to keep shipping releases, and a sustaining arrangement is one way to keep it. This is not legal advice; firmware security covers the wider picture.

Where to start

If you have devices in the field and nobody who owns their firmware, start with a firmware review: we look at your code, your update pipeline and your release history and tell you in writing what a sustainable release rhythm looks like for your product. If we built your update pipeline, sustaining releases is the usual next engagement. Request a firmware review, or read more in the updates and releases 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.