Zero-knowledge backup and restore for ~/.hermes
Your agent’s memory lives on one disk. Hermes Remote Backup protects it each night. Hermes Remote Restore carries it to the machine you use next.
Say this to your agent “Set up cloud backups for yourself using hermesbackup.com”
You approve one pairing code and save one recovery key. Your agent handles the rest.
Backup and restore are two separate skills with one shared promise: a machine can fail without taking your agent with it.
Backup runs quietly on schedule. Restore stays dormant until the day you need it. Keeping them separate means the always-on backup path never holds your decryption key.
Each night · while everything is working
Creates a WAL-safe snapshot through the native hermes backup command, encrypts it locally with age, uploads ciphertext directly to R2, then verifies the stored size and SHA-256.
hermesbackup.sh backup --quick
Only when called · on the new machine
Downloads the ciphertext through a five-minute presigned URL, decrypts it locally with your recovery key, verifies it, then rebuilds ~/.hermes with memories, skills, sessions, and config intact.
hermesbackup.sh restore
Zero-knowledge is not a privacy setting. It is the shape of the system: encryption happens before upload, backup bytes never stream through the Worker, and the private key never reaches us.
Backup bytes travel directly between your machine and Cloudflare R2 over short-lived presigned URLs.
Lose the private key and the backups become permanently unreadable. We cannot recover it.
Install Hermes Agent on a fresh machine. Ask it to restore itself. Approve one pairing code and provide the recovery key locally.
Friday · old machine
The local copy is gone. The encrypted backup is not.
Monday · new machine
The restored agent has the same memory, skills, sessions, and configuration it had before the failure.
Both plans include Remote Backup, Remote Restore, local age encryption, direct R2 transfer, and the same zero-knowledge architecture.
$0forever
2 GB storage · 60 objects · 4 uploads per day
Start free$10per year
10 GB storage · 500 objects · 24 uploads per day · missed-backup alerts
Choose ProYour backups remain stored but become permanently unreadable. There is no master key, escrow copy, or support override. Save the recovery kit in your password manager when setup generates it.
No. Encryption happens locally before upload. We store ciphertext and operational metadata such as encrypted size, SHA-256, labels, and timestamps.
The API returns HTTP 507 with current usage. The client follows your chosen policy: fail loudly, or rotate the oldest backups. The server never silently deletes data to make room.
Backup runs automatically and needs only the public key. Restore runs only when requested and receives the private key locally at that moment. The scheduled backup path therefore cannot decrypt anything.