← Back to home
Comparison · Infra & APIs

CrowdSec vs Merge

A side-by-side editorial comparison of CrowdSec and Merge — release velocity, themes, recent moves, and the top alternatives to consider.

CrowdSec vs Merge: at a glance

FeatureCrowdSecMerge
SectorInfra & APIsInfra & APIs
Velocity score3.86.3
Sparks · 30d11
Top themeswaf, bot-detection, intrusion-detection, kubernetesunified api, agent handler, mcp connectors, ai gateway
Last editorial update14d ago12h ago
WebsiteVisit →

What is CrowdSec?

CrowdSec's WAF is growing a bot-detection challenge — log analysis meets active interception.

The feed carries only release candidates, roughly one every two to three months, and the WAF has been the centre of gravity across all of them: OpenAPI schema validation, request body size limits, arbitrary AND/OR mixing in rule conditions, more Coraza transformations exposed, RE2 enabled by default on Linux. The 1.8.0 candidate breaks that pattern by adding challenge-and-fingerprint bot detection, serving an interstitial page and evaluating the result against configured rules. The same candidate adds a dedicated Kubernetes datasource that reads logs from the apiserver directly, and HTTP helpers so parsers and scenarios can query external services. Two earlier candidates in the window are pure refactoring with no user-visible change.

Read the full CrowdSec trajectory →

What is Merge?

Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.

Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.

Read the full Merge trajectory →

CrowdSec vs Merge: editorial side-by-side

C
CrowdSec
INFRA · APIS
3.8

CrowdSec's WAF is growing a bot-detection challenge — log analysis meets active interception.

◆ Current state

The feed carries only release candidates, roughly one every two to three months, and the WAF has been the centre of gravity across all of them: OpenAPI schema validation, request body size limits, arbitrary AND/OR mixing in rule conditions, more Coraza transformations exposed, RE2 enabled by default on Linux. The 1.8.0 candidate breaks that pattern by adding challenge-and-fingerprint bot detection, serving an interstitial page and evaluating the result against configured rules. The same candidate adds a dedicated Kubernetes datasource that reads logs from the apiserver directly, and HTTP helpers so parsers and scenarios can query external services. Two earlier candidates in the window are pure refactoring with no user-visible change.

◆ Where it's heading

CrowdSec started as a log-reading detection engine that handed decisions to external bouncers, and the WAF work has been steadily moving it into the request path. Bot detection completes that move: the product now generates its own signal by interrogating the client rather than only inferring from logs. The Kubernetes datasource and the expression-language HTTP helpers point the same way — fewer intermediaries between CrowdSec and both the telemetry and the enforcement point.

◆ Prediction

Expect the fingerprinting rules to become a shared, community-curated resource in the same way detection scenarios already are, since that is the pattern this project applies to every new signal it collects.

M
Merge
INFRA · APIS
6.3

Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.

◆ Current state

Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.

◆ Where it's heading

The through-line is that Merge is repositioning from data plumbing to the layer agents pass through. Each week adds either reach (more connectors, more tools per connector, more models) or control (guardrails, per-project policy, access configuration). This window is reach-and-efficiency: the GitHub connector expanded to 145 tools, Outlook payloads were cut substantially, and Gateway guardrails became configurable per project rather than per account.

◆ Prediction

Expect the per-project granularity applied to guardrails to spread to the rest of Gateway's controls, and the connector catalog to keep absorbing hosted third-party MCP servers the way Axiom was added.

Alternatives to CrowdSec and Merge

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 Merge.

See all CrowdSec alternatives → · See all Merge alternatives →

Recent activity from CrowdSec and Merge

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
  2. 19d agoMergeHundreds of generic MCP connectors land in Agent Handler
  3. 22d agoCrowdSecCrowdSec 1.8 RC adds WAF bot detection and a Kubernetes datasource
  4. 26d agoMergeLink setup flow becomes configurable per integration
  5. 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
  6. 1mo agoMergeGateway breakout page for the week already covered by Week 2
  7. 1mo agoMergeUnified breakout page for the week already covered by Week 3
  8. 3mo agoCrowdSec1.7.8 RC: OpenAPI schema validation in the WAF
  9. 4mo agoCrowdSec1.7.7 RC: flexible WAF rule conditions and RE2 by default
  10. 7mo agoCrowdSec1.7.5 RC: acquisition and leaky-bucket refactoring
  11. 8mo agoCrowdSec1.7.4 RC2: acquisition module split and lint cleanup

Frequently asked questions

What is the difference between CrowdSec and Merge?

They serve adjacent needs but don't currently overlap on shipped themes. Merge is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is CrowdSec better than Merge?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

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.

What are the best alternatives to Merge?

Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.