Custom Backup vs Rclone
A side-by-side comparison of two self-hosted backup & recovery options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
Custom Backup
Backup extra paths not already managed by YunoHost backup feature
VS
Rclone
Sync and copy files to dozens of cloud providers
| Feature | Custom Backup | Rclone |
|---|---|---|
| Category | Backup & Recovery | Backup & Recovery |
| License | AGPL-3.0-only | MIT |
| Language | Shell | Go |
| Setup difficulty | Easy | Medium |
| Min. RAM | 512 MB | 128 MB |
| Deployment | bare-metal | binary, docker |
| GitHub stars | ★ 4 | ★ 58,995 |
| First released | 2024 | 2014 |
| Replaces | — | Backblaze |
Why pick each one
Choose Custom Backup if…
- Released under the AGPL-3.0-only license
- Easy to set up — beginner-friendly
- Written in Shell
- Lightweight — runs in 512 MB RAM
Frequently asked questions
Is Custom Backup or Rclone better?
Neither is universally better. Rclone has the larger community, while Custom Backup is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.
Are Custom Backup and Rclone free and open-source?
Yes. Custom Backup is licensed under AGPL-3.0-only and Rclone under MIT. Both can be self-hosted at no software cost.
Can I run Custom Backup and Rclone with Docker?
Custom Backup: check the project docs for container support. Rclone: yes.