2026.10.01
borgmatic: Configuration-Driven Borg Backup
borgmatic organizes file and database backups through configuration, with repository checks, retention rules, and notifications. Before adoption, review Borg dependencies, recovery workflows, key management, and monitoring coverage.
What it is for
borgmatic is configuration-driven backup software for servers and workstations, built on Borg Backup. It suits self-hosted users, small teams, and operators who want source directories, repositories, retention rules, and checks described in configuration rather than maintained as scattered manual commands. The README also describes client-side encryption. However, the operator remains responsible for protecting, rotating, and recovering encryption keys.
Known capabilities
A configuration can describe multiple source directories and local or remote repositories. The example includes daily, weekly, and monthly retention counts, repository and archive checks, and custom preparation commands that run before a backup action. This makes borgmatic relevant to repeatable operational workflows, provided the surrounding credentials, scheduling, and storage are managed separately.
Database backup is also part of the documented use case. The README shows PostgreSQL database dumping, while repository topics list MariaDB, MongoDB, MySQL, and SQLite. The 2.1.9 release notes add glob matching for configured PostgreSQL, MariaDB, and MySQL database names, plus glob support for the restore action’s data-source option. That can reduce repetitive configuration in environments with predictable database names, but each dump and restore path still needs validation.
For monitoring and notifications, the README shows a Healthchecks integration for detecting whether backups are occurring. Repository topics also mention Apprise, ntfy, Loki, Zabbix, and Uptime Kuma. The topic list alone does not establish the full behavior or configuration details of each integration, so operators should verify the relevant project documentation and the selected service.
Who it suits
borgmatic is a reasonable candidate for self-hosted users and operations teams comfortable with Linux, SSH, Borg repositories, and YAML configuration. Teams seeking a graphical wizard, managed key custody, or a prebuilt disaster-recovery process should first confirm that borgmatic and Borg fit their existing procedures; the supplied sources do not make complete claims in those areas.
Limits and deployment considerations
Because borgmatic is powered by Borg Backup, deployment planning should include Borg versions, remote repository access, and SSH credentials. The supplied sources do not confirm minimum hardware requirements, a complete compatibility matrix, or performance figures, so they should not be used to estimate capacity or backup windows.
A successful backup is not proof of a successful recovery. Database dumps, archive checks, encryption-key protection, and scheduled restoration exercises should be validated separately. Notifications should supplement local logs and human review, not replace them. Remote repositories also require planning for network failures, credential scope, retention mistakes, and lost keys.
The GitHub repository identifies GPL-3.0, while the README describes the project as GPL version 3 or any later version. Before adoption, confirm that the license fits internal modification, distribution, and release practices. The supplied sources do not provide pricing, minimum resource requirements, or an independent security-audit conclusion, so none should be treated as established guarantees.
Sources
Sources checked: 2026-10-01