← Back to home
Comparison · Infra & APIs

BorgBackup vs Dragonfly

A side-by-side editorial comparison of BorgBackup and Dragonfly — release velocity, themes, recent moves, and the top alternatives to consider.

BorgBackup vs Dragonfly: at a glance

FeatureBorgBackupDragonfly
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesbackup, deduplication, storage, encryptionin-memory datastore, clustering, slot migration, performance
Last editorial update18h ago4h ago
WebsiteVisit →Visit →

What is BorgBackup?

Borg 2.0 beta 25 breaks repositories to swap its hash and repository format.

BorgBackup's 2.0 beta line is still making breaking format changes. Beta 25 requires new repositories: it moves store object names to blake3, replaces several repository objects with an ini-style config, removes the none-sha256 and none-blake3 modes in favor of authenticated ones, and protects lock, index and cache objects with the repository key. The stable 1.4 line remains the production track.

Read the full BorgBackup trajectory →

What is Dragonfly?

Dragonfly speeds up slot lookups on 2.0 as its cluster-mode fixes keep coming.

Dragonfly maintains two incremental lines, 1.40 and 2.0, with small targeted releases. The 2.0 line has fixed dropped writes during slot migration and moved experimental slot-based sharding to Fibonacci hashing. i2.0.6 on October 30 makes GetSlotInfo faster, another cluster-mode refinement.

Read the full Dragonfly trajectory →

BorgBackup vs Dragonfly: editorial side-by-side

B
BorgBackup
INFRA · APIS
0.0

Borg 2.0 beta 25 breaks repositories to swap its hash and repository format.

◆ Current state

BorgBackup's 2.0 beta line is still making breaking format changes. Beta 25 requires new repositories: it moves store object names to blake3, replaces several repository objects with an ini-style config, removes the none-sha256 and none-blake3 modes in favor of authenticated ones, and protects lock, index and cache objects with the repository key. The stable 1.4 line remains the production track.

◆ Where it's heading

Twenty-five betas in, the format is not settled, but this beta is decisive: it removes old modes and object types, which narrows what 2.0 has to support. Treating lock and cache objects as keyed data also extends the security model beyond archive contents.

◆ Prediction

Further betas are likely to keep requiring new repositories until the format freezes, so a release candidate should not be assumed soon. The 1.4 line stays the safe choice until then.

D
Dragonfly
INFRA · APIS
5.0

Dragonfly speeds up slot lookups on 2.0 as its cluster-mode fixes keep coming.

◆ Current state

Dragonfly maintains two incremental lines, 1.40 and 2.0, with small targeted releases. The 2.0 line has fixed dropped writes during slot migration and moved experimental slot-based sharding to Fibonacci hashing. i2.0.6 on October 30 makes GetSlotInfo faster, another cluster-mode refinement.

◆ Where it's heading

The 2.0 line is maturing through cluster and migration work, while 1.40 gets targeted performance backports. Release cadence has slowed from paired weekly builds to occasional single fixes.

◆ Prediction

Expect further 2.0.x builds focused on cluster mode and slot migration; whether scope-based memory tracking gets switched on is still unclear.

Alternatives to BorgBackup and Dragonfly

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either BorgBackup or Dragonfly.

See all BorgBackup alternatives → · See all Dragonfly alternatives →

Recent activity from BorgBackup and Dragonfly

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3d agoDragonflyi2.0.6: faster slot info lookups in cluster mode
  2. 12d agoDragonflyi1.40.13: Sidekiq queues placed on the same shard
  3. 12d agoDragonflyi2.0.5: Fibonacci hashing evens out slot-based sharding
  4. 12d agoDragonflyi1.40.12: single-shard BLMOVE completes in one hop
  5. 12d agoDragonflyi2.0.4: slot migration no longer drops writes to empty buckets
  6. 13d agoDragonflyi2.0.3: storage read-lifetime fix backported
  7. 1mo agoBorgBackupBeta 25 moves to blake3 and requires new repositories
  8. 2mo agoBorgBackupBorgBackup 2.0.0b24
  9. 2mo agoBorgBackupBorgBackup 2.0.0b23
  10. 3mo agoBorgBackupBorgBackup 1.4.5 — security fix and new features
  11. 3mo agoBorgBackupBorgBackup 2.0.0b22 — PACKS storage format debuts ⚡
  12. 7mo agoBorgBackupBorgBackup 1.4.4

Frequently asked questions

What is the difference between BorgBackup and Dragonfly?

They serve adjacent needs but don't currently overlap on shipped themes. Dragonfly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is BorgBackup better than Dragonfly?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dragonfly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to BorgBackup?

Top BorgBackup alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BorgBackup alternatives" section above for the current picks, or visit /alternatives/borgbackup for the full list with editorial commentary on each.

What are the best alternatives to Dragonfly?

Top Dragonfly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dragonfly alternatives" section above for the current picks, or visit /alternatives/dragonfly for the full list with editorial commentary on each.