MongoDB Software / SaaS France

CrowdSec

Security and Compliance

CrowdSec needed a more agile data platform than PostgreSQL so it could evolve threat-intelligence schemas quickly, avoid downtime-heavy upgrades, and turn growing cyber-threat telemetry into searchable and AI-ready products.

CrowdSec has more than 110,000 live engines sending data regularly.
The company ingests 900 million telemetry documents every 30 days.
The startup was launched in France in 2020 and has expanded its CTI offerings significantly over the last year and a half.

Reported impact

Business outcome

CrowdSec improved developer velocity, removed painful upgrade downtime, expanded its threat-intelligence product set, and created a more scalable security-data platform for customer-facing CTI services.

  • Productivity Improvement
  • Risk Reduction
  • Scalability

Solution

CrowdSec moved core cyber-threat intelligence and telemetry workloads onto MongoDB so it could iterate faster and turn security data into a richer product. Its open source engines detect attacks on host machines, remediate them locally, and send the resulting events to CrowdSec’s cloud platform, where AI and machine-learning models classify malicious IP addresses and publish curated blocklists. As the company grew, PostgreSQL schema migrations and version upgrades slowed development, so CrowdSec shifted increasing volumes of API and CTI data to MongoDB Atlas, added Atlas Search for fast queries, adopted Atlas Vector Search to cluster IPs with similar behavior, and used Time Series collections for high-volume engine telemetry. Data Federation exports colder data for deeper analysis, and Professional Services helped tune indexing and collection design. This integrated architecture lets CrowdSec search, enrich, and analyze huge threat datasets without breaking developer velocity.

Data flow

Host engines detect attacks and send telemetry to CrowdSec’s cloud, Atlas stores CTI and blocklist data, Atlas Search and Vector Search expose that intelligence for queries and similarity analysis, and Data Federation moves colder data into deeper analytical workflows.

Solution architecture

5 components · 2 layers
  1. Storage
    • MongoDB Atlas Stores CrowdSec’s API, CTI, and security blocklist data as the main operational threat-intelligence platform.
    • MongoDB Time Series collections Stores high-volume telemetry from active security engines efficiently over time.
  2. Serving
    • MongoDB Atlas Search Makes CrowdSec’s CTI datasets quickly searchable for user-facing threat exploration.
    • MongoDB Atlas Vector Search Clusters IPs with similar behavior so the team can detect related or emerging threat actors.
    • MongoDB Data Federation Exports and queries colder data so data scientists can analyze it without stressing live operational clusters.

Architecture clues

  • Atlas Search and Vector Search are both used directly on customer-facing CTI datasets.
  • CrowdSec retains PostgreSQL only with a limited perimeter while moving CTI and API data into MongoDB.
  • Data Federation is used to move colder data into data-science analysis without exploring live data directly.
  • Time Series collections capture telemetry from over 100,000 active engines.

Evidence from the source

“From an operations standpoint, MongoDB is a no-brainer. It’s there, it works, there’s no headache.”
“Our first motivation was developer velocity.”
“With MongoDB, we can truly leverage our data to power AI algorithms on data all in one place.”
“With more than 110,000 live engines sending data regularly, we know a lot of things about a lot of IPs.”
Transparency Evidence & methodology 90/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. MongoDB

    CrowdSec customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/crowdsec
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jul 29, 2025 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Aug 1, 2025 · MongoDB · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.