Industries / Technology / Software and SaaS / Cloud and data centers / Edge computing
Managing many devices
This is the work of keeping thousands of small computers in shops, plants, vehicles and towers set up, updated, secure and counted, without sending a person to each one.
6
Milestones achieved, from 2010 to 2023.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
2010
Signing that survives stolen keys
A paper at the ACM CCS conference in Chicago in October 2010 described The Update Framework (TUF), a way to sign updates, attaching a cryptographic mark that proves who made them, with several keys that have separate jobs and a way to revoke a key, so devices can still refuse bad software after one key is stolen. TUF graduated from the Cloud Native Computing Foundation on 18 December 2019; NYU called it "the first specification project to graduate" there and reports that Amazon, Microsoft, Google and Docker use it.
LessonThe paper found that update systems had "little or no defense against key compromise", so TUF assumes from the start that a key will one day leak.
Credit
Justin Samuel, Nick Mathewson, Justin Cappos and Roger Dingledine; later NYU Tandon
2016
Updates with a spare copy
Google's Pixel phones, sold from October 2016, came with A/B updates: the device keeps two sets of system partitions and writes the update to the one not in use, and if the new system fails to start it rolls back to the old copy and stays usable. Chromebooks use the same update engine, and the Yocto Project, a common toolkit for building embedded Linux, lists open tools that give edge boxes the same spare copy: SWUpdate, Mender, RAUC and OSTree.
LessonThe spare copy does not protect the bootloader, the small program that starts the system; Pengutronix notes that writing it "is often vulnerable to power loss".
Credit
Google (Android and ChromeOS); Northern.tech (Mender); Pengutronix (RAUC)
2018
One cluster per restaurant
At KubeCon North America in 2018 Chick-fil-A described a small Kubernetes cluster of Intel computers in each restaurant, managed by GitOps: each site's intended setup is kept as files in a Git repository, a shared store of versioned files, and each restaurant pulls changes and applies them itself. Cloud Native Now reported "6,000 devices in all 2,000" restaurants in August 2019, and Analysys Mason, an analyst firm, reported edge computing in "nearly 3000 restaurants" in January 2024.
LessonNotes from a 2023 Chick-fil-A talk record the rule "Default to making things highly recoverable over super high available": new versions go to selected restaurants first and are rolled back if error rates rise.
raw.githack.comcloudnativenow.comanalysysmason.comrobkenis.github.io
Credit
Chick-fil-A (Sean Drucker, Brian Chambers), with Weaveworks
2019
A standard for car updates
Uptane, a version of TUF for vehicles, became a formal standard on 31 July 2019, when version 1.0.0 was released under IEEE-ISTO, a standards body linked to the engineers' association IEEE, and it joined the Linux Foundation's Joint Development Foundation the same year. The suppliers Airbiquity and HERE built it into their over-the-air update products (updates sent over a device's network link); it also ships in Automotive Grade Linux, and Torizon offers it for industrial Linux devices.
Credit
NYU Tandon (Justin Cappos), the University of Michigan Transportation Research Institute and Southwest Research Institute, with funding from the US Department of Homeland Security
2021
Zero-touch setup gets a standard
The FIDO Alliance published FIDO Device Onboard (FDO) 1.0 as a Proposed Standard on 23 March 2021, developed from Intel's earlier Secure Device Onboard. A maker can ship the same device to every customer; when it is first powered on, it asks a "rendezvous" server where its owner's management system is, and the owner proves it bought the unit with a signed "ownership voucher".
LessonUptake has been slow: when certification began on 26 September 2023 the Alliance named Dell, IBM, Intel, Red Hat and VinCSS as users, and on 19 November 2026 its certified list held four products.
Credit
Intel (Geoffrey Cooper), with editors from Amazon, Google, Microsoft, Qualcomm and Arm; FIDO Alliance
2023
A device cloud shuts down
Google retired Cloud IoT Core, its service for connecting and managing device fleets, on 16 August 2023, about a year after giving notice. From that date devices could no longer connect to its MQTT and HTTP bridges (MQTT is a light messaging protocol many devices use), so owners had to switch every device to another service first.
LessonNest's Revolv home hub had shown the harsher version when it "would stop working entirely" on 15 May 2016; a device needs a way to be pointed at a new server before the old one closes.
Credit
Google Cloud; reported by InfoQ and The Stack
Watch for
Version 2.0 of FDO
The FIDO Alliance published FDO 2.0 as a Proposed Standard on 2 April 2026. It drops Intel's EPID signing method, adds a "Delegate Owners" role and a way for each side to state what it supports, and allows longer messages to fit post-quantum cryptography, encryption meant to resist future quantum computers.
Achieved whena product certified against FDO 2.0 appears on the Alliance's certified list and a user outside the maker reports onboarding units with it.
Claimed by
FIDO Alliance (editors from Intel and Dell), April 2026
Rollouts that halt themselves
Esper says its Airwave service, in product preview since 22 May 2026, sends firmware to Android devices in stages and stops a rollout by itself "if failure rates exceed defined thresholds", and that the same update system already delivers firmware "across tens-of-thousands of devices in production".
Achieved whenthe service is generally available and a customer or independent tester publishes failure and rollback rates for a named fleet.
Claimed by
Esper, May 2026
Open
01
A power-cut tally for updaters
A public test of how often open update tools bring a board back after a power cut. Use one board model for Mender, RAUC, SWUpdate and an OSTree-based updater, each set up with its spare copy; cut power at 100 random moments during each tool's updates, plus targeted cuts while the bootloader is being written, and record whether each unit starts a working system with no help. (The power-cut test under Software covers cluster software; this one covers the updaters.)
The briefCredit · unclaimed02
A register of support periods
An open table of edge gateways and industrial PCs from makers such as Moxa, Siemens, Advantech, Dell and ASRock Industrial, giving for each model the declared end date or length of security updates, a link to the maker's statement (or "none found"), and the date it was checked. An AI model that reads long documents and pulls out named fields extracts the dates (see the Note "The jobs agents repeat"), a web agent such as Browser Use 1.0 finds the statement pages (see the Note "Deleting 80% to start over"), and a person checks a sample by hand.
The briefCredit · unclaimed
Open 01 · the brief
A power-cut tally for updaters
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public test of how often open update tools bring a board back after a power cut. Use one board model for Mender, RAUC, SWUpdate and an OSTree-based updater, each set up with its spare copy; cut power at 100 random moments during each tool's updates, plus targeted cuts while the bootloader is being written, and record whether each unit starts a working system with no help. (The power-cut test under Software covers cluster software; this one covers the updaters.)
Why it is still open
No head-to-head results were found, only test plans and stories from the field. A July 2026 testing guide says "most teams' test infrastructure is not equipped to inject the specific failures that cause field bricking", and Witekio, an embedded software firm, describes a case where "20 out of 20,000 devices" failed to update after a power failure, without controlled data.
Built with what exists
The Yocto Project; Mender; RAUC; SWUpdate; OSTree; labgrid, a Python library for controlling boards, with drivers for power switches; a USB relay or switchable power supply; one widely sold board such as a Raspberry Pi 4.
First step
Wire a relay into one board's power lead, script random cuts with labgrid, and run 10 cuts during a RAUC update.
Done looks like
A published table giving, for each of the four tools, how many of 100 cuts ended in a working system with no help and how many needed the storage rewritten by hand, with scripts and logs that let another lab repeat the run on the same board.
Open 02 · the brief
A register of support periods
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
An open table of edge gateways and industrial PCs from makers such as Moxa, Siemens, Advantech, Dell and ASRock Industrial, giving for each model the declared end date or length of security updates, a link to the maker's statement (or "none found"), and the date it was checked. An AI model that reads long documents and pulls out named fields extracts the dates (see the Note "The jobs agents repeat"), a web agent such as Browser Use 1.0 finds the statement pages (see the Note "Deleting 80% to start over"), and a person checks a sample by hand.
Why it is still open
Even for consumer goods, support periods are hard to find. A UK government study of December 2024 could not tell for 34 of 70 companies (49%) whether they had published the information; the US Federal Trade Commission found in November 2024 that nearly 89% of 184 smart products did not disclose a support period on their websites; and a SANS diary of June 2024 says, "I haven't found a simple database to look up this declaration of compliance." No such register was found for gateways or industrial PCs.
Built with what exists
A public Git repository or spreadsheet; a long-document AI model; Browser Use 1.0; makers' policy pages, such as Moxa's software life-cycle policy for Moxa Industrial Linux.
First step
Pick 10 makers, collect statements for 20 models by hand, and fix the list of columns.
Done looks like
At least 200 models from at least 10 makers, each with a linked statement or "none found", re-checked every quarter, with a hand-checked sample of 40 entries showing under 5% errors.