Run
Run autonomous systems on a secure, recoverable Linux foundation.
GWOS is the operating system on each device. It runs your applications and AI workloads, verifies software updates, and keeps a working system available if an installation fails. Your team can develop mission software without building its own device update and recovery system.
KEY FEATURES
- Common build tools across hardware platforms, including NVIDIA Jetson and Raspberry Pi Compute Module 5
- A/B operating system slots with health checks and automated rollback on failure
- Signed update bundles and hardware compatibility checks that preserve the chain of trust
- Persistent device identity, credentials, and application data across updates
Build on a consistent foundation across hardware platforms
An autonomy application depends on more than its own code. Its operating system, drivers, and runtime libraries must work together on the target hardware. GWOS packages that foundation as a controlled image so devices start from the same tested configuration.
One set of build tools produces releases for different compute modules, including NVIDIA Jetson and Raspberry Pi Compute Module 5 (CM5). Hardware support and recovery behavior depend on the board and boot firmware, so evaluation starts with your exact device configuration.
Install updates without overwriting the running system
GWOS keeps two operating system slots on the device. An update replaces the inactive slot while leaving the current working system intact, so an interrupted installation does not overwrite the system the device needs to boot.
On restart, the device tries the new operating system and runs local health checks before committing it. It reports the result to the coordinator when a connection is available. If the trial boot or health checks fail, the boot recovery mechanism returns to the previous working slot. Device identity, credentials, and accumulated data live separately from the operating system, so they survive each replacement.
Verify that every update comes from a trusted source
A signed update bundle identifies the release and its compatible hardware. GWOS verifies the signature and hardware compatibility before installation, maintaining a chain of trust from the release signer to the software installed on the device.
Poolboy selects which devices receive the release, and Poolnet carries it across available links. GWOS handles verification, installation, and local recovery on each device.
Use Cases
Procurement
Evaluate a repeatable device image and its software bill of materials alongside your hardware requirements. Confirm support and validation evidence for your board before fielding.
Scale
Provision devices from the same tested image. Keep the operating system and workload dependencies consistent as the fleet grows.
Security
Devices verify the update signature and hardware compatibility before installation. Device identity and credentials persist separately from the replaceable operating system.
Reliability
An update writes to the inactive operating system slot. The new system must pass health checks before it becomes the default boot choice.
Common questions
- How does GWOS get updated?
- Your team builds software on top of GWOS, which is a hardened Linux image. We help set up continuous integration (CI) workflows to build and sign new releases, which your team can distribute to devices through Poolboy.
- What happens if power fails during installation?
- The update writes to the inactive slot, leaving the current operating system intact. A failed trial boot can return to the previous slot using the recovery mechanism built into each GWOS image.