Back In Time vs pgBackRest
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?
Back In Time
Simple backup tool inspired by Apple Time Machine
VS
pgBackRest
Reliable backup and restore solution for PostgreSQL
| Feature | Back In Time | pgBackRest |
|---|---|---|
| Category | Backup & Recovery | Backup & Recovery |
| License | GPL-2.0 | MIT |
| Language | Python | C |
| Setup difficulty | Easy | Hard |
| Min. RAM | 128 MB | 256 MB |
| Deployment | binary | docker, binary |
| GitHub stars | ★ 2,641 | ★ 4,296 |
| First released | 2008 | 2013 |
| Replaces | Time Machine | Veeam |
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
Choose pgBackRest if…
- Released under the MIT license
- First-class Docker support for quick deployment
- Active community (4.3k GitHub stars)
- Written in C
Frequently asked questions
Is Back In Time or pgBackRest better?
Neither is universally better. pgBackRest has the larger community, while Back In Time is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.
Are Back In Time and pgBackRest free and open-source?
Yes. Back In Time is licensed under GPL-2.0 and pgBackRest under MIT. Both can be self-hosted at no software cost.
Can I run Back In Time and pgBackRest with Docker?
Back In Time: check the project docs for container support. pgBackRest: yes.