Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
Bugsnag vs CrowdSec
A side-by-side editorial comparison of Bugsnag and CrowdSec — release velocity, themes, recent moves, and the top alternatives to consider.
Bugsnag vs CrowdSec: at a glance
| Feature | Bugsnag | CrowdSec |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | error-tracking, correlated-events, mcp, mobile-monitoring | waf, bot-detection, security, fingerprinting |
| Last editorial update | 3h ago | 1h ago |
| Website | — | Visit → |
What is Bugsnag?
Bugsnag names GraphQL operations and lets iOS teams attach context to app hangs.
September's release is narrow and practical. The iOS SDK's new appHangCallback adds diagnostic context the moment a hang is detected, aimed at SwiftUI hangs where the stack trace alone doesn't show the cause, and GraphQL requests now appear by operation in Network performance views rather than under a single POST /graphql. It follows source-side discard enforcement in August and the Correlated Events work earlier in the year.
What is CrowdSec?
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.
Bugsnag vs CrowdSec: editorial side-by-side
Bugsnag
2.5INFRA · APIS
Bugsnag names GraphQL operations and lets iOS teams attach context to app hangs.
◆ Current state
September's release is narrow and practical. The iOS SDK's new appHangCallback adds diagnostic context the moment a hang is detected, aimed at SwiftUI hangs where the stack trace alone doesn't show the cause, and GraphQL requests now appear by operation in Network performance views rather than under a single POST /graphql. It follows source-side discard enforcement in August and the Correlated Events work earlier in the year.
◆ Where it's heading
Bugsnag is moving from single-service error tracking toward cross-service observability: Correlated Events, trace correlation, and the MCP server all point at workflows where an error in one service is causally linked to events in others. The Flutter SDK parity work (CPU, memory, rendering metrics) reflects a deliberate effort to close the feature gap between mobile and web monitoring. SDK Source-Side Discard Enforcement (remote rule push to SDK) reduces bandwidth and processing overhead at scale — a signal that larger enterprise deployments are a growth priority.
◆ Prediction
Correlated Events will likely expand to support more correlation dimensions — custom attributes, error clusters — and the MCP server toolset will grow to include mutation tools (creating alerts, snoozing errors) rather than just read-only access. The Performance Score metric will gain more visibility and dashboard integrations.
CrowdSec
5.0INFRA · APIS
CrowdSec's 1.8.2 candidates let operators write their own bot fingerprints.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Bugsnag and CrowdSec
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 Bugsnag or CrowdSec.
Apache ShenYu
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
All Quiet
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta
Robusta's recent releases patch its runner image rather than add features.
See all Bugsnag alternatives → · See all CrowdSec alternatives →
Recent activity from Bugsnag and CrowdSec
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10d agoCrowdSec1.8.2 rc2 adds a WAF RateLimit helper and decision stream limits
- 19d agoCrowdSec1.8.2 rc1 adds custom JS fingerprinting for bot detection
- 24d agoBugsnagBugsnag September: iOS appHangCallback and GraphQL by operation
- 2mo agoBugsnagBugsnag August: Remote SDK Source-Side Discard Enforcement goes live
- 2mo agoCrowdSec1.8 rc2 tunes the bot-detection challenge, hardens acquisition
- 3mo agoBugsnagBugsnag July: Custom session windows and CPU/memory metrics
- 3mo agoCrowdSecCrowdSec 1.8 RC adds WAF bot detection and a Kubernetes datasource ⚡
- 4mo agoBugsnagBugsnag June: Side-by-side span comparison and Vue Router v5 support
- 4mo agoBugsnagBugsnag May: iOS pre-main view, MCP OAuth 2.0, Flutter metrics
- 5mo agoBugsnagBugsnag April: Correlated Events across users, sessions and traces ⚡
- 6mo agoCrowdSec1.7.8 RC: OpenAPI schema validation in the WAF
- 7mo agoCrowdSec1.7.7 RC: flexible WAF rule conditions and RE2 by default
Frequently asked questions
What is the difference between Bugsnag and CrowdSec?
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.
Is Bugsnag better than CrowdSec?
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.
What are the best alternatives to Bugsnag?
Top Bugsnag alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Bugsnag alternatives" section above for the current picks, or visit /alternatives/bugsnag for the full list with editorial commentary on each.
What are the best alternatives to CrowdSec?
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.