The device protects itself; Robustel maintains 2.x through 2031; four things are always yours.
This guide follows one RobustOS Pro 2.4.x device through its whole life. At each moment it says what the device (and Robustel) does, what is left to you, and which guide has the detail. It describes the product as it behaves today: nothing planned, nothing assumed.
Eleven moments, from knowing what you hold to handing it over.
1Know what you're holding2Build the standard3Put the fleet into service4An update arrives5Something goes wrong6A vulnerability is published7Patch it8Show where you stand9Your application moves on10Fix it without going there11Retire it or hand it over
| Moment | What the device and Robustel do | What you do |
|---|---|---|
| 1. Know what you're holding | Dashboard shows the release, kernel line, Cybersecurity Version and hardware identity | Record versions; check your factory baseline |
| 2. Build the standard | Captures a complete device as a clone package | Build one reference unit; decide which credentials must be unique |
| 3. Put the fleet into service | Factory pre-install of your image; factory pre-registration to your RCMS account | Choose the route; have RCMS switched on at the factory or in your build |
| 4. An update arrives | Verifies, installs in place, removes nothing you installed | Back up, start the update, validate on one device first |
| 5. Something goes wrong | Aborts failed installs; restores your last backup after three failed boots | Keep backups current; physical access for the last resorts |
| 6. A vulnerability is published | Assesses Critical and High within 3 / 5 days | Subscribe to announcements; report through the Security Centre |
| 7. Patch it | Fixes in 14 / 30 days, as security update packages | Install them; maintain the software you added yourself |
| 8. Show where you stand | Versions per device; fleet view in RCMS; fixes in release notes | Review the fleet periodically |
| 9. Your application moves on | Gives you a Debian machine to update it on | Run your own update route: signed repository + SSH |
| 10. Fix it without going there | Automatic recovery; RCMS remote access | Keep backups current; plan physical access |
| 11. Retire it or hand it over | Maintained through 2031; identity follows the serial number | Export, reset, release from RCMS |
Moments 1 to 3.
| Robustel and the device | You | |
|---|---|---|
| 1 · Know what you're holding | The Dashboard shows the release, kernel line, Cybersecurity Version and hardware identity. | Record versions; check your factory baseline. |
| 2 · Build the standard | Captures a complete device as a clone package. | Build one reference unit; decide which credentials must be unique. |
| 3 · Put the fleet into service | Factory pre-install of your image; factory pre-registration to your RCMS account. | Choose the route; have RCMS switched on at the factory or in your build. |
What the device does. The Dashboard's System Information panel shows the aggregate firmware version (the one number that identifies the release), the kernel line, the Cybersecurity Version and the hardware identity: serial number, MAC addresses, IMEI. The modem firmware version is on the Cellular status page. The base image version, per-component versions and whether the unit carries a custom factory image are command-line checks.
What it does not do. There is no single "patch level" field. The Cybersecurity Version is the certification baseline the firmware was certified against; it does not change when individual fixes are installed. A release's fixes are listed in its release notes.
What you do. Record the aggregate version and the modem firmware version for each unit; together they identify its software state for most support conversations. Check which factory baseline your units carry (/etc/version-clone is present on custom or cloned units) before you ever need recovery.
Detail: What's on Your Device.
What the device does. Your side of the device is a Debian machine: SSH, sudo, apt. Set one reference device up by hand or by script, then capture it as a clone package from the command line (rbt-system-mgmt clone create). The package holds the device's complete software state: your configuration, packages, apps, containers and data, and the Robustel system software on the reference unit. A configuration file can also be exported and imported on its own (a super-admin operation), but it carries settings only.
What travels with the image. A clone carries the device's identity material: SSH host keys, TLS certificates, VPN credentials and cloud identifiers. It becomes the factory baseline of every unit it is restored onto. It restores only onto the same model and the same hardware variant. And whatever state the reference unit is in propagates: automatic USB updates and remote management included.
What you do. Decide which credentials must be unique per device and issue them after restore. Before capturing, check that automatic USB updates are off (unless you need them) and that remote management is in the state you want.
Detail: Setting Up Your Devices; Securing Your Device.
What Robustel and the device do. Two routes for the image: send the clone package to Robustel Technical Support and it can be pre-installed during manufacturing (the practical route at volume), or restore it per device by USB. Per-site settings go on top as a configuration file. Robustel can also pre-register the devices to your RCMS account at the factory, by serial number and IMEI or MAC address: with RCMS switched on at the factory, each device appears in your account the first time it starts, with no setup. You can also add a device to your account yourself, by its serial number. Otherwise RCMS ships switched off; once it is enabled, a device's cloud identity is derived from its serial number, so it re-registers itself after a reset or re-image. Which RCMS operations are available depends on your RCMS plan.
What you do. If you will manage the fleet remotely, have RCMS switched on at the factory or switch it on in your build. Restoring the default configuration switches it off again, so check it after any configuration restore.
Detail: Setting Up Your Devices.
Moments 4 and 5.
| Robustel and the device | You | |
|---|---|---|
| 4 · An update arrives | Verifies, installs in place, removes nothing you installed. | Back up, start the update, validate on one device first. |
| 5 · Something goes wrong | Aborts failed installs; restores your last backup after three failed boots. | Keep backups current; plan physical access for the last resorts. |
What the device does. Nothing installs on its own: an update is started by you (Web UI, command line, or a USB stick with your key) or by your fleet operator through RCMS. A standard firmware update is signature-verified (RSA-4096) before it installs; a package that fails verification does not install. It installs in place and finishes with a reboot. It removes nothing you installed: apps, containers, settings and data are untouched, and your Debian packages are still installed, though a package version can change. If the installation fails, it aborts and the device keeps running its old software. Phasing a rollout across a fleet is done on the RCMS side.
What it does not do. The device never creates a backup on its own, not even before an update.
What you do. Back up first: your last backup is your rollback point. Know which package type you are applying: a firmware update keeps your software, a full-image install erases it, a clone restore replaces it. Validate a new release on one device, check the package versions you depend on, then roll it out.
Detail: What an Update Changes; Updating Your Device.
What the device does. Failures are handled in stages:
What it does not do. A factory restore clears the on-device backups, including the backup kernel copy, so a freshly restored device has nothing to recover to until you create a new backup.
What you do. Back up before every change, and keep a clone package off the device as well. Know what your factory baseline contains before you press RST.
Detail: When Something Goes Wrong.
Moments 6 to 8.
| Robustel and the device | You | |
|---|---|---|
| 6 · A vulnerability is published | Assesses Critical and High within 3 / 5 days. | Subscribe to announcements; report through the Security Centre. |
| 7 · Patch it | Fixes in 14 / 30 days, as security update packages. | Install them; maintain the software you added yourself. |
| 8 · Show where you stand | Versions per device; fleet view in RCMS; fixes in release notes. | Review the fleet periodically. |
What Robustel does. Robustel's Product Security Incident Response Team assesses every published Critical and High vulnerability affecting the software in the firmware image (the Debian packages Robustel ships, Robustel's own software and the Linux kernel) and fixes it, publishes a mitigation, or documents it as not affected. Critical: assessed within 3 days. High: within 5 days. Actively exploited vulnerabilities are prioritized regardless of score. Medium and low vulnerabilities are assessed case by case.
What you do. Subscribe to update and security announcements in the Robustel knowledge base; managed fleets also see available updates in RCMS. Report suspected vulnerabilities through the Robustel Security Centre (robustel.com/security-centre); reports are acknowledged within 7 calendar days. Software you added to the device yourself is yours to watch.
Detail: Keeping Your Device Secure Over Time; Maintenance After Debian 11.
What Robustel and the device do. Critical fixes within 14 days, High within 30. Fixes for the software Robustel ships arrive as individual security update packages, from the Robustel website or through RCMS, without a full firmware upgrade. The kernel does not change within 2.x; fixes are backported into it. Since 31 August 2026 the Debian 11 repositories receive no new fixes: apt still works against them, but new security fixes come only from Robustel.
What it does not do. Nothing is scheduled: every update is started by you or through RCMS. A package operation has no automatic rollback.
What you do. Back up, install the security update packages, and after the first update of a new release check the package versions you depend on. Maintain the Debian packages you added yourself.
Detail: Keeping Your Device Secure Over Time; Maintenance After Debian 11.
What the device and Robustel give you. Per device, the Dashboard shows the release and the Cybersecurity Version. For enrolled devices, RCMS gives you the fleet view. Release notes list the fixes each release contains, and security advisories are published on the Robustel Security Centre.
What you do. Review the fleet periodically: firmware versions, patch state, where each device generation stands in its support life, and who holds the USB keys and backups.
Detail: Keeping Your Device Secure Over Time; Securing Your Device.
Moment 9: your software updates on its own clock.
| Robustel and the device | You | |
|---|---|---|
| 9 · Your application moves on | Gives you a Debian machine to update it on. RCMS does not carry your packages or containers. | Run your own route: a signed repository you control, driven over SSH. |
What the device gives you. Your software updates on its own clock, separately from the firmware. Debian packages move to new versions with apt from the command line (the Web UI's Debian Management page installs and removes only). RobustOS Pro apps are updated in the App Center, one device at a time. Containers are managed with the Docker command line (Docker is not pre-installed).
What it does not do. RCMS carries Robustel firmware, Robustel-built apps and device configuration. It does not carry your own packages or containers. A golden image builds a fleet; it does not update one.
What you do. Bring your own route, the one you would use for any Debian estate: publish your packages to a signed repository you control, point the devices at it, and drive the upgrade over SSH with your own tooling. Stage it on one device first; your rollback is the previous version in your repository plus the backup you took.
Detail: Updating Your Device.
Moment 10: the first recovery stages need nobody on site.
| Robustel and the device | You | |
|---|---|---|
| 10 · Fix it without going there | Automatic recovery; RCMS remote access for enrolled devices. | Keep backups current; plan physical access. Switch logs to persistent storage if you need them after a restart. |
What the device and RCMS do. The first recovery stages need nobody on site: a failed install aborts and a device that cannot boot restores your last backup. For enrolled devices, RCMS provides remote access (Essentials plan and above) along with firmware and configuration pushes.
What it does not do. The RST button and a USB re-flash need hands on the device. The system journal is kept in memory by default and is lost at reboot.
What you do. Keep backups current: that is what keeps recovery in the automatic stages. If you need logs to survive a restart, switch the log destination to persistent storage.
Detail: When Something Goes Wrong; What's on Your Device.
Moment 11: 2.x is maintained through 2031.
| Robustel and the device | You | |
|---|---|---|
| 11 · Retire it or hand it over | Maintained through 2031; the identity follows the serial number. | Export, reset, release from RCMS. |
What Robustel does. The 2.x generation is maintained through 2031. After that, no fixes or support are available for it; service beyond that scope needs a separate contract. Moving a device to 3.x (Debian 13) is a reflash and a planned migration, not an update, and it is not required while 2.x is maintained.
What the device does. A factory reset returns the device to its factory baseline: a clean default state, or your custom image if your units carry one. On devices provisioned for it, the writable storage is encrypted with a key bound to the device's hardware. The serial number and IMEI stay with the device for life, and its cloud identity is derived from the serial number.
What you do. Export what you need first: a clone package and the configuration file. Factory-reset the device. Have it released from your RCMS account: a factory reset alone does not unbind it. For specific data-sanitization requirements, agree the procedure with Robustel support.
Detail: End of Life; Maintenance After Debian 11.
The device and Robustel Verify every firmware update · keep what you installed through a firmware update · abort failed installs, recover after three failed boots · fix Critical and High in 14 and 30 days through 2031 · keep the kernel stable within 2.x. | You Create backups · choose when to update, validate on one device · update your own packages, apps and containers · control physical access and the USB key · release devices from RCMS when they change hands. |
| The device and Robustel | You |
|---|---|
| Verify every firmware update before it installs | Create backups: the device never does |
| Keep everything you installed through a firmware update | Choose when to update, and validate on one device first |
| Abort a failed install; restore your last backup after three failed boots | Update your own packages, apps and containers |
| Fix Critical and High vulnerabilities within 14 and 30 days, through 2031 | Control physical access, the USB update path and its key |
| Keep the kernel and your platform stable within 2.x | Release devices from RCMS when they change hands |
What's on Your Device Every part of the stack and where to see its version. | Setting Up Your Devices The four provisioning routes. | What an Update Changes What survives every operation. |
When Something Goes Wrong The recovery ladder. | Securing Your Device The deployment hardening checklist. | Updating Your Device How to perform each update. |
Keeping Your Device Secure Over Time Patching and support life. | End of Life Decommissioning and ownership transfer. | Maintenance After Debian 11 2.x maintained to 2031. |
| Next · step 3 of 13What's on your device →Every part of the software stack, and where to see its version. |