Detection as Code

Detecteam vs Sekoia.io

Detecteam totals 5.26 and Sekoia totals 3.46 on the 10 point detection-as-code rubric (sources read 2026-11-03 and 2026-11-04). Detecteam leads by 1.80 points. The pair turns on rule languages: Sekoia documents it in full, and Detecteam publishes nothing on it. Neither publishes anything on pricing.

The difference that decides this pair

The largest weighted gap on the rubric is testing: Detecteam scores 7.0 against 3.5 for Sekoia.io, which is 0.53 of the 10 point total.

For rule languages, Sekoia runs native Sigma YAML, including event_count, value_count and temporal correlation, alongside its own SOL queries, whereas Detecteam lists Splunk, Microsoft Sentinel, Google SecOps and Elastic Security as targets and names no rule language. docs.sekoia.com read 2026-11-03 detecteam.com read 2026-11-04

Rubric side by side

Detecteam totals 5.26 and Sekoia.io totals 3.46 out of 10.

Rubric criteria for Detecteam and Sekoia.io, scores out of 10. A plus marks a criterion where Sekoia.io scores higher, a minus where Detecteam does.

MarkerCriterionWeightDetecteamSekoia.io
-Rule languages and conversion paths155.04.0
-Git-native workflow and CI/CD185.03.5
-Testing157.03.5
-Coverage analytics127.03.5
-Rule health185.03.0
-Versioning and rollback84.03.0
Content library size and freshness84.04.0
Pricing transparency63.03.0
Total1005.263.46

The 33 capabilities as a diff

Read it as a diff from Detecteam to Sekoia.io: 17 of 33 rows differ. A plus marks a row where Sekoia.io documents more (14 rows), a minus a row where Detecteam documents more (3 rows). Rows with no marker match.

Capability rows for Detecteam and Sekoia.io, grouped. Changed rows are shaded and carry a marker.

MarkerCapabilityDetecteamSekoia.io
Languages
Sekoia.io documents moreSigma nativeDetecteam, Sigma native: not documentednot documentedSekoia.io, Sigma native: documenteddocumented
Sigma conversionDetecteam, Sigma conversion: not documentednot documentedSekoia.io, Sigma conversion: not documentednot documented
YARA-LDetecteam, YARA-L: not documentednot documentedSekoia.io, YARA-L: not documentednot documented
SPLDetecteam, SPL: not documentednot documentedSekoia.io, SPL: not documentednot documented
KQLDetecteam, KQL: not documentednot documentedSekoia.io, KQL: not documentednot documented
EQL or ES|QLDetecteam, EQL or ES|QL: not documentednot documentedSekoia.io, EQL or ES|QL: not documentednot documented
PythonDetecteam, Python: not documentednot documentedSekoia.io, Python: not documentednot documented
Visual builderDetecteam, Visual builder: not documentednot documentedSekoia.io, Visual builder: not documentednot documented
YARADetecteam, YARA: not documentednot documentedSekoia.io, YARA: not documentednot documented
Sekoia.io documents moreLucene or KQL-likeDetecteam, Lucene or KQL-like: not documentednot documentedSekoia.io, Lucene or KQL-like: partialpartial
Source control and CI
Git syncDetecteam, Git sync: not documentednot documentedSekoia.io, Git sync: not documentednot documented
PR deployDetecteam, PR deploy: not documentednot documentedSekoia.io, PR deploy: not documentednot documented
CLIDetecteam, CLI: not documentednot documentedSekoia.io, CLI: not documentednot documented
Sekoia.io documents moreRule APIDetecteam, Rule API: not documentednot documentedSekoia.io, Rule API: documenteddocumented
Detecteam documents moreCI examplesDetecteam, CI examples: partialpartialSekoia.io, CI examples: not documentednot documented
Env promotionDetecteam, Env promotion: not documentednot documentedSekoia.io, Env promotion: not documentednot documented
Testing
Unit testsDetecteam, Unit tests: partialpartialSekoia.io, Unit tests: partialpartial
Sekoia.io documents moreReplayDetecteam, Replay: not documentednot documentedSekoia.io, Replay: documenteddocumented
Detecteam documents moreSynthetic eventsDetecteam, Synthetic events: partialpartialSekoia.io, Synthetic events: not documentednot documented
Sekoia.io documents moreBacktest reportsDetecteam, Backtest reports: not documentednot documentedSekoia.io, Backtest reports: partialpartial
Detecteam documents moreTest coverageDetecteam, Test coverage: partialpartialSekoia.io, Test coverage: not documentednot documented
Coverage analytics
Sekoia.io documents moreATT&CK mapDetecteam, ATT&CK map: partialpartialSekoia.io, ATT&CK map: documenteddocumented
Gap viewDetecteam, Gap view: partialpartialSekoia.io, Gap view: partialpartial
Sekoia.io documents moreData sourcesDetecteam, Data sources: not documentednot documentedSekoia.io, Data sources: partialpartial
Sekoia.io documents moreLog source healthDetecteam, Log source health: not documentednot documentedSekoia.io, Log source health: partialpartial
Rule health
Sekoia.io documents moreNoisy rulesDetecteam, Noisy rules: not documentednot documentedSekoia.io, Noisy rules: partialpartial
Sekoia.io documents moreBroken rulesDetecteam, Broken rules: not documentednot documentedSekoia.io, Broken rules: partialpartial
Field driftDetecteam, Field drift: not documentednot documentedSekoia.io, Field drift: not documentednot documented
Sekoia.io documents moreRule costDetecteam, Rule cost: not documentednot documentedSekoia.io, Rule cost: partialpartial
Sekoia.io documents moreLifecycleDetecteam, Lifecycle: not documentednot documentedSekoia.io, Lifecycle: documenteddocumented
Library
Sekoia.io documents moreLibrary countDetecteam, Library count: partialpartialSekoia.io, Library count: documenteddocumented
CommunityDetecteam, Community: not documentednot documentedSekoia.io, Community: not documentednot documented
Sekoia.io documents moreCadenceDetecteam, Cadence: not documentednot documentedSekoia.io, Cadence: partialpartial

documenteddocumentedpartialpartialnot documentednot documented

Sources for the rows that differ

Verdict by buyer type

Which of the two fits each kind of team.

BuyerVerdict
Microsoft Sentinel estateDetecteam is the better fit: it lists Microsoft Sentinel among its targets on its home page (vendor claim); Sekoia documents no Sentinel path.
Elastic estateDetecteam is the better fit: it lists Elastic Security among its targets on its home page (vendor claim); Sekoia documents no Elastic path.
Splunk estateDetecteam is the better fit: it lists Splunk among its targets on its home page (vendor claim); Sekoia documents no Splunk path.
Google SecOps estateDetecteam is the better fit: it lists Google SecOps among its targets on its home page (vendor claim); Sekoia documents no Google SecOps path.
a team starting from scratch with SigmaSekoia is the better fit: it runs native Sigma YAML, correlation rules included, but documents no CI workflow; Detecteam documents no Sigma path.

When to pick each

Detecteam: Pick Detecteam when testing matters more to you than rule health, where Sekoia documents more: it generates attack behaviour data from an ATT&CK scenario library to test detections, with no replay or test format published.

Sekoia.io: Pick Sekoia when rule health is the deciding need: it groups repeat matches with alert similarity and documents no failed-rule alert. It also leads on rule languages.

Profiles: Detecteam, Sekoia.io. Alternatives: to Detecteam, to Sekoia.io.