ToolScore

Borg

BorgBackup project · backups · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-12

The compression workhorse (zstd/lzma) over an SSH-only transport, with repo-side append-only immunity — and a Borg 2 you must not use on production yet.

#4 of 12 in Backups

Try Borg for $0
Real price
$0 · OSS
open-source
Free tier
Yes
$0 — BSD-3-Clause open source. 1.4.5 stable (2026-07-19). Borg 2 is beta — “DO NOT USE BORG2 FOR YOUR PRODUCTI
Limits
9.5/10
$0 (BSD-3-Clause) · 1.4.5 stable (2026-07-19) · Borg 2 beta: do not use on production
Verdict
COMPRESSION WORKHORSE
Repository-wide lock = one writer at a time. Ransomware defense: borg serve --append-only (or append_only 1 in

ToolScore breakdown — why 81/100

Price / Value
10.0
Token & Rate Limits
9.5
Speed / Latency
7.5
Privacy & Retention
5.0
BYOK (Own API Key)
7.0
Output Quality
9.0
Stability
8.0
Ease of Setup
8.0
Billing Transparency
9.5
Support & Community
6.5

10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →

What it does well

  • ▸The compression workhorse — zstd and lzma over an SSH-only transport
  • ▸borg serve --append-only (or append_only 1 in repo config) gives repo-side immunity — easiest with per-client SSH keys
  • ▸1.4.5 stable (2026-07-19); Vorta puts a tray-icon GUI on top without a terminal

Where it costs you

  • ▸Repository-wide lock = one writer at a time — parallel multi-client is Restic's model, not Borg's
  • ▸Borg 2 is beta: “DO NOT USE BORG2 FOR YOUR PRODUCTION BACKUPS!” (2.0.0b25, no beta-to-beta upgrade path)
  • ▸SSH-only transport — no native object-storage backend in this snapshot's facts

Hidden traps — the stuff the pricing page doesn't say

high riskBorg 2 is beta — loudly

The project's own words: “DO NOT USE BORG2 FOR YOUR PRODUCTION BACKUPS!” (2.0.0b25) — and there is no beta-to-beta upgrade path. Production stays on 1.4.5 stable until the project says otherwise.

medium riskOne writer at a time

The repository-wide lock serializes writers. For a single machine or a serial schedule that is fine; households and fleets writing concurrently should look at Restic's non-exclusive model.

low riskAppend-only lives in the server config

append_only 1 in the repo config (or borg serve --append-only) is what makes the repo immune to a compromised client. Without it, the client can prune its own history.

Try Borg

Know the limits before you pay: read the traps above, then decide with eyes open.

Visit official site

Affiliate link where available — never affects the score.

What the advertised price hides
$0 — BSD-3-Clause open source. 1.4.5 stable (2026-07-19). Borg 2 is beta — “DO NOT USE BORG2 FOR YOUR PRODUCTION BACKUPS!” (2.0.0b25, no beta-to-beta upgrade path). Vorta adds the tray-icon GUI.
Sources & freshness

Data as of 2026-11-12. Prices and limits change monthly — report anything stale. How we verify: methodology.

Closest alternatives

Borg review

In-depth analysis · last updated 2026-11-12

The compression workhorse

Borg's identity is in the hub's first phrase for it: the compression workhorse — zstd and lzma — over an SSH-only transport. The current stable is 1.4.5 (2026-07-19), BSD-3-Clause, and the repo model is classic: one repository-wide lock, one writer at a time, per-client SSH keys if you want them.

The immunity is repo-side

The ransomware defense is the equal of Restic's, implemented one layer down: borg serve --append-only, or append_only 1 in the repo config, makes the repository refuse deletion and modification — repo-side immunity, easiest to arrange with per-client SSH keys. A compromised client can add backups; it cannot erase them.

The Borg 2 asterisk

The beta warning is the project's own and worth quoting whole: “DO NOT USE BORG2 FOR YOUR PRODUCTION BACKUPS!” Borg 2 sits at 2.0.0b25 with no beta-to-beta upgrade path — meaning a beta repo today may not carry to the next beta. Production belongs on 1.4.5; the warning itself, published loudly, is the kind of honesty you want from a backup project.

How the pillars land

Price/Value 10 — $0, BSD-3-Clause; the bill is a host and electricity. Retention & versioning 9.5 — full client-side retention plus the append_only wall in the repo config. Speed limits 7.5 — compression is the throughput story, but the repository-wide lock serializes writers: one at a time. Encryption model sits at the neutral 5 — no cipher facts are verifiable in this snapshot. BYO storage (B2/S3) 7 — the repo goes wherever SSH goes, but no native object-storage backend appears in these facts; B2/S3 buckets need a bridge. Feature set 9 — zstd/lzma compression, per-client SSH keys, the Vorta GUI on top; docked for the serial-writer model. Track record 8 — a dated stable line (1.4.5, 2026-07-19) and a loudly-documented beta; the no-upgrade-path caveat costs the points. Ease of use 8 — Vorta makes Borg usable without a terminal, which no other engine here can say. Pricing transparency 9.5 — license, versions and the production warning are all published by the project itself. Support & docs 6.5 — docs and repo verified; community support only.

Verdict — 81/100

For a single machine or a serially-scheduled set of boxes over SSH, Borg plus Vorta is the most polished free answer on the board — compress hard, lock the repo with append_only, and let per-client keys keep clients honest. Just keep production on 1.4.5 until Borg 2's warning comes down.

From the insights