You already chose Restic. You don't want to also become a sysadmin for a backup target. ServerCrate gives you a private hosted Restic endpoint - SFTP, ZFS-backed, zero-knowledge - provisioned in in under a minute. No RAID to plan, no SSH keys to rotate, no rest-server to monitor. Just a working endpoint.
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.
Restic is one of the most popular open-source backup tools among Linux users, developers, and homelab operators. It handles encryption, deduplication, and snapshot management locally - but it needs somewhere to send the data. That's where a Restic backup server comes in.
A Restic backup server is a remote storage endpoint that Restic connects to over SFTP (or REST) to store your encrypted backup snapshots. The server stores the data; Restic handles all the encryption and deduplication logic on your side before anything is transmitted.
You have two options: self-host a Restic-compatible server on a VPS or dedicated machine, or use a managed service like ServerCrate. Self-hosting means managing SSH access, storage, RAID arrays, monitoring, and backups of the backup server itself. ServerCrate handles all of that so you can focus on running your actual workloads.
ServerCrate provisions a dedicated SFTP vault for each user on ZFS-backed storage. Your Restic client connects to the vault over SFTP using the connection string from your portal. Restic encrypts everything on your machine before transmission - ServerCrate receives only encrypted data it cannot read.
The connection looks like this:
Self-hosting your Restic repository on a VPS or storage box is a perfectly valid approach. But it comes with real operational overhead that adds up over time:
ServerCrate removes all of that. You get a hardened, monitored, ZFS-backed Restic endpoint that you connect to over SFTP - and everything else is handled. The time you save is better spent on your actual projects.
Restic's encryption model is genuinely zero-knowledge: your repository password is used to derive the encryption key, and that key never leaves your machine. When Restic sends data to the server, it's already encrypted with AES-256. ServerCrate stores only the encrypted chunks - we cannot decrypt your data even if we wanted to.
This means your backups are safe even in the event of a full infrastructure compromise on our end. The encrypted data is mathematically worthless without your repository password.
Restic's repository format relies on content-addressed chunks being stored reliably over months and years. Bit rot - the silent corruption of stored data - is a real problem in long-term storage, and most systems don't detect it until a restore fails.
ServerCrate uses ZFS for all vault storage. ZFS checksums every block on write and verifies every block on read, automatically detecting and flagging any corruption. Your Restic repository stays byte-perfect over its entire lifetime.
ServerCrate plans are flat monthly pricing with no egress fees. You pay one price per month and restore as many times as you need without additional charges.
The simplest automation uses a systemd timer or cron job to run daily backups. Here is a minimal systemd setup:
Frequently asked