Back In Time vs Backup wrapper nono Backup-rsync-time-backup

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?
FeatureBack In TimeBackup wrapper nono Backup-rsync-time-backup
CategoryBackup & RecoveryBackup & Recovery
LicenseGPL-2.0MIT
LanguagePythonShell
Setup difficultyEasyEasy
Min. RAM128 MB32 MB
Deploymentbinarybinary
GitHub stars★ 2,641★ 3,608
First released20082014
ReplacesTime MachineTime Machine

Why pick each one

Choose Back In Time if…

  • Released under the GPL-2.0 license
  • Easy to set up — beginner-friendly
  • Active community (2.6k GitHub stars)
  • Written in Python
Back In Time details

Choose Backup wrapper nono Backup-rsync-time-backup if…

  • Released under the MIT license
  • Easy to set up — beginner-friendly
  • Active community (3.6k GitHub stars)
  • Written in Shell
Backup wrapper nono Backup-rsync-time-backup details

Frequently asked questions

Is Back In Time or Backup wrapper nono Backup-rsync-time-backup better?

Neither is universally better. Backup wrapper nono Backup-rsync-time-backup has the larger community; both share a easy setup difficulty, so the decision comes down to features and licensing.

Are Back In Time and Backup wrapper nono Backup-rsync-time-backup free and open-source?

Yes. Back In Time is licensed under GPL-2.0 and Backup wrapper nono Backup-rsync-time-backup under MIT. Both can be self-hosted at no software cost.

Can I run Back In Time and Backup wrapper nono Backup-rsync-time-backup with Docker?

Back In Time: check the project docs for container support. Backup wrapper nono Backup-rsync-time-backup: check the project docs for container support.

Related comparisons