Encrypted server & file backups.
xbackupman backs up any directory on any reachable server over SSH. It tars and compresses the path, encrypts the archive with AES-256-GCM inside the worker, and stores the ciphertext in a bucket you own — no agent to install, just an SSH login.
What gets captured
- Any directory tree you point at — application code, uploads, config, certificates or a whole home folder.
- A tar archive of the path, preserving file layout and permissions, produced over a plain SSH session.
- In-stream gzip compression and AES-256-GCM encryption applied in the worker before upload.
- A SHA-256 checksum recorded with each snapshot so you can confirm the archive is intact.
How it works
Add an SSH target
Give the host, port, user and the directory to back up. Authenticate with an SSH key or a password — no daemon or agent is installed on your server.
Tar over SSH
The worker opens an SSH session, tars the chosen directory and streams the archive back — nothing is staged on the remote host beyond the read itself.
Compress, encrypt, upload
The tar stream is gzipped and sealed with AES-256-GCM in the worker, then the ciphertext is uploaded to your own S3-compatible bucket.
Verify and retain
Each archive carries a SHA-256 checksum. Schedule the job on any cadence and let retention prune old snapshots while preserving your last copy.
Your storage, your keys
Your file archives are written straight to your own bucket — S3, R2, B2 or MinIO. Encryption happens in the worker before upload, so your storage provider only ever sees ciphertext. The backups are yours end to end: your server, your bucket, your keys.
xbackupman never stores your backups on its own servers. It orchestrates the pipeline and records metadata — the encrypted artifacts live only in the S3-compatible bucket you connect. See how encryption works.
One-click restore
Restore streams the archive back to a target over SSH, unpacking the directory tree with its layout intact — into a separate path by default so nothing live is overwritten. Because it is a standard gzipped tar, you can also download it and extract it anywhere with tar for a manual or partial restore.
Questions
QDo I need to install an agent on my server?
No. Backups run over an ordinary SSH session, so there is nothing to install or keep updated on the machine — just an account we can log in with to read the directory.
QCan I authenticate with an SSH key instead of a password?
Yes. Key-based auth is supported and recommended; password auth is available where keys are not practical.
QWhat kinds of directories can I back up?
Any readable path — application code, user uploads, /etc config, TLS certificates, static sites or a full home directory. If SSH can read it, xbackupman can archive it.
QAre file permissions preserved?
Yes. The tar archive keeps the directory structure and permission bits, so a restore reproduces the tree faithfully.
Back up more
One engine covers every source you run — on a single schedule, in one dashboard, encrypted into the same storage.