← Back to home
Comparison · Infra & APIs

BorgBackup vs nuggets

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

BorgBackup vs nuggets: at a glance

FeatureBorgBackupnuggets
SectorInfra & APIsInfra & APIs
Velocity score6.32.5
Sparks · 30d10
Top themesbackup, deduplication, repository-format, dual-branchpattern-mining, association-rules, guha, cpp-performance
Last editorial update15d ago1h ago
WebsiteVisit →Visit →

What is BorgBackup?

Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.

Borg runs two trains in the same feed. The 1.4.x line is explicitly a refreshed 1.2 — same features and behaviour, with the riskier changes isolated so they could be tested before shipping — and it has taken over as the recommended branch since 1.2.9 was called the final 1.2 release. The 2.0 line has been in beta since well before this window, at b22 as of July 2026, with every release carrying a do-not-use-on-production warning. b22 introduced packs and the maintainers told users to expect alpha stability despite the beta number.

Read the full BorgBackup trajectory →

What is nuggets?

nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.

nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.

Read the full nuggets trajectory →

BorgBackup vs nuggets: editorial side-by-side

B
BorgBackup
INFRA · APIS
6.3

Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.

◆ Current state

Borg runs two trains in the same feed. The 1.4.x line is explicitly a refreshed 1.2 — same features and behaviour, with the riskier changes isolated so they could be tested before shipping — and it has taken over as the recommended branch since 1.2.9 was called the final 1.2 release. The 2.0 line has been in beta since well before this window, at b22 as of July 2026, with every release carrying a do-not-use-on-production warning. b22 introduced packs and the maintainers told users to expect alpha stability despite the beta number.

◆ Where it's heading

The split is the story: one branch exists purely to keep existing users safe and current, while the other rewrites how data is stored on disk. Packs are the kind of change that determines whether 2.0 ever ships — repository layout affects performance, resumability and every recovery path at once, and the honesty about stability regressing suggests the shakeout is still ahead. The 1.4 line will keep absorbing fixes and low-severity security work in the meantime, and the b18 corruption bug shows why the two trains are kept firmly apart.

◆ Prediction

Expect further 2.0 betas focused on packs stability before anything resembling a release candidate, with 1.4.x continuing to carry routine fixes for production users.

N
nuggets
INFRA · APIS
2.5

nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.

◆ Current state

nuggets searches for association rules, contrasts and other conditional patterns in the GUHA tradition, with a C++ core behind dig() and an interactive explore() app for reading results. Since the 2.0 rewrite of that core, every release has widened the same three surfaces: more pattern families to mine, more of explore() to inspect them in, and steady performance work underneath. The most recent tag optimises dig() on sparse crisp data with a sparse bit chain and adds clustering characteristics to explore() for association rules.

◆ Where it's heading

Two forces are shaping the package. One is coverage: baseline, complement and paired-baseline contrasts, correlations, tautologies, ancestors and clustering have all been added as first-class dig_ or explore_ surfaces, so the same search engine now answers a widening set of questions. The other is weight — Shiny packages moved from Imports to Suggests, BH and RcppThread dropped, XSIMD updated, parse_condition() rewritten in C++ — which keeps a package with an interactive app from forcing that app's dependencies on every user. Deprecations are handled through lifecycle rather than removed abruptly.

◆ Prediction

Expect the sparse-data optimisation to extend from crisp to fuzzy data, and explore() to keep gaining tabs as each new pattern family lands, on the roughly six-week cadence the 2.2 line has held.

Alternatives to BorgBackup and nuggets

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 nuggets.

See all BorgBackup alternatives → · See all nuggets alternatives →

Recent activity from BorgBackup and nuggets

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

  1. 19d agoBorgBackup1.4.5: fixes, a low-severity security fix and small features
  2. 27d agonuggetsSparse bit chain speeds dig(); explore() gains clustering
  3. 28d agoBorgBackup2.0.0b22 introduces packs — and warns stability regressed to alpha
  4. 2mo agonuggetspartition() gains .subsets; geom_diamond() layout improved
  5. 4mo agoBorgBackup1.4.4 maintenance release
  6. 5mo agoBorgBackup2.0.0b21 beta, testing only
  7. 5mo agonuggetsexplore() covers contrasts and correlations; dig_ancestors() added
  8. 6mo agonuggetsCritical explore() bug fixed; is_logicalish() added
  9. 6mo agonuggetsShiny deps moved to Suggests; BH and RcppThread dropped
  10. 7mo agoBorgBackup2.0.0b20 beta, testing only
  11. 8mo agoBorgBackup1.4.3 maintenance release
  12. 8mo agonuggetscluster_associations() and add_interest() arrive; C++ condition parser

Frequently asked questions

What is the difference between BorgBackup and nuggets?

They serve adjacent needs but don't currently overlap on shipped themes. BorgBackup is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 nuggets?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BorgBackup is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 nuggets?

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