PAGES
← all tools
◆ Backup & Recovery

BorgBackup

1.1.7 open-source

Free plan: not checked yet · Open source: yes

Starting price: not checked yet

BorgBackup is an open-source deduplicating archiver with compression and authenticated encryption, used for space-efficient, verifiable backups.

What you can do now

Checking Plays…

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

all 24 features, with the evidence for each →

Languages

Not documented

Features

24 capabilities · 1 backed by code, an API document or a real run

Built from BorgBackup's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What BorgBackup offers you

  • Command-line interface10
  • JSON data export2
  • Disaster recovery1
  • Scripting language support1

All capabilities 24 capabilities
Data deduplication The tool uses chunk-based data deduplication to store only changes, making it efficient for daily backups and disk images. 26 other sources
Backup archive creation The tool can create new backup archives, with optional verbose statistics output. 24 other sources
Authenticated encryption support The tool supports authenticated encryption to ensure data confidentiality and integrity. 20 other sources
Remote repository support via SSH The tool can store backups in remote repositories using various SSH-based URL syntaxes. 14 other sources

Also counts toward: Command-line interface

Repository configuration management The tool can read, list, set, and delete configuration keys for the repository or its cache. 13 other sources

Also counts toward: Command-line interface

SSH access restriction and security hardening The tool supports restricting SSH-based backups to specific repositories or paths, enforcing storage quotas, and managing key exports for secure remote access. 12 other sources

Also counts toward: Command-line interface

Backup restoration and extraction The tool allows extracting selected or full archives to restore data, with options for dry-runs and sparse file support. 11 other sources

Also counts toward: Command-line interface, Disaster recovery

Repository compaction The tool can compact the repository to reclaim unused space left by deleted archives. 10 other sources

Also counts toward: Command-line interface

Archive diff comparison The tool can compare two archives or files within them to identify content and metadata differences. 8 other sources

Also counts toward: Command-line interface, JSON data export

Automated backup via udev and systemd The tool can be integrated with udev rules and systemd to automatically trigger backups when a block device such as a backup hard drive is connected. 7 other sources
Backup deletion The tool can remove specific archives or entire repositories from storage. 7 other sources

Also counts toward: Command-line interface

Benchmark mode The tool includes benchmark functionality to measure performance across scenarios such as deduplication of unchanged files, heavily duplicated files, and random data. 6 other sources
Encrypted repository initialisation The tool can initialise a new encrypted repository for storing backup data. 6 other sources
GPG signature verification The tool's release binaries are signed with a GPG key, and the tool's documentation describes how to verify those signatures using the published key fingerprint. 6 other sources
Repository integrity checking The tool can check the consistency and correctness of repository data, detecting bit rot and accidental damage via CRC checks, with optional cryptographic verification of file content. 6 other sources
Archive tagging The tool can assign tags to backups for organization and filtering. 5 other sources · first seen Sep 2026
JSON log output The tool can emit structured JSON lines on stderr to allow graphical frontends and scripts to parse and reformat progress and log information. 5 other sources

Also counts toward: Command-line interface, JSON data export

Pull-mode backup via SSHFS The tool supports a pull-mode backup setup where a backup server mounts the target's filesystem via SSHFS and runs backups without requiring the client to initiate the connection. 5 other sources
Python 3.7 support The tool can be used with Python 3.7 environments. 1 release · 2 other sources · first seen Aug 2018

Also counts toward: Command-line interface, Scripting language support

Compression support The tool can compress backup data using multiple algorithms including lz4 and zstd, with options trading speed against compression ratio. 3 other sources
Stdin backup input The tool can accept file paths or data from standard input for flexible backup workflows. 3 other sources

Also counts toward: Command-line interface

Debug profiling The tool provides a debug profile option that writes an execution profile of the main program to a file for developer analysis. 2 other sources
Size obfuscation The tool can actively obfuscate file and chunk sizes to make fingerprinting attacks against backup data more difficult. 2 other sources
Sparse file creation support The tool can create sparse files during extraction to save disk space for zero-filled chunks. 1 other source

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Releases

3 entries

  1. August 20261
  2. August 20231
  3. August 20181

    3 entries

    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.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 52% of issues opened, last 12 months
    5. Median time to close 104 days first maintainer reply 6.4 hours
    6. Open backlog 150 of 4,704 issues ever filed
    1. Issues opened / month 9 · 7 communitymaintainers
    2. Open backlog 150
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.