Signed OTA
Signed OTA is how edge AI devices accept firmware and software updates without trusting the network in between. Teams comparing Foundries.io, Allxon, Avassa, Qbee, Mender, and in-house pipelines need verified manifests, delta delivery over low bandwidth, and rollback that works offline. Gentle Weapons combines GWOS signed image updates on Jetson with Poolboy fleet rollout—cryptographic verification end to end, A/B promotion on the OS side, and canary-to-wave orchestration on the payload side.
Firmware updates with verification, not hope
OTA for edge AI devices must assume DDIL links and adversarial networks. Updates are signed, acknowledged per node, and paired with rollback paths—not silent auto-updates from a vendor cloud you do not control.
- [ OK ]GWOS: signed OS images, delta OTA, A/B rollback on Jetson
- [ OK ]Poolboy: signed payload manifests, fleet waves, LKG rollback
- [ OK ]Delivery over Poolnet when backhaul is unavailable
- [ OK ]SBOM and attestation metadata carried with images
One stack, two layers
OS updates and model or application payloads often land on different cadences. GWOS and Poolboy interlock so integrators can reason about platform and payload independently while sharing signing and rollout discipline.
Production remote updates, not Pi hobby deploy
Deploy software to Raspberry Pi SERPs skew toward SSH, VS Code Remote SSH, Docker, and CI runners—fine for bench work, not field rollback. Production edge programs instead need A/B image promotion and remote software updates with verification—the same discipline GWOS and Poolboy bring to Jetson fleets. See fleet management for payload waves and rollback policy.
Gentle Weapons builds defense autonomy infrastructure in Mesa, AZ. Technical specifications and deployment references are shared under NDA with qualified program parties. Request a briefing.