Use case
Deploy behind NAT and firewalls without inbound access
The agent keeps one outbound TLS connection to the control plane. Deployments, commands, logs, and diagnostics flow over it. Nothing inbound, ever.
For: Devices on customer networks, cellular routers, and locked-down sites.
remote-docker-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
- Every site needs a VPN or a port forward, and a conversation with their IT.
- Shared SSH keys on a fleet are a liability.
With Simple Docker Ops
- Per-device credentials issued at pairing, revocable from the portal.
- No listening ports on the device.
- Every action audited: who deployed what, where, when.
Setup
- 1Install and pair.
- 2Deploy from anywhere.
- 3Revoke a device with one click if it is lost.
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