Find your fit
Who it is for
A system administrator can keep repeated backups of folders or machines while avoiding duplicate stored chunks across the repository's history. Borg suits teams prepared to choose a storage destination and operate a backup routine themselves.
Local disk, removable storage and SSH-reachable machines are the advertised repository options. Check the intended operating system and whether FUSE archive browsing fits the actual recovery workflow.
The work it supports
Core capabilities
Archive storage. Borg divides source files into content-defined chunks and stores a matching chunk only once across files and archive history. Actual space savings depend on the data and history being backed up.
Compression choices. The project lists lz4, zstd, zlib and lzma, plus no compression. Compare backup time, storage use and restore needs using representative files rather than assuming one setting will suit all data.
Authenticated encryption. Borg advertises AES encryption with cryptographic authentication so the backup server can hold ciphertext instead of plaintext. Confirm the chosen setup and key-handling procedure before relying on a remote destination.
Repository destinations. The site names local disk, USB drives and machines reachable over SSH. That makes the storage location a choice for the operator; the team should price and operate its chosen storage separately.
Archive browsing. Borg can mount an archive as a regular filesystem with FUSE, letting an operator browse older file versions as folders. A useful evaluation is to open an older archive and locate a known file on the intended system.
Deployment shape. The project advertises installation on Linux, macOS and BSD and describes operation without daemons or agents. Confirm the package version and platform-specific setup for the machines you plan to protect.
Understand the offer
Pricing and getting started
BorgBackup itself is free software under a BSD license, with free community support through documentation, issues and mailing-list posts. Storage, remote hosting and administration remain separate operational choices; the site also lists independent commercial service and support providers.
As of the reviewed release page, Borg 1.4 is the stable series and 1.4.5 is the listed release. Borg 2.0 is marked testing with a production-use warning; its preliminary note says 1.x repositories are not directly compatible and scripts need review. Plan any future migration separately.
Look a little closer
Before you choose
Pilot a representative backup to a chosen local, removable or SSH destination, then use the advertised FUSE browsing workflow to find an older file. Also decide how the team will confirm it can recover the data when the source machine is unavailable.
Compare compression settings with real file types and consider where encrypted repository credentials will be kept. Assign someone to monitor the process and storage capacity; Borg's agentless design leaves those operating choices to the team.
Use stable 1.4 for a production evaluation and keep any Borg 2.0 experiment isolated from an existing 1.x repository. The project's own preliminary note warns that it is a breaking upgrade and that command-line scripts need review.
3 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →
