Installing an agent on a cloud server and on a home router initially looks like the same job: copy an executable, write a configuration file and start it. Long-term operation raises different questions. Who starts it after a reboot? What if the network is not ready? Where are the logs? Will device identity and command records survive a restart?

Fleetd manages Linux servers alongside OpenWrt and iStoreOS routers. After covering enrollment and browser-signed commands , this article focuses on making the agent a persistent, diagnosable system service. The implementation described is v0.3.0. Its installer supports amd64 and arm64, with systemd or OpenWrt's procd; that does not mean every Linux-based device is supported.

One codebase, architecture-specific binaries

OpenWrt is Linux too. Connections, authentication, command authorization and basic kernel metrics can share code. Fleetd therefore does not maintain separate server-machine and router agents.…