Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of CrowdSec and KubeArmor — 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.
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
KubeArmor's feed shows five release-candidate tags and one merge-commit entry from October for 1.7.6 and 1.7.7, each carrying one or two commits: a relay-channel memory leak fix with pprof added, a snitch fix, removed limits and an AppArmor alert-throttling fix. GitHub shows 1.7.6 went final on 23 October, which the feed missed; it replaced the execve kprobe with a tracepoint, fixed pods not terminating on AppArmor nodes, added audit alerts from the BPF-LSM enforcer and expanded arm64 eBPF testing.
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.
KubeArmor's feed shows five release-candidate tags and one merge-commit entry from October for 1.7.6 and 1.7.7, each carrying one or two commits: a relay-channel memory leak fix with pprof added, a snitch fix, removed limits and an AppArmor alert-throttling fix. GitHub shows 1.7.6 went final on 23 October, which the feed missed; it replaced the execve kprobe with a tracepoint, fixed pods not terminating on AppArmor nodes, added audit alerts from the BPF-LSM enforcer and expanded arm64 eBPF testing.
The project is mid-way through stabilising its eBPF enforcement across architectures: arm64 syscall matching, multi-arch image tests and the move from kprobes to tracepoints all reduce kernel-specific breakage. The release process remains RC-heavy, with near-identical tags cut minutes apart, which makes the feed a poor guide to what users actually get.
Expect 1.7.7 final soon after rc1, carrying the AppArmor throttling fix. The arm64 work in 1.7.6 suggests further multi-architecture fixes rather than new policy features next.
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 KubeArmor.
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.
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.
Uptrends spent October on account plumbing: vault credentials, bulk edits and a free trial path.
See all CrowdSec alternatives → · See all KubeArmor alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CrowdSec and KubeArmor are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 and KubeArmor are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 KubeArmor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "KubeArmor alternatives" section above for the current picks, or visit /alternatives/kubearmor for the full list with editorial commentary on each.