Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of CrowdSec and Dagger — release velocity, themes, recent moves, and the top alternatives to consider.
CrowdSec's 1.8.2 candidates let operators write their own bot fingerprints.
The bot detection introduced with 1.8 is now being opened to customization. The 1.8.2 candidates add custom JavaScript fingerprinting, a cscli bot subcommand and a FlagSubmission helper, and rc2 adds a RateLimit helper for the WAF plus a cookie option for embedded contexts. Operational work runs alongside it: a cs_features metric, optional limits on concurrent decision streams and TLS certificate reloads.
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.
The bot detection introduced with 1.8 is now being opened to customization. The 1.8.2 candidates add custom JavaScript fingerprinting, a cscli bot subcommand and a FlagSubmission helper, and rc2 adds a RateLimit helper for the WAF plus a cookie option for embedded contexts. Operational work runs alongside it: a cs_features metric, optional limits on concurrent decision streams and TLS certificate reloads.
The WAF remains the center of gravity, and the direction is programmability. RateLimit, SkipProcessing and the fingerprinting hooks give rule authors primitives rather than fixed behavior. The LAPI changes point at larger deployments, where decision streaming puts load on the central API.
The final 1.8.2 is dated 26 October on GitHub, though it has not reached this feed yet. Whether fingerprint data ever joins the community blocklist remains unanswered in these notes.
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 CrowdSec 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 CrowdSec 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. CrowdSec is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. CrowdSec is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 CrowdSec alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CrowdSec alternatives" section above for the current picks, or visit /alternatives/crowdsec 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.