Rested

VPS backups that stay boring for the right reasons.

Rested helps you back up Linux VPS files, app data, uploads, and service state with encrypted storage, visible schedules, failure history, and restores.

Start VPS backupsView pricing

Visible backup state for each Linux host.

Filesystem paths, app files, uploads, and service data.

Restic encryption without spreadsheet operations.

VPS backup example
Example of the backup status you can see after setup.
Example only

Agent

Online

example server connected 1 min ago

Storage

B2 connected

example backup storage

Latest run

Succeeded

example run completed 18 min ago

Bytes reported

3.8 GB

example new backup data

Built around the VPS backup loop

The useful path is simple: connect the server, run backups, watch history, and know how to restore.

Choose what to back up
Pick the VPS paths, app files, uploads, and service data that matter for recovery.
Connect the VPS
Connect the server so backups can run where the files live.
Run encrypted backups
Rested shows backup status, schedule, failures, and history after the server is connected.
Restore when needed
Find recovery points and start a restore from the same place you watch backups.

Encrypted backups with a clearer recovery path

Rested keeps schedules, storage, history, and restores understandable without hiding the recovery key.

You keep the recovery key
The key that unlocks your encrypted backups stays with you. The web app coordinates the work and never unlocks your data.
Backup files skip the web app
Your server writes encrypted backup data straight to your storage. Rested never sees the file contents.
Narrow storage access
Each backup uses only the storage access it needs.
Real history after setup
Run history, backup size, recovery points, and failures appear after the server starts backing up.

Good to know

Reliable VPS backups depend on storage, schedules, encryption keys, and restore tests all being clear.

Roadmap
Installer rollout
Setup matches the deployment you are using.
Careful
Storage setup
Storage setup should be clear before scheduled backups are trusted.
Open
Backup engine setup
The server needs the backup engine available before real runs can succeed.
Principle
Example status
The status card is illustrative; the app shows real backup results after setup.

Frequently asked questions

Answers to the questions teams ask before trusting a backup workflow.

What does Rested back up on a VPS?

An agent runs on the Linux server itself and backs up the paths you choose — filesystem paths, app files, uploads, and service data. Because it runs where the files live, it captures the state that matters for recovery.

Where are my VPS backups stored?

In storage you own and configure — any S3-compatible bucket, including Backblaze B2. restic encrypts the backup data on your server before it leaves the host, so the storage provider only ever holds ciphertext.

Who holds the encryption key?

You do. The recovery key that unlocks your encrypted backups stays with you. Rested coordinates schedules and history and never sees your key or your file contents, so a compromise of the control plane cannot read your data.

How do restores work?

You find recovery points and start a restore from the same place you watch backups. Real run history, backup size, recovery points, and failures appear once the server runs its first backup — not placeholder numbers.

Explore more backup workflows

Server backupsPostgres backupsRestic dashboardBackup automationRestore backups

Start with one Linux server. Keep the recovery path visible.

Connect a VPS, run a backup, and keep recovery points visible before you need them.

Create accountView pricing