Containers and apps
In preview
Docker Compose stacks for each account. Your compose file is parsed and rewritten from an allow-list before Docker sees it, and checked again on the server.
Built and lab-tested
- privileged, host networking, devices, extra capabilities, Docker socket mounts and paths outside your home are refused, each with the offending line.
- Validated twice: by the control plane, and again by the agent on the server.
- Every container drops all capabilities except a small set, runs with
no-new-privileges, CPU, memory and process limits, user-namespace remapping and log rotation, inside the account's cgroup slice. - Ports are published on 127.0.0.1 only. Secrets are kept in the vault and a root-only environment file, masked everywhere else.
- A signed catalogue of 10 apps: WordPress, Ghost, n8n, Uptime Kuma, Gitea, Nextcloud, Plausible, Metabase, SeaweedFS and Valkey. A tampered catalogue is refused.
- Upgrades take a snapshot first and roll back automatically when health checks fail; manual rollback stays available for 7 days.
- Logs, stats, image pull and prune, and private registries.
- A recorded shell inside a container of your own stack, and bounded live logs.
Not there yet
- Rootless Podman per account.
- A stack's volumes in the account's backup.
- Image vulnerability scans.
Every action in this area is in the panel, one keystroke away in the command palette (Ctrl K), on the command line and in the API, and most changes can be previewed as a plan first. Built and tested in our lab; RespireCloud is not released yet.