Detection as Code

Hunters vs Panther

Hunters totals 3.44 and Panther totals 6.31 on the 10 point detection-as-code rubric (sources read 2026-11-03 and 2026-11-04). Panther leads by 2.87 points. The pair turns on rule languages: Panther documents it in full, and Hunters publishes nothing on it. 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.0 for Hunters, which is 1.08 of the 10 point total.

For rule languages, Panther writes detections in Python and converts Sigma rules with sigma-cli, whereas Hunters names no rule language and normalises data to OCSF. docs.panther.com read 2026-11-03 hunters.security read 2026-11-04

Rubric side by side

Hunters totals 3.44 and Panther totals 6.31 out of 10.

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

MarkerCriterionWeightHuntersPanther
+Rule languages and conversion paths153.08.0
+Git-native workflow and CI/CD183.09.0
+Testing154.08.0
+Coverage analytics124.05.0
Rule health183.53.5
+Versioning and rollback83.06.0
+Content library size and freshness84.05.0
Pricing transparency63.03.0
Total1003.446.31

The 33 capabilities as a diff

Read it as a diff from Hunters to Panther: 17 of 33 rows differ. A plus marks a row where Panther documents more (15 rows), a minus a row where Hunters documents more (2 rows). Rows with no marker match.

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

MarkerCapabilityHuntersPanther
Languages
Sigma nativeHunters, Sigma native: not documentednot documentedPanther, Sigma native: not documentednot documented
Panther documents moreSigma conversionHunters, Sigma conversion: not documentednot documentedPanther, Sigma conversion: documenteddocumented
YARA-LHunters, YARA-L: not documentednot documentedPanther, YARA-L: not documentednot documented
SPLHunters, SPL: not documentednot documentedPanther, SPL: not documentednot documented
KQLHunters, KQL: not documentednot documentedPanther, KQL: not documentednot documented
EQL or ES|QLHunters, EQL or ES|QL: not documentednot documentedPanther, EQL or ES|QL: not documentednot documented
Panther documents morePythonHunters, Python: not documentednot documentedPanther, Python: documenteddocumented
Panther documents moreVisual builderHunters, Visual builder: partialpartialPanther, Visual builder: documenteddocumented
YARAHunters, YARA: not documentednot documentedPanther, YARA: not documentednot documented
Panther documents moreLucene or KQL-likeHunters, Lucene or KQL-like: not documentednot documentedPanther, Lucene or KQL-like: partialpartial
Source control and CI
Panther documents moreGit syncHunters, Git sync: not documentednot documentedPanther, Git sync: documenteddocumented
Panther documents morePR deployHunters, PR deploy: not documentednot documentedPanther, PR deploy: documenteddocumented
Panther documents moreCLIHunters, CLI: not documentednot documentedPanther, CLI: documenteddocumented
Panther documents moreRule APIHunters, Rule API: not documentednot documentedPanther, Rule API: documenteddocumented
Panther documents moreCI examplesHunters, CI examples: not documentednot documentedPanther, CI examples: documenteddocumented
Env promotionHunters, Env promotion: not documentednot documentedPanther, Env promotion: not documentednot documented
Testing
Panther documents moreUnit testsHunters, Unit tests: not documentednot documentedPanther, Unit tests: documenteddocumented
ReplayHunters, Replay: documenteddocumentedPanther, Replay: documenteddocumented
Synthetic eventsHunters, Synthetic events: not documentednot documentedPanther, Synthetic events: not documentednot documented
Panther documents moreBacktest reportsHunters, Backtest reports: not documentednot documentedPanther, Backtest reports: partialpartial
Test coverageHunters, Test coverage: not documentednot documentedPanther, Test coverage: not documentednot documented
Coverage analytics
ATT&CK mapHunters, ATT&CK map: documenteddocumentedPanther, ATT&CK map: documenteddocumented
Gap viewHunters, Gap view: documenteddocumentedPanther, Gap view: documenteddocumented
Data sourcesHunters, Data sources: partialpartialPanther, Data sources: partialpartial
Log source healthHunters, Log source health: partialpartialPanther, Log source health: partialpartial
Rule health
Hunters documents moreNoisy rulesHunters, Noisy rules: partialpartialPanther, Noisy rules: not documentednot documented
Panther documents moreBroken rulesHunters, Broken rules: not documentednot documentedPanther, Broken rules: documenteddocumented
Panther documents moreField driftHunters, Field drift: not documentednot documentedPanther, Field drift: partialpartial
Panther documents moreRule costHunters, Rule cost: not documentednot documentedPanther, Rule cost: partialpartial
Hunters documents moreLifecycleHunters, Lifecycle: partialpartialPanther, Lifecycle: not documentednot documented
Library
Library countHunters, Library count: partialpartialPanther, Library count: partialpartial
Panther documents moreCommunityHunters, Community: not documentednot documentedPanther, Community: documenteddocumented
CadenceHunters, Cadence: partialpartialPanther, 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 SigmaPanther is the better fit: it converts Sigma with sigma-cli into Python or Simple detections and tests them in CI; Hunters documents no Sigma path.
Microsoft Sentinel estateNeither Hunters nor Panther documents a path for this buyer, so it does not separate them.
Elastic estateNeither Hunters nor Panther documents a path for this buyer, so it does not separate them.

When to pick each

Hunters: Pick Hunters when coverage analytics matters more to you than testing, where Panther documents more: it draws a Threat Coverage map on ATT&CK v14 with uncovered techniques in gray.

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.

Profiles: Hunters, Panther. Alternatives: to Hunters, to Panther.