Your homelab probably has more important data than you think: configs, Docker volumes, VM exports, app data, keys, scripts, and snapshots. ServerCrate gives you encrypted offsite backup with private vaults, Restic over SFTP, and no egress fees when you need to restore.
Built for Restic from day one. Borg works too, but Restic is the default voice. BorgBase is Borg-first. We're the inverse.
Every vault sits on ZFS with checksumming and snapshots. Bit rot on a 3-year-old archive gets caught. Most providers won't tell you their backend.
Single Los Angeles datacenter. Low latency for North American users. BorgBase is EU-only. rsync.net is multi-region but priced for it.
A lot of people back up media and forget the real high-value data: router configs, compose files, reverse proxy configs, VM exports, app databases, SSH keys, automation scripts, and the weird pile of files that took months to get right.
ServerCrate is for getting that critical stuff offsite, encrypted, and recoverable without turning your homelab into a second full-time job.
These numbers are from an actual Proxmox homelab pushing data to a ServerCrate vault over a 1 Gbps residential uplink. Your speeds depend on your upload, the file mix, and how much data has changed since the last run.
restic restore on a gigabit downlink. No egress fees.Homelab backup sets are full of overlapping data: the same base OS image in three VMs, the same config files in five containers, the same Docker layers shared across a dozen services. Restic's content-defined chunking sees that overlap at the block level and stores each unique chunk exactly once, even across different hosts backing up to the same vault.
That matters for cost. A 500 GB nominal backup set often fits in 150 GB of actual vault usage after the first run, and incremental runs typically upload 1-3% of total size per day.
If any of these look like your rack, you are the target user. These are the workloads we tested and optimized for.
You have a three-node Proxmox cluster running a mix of VMs (a FreeBSD router, a Debian NAS, a Windows box) and LXC containers (Pi-hole, Jellyfin, Home Assistant, Nextcloud). You want vzdump exports going offsite, plus the config files inside each container so you can rebuild the stack if your entire rack dies. ServerCrate handles this as a single deduplicated vault. See our Proxmox backup guide for exact commands.
Nextcloud, Vaultwarden, Paperless-ngx, Immich, Home Assistant, Grafana, and the long tail of apps you accumulate running a homelab. Each has its own persistent volume and database. You need a single backup job that captures all of /var/lib/docker/volumes, the compose files in /opt, and any mounted bind-mount paths. One Restic run covers everything. See our Docker backup guide for volume-safe flags.
Your primary data lives on a NAS with on-box snapshots or RAID. That protects against disk failure, not against fire, theft, ransomware, or a botched update that nukes a pool. Restic pulls from an SSH-capable NAS to a ServerCrate vault overnight while you sleep. Works natively on TrueNAS and Synology.
Beelink, Minisforum, or Intel NUC running Debian or Proxmox. One machine doing everything: router, DNS, file sharing, a dozen self-hosted apps, and whatever else landed on it over the years. A full hardware failure would mean rebuilding from memory. ServerCrate gets a complete copy offsite, and setup is five minutes of copy-paste.
Connection details, storage usage, snapshot history, and device management without digging through a maze of settings.
restic init and restic backup commands to run.When you first provision a vault, ServerCrate generates a Restic repository password on your behalf and shows it to you once. That password is the key that encrypts every chunk before it leaves your machine. Our database stores a hash of it, not the password itself, so even a full server compromise reveals only ciphertext.
You can rotate this password any time with Restic's key passwd command. We never see the new one. If you lose it, the data is mathematically unrecoverable - not even we can help. That's the tradeoff of real zero-knowledge encryption, and it's the whole point.
All four options work. These are the practical tradeoffs for homelab use.
| ServerCrate | rsync.net | BorgBase | Backblaze B2 | |
|---|---|---|---|---|
| Entry price | $5/mo for 200 GB | $24/yr for ~100 GBLong-term cheaper | $16.80/yr for 250 GB | $6/TB/mo+ egress fees |
| Free tier | 10 GB, 1 device | None | 10 GB free forever | 10 GB |
| Backup tool | Restic (SFTP) | Borg, Restic, rclone | Borg + Restic | Anything S3-compatible |
| Zero-knowledge encryption | Client-side | Client-side | Client-side | Depends on tool |
| Egress fees | None | None | None | $0.01/GB after 3x stored |
| Underlying storage | ZFS, dedicated vault | ZFS, shared pool | Shared pool | Object storage |
| Setup friction | 5-minute setup | Manual SSH key setup | Manual SSH key + config | S3 keys, bucket config, rclone |
| Multi-device on one vault | Up to 5 (Pro) | Yes | Unlimited | S3 has no concept of devices |
| Who it's best for | Homelabs wanting managed Restic | Long-tenure backup admins | Borg-first workflows | High-volume or custom tooling |
See detailed head-to-head comparisons: ServerCrate vs BorgBase and ServerCrate vs rsync.net.
Here's exactly what happens from the moment you sign up to the moment your first snapshot lands offsite.
apt install restic. On Arch: pacman -S restic. On Alpine: apk add restic. The binary is a single ~20 MB file.RESTIC_REPOSITORY and RESTIC_PASSWORD from the portal. Run restic init. Your encrypted repository is now live.restic backup. Your first snapshot uploads encrypted in the background. From here, schedule it with a systemd timer and forget about it.Keep three copies of data, on two different media, with one copy offsite. The rule has been around since 2005 and it still works because disk failures, power surges, fires, floods, theft, and ransomware all have one thing in common: they hit locally.
For a typical homelab:
The files as they exist on your NAS, server, or primary host right now. This is the copy you use daily.
A snapshot on a separate disk or pool in the same building - typically ZFS snapshots on a secondary NAS, rsnapshot on a USB drive, or Restic to a second local repository. Fast to restore from, but vulnerable to anything that hits your whole location.
An encrypted copy somewhere that is physically and administratively separate from your homelab. This is the copy that survives the disasters that wipe out copies 1 and 2 simultaneously. See our full 3-2-1 strategy guide with Restic commands for each layer.
You do not need flashy consumer sync. You need private offsite backup that works with the stack you already run.
Start with the workflow, then compare options if you want.
Protect the data that actually matters.
Private vaults. Zero-knowledge design. No egress fees.
Built for real self-hosted workloads, cancel anytime
10 GB. No credit card. Setup in 5 minutes. Bitcoin or card when you upgrade.
Start free vault →