Barman vs WAL-G
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?
Barman
Backup and recovery manager for PostgreSQL
VS
WAL-G
Archival and restoration tool for databases
| Feature | Barman | WAL-G |
|---|---|---|
| Category | Backup & Recovery | Backup & Recovery |
| License | GPL-3.0 | Apache-2.0 |
| Language | Python | Go |
| Setup difficulty | Hard | Hard |
| Min. RAM | 256 MB | 256 MB |
| Deployment | bare-metal | docker, binary |
| GitHub stars | ★ 3,214 | ★ 4,215 |
| First released | 2012 | 2017 |
| Replaces | Veeam | pgBackRest |
Why pick each one
Choose Barman if…
- Released under the GPL-3.0 license
- Active community (3.2k GitHub stars)
- Written in Python
- Tiny footprint — runs in 256 MB RAM
Choose WAL-G if…
- Released under the Apache-2.0 license
- First-class Docker support for quick deployment
- Active community (4.2k GitHub stars)
- Written in Go
Frequently asked questions
Is Barman or WAL-G better?
Neither is universally better. WAL-G has the larger community; both share a hard setup difficulty, so the decision comes down to features and licensing.
Are Barman and WAL-G free and open-source?
Yes. Barman is licensed under GPL-3.0 and WAL-G under Apache-2.0. Both can be self-hosted at no software cost.
Can I run Barman and WAL-G with Docker?
Barman: check the project docs for container support. WAL-G: yes.