Set-and-forget backup orchestration for self-hosted Docker containers with one-click disaster recovery.
Added Mar 22, 2026
Last signal 3d ago
Self-hosters running dozens of Docker containers rely on fragile, hand-written shell scripts to back up volumes and databases. These ad-hoc approaches break silently, skip critical data, and offer no easy restore path—leaving users one disk failure away from losing everything.
A lightweight agent that auto-discovers running containers, intelligently snapshots volumes and databases (with minimal downtime scheduling), encrypts and ships backups to local or cloud targets, and provides a single-command restore workflow. A dashboard shows backup health, retention status, and alerts on failures.
The self-hosting movement has surged with growing privacy awareness and affordable mini-PCs, but backup tooling hasn't kept pace—most users still cobble together cron jobs and rsync scripts, creating a clear gap for a purpose-built solution.
55
62% score confidenceTrend snapshot pending
No matched competitors yet
Showing 1-20 of 20 signals
One thing that would be really helpful is a built-in backup scheduler with off-site destinations like S3 or Backblaze B2. A lot of folks moving from cPanel rely on those automated backups, and having it baked in would make migrations feel way less risky.
I'd separate backing up the VMs from backing up the actual data. For the Proxmox side, I'd use PBS if you can. It's honestly one of the best parts of the Proxmox ecosystem. Incremental, deduplicated backups, built-in verification, retention policies, and restores are incredibly straightforward. If your backup server has to stay on Ubuntu, you can still run PBS in a VM or LXC, or even on a small dedicated machine. For the TrueNAS data, I'd use restic or borg to back up the datasets themselves. Both are excellent, but I'd lean slightly towards restic because I find it a bit simpler to manage, and it supports encrypted, deduplicated backups to a wide range of storage backends. My biggest recommendation is not to rely solely on VM-level backups. If your Docker containers are configured properly (Compose files, configs, and persistent volumes), make sure you're backing up the persistent data as well. Restoring a VM is great, but restoring just the data you actually care about is even better.
You can run Proxmox backup server on bare metal on the same machine as Proxmox. You can also run it in a VM. It’s by far the best solution for backing up VMs. Nothing else will get close in terms of data deduplication and minimizing storage requirements. You can use it to back up the Proxmox hosts too. Then use borg/restic/whatever to backup the datastore offsite.
Hi, I'm setting up my first home server. For now, I only have a Proxmox node, but I'd like to expand it later on. I'm here to ask how to set up a backup and how many drives you recommend I buy. I don't need a lot of storage—I was thinking of getting three 500 GB HDDs—but I'm not sure how I should configure the backup, such as RAID 1, mirroring, etc.
AWS S3 pricing pushed me to build this. StorForge: • S3-compatible • \~$3/TB • No lock-in • Use your existing tools • Encrypt your data before upload Early access: storforge.io
+17 more signals