Implemented layer
Encrypted Restic repositories
Client VM backups are implemented with Restic. Each repository is encrypted before data leaves the server.
Backups
ReefOffice backs up client servers with encrypted Restic repositories and shows backup health, key custody, and restore evidence in the client dashboard.
Implemented layer
Client VM backups are implemented with Restic. Each repository is encrypted before data leaves the server.
Implemented layer
The production module is built for Hetzner Storage Box over SFTP with a dedicated SSH wrapper.
Implemented layer
The NixOS module schedules hourly backups and keeps hourly, daily, weekly, and monthly snapshots.
Implemented layer
The API exposes backup status, restore requests, and restore-drill proof for authenticated clients.
Key custody
Backup encryption decides who can perform a restore under pressure. ReefOffice supports managed recovery and client-held zero-knowledge keys.
ReefOffice can escrow an encrypted copy of the Restic key for audited disaster recovery when this mode is selected.
The server waits for the client-held Restic key before backups can run. ReefOffice cannot restore without that key.
Dashboard visibility
The backup API checks stored snapshot records and the VM status beacon, then explains the result in plain language.
Service data, Nextcloud data, Vaultwarden state, ReefOffice configuration, and supported database dumps.
Placeholder repositories and missing client-held keys are reported explicitly instead of producing fake success states.
A real destination must be configured per production server. Until then, the dashboard reports storage as not configured.
Related security controls
LUKS protects offline storage; backups protect against deletion, corruption, and recovery events. They address different risks.
Read the full security pageWe set the key-custody model before provisioning so the restore workflow matches your risk tolerance.