BorgBackup
1.1.7 open-sourceFree plan: not checked yet · Open source: yes
Starting price: not checked yet
The section your link pointed to isn't on BorgBackup's page any more, so we've brought you to the top.
BorgBackup is an open-source deduplicating archiver with compression and authenticated encryption, used for space-efficient, verifiable backups.
What you can do now
Summary
BorgBackup is an open-source command-line backup and recovery program that stores versioned archives in repositories, with no licence cost, for people managing their own backups rather than a hosted service. It creates encrypted repositories and archives, supports tags and verbose statistics, and deduplicates across machines and previous backups, so moving files or making small changes does not require storing whole files again. It sits in the backup-recovery category and suits system administrators and technical users who can operate a CLI. Launched in 2015, it remains an active project, though Borg2 is marked beta and unsuitable for production.
BorgBackup is an open-source deduplicating archiver with compression and authenticated encryption, used for space-efficient, verifiable backups.
How BorgBackup helps
Which files can I recover from each backup point?
stores versioned archives in a repository, letting you select an earlier archive and recover the backed-up data
Can I back up data to a target I do not fully trust without exposing its contents?
encrypts data on the client side with authenticated encryption and verifies integrity and authenticity with HMAC-SHA256; access to the repository still requires the encryption key
Will moving files or changing part of a large file cause another full copy to be stored?
matches chunks by their content-derived identifiers rather than by names, timestamps, or positions, so moved data and unchanged portions can be reused; changed content creates new chunks
Which archives contain a particular group of backups?
records archives with tags and can display verbose archive statistics, allowing tagged archives to be identified and their reported contents and sizes reviewed
How can I verify that stored backup data has not been altered?
uses authenticated encryption and integrity checks when handling repository data, reporting verification failures rather than treating altered data as valid; this does not prove that every intended file was originally included
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for BorgBackup, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail BorgBackup puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
3 entries
No entries match these filters.
- August 20261
- August 20231
- August 20181
Project health
Issue, contributor and maintainer activity in borgbackup/borg, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors not measured distinct committers, last 12 months
- Maintainers not measured core set, last 12 months
- Bus factor not measured committers behind half the commits
- Community-filed 52% of issues opened, last 12 months
- Median time to close 104 days first maintainer reply 6.4 hours
- Open backlog 150 of 4,704 issues ever filed
- Issues opened / month 9 · 7 communitymaintainers
- Open backlog 150
- Contributors / month not measured
- Commits / month not measured
- Stars not measured
- bugs 10%
- features 1%
- questions 10%
- docs 2%
- other 77%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
How BorgBackup helps against real attacks
BorgBackup documents controls for 1 defense technology seen in attacks this year.
See the controls and how to set them → Included with Researcher and Business.
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.