Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of CrowdSec and v0 by Vercel — 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.
v0 lets ChatGPT subscribers pay with their plan and pulls Slack in as working context.
v0's recent releases concentrate on who pays and where context comes from. ChatGPT Plus and Pro subscribers can spend their plan instead of v0 credits, personal accounts became team workspaces, and the model picker now browses AI Gateway models with token pricing and Enterprise owner controls. Slack joined through MCP, and a lighter Code tab lets users edit files and leave comments as prompt context.
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.
v0's recent releases concentrate on who pays and where context comes from. ChatGPT Plus and Pro subscribers can spend their plan instead of v0 credits, personal accounts became team workspaces, and the model picker now browses AI Gateway models with token pricing and Enterprise owner controls. Slack joined through MCP, and a lighter Code tab lets users edit files and leave comments as prompt context.
The billing change is the directional one: eligible responses no longer have to be paid for in v0 credits. Paired with a picker that shows token prices, v0 is treating the model layer as something users bring or choose, while it competes on the builder, the collaboration surface and deployment. Making every account a workspace puts team features in front of solo users.
The ChatGPT option suggests other model subscriptions could be connected, though these entries name no other provider. More MCP connectors after Slack are the likeliest near-term release, given the existing connector pattern.
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 v0 by Vercel.
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 v0 by Vercel 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 v0 by Vercel 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 v0 by Vercel 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 v0 by Vercel alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "v0 by Vercel alternatives" section above for the current picks, or visit /alternatives/v0 for the full list with editorial commentary on each.