Encrypted backups for your Postgres, Redis, MySQL, MongoDB, and filesystem.

Watch server backups, spot failed jobs, and restore data from one calm Rested workspace.

Free plan: 1 server, 1 backup target, daily backups, and no credit card required. Compare plan limits Paid plans include MCP access.

Rested overview with repository health, server status, 30-day backup activity, and recent successful runs

From server connection to recovery point

Rested keeps the practical parts of backup operations connected, from the first agent check-in to the restore path you may need later.

Connect a Linux server

Install the Rested agent where your files live so backup work stays close to the source.

Choose what to protect

Define paths, schedules, retention, and the storage destination that fits your recovery plan.

Run encrypted backups

Restic encrypts backup data on the server while Rested keeps schedules, outcomes, and failures visible.

Restore from history

Browse recovery points, choose a target, and start restore work from the same place you monitor backups.

A calmer surface for serious backup work

The product keeps operational visibility close while storage, encryption, and recovery-key ownership remain explicit.

Encrypted on the host

EncryptedBackup files are encrypted before they leave the server, with restic doing the backup work.

Storage you choose

User-ownedConnect S3-compatible storage you own and keep provider billing separate from Rested.

Failures stay visible

OperationalSee schedules, run outcomes, and recent failures without digging through cron output.

Recovery stays close

RecoveryKeep snapshots and restore actions near backup history so recovery is easier to reason about.

Good to know before you start

Reliable recovery depends on the surrounding setup too: permissions, keys, reachable paths, and tested restores all matter.

Keep your recovery key

ImportantRested cannot unlock encrypted backups for you if the recovery key is lost.

The agent runs on your server

Agent-basedBackups run where your data lives, so the connected host needs access to the selected paths.

Storage permissions matter

ExplicitYour bucket or storage key still needs the permissions required to write, read, and remove backup objects.

Test restores matter

PracticeA backup plan is incomplete until you know where files come back and the restore path works.

Explore more backup workflows

Start with one server and prove the restore path.

Connect a Linux server, run an encrypted backup, and keep its recovery points visible before you need them.

Create free account See how it works

Encrypted backups for your Postgres.Postgres, Redis, MySQL, MongoDB, and filesystem.