Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of CrowdSec and Okta — 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.
Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features
Okta's developer feed is still led by Cross App Access, the token-exchange grant that lets an app or agent reach a third-party API on a user's behalf from an existing SSO trust. The newest guide builds a TypeScript MCP client with it, following an earlier C# version. The other notable item is a hard date: from March 5, 2027, Okta ends support for SSR, Desktop SSO and Device Trust on Classic Engine.
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.
Okta's developer feed is still led by Cross App Access, the token-exchange grant that lets an app or agent reach a third-party API on a user's behalf from an existing SSO trust. The newest guide builds a TypeScript MCP client with it, following an earlier C# version. The other notable item is a hard date: from March 5, 2027, Okta ends support for SSR, Desktop SSO and Device Trust on Classic Engine.
The XAA guides keep working through federation shapes and languages rather than adding a new grant. The Classic Engine notice points the same way from the platform side: customers are being moved onto Okta Identity Engine, with the end-of-support date as the push. Both threads are about adoption of what already exists.
Expect more Identity Engine migration guidance ahead of March 2027, alongside further XAA walkthroughs for other languages and agent frameworks.
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 Okta.
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 Okta 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 Okta alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Okta alternatives" section above for the current picks, or visit /alternatives/okta for the full list with editorial commentary on each.