Each generation is maintained for ten years. After that, no support, fixes or root-cause analysis.
| Generation | Support life |
|---|---|
| 2.x · Debian 11 | Released 2022 · maintained through 2031 |
| 3.x · Debian 13 | End of 2026 (expected) · maintained through 2035 (expected) |
Every RobustOS Pro release generation has a defined support life, and every device eventually leaves service or changes hands. This guide covers the three questions that matter at that stage: when does support end, how do you retire a device cleanly, and how does a device move to a new owner.
When support ends
| Version | Based on | Release | Maintained through |
|---|---|---|---|
| 2.x | Debian 11 | 2022 | 2031 |
| 3.x | Debian 13 | End of 2026 (expected) | 2035 (expected) |
Each generation is maintained for ten years. For 2.x, Debian's own support for Debian 11 ended on 31 August 2026; from 1 September 2026 to 2031, Robustel provides critical and high-severity vulnerability fixes and critical bug fixes. The details are in Keeping Your Device Secure Over Time and Maintenance After Debian 11.
After the maintenance life ends, no technical support, bug fixes, security fixes, or root-cause analysis are available for that generation. If you require service beyond the defined scope, contact your local sales representative — services beyond the standard scope are subject to a separately defined service contract.
Moving from 2.x to 3.x is a planned migration, not a firmware update.
Know where your fleet stands The aggregate system version on the Dashboard tells you each release. | Plan migrations early With your Robustel contact, well before the maintenance life closes. | Keep a known-good state A clone package and the configuration file, off the device. |
Three steps. Check what your factory baseline contains before the device leaves your control.
3 Know your baseline Clean default, or your company's custom image? |
| 1 | A clone package (the complete device state) and the configuration file — once the device is reset, its working state is gone. |
| 2 | Web UI, or the RST button with physical access — returns the device to its factory baseline, removing your configuration, installed software, and data from the working system. |
| 3 | Know what your factory baseline contains Standard unit: a clean default state. Custom-factory-image unit: your company's pre-configured image — check before the device leaves your control. |
/etc/version-clone (present on custom/cloned units).On devices provisioned for it, the writable storage is encrypted with a key bound to the device's hardware — stored data is not readable off the storage medium on another device.
For deployments with specific data-sanitization or compliance requirements at decommissioning, contact Robustel support to agree the appropriate procedure for your units.
An enrolled device re-registers by serial number after a reset. Handle that deliberately at transfer.
Release from your RCMS account Fleet administration, or Robustel support. | → | The new owner claims it The hardware identity stays with the device for life. |
A RobustOS Pro device's cloud identity is derived from its serial number: if the device is enrolled in RCMS, it re-registers automatically after a factory reset or re-image — as long as RCMS stays enabled. That is a feature for recovery — a recovered device comes back online in your fleet by itself — and it is the one thing to handle deliberately at transfer:
Keeping Your Device Secure Over Time The support periods and patching. | What an Update Changes Backups, and what resets change. | When Something Goes Wrong Recovery of a device you still operate. |
| You have reached the end of the pathBack to Start here →The four questions and their short answers. |