Flamingo Raises $4.5M to Get MSPs Out of the Ticket Queue

Skip to content
BorgBackup logo

BorgBackup

Cloud Backup Solutions

Open Source
Free Tier
Self-hosted
OpenMSP Score
87
83
Reddit Impact Score
Github Score
325M
13KStars
884Forks
11KCommits
OtherLicense
Nov 17, 2026Last commit
BorgBackup (Borg) is a free, BSD-licensed command-line backup program. It splits data into content-defined chunks and stores each chunk only once, so repeated daily backups and moved files take very little extra space. Data can be compressed with lz4, zstd, zlib or lzma and is encrypted and authenticated on the client, so the repository can live on an untrusted server reached over SSH. Borg 1.4 is the current stable series (1.4.5, July 2026). Borg 2.0 is in public beta and is not yet recommended for production; its repositories are not compatible with 1.x and need a transfer step. Borg runs on Linux, macOS and the BSDs. It has no built-in GUI or central console: MSPs usually drive it with scripts or wrappers such as borgmatic or Vorta, and store repositories on their own servers or on Borg-aware hosting such as BorgBase, Hetzner Storage Box or rsync.net. Commercial support is offered by Waldmann EDV.
image media

Key Features

Advanced Deduplication

Content-defined chunking with rolling hash algorithm that identifies and eliminates duplicate data segments across all backups, significantly reducing storage requirements.

Strong Encryption

Data is encrypted with AES and authenticated on the client before it leaves the machine, so backups can be stored on untrusted servers.

Multiple Compression Options

Supports lz4, zstd, zlib and lzma compression (or none), so speed and compression ratio can be balanced per repository.

FUSE Mounting

Backup archives can be mounted as filesystems using FUSE, enabling easy interactive examination and restoration of individual files without full extraction.

Cross-Platform Support

Runs on Linux, macOS and the BSDs, with repositories on local disks, USB drives or any machine reachable over SSH.

Retention and Pruning

borg prune keeps archives by daily, weekly, monthly and yearly rules, and borg compact frees the space afterwards.

Pros and Cons

Pros

Strong Client-Side Encryption

Data is encrypted and authenticated before it leaves the client, so backups can sit on untrusted storage

Open Source and Free

BSD licensed, no licensing cost per device or per client, actively maintained

Excellent Deduplication

Content-defined chunking stores identical data once, so daily backups and moved files add very little space

Efficient Performance

Incremental runs only process changed data, which keeps daily backups fast and light on resources

Wide Hosting Choice

Repositories can be kept on any SSH server or on Borg-aware hosting such as BorgBase, Hetzner Storage Box and rsync.net

Cons

Learning Curve

Complex configuration and concepts can be challenging for beginners, especially understanding repository management and pruning strategies

Borg 2.0 Migration Ahead

Borg 2.0 is still in beta; its repositories are not compatible with 1.x, so moving to it later needs a transfer of existing archives

Command Line Only

No built-in graphical interface; GUIs such as Vorta and wrappers such as borgmatic are separate projects

No Multi-Tenant Console

No central dashboard, alerting or per-client management; MSPs must build monitoring and reporting themselves

No Native Windows Support

Officially supports Linux, macOS and BSD only, so Windows endpoints need another tool

Feature Comparison

Features
Cost and Licensing
Loading the comparison

Comments

No reviews yet. Be the first to share your experience with BorgBackup.

Frequently Asked Questions

/vendor/borgbackup