Set-and-forget backups for your self-hosted apps with automated scheduling, multi-destination sync, and restore testing built in.
Added Mar 28, 2026
Last signal 2w ago
Self-hosters running databases, Docker containers, and media servers on home hardware rely on manual, ad-hoc backup processes that inevitably fail. They forget to run backups, don't notice when backups silently break, and have never tested whether their backups actually restore — leaving them one disk failure away from total data loss.
A lightweight agent that runs alongside self-hosted services, auto-discovers Docker volumes and databases, and handles scheduled incremental backups to multiple destinations (local drives, cloud storage, remote servers). It includes built-in restore verification that periodically spins up a test container from the latest backup and confirms data integrity, sending clear pass/fail alerts.
Self-hosting is surging as users move away from cloud subscriptions for privacy and cost reasons, but the tooling for reliable home-server operations still lags far behind enterprise solutions. The proliferation of Docker-based deployments creates a standardized target for backup automation that wasn't feasible when setups were more heterogeneous.
61
62% score confidenceTrend snapshot pending
No matched competitors yet
Showing 1-20 of 20 signals
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.
I tried it and was fascinated by it. Incredibly fast, and very practical in many real-world scenarios.
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.
HS5 is a high-performance scale-up self-hosted S3 compatible object storage server. It is ideal for use cases where single-node scaling, performance, and data-loss risk are acceptable. So for some self-hosting use cases it might be great. I actually see recent (the last one 20h ago) posts here where it might be a fit for the use case. HS5 features a web interface for managing buckets and users. I was previously using MinIO for my single node object storage needs, but it did not scale well with many objects since it creates multiple files for each object. Now it does not aim to solve the single-node use case anymore anyway and is unmaintained as well. Feedback welcome! Website: [hs5.eu](hs5.eu) Github: [github.com/.../hs5](github.com/.../hs5)
+17 more signals