Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of BorgBackup and Dagger — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Dagger now runs the engines for you and reports CI per test, not per job.
Dagger's recent changelog holds two product moves. Cloud Engines, in September, are hosted engines with scale-out, distributed cache and observability, billed only for resources used, with Dagger claiming repeat work costs 5× less. Test-native CI, in October, tracks individual tests, so a failure names the test and only that test is run again. Around them sit cache and plumbing changes, including COPY steps that depend only on the files they copy and SSH-mounted remote filesystems.
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.
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.
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.
Dagger's recent changelog holds two product moves. Cloud Engines, in September, are hosted engines with scale-out, distributed cache and observability, billed only for resources used, with Dagger claiming repeat work costs 5× less. Test-native CI, in October, tracks individual tests, so a failure names the test and only that test is run again. Around them sit cache and plumbing changes, including COPY steps that depend only on the files they copy and SSH-mounted remote filesystems.
Both moves rest on the same idea: treat the pipeline as a graph Dagger can see into, then avoid repeating work. A layer cache that survives unrelated file changes, per-test reruns and a distributed cache all reduce what a run must redo. Cloud Engines turn that saving into something sold, the one metered offering in these entries.
Expect Test-native CI and Cloud Engines to converge, with per-test reruns offered through hosted engines. That link is inferred from the two launches; the entries neither state it nor give pricing detail.
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 Dagger.
Oh Dear's weekly changelogs have carried a security section five weeks running.
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta's recent releases patch its runner image rather than add features.
See all BorgBackup alternatives → · See all Dagger alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dagger is currently shipping more aggressively (velocity 2.5 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dagger is currently shipping more aggressively (velocity 2.5 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.
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.
Top Dagger alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dagger alternatives" section above for the current picks, or visit /alternatives/dagger for the full list with editorial commentary on each.