Detection as Code

Panther vs Sekoia.io

Panther totals 6.31 and Sekoia totals 3.46 on the 10 point detection-as-code rubric (sources read 2026-11-03 and 2026-11-04). Panther leads by 2.85 points. The pair turns on testing: Panther documents it in full, and Sekoia documents it only in part, or as a vendor claim. Neither publishes anything on pricing.

The difference that decides this pair

The largest weighted gap on the rubric is Git-native workflow and CI/CD: Panther scores 9.0 against 3.5 for Sekoia.io, which is 0.99 of the 10 point total.

On testing, Panther runs per-detection unit tests with panther_analysis_tool test and previews a rule on stored logs with Data Replay (Beta), while Sekoia tests a Sigma pattern against historical data in a rule testing view, with results that are not saved as a report. docs.panther.com read 2026-11-03 docs.sekoia.com read 2026-11-03

Rubric side by side

Panther totals 6.31 and Sekoia.io totals 3.46 out of 10.

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

MarkerCriterionWeightPantherSekoia.io
-Rule languages and conversion paths158.04.0
-Git-native workflow and CI/CD189.03.5
-Testing158.03.5
-Coverage analytics125.03.5
-Rule health183.53.0
-Versioning and rollback86.03.0
-Content library size and freshness85.04.0
Pricing transparency63.03.0
Total1006.313.46

The 33 capabilities as a diff

Read it as a diff from Panther to Sekoia.io: 16 of 33 rows differ. A plus marks a row where Sekoia.io documents more (4 rows), a minus a row where Panther documents more (12 rows). Rows with no marker match.

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

MarkerCapabilityPantherSekoia.io
Languages
Sekoia.io documents moreSigma nativePanther, Sigma native: not documentednot documentedSekoia.io, Sigma native: documenteddocumented
Panther documents moreSigma conversionPanther, Sigma conversion: documenteddocumentedSekoia.io, Sigma conversion: not documentednot documented
YARA-LPanther, YARA-L: not documentednot documentedSekoia.io, YARA-L: not documentednot documented
SPLPanther, SPL: not documentednot documentedSekoia.io, SPL: not documentednot documented
KQLPanther, KQL: not documentednot documentedSekoia.io, KQL: not documentednot documented
EQL or ES|QLPanther, EQL or ES|QL: not documentednot documentedSekoia.io, EQL or ES|QL: not documentednot documented
Panther documents morePythonPanther, Python: documenteddocumentedSekoia.io, Python: not documentednot documented
Panther documents moreVisual builderPanther, Visual builder: documenteddocumentedSekoia.io, Visual builder: not documentednot documented
YARAPanther, YARA: not documentednot documentedSekoia.io, YARA: not documentednot documented
Lucene or KQL-likePanther, Lucene or KQL-like: partialpartialSekoia.io, Lucene or KQL-like: partialpartial
Source control and CI
Panther documents moreGit syncPanther, Git sync: documenteddocumentedSekoia.io, Git sync: not documentednot documented
Panther documents morePR deployPanther, PR deploy: documenteddocumentedSekoia.io, PR deploy: not documentednot documented
Panther documents moreCLIPanther, CLI: documenteddocumentedSekoia.io, CLI: not documentednot documented
Rule APIPanther, Rule API: documenteddocumentedSekoia.io, Rule API: documenteddocumented
Panther documents moreCI examplesPanther, CI examples: documenteddocumentedSekoia.io, CI examples: not documentednot documented
Env promotionPanther, Env promotion: not documentednot documentedSekoia.io, Env promotion: not documentednot documented
Testing
Panther documents moreUnit testsPanther, Unit tests: documenteddocumentedSekoia.io, Unit tests: partialpartial
ReplayPanther, Replay: documenteddocumentedSekoia.io, Replay: documenteddocumented
Synthetic eventsPanther, Synthetic events: not documentednot documentedSekoia.io, Synthetic events: not documentednot documented
Backtest reportsPanther, Backtest reports: partialpartialSekoia.io, Backtest reports: partialpartial
Test coveragePanther, Test coverage: not documentednot documentedSekoia.io, Test coverage: not documentednot documented
Coverage analytics
ATT&CK mapPanther, ATT&CK map: documenteddocumentedSekoia.io, ATT&CK map: documenteddocumented
Panther documents moreGap viewPanther, Gap view: documenteddocumentedSekoia.io, Gap view: partialpartial
Data sourcesPanther, Data sources: partialpartialSekoia.io, Data sources: partialpartial
Log source healthPanther, Log source health: partialpartialSekoia.io, Log source health: partialpartial
Rule health
Sekoia.io documents moreNoisy rulesPanther, Noisy rules: not documentednot documentedSekoia.io, Noisy rules: partialpartial
Panther documents moreBroken rulesPanther, Broken rules: documenteddocumentedSekoia.io, Broken rules: partialpartial
Panther documents moreField driftPanther, Field drift: partialpartialSekoia.io, Field drift: not documentednot documented
Rule costPanther, Rule cost: partialpartialSekoia.io, Rule cost: partialpartial
Sekoia.io documents moreLifecyclePanther, Lifecycle: not documentednot documentedSekoia.io, Lifecycle: documenteddocumented
Library
Sekoia.io documents moreLibrary countPanther, Library count: partialpartialSekoia.io, Library count: documenteddocumented
Panther documents moreCommunityPanther, Community: documenteddocumentedSekoia.io, Community: not documentednot documented
CadencePanther, Cadence: partialpartialSekoia.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
a team starting from scratch with SigmaBoth document a route: Panther converts Sigma with sigma-cli into Python or Simple detections and tests them in CI, and Sekoia runs native Sigma YAML, correlation rules included, but documents no CI workflow, so the difference above decides.
Microsoft Sentinel estateNeither Panther nor Sekoia documents a path for this buyer, so it does not separate them.
Elastic estateNeither Panther nor Sekoia documents a path for this buyer, so it does not separate them.

When to pick each

Panther: Pick Panther when testing is the deciding need: it runs per-detection unit tests with panther_analysis_tool test and previews a rule on stored logs with Data Replay (Beta). It also leads on CI and deployment.

Sekoia.io: Pick Sekoia when versioning and lifecycle is the deciding need: it documents rule states Active, Scheduled for Deprecation and Deprecated with a valid-until date. It also leads on library size.

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