Use case
Update containers on remote devices without opening SSH
Devices behind customer firewalls, on cellular, or in a cabinet nobody visits. The agent connects out; you deploy from the portal or the API.
For: Small product companies with one Linux box at each customer location.
remotely-update-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
- Inbound SSH means VPNs, port forwards, and a security conversation with every customer.
- A failed update at a remote site means a truck roll.
With Simple Docker Ops
- Outbound-only TLS from the device; nothing to open on the customer network.
- Releases pinned to digests, health-checked per device, rolled back automatically on failure.
- Bounded container logs and device diagnostics for support.
Setup
- 1Install the agent during appliance provisioning.
- 2Assign the appliance to the customer fleet.
- 3Ship releases on your schedule with a health gate and a deadline.
Questions
What if the device is offline during the deployment?
It receives the release when it reconnects, applies it, and reports. The rollout tracks it as pending, not failed, until the deadline you set.
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