Hunters
Hunters scores 3.44 of 10, twelfth of the 12 profiled, in band E with Sekoia.io. It sells vendor-maintained detections for small teams, so it is kept to show buying content next to writing it. Its docs add a custom detector with a Test logic step and an ATT&CK Threat Coverage map.
- Rubric total
- 3.44 of 10, fourteenth of 14 scored, twelfth of 12 profiled
- Matrix score
- 6.5 of 33 (3 documented, 7 partial, 23 not documented)
- Rule health
- 0 documented, 2 partial of 5 matrix rule-health columns
- Ownership
- Independent company. No acquisition, merger or rebrand found on the vendor's site or in one 2026 news search. The read was of the homepage, platform, blog and news pages. Aggregators list the company as independent with its last large round in 2022. hunters.security read 2026-11-03
- Website
- hunters.security
What Hunters is
Hunters sells the Hunters SOC Platform, a SIEM aimed at small security teams. Data is standardised to OCSF in a security data lake that the customer owns or Hunters manages, and detections are built in and maintained by Hunters' Team Axon service group (vendor claims, hunters.security, read 2026-11-03). The model is buy the content, not write it.
The docs add a guided custom detector with Filter and Group By modes and a Test logic step, and a detectors page listing leads, alerts and clusters per detector. The platform page names no rule language and describes no repo sync or CI. The matrix keeps Hunters so a reader can see the buy-the-content model next to the write-it model.
Vendor description: Hunters sells the Hunters SOC Platform, a SIEM built for small security teams. It ingests data into a security data lake that the customer owns or Hunters manages, standardises it to OCSF, and runs vendor-maintained detections from its Team Axon service group. The platform adds AI triage, investigation and response. hunters.security read 2026-11-03 vendor claim
How Hunters scores on the rubric
3.44 of 10 across eight weighted criteria. It sits in band E with Sekoia.io: totals within 0.25 are a band, not a ladder. Each score has its reason and the page it was read from. The rubric explains the bands.
Hunters on the eight rubric criteria. Part = weight times score over 100; the parts sum to the total.
| Criterion | Weight | Score | Status | Reason and source |
|---|---|---|---|---|
| Rule languages and conversion paths | 15 | 3.0 | not documented | Data is normalised to OCSF; the platform page names no rule language. hunters.security read 2026-11-04 |
| Git-native workflow and CI/CD | 18 | 3.0 | not documented | Page says customers are not required to build detections themselves; no repo sync or CI. vendor claim hunters.security read 2026-11-04 |
| Testing | 15 | 4.0 | not documented | Detections are 'continuously tested and refined by Team Axon' (vendor claim); customers get no documented test tooling. vendor claim hunters.security read 2026-11-04 |
| Coverage analytics | 12 | 4.0 | not documented | No ATT&CK coverage view on the page read. hunters.security read 2026-11-04 |
| Rule health | 18 | 3.5 | not documented | Claims a 90 percent cut in excessive alerting (vendor claim, no method); no rule-level health view. vendor claim hunters.security read 2026-11-04 |
| Versioning and rollback | 8 | 3.0 | not documented | Not documented. hunters.security read 2026-11-04 |
| Content library size and freshness | 8 | 4.0 | not documented | Built-in detections maintained by Team Axon; no count. vendor claim hunters.security read 2026-11-04 |
| Pricing transparency | 6 | 3.0 | not documented | hunters.security/pricing returned 404. hunters.security read 2026-11-04 |
| Total, of 10 | 100 | 3.44 | Sum of the eight parts: 0.45 + 0.54 + 0.60 + 0.48 + 0.63 + 0.24 + 0.32 + 0.18 | |
The 33 capabilities for Hunters
documentedpartialnot documented
Where Hunters is strong
- Test logic lets you choose a timeframe and view samples of the events a custom detector would turn into leads, a replay step for customer-written detectors. docs.hunters.ai read 2026-11-03
- The Threat Coverage map is built on ATT&CK v14 and counts detectors per technique. docs.hunters.ai read 2026-11-03
- The detectors page shows the number of leads, alerts and clusters each detector created, a per-detector view that comes close to a noise measure. docs.hunters.ai read 2026-11-03
Where Hunters is behind
- The platform page names no rule language and says customers are not required to build detections themselves. No repo sync or CI is described. hunters.security read 2026-11-04
- There is no rule-level health view beyond per-detector counts. The page claims a 90 percent cut in excessive alerting, a vendor claim with no method. hunters.security read 2026-11-04
- No pricing page was found on hunters.security on 2026-11-03 (the /pricing path returned 404), so no price or unit was read. hunters.security read 2026-11-04
What only Hunters publishes
Hunters standardises security data to OCSF and lets a customer bring its own data lake or have Hunters manage one (vendor claim). hunters.security read 2026-11-03
Pricing as published for Hunters
No public pricing. No pricing page was found on hunters.security on 2026-11-03, so the price model is not published. hunters.security read 2026-11-03
Named customers of Hunters
Names below are as the source page lists them.
Customers named on public pages. Every name is a vendor claim from the page cited in its row.
| Customer | Source |
|---|---|
| TheRealReal | hunters.security read 2026-11-03 |
| ChargePoint | hunters.security read 2026-11-03 |
| Skyscanner | hunters.security read 2026-11-03 |
| Booking (from logo alt text) | hunters.security read 2026-11-03 |
| Cimpress (named by a quoted reviewer) | hunters.security read 2026-11-03 |
| Unzer (named by a quoted reviewer) | hunters.security read 2026-11-03 |
| Pennymac (named by a quoted reviewer) | hunters.security read 2026-11-03 |
Recent releases and news for Hunters
No dated releases were recorded for Hunters in the read.
Claims Hunters makes about itself
Each figure is the vendor's. The evidence grade is defined on the rubric page: A measured by a third party with the method published, B vendor-measured with sample and method, C vendor figure with no method, D figure with no source.
Vendor claims with the evidence grade and who measured.
| Claim | Grade | Measured by | Source |
|---|---|---|---|
| Reduces alert triage by 80 percent vendor claim | C | vendor | hunters.security read 2026-11-03 |
| Reduces excessive alerting by 90 percent vendor claim | C | vendor | hunters.security read 2026-11-03 |
| Gartner Peer Insights overall rating of 4.8 out of 5.0 vendor claim | B | third_party | hunters.security read 2026-11-03 |
Shortlist Hunters when
- You have a small team and want detections maintained for you, not written by you.
- You want an ATT&CK coverage map and can live with a vendor-owned detection library.
- You prefer a customer-owned data lake in OCSF and will confirm rule export and price in a sales call.
Verdict on Hunters
Twelfth of 12 at 3.44, in band E with Sekoia.io (3.46); the buy-the-content model scores low on a rubric built for teams that write rules.
Compare Hunters
Alternatives to Hunters. Head-to-head diffs: SOC Prime, Anvilogic, Panther, Sigma and pySigma, Detecteam, Elastic Security, Splunk Enterprise Security (Cisco), Sekoia.io, Google Security Operations, Microsoft Sentinel, Mate Security.