Documentation

Guides for keeping your Rested backups recoverable — how the system works, restoring your data, and fixing common problems.

How Rested backups work

Rested is a control plane over restic. An agent runs on each server and does the actual work; the web app schedules it and shows the results. Understanding the pieces makes the recovery and troubleshooting guides easier to follow.

• The agent runs on your Linux server, where your files already live. It runs backups on the schedule you set and reports each run back to Rested.
• Encryption happens on the server. restic encrypts the repository contents and metadata before anything is uploaded, so your storage provider only ever holds ciphertext.
• Your storage, your keys.Backups are written to your own S3-compatible bucket. Repository and storage credentials are sealed in your browser to the agent's key — the control plane stores ciphertext it cannot read, and the agent opens it locally.
• Restores are agent commands.Starting a restore queues a command the agent runs on the server; the result and logs appear in the repository's history.
• Standard restic underneath. Because the repository is ordinary restic, you can always list snapshots and restore with the restic CLI directly, even if Rested is unreachable.

Guides

Setting up billing or agents for the first time? See pricing and the security overview for how credentials and backups are protected.