Use case
Fleet management for Raspberry Pis, without Kubernetes
Rollouts, health gates, and rollback borrowed from cloud practice, applied to physical devices, explained in Compose terms.
For: Teams that looked at k3s and decided their workload did not justify it.
raspberry-pi-01Raspberry Pi 5 · arm64
Healthy- Desired
- collector 1.8.4
- Actual
- collector 1.8.4
- Docker
- 29.0.2
- CPU
- 12%
- RAM
- 43%
- Disk
- 31%
- Temp
- 48 °C
- Uptime
- 38 d
- Last deploy
- 2 d ago
collector1.8.4healthy
mqtt2.0.22healthy
watchdog2.1.0healthy
LogsDiagnosticsRestart appDeployRoll back
The usual pain
- Kubernetes on SBCs adds memory pressure, YAML, and a second learning curve.
- Without it, nobody owns "how do we update 40 boxes safely".
With Simple Docker Ops
- Fleets, releases, and staged deployments with no cluster to run.
- The agent reconciles desired state locally, so a device behind NAT or offline for a day still converges.
- Architecture checked before deployment; drift reported after.
Setup
- 1Group devices into fleets: test, production, per customer.
- 2Promote a release from test to a 10 percent wave to everyone.
- 3Let the health gate stop a bad release before it reaches the whole fleet.
Add your first device free.
Five devices and five gigabytes of registry on the Free plan. No card, no sales call, no Kubernetes.
curl -fsSL https://simpledockerops.com/install | sudo sh