What's on Your Edge Computing Gateway

What's on Your Edge Computing Gateway

The stack at a glance

What you add sits on top. Robustel releases replace the layer beneath yours.

LayerWhat it holds
Software you installedDebian packages, apps, containers, your own programs · writable, yours
Your settings and dataConfiguration, user data, logs · writable, yours
Robustel system softwareLinux kernel, web interface, cloud agent, device services · Robustel releases
Factory pre-installed softwareAdded at production for your device family · read-only
OS foundationDebian-based read-only image
Boot softwareFirst program at power-on, kept with a backup copy · read-only

Your device runs a layered software stack: a read-only operating-system foundation at the bottom, Robustel's system software on top of it — the Linux kernel and Robustel's own components — and a writable layer above that holding everything you add: packages, apps, containers, your own programs, settings, and data.

Why the device behaves this way
Why the device behaves this way>

What survives which operation — including the one case where “not removed” is not the same as “unchanged” — is covered in What an Update Changes.

This document lists every part of the stack, what it does, and — the part you'll use most — where to see its version or state.

Software you installedDebian packages · apps · containers · your own programsWritable · yours
Your settings & dataConfiguration · user data · logsWritable · yours
Robustel system softwareLinux kernel · web interface · cloud agent · device servicesRobustel releases
Factory pre-installed softwareRead-only layer added at production for your device familyRead-only
OS foundationDebian-based read-only imageRead-only
Boot softwareFirst program at power-on · kept with a backup copyRead-only
The stack, top to bottom. Beside it, on their own tracks: radio firmware (modem, WiFi/Bluetooth), recovery artifacts (backups, factory baseline), and identity (serial number, RCMS, security anchors).

Every part, and where to see it

Your side is a Debian machine. Beside the stack: radio firmware, recovery artifacts and identity.

Software you installed
Debian Management or apt list --installed · App Center · docker.
Settings and data
Configuration exports as an XML file. Logs page for logs.
System software
Aggregate version and kernel line on the Dashboard.
Radio firmware
Modem: Cellular status page. WiFi/Bluetooth: command line.
Recovery artifacts
Backups and snapshots: Backup & Restore.
Identity and security
Serial number, MAC and IMEI on the Dashboard, beside the Cybersecurity Version: the certification baseline, not a patch level.

See every part in detail

Software you installed

Your side of the device is a Debian machine. You reach it over SSH, use sudo, and install software with apt, the same as any Debian 11 host (since 31 August 2026 the Debian 11 repositories receive no new fixes — see Maintenance After Debian 11). Robustel’s releases replace the layer beneath yours — they do not manage what you put here.

PartWhat it isWhere to see it
Debian packagesStandard Debian software you install with aptWeb UI → Debian Management, or command line: apt list --installed
RobustOS Pro appsApplications installed through the App Center — tracked separately from ordinary Debian packagesApp Center
ContainersDocker containers and images. Docker is not pre-installed — you install it from Debian yourself. It works alongside the device firewall; which container ports can be reached from outside is controlled with Custom Rules (Network → Firewall)docker command line
Your own programsSoftware you put on the device yourself rather than installing it from a package — it lives in the same writable layer as your packages, apps and containersCommand line

Your settings and data

PartWhat it isWhere to see it
ConfigurationEverything you set anywhere in the web interface — interfaces, firewall, VPN, users, services — held as a single file the device reads at boot. Settings only: it is not your installed software and not your data, so on its own it cannot rebuild a device.Web UI (any page); exportable and importable as an XML file (a super-admin operation)
User data & logsFiles, databases, and logs your applications writeLogs page (Web UI) / command line ¹

¹ By default the system journal is kept in memory and is lost at reboot; switch the log destination to persistent storage in the log settings if you need logs to survive restarts.

System software (managed through Robustel releases)

PartWhat it isWhere to see its version
Base operating systemThe read-only foundation image (Debian-based)The Dashboard (System Information) shows the aggregate (composite) firmware version, not the base image number on its own. The base system image version: command line /etc/version-system
Factory pre-installed softwareA read-only software layer added at production for your device familyCommand line: /etc/version-extend; also included in diagnostic exports
Robustel system componentsThe management layer: web interface, cloud agent, device servicesAggregate version on the Dashboard (System Information); per-component versions via command line (apt list --installed)
KernelThe Linux core. Its version line follows your device's hardware platform, so two models on the same RobustOS Pro version can show different kernel versionsThe Dashboard's System Information panel shows the kernel line — the mainline Linux version, not Robustel's build number; the exact installed package version via command line
Boot software (bootloader)The first program that runs at power-onNot shown in the UI — service/diagnostic level only

Radio firmware

PartWhat it isWhere to see its version
Cellular modem firmwareFirmware inside the modem module itself — updated on its own track, never as part of an OS updateCellular status page — firmware version field
WiFi/Bluetooth firmwareFirmware files shipped with the operating system, loaded at bootCommand line only (model-specific command); no UI field ²

² On some models the WiFi/Bluetooth firmware is also refreshed by standard firmware updates — see the model notes at the end.

Recovery artifacts and cloud identity

PartWhat it isWhere to see it
Backups & snapshotsRestore points you create; used by manual restore and by the automatic boot-failure recoveryWeb UI → Backup & Restore
Factory baselineWhat a factory reset returns to: a clean default state — or your company's custom factory image, if your units were ordered that wayCommand line: /etc/version-clone exists on units carrying a custom or cloned image; not shown in the Web UI
RCMS cloud identityThe device's registration with the RCMS fleet platform. RCMS is disabled by default; once enabled, identity is derived from the serial number — while RCMS stays enabled, the device re-registers automatically even after a full resetRCMS status page

Identity and security

PartWhat it isWhere to see it
Hardware identitySerial number, MAC addresses, IMEIDashboard → System Information
Cybersecurity VersionThe security-certification baseline the installed firmware was certified against. Not a patch level — it changes only with firmware certified against a newer baseline; individual fixes are listed in release notesDashboard → System Information
USB update keyThe key file that unlocks the automatic USB update path on this device. It does not apply to USB image flashing, which uses no keyInterface → USB → Key exports the key file for the device's current key (Generate); the key value itself is set from the command line (see Securing Your Device for key management)
Security anchors (where provisioned)Hardware-protected storage for the disk-encryption key, and the secure-boot stateNot user-visible in the UI; secure-boot state is confirmable from the command line

Checking versions

The Web UI covers day-to-day support conversations; the command line covers audits and fleet inventory.

In the Web UI
Dashboard: aggregate version, kernel line, Cybersecurity Version, hardware identity. Cellular status: modem firmware.
Command line only
/etc/version-system · apt list --installed · /etc/version-extend · /etc/version-clone
For most support cases: the aggregate system version plus the modem firmware version identify your software state.
Web UIbrowser
Dashboard
System Information: version · kernel · CSV
Cellular status
modem firmware
Debian Management
installed packages
App Center
installed apps
Backup & Restore
backups · snapshots
RCMS status
cloud identity
↓ day-to-day answers↑ one device state
ROBUSTEL
EG5120
RobustOS Pro 2.4.x
↓ deeper detail↑ audits · inventory
Command lineSSH
apt list --installed
per-component versions
/etc/version-extend
factory pre-installed layer
/etc/version-clone
custom baseline marker
WiFi/BT firmware
model-specific command
Secure-boot state
where provisioned
Where every version lives — the Web UI covers day-to-day support conversations; the command line covers audits and fleet inventory.

In the Web UI (Dashboard → System Information panel):

  • Aggregate (composite) system version — the one number that identifies your firmware release; it combines the base image and the Robustel layer. The base image version on its own is a command-line check (below)
  • Kernel line
  • Cybersecurity Version
  • Hardware identity (serial number, MAC addresses, IMEI)
Web UIDashboard
Drop a screenshot of the Dashboard
The Dashboard's System Information panel — the aggregate system version, kernel line, and Cybersecurity Version in one view.

In the Web UI (elsewhere):

  • Modem firmware version — Cellular status page
  • Installed Debian packages — Debian Management page
  • Installed apps — App Center
  • Backups and snapshots — Backup & Restore page

Command line only:

  • Base system image version — /etc/version-system (the base image on its own, separate from the composite Dashboard version)
  • Per-component versions of the Robustel management layer — apt list --installed (this list is command-line only; the Web UI's Debian Management page does not show every installed package)
  • Factory pre-installed layer version — /etc/version-extend
  • Whether your factory baseline is a custom/cloned image — /etc/version-clone
  • WiFi/Bluetooth firmware version (model-specific command)
  • Secure-boot state (where provisioned)
Web UIInterface → Cellular → Status
Drop a screenshot of the Cellular status page
Cellular status — the modem firmware version lives here, on its own track.

Practical tip for support cases: the aggregate system version (Dashboard → System Information) plus the modem firmware version (Cellular page) identify your software state for most support conversations. The command-line checks matter mainly for audits and fleet inventory.

Know your factory baseline

What every factory reset and recovery falls back to. Check it before you need recovery.

Most units
A clean default state.
Custom factory image
A factory reset returns to your delivery state, not an empty device.

One item in the list above deserves special attention: the factory baseline is what every factory reset and recovery falls back to. On most units it's a clean default state. On units ordered with a custom factory image, it's your company's pre-configured image — so a "factory reset" returns to your delivery state, not an empty device.

Check which one your fleet carries before you need recovery (command line: /etc/version-clone is present on custom/cloned units). What an Update Changes explains what this means for resets; When Something Goes Wrong explains when the baseline is used.

Model notes

The stack is identical across the 2.4.x portfolio. Two things vary between devices.

WiFi/Bluetooth firmware delivery
On some models refreshed by a standard firmware update; on others only with the base OS image.
Hardware-anchored protection
Key storage, storage encryption and boot-time verification only on devices provisioned for them.

The stack above is identical across the RobustOS Pro 2.4.x portfolio. Two things vary between devices:

  • WiFi/Bluetooth firmware delivery: on some models these firmware files are bundled with the kernel package and are refreshed by a standard firmware update; on others they ship only with the base operating system image.
  • Hardware-anchored boot and storage protection: hardware-protected key storage, storage encryption and boot-time verification are present only on devices provisioned for them. Otherwise the device relies on install-time package verification.
What an Update Changes
What happens to each part during updates and resets.
Updating Your Device
How to perform updates.
When Something Goes Wrong
Recovery behaviour.

What this guide does not cover

Next · step 4 of 13Setting up your devices →The four ways to put your software and settings onto a fleet.