One deployment loop, many fleets
Pick the one closest to yours.
Deploy one Compose file to every Raspberry Pi you own
Stop SSH-ing into each Pi to pull and restart. Register the devices, create a release, and roll it out with a health gate.
Fleet management for Raspberry Pis, without Kubernetes
Rollouts, health gates, and rollback borrowed from cloud practice, applied to physical devices, explained in Compose terms.
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.
A Balena alternative for fleets of 5 to 100 devices
Balena is excellent at scale, with its own OS and a $159 jump after ten devices. Simple Docker Ops keeps your Linux and prices small fleets fairly.
A Portainer alternative built for physical fleets
Portainer is a server container UI. Edge fleets need desired state, offline reconciliation, staged rollouts and a licence that fits fifteen boxes.
Canary deployments for Compose workloads on real devices
Deploy to two test devices, then 10 percent, then everyone. Each wave waits for health. A failure threshold pauses or rolls back.
ARM64 and x86_64 in one fleet, without exec format errors
Releases inspect the OCI manifest list for every image and record its platforms. Devices report their architecture. Incompatible pairs are blocked before deployment.
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.
Add your first device free.
Five devices and one gigabyte of registry on the Free plan. No card, no sales call, no Kubernetes.
curl -fsSL https://simpledockerops.com/install | sudo sh