Mate SecurityvTorq
Mate Security 6.22Torq 6.77
Mate Security v Torq: the totals are 0.55 apart, outside the 0.25 band. Torq leads on the total; the rows below say why. Rows won: Mate Security 2, Torq 6, level 1.
The difference that decides Mate Security v Torq
On case management, Torq has a Manage module that creates, assigns and manages cases from one record (vendor claim, score 8.0), while Mate has no case management product, only an investigations dashboard and ticket context (vendor claim, score 5.0). torq.io, read 2026-11-03
Rows with the widest weighted gap: Case management and collaboration (Torq ahead by 3.0), Pricing model and transparency (Mate Security ahead by 3.0), Ownership stability (Torq ahead by 1.5).
Mate Security v Torq: the nine rows side by side
Playbook authoring model
weight 14 of 100Mate Security
7.0
Not a playbook builder. Documented answer: a Gamebook describes investigative intent, required evidence, permitted actions and escalation points in plain language; Mate says it tests the description against past cases and runs it in shadow mode before sign-off. Tool contact sits in separate Flows that Mate maintains.
mate.security, read 2026-11-03 (vendor claim); mate.security, read 2026-11-03 (vendor claim)
Torq
8.0Ahead
Low-code and full-code workflow builder; natural-language workflow creation and agentic runbooks for hunting.
torq.io, read 2026-11-03 (vendor claim) (search summary only)
Integration count and depth documented
weight 14 of 100Mate Security
5.0
Platform page lists ten integration categories (Slack, ticketing, Microsoft identity and mail, cloud risk, email security, threat intel, EDR, Google, identity context) and names Defender and AWS IAM actions. No count.
mate.security, read 2026-11-03 (vendor claim)
Torq
5.0
The torq.io home page read states no count. A third party reading Torq pages reports 300 integrations and 4,000+ pre-built steps; confirm on Torq's own page before publishing.
torq.io, read 2026-11-03
Case management and collaboration
weight 8 of 100Mate Security
5.0
No case management product. Documents an investigations dashboard with priority, status and analyst notes and a ticket-context integration.
mate.security, read 2026-11-03 (vendor claim)
Torq
8.0Ahead
A 'Manage' module creates, assigns and manages cases from one record, per the vendor page.
torq.io, read 2026-11-03 (vendor claim)
Approvals and human-in-the-loop controls
weight 12 of 100Mate Security
8.5Ahead
Three autonomy modes on the platform page: Recommend only, Supervised (risky changes still ask) and Auto-run under guardrails and audit; Gamebooks define when the agent must escalate, stop or ask for approval.
mate.security, read 2026-11-03 (vendor claim); mate.security, read 2026-11-03 (vendor claim)
Torq
8.0
Vendor page: response can run completely autonomously or with human-on-the-loop oversight, with a manual override and transparent audit logs. Per-action gating detail not read.
torq.io, read 2026-11-03 (vendor claim)
Agentic or AI features that are documented
weight 12 of 100Mate Security
8.0
Agents on a Security Context Graph for triage, investigation, response and hunting. Mate's own figures (98.7 percent accuracy on 7,200 alerts, 97 percent false-positive auto-closure) are unaudited vendor claims; the page does not give who measured. Agents do not hold open access to systems; Flows make the tool calls.
mate.security, read 2026-11-03 (vendor claim); siliconangle.com, read 2026-11-03 (vendor claim)
Torq
8.5Ahead
Agents for triage, investigation, response, hunting and reporting on a continuously updated context model that records verdicts, exceptions and overrides. Limits of the agents are not stated. 'Over 90 percent of cases closed autonomously' is a vendor claim reported by third parties; not on the page read.
torq.io, read 2026-11-03 (vendor claim)
Hosting and data residency options
weight 8 of 100Mate Security
3.5
Platform page and home page do not state deployment model or data residency; a Trust Center and compliance badges are shown.
mate.security, read 2026-11-03
Torq
5.0Ahead
Described as cloud-native with SOC 2, HIPAA and ISO certifications per third-party reading; no regions or self-hosted option read.
torq.io, read 2026-11-03
Pricing model and transparency
weight 8 of 100Mate Security
6.0Ahead
A USD 150,000 per 12 months Enterprise tier list price appears on AWS Marketplace with private offers by email; mate.security itself publishes no price.
aws.amazon.com, read 2026-11-03
Torq
3.0
No price on the home page; its pricing URL returned 404. Review sites report demo-only pricing and no free trial.
torq.io, read 2026-11-03
Migration tooling and import or export formats
weight 14 of 100Mate Security
5.0
Mate says it translates SOAR playbooks into Gamebooks and its blog cites one unnamed customer's 711 playbooks becoming 10 Gamebooks (vendor claim). The pages name no source platform and no format, and no export of Gamebooks is documented, so the claim sits at the floor of the partial band and the matrix scores it as no documented path.
mate.security, read 2026-11-03 (vendor claim); mate.security, read 2026-11-03 (vendor claim)
Torq
6.0Ahead
Workflows export and import as YAML including custom steps, nested workflows and tags. No converter from XSOAR or Splunk SOAR found; a 'Kill Your SOAR' guide is behind a form.
kb.torq.io, read 2026-11-03
Ownership stability
weight 10 of 100Mate Security
7.0
Independent; SiliconANGLE reports a USD 35M Series A led by Canaan in July 2026 and more than USD 50M raised in total. Founded recently; Gamebooks reached general availability on 2026-08-26.
siliconangle.com, read 2026-11-03
Torq
8.5Ahead
Independent. USD 140M Series D at USD 1.2B valuation announced 2026-01-12; USD 332M raised in total per press.
businesswire.com, read 2026-11-03
The verdict for Mate Security v Torq, by buyer type
- Microsoft shop
- Mate fits better, because it names Microsoft Defender and Microsoft identity and mail among its integration categories (vendor claim); Torq documents nothing for this buyer type on the pages read.
- agent-first
- No separation on the evidence read: Mate documents three autonomy modes and Gamebooks that set when agents must escalate, stop or ask for approval (vendor claim), and Torq runs agents for triage, investigation, response and hunting on a context model that records overrides (vendor claim).
- leaving a legacy SOAR
- Torq fits better, because it documents a YAML workflow export and import and advises redesign over lift and shift; Mate claims it translates SOAR playbooks into Gamebooks, naming no source or format (vendor claim).
When to pick each
Pick Mate Security when
Pick Mate when you are leaving a legacy SOAR and will ask it in writing which source formats it reads: it claims it translates SOAR playbooks into Gamebooks and names no source or format (vendor claim).
Pick Torq when
Pick Torq when you are agent-first and you want a tool that runs agents for triage, investigation, response and hunting on a context model that records overrides (vendor claim), though Mate matches it on that point.
Moving playbooks between Mate Security and Torq
The portability matrix records seven playbook types for each direction it covers. Verdicts are documentation findings, not test results. How the matrix is built.
| Playbook type | Verdict | Reason |
|---|---|---|
| Enrichment lookups | rebuild from scratch | Mate says it translates SOAR playbooks into Gamebooks of investigative intent but its page names no source platform or format, so no documented path on 2026-11-03 (vendor claim, unverified). mate.security, read 2026-11-03 (vendor claim) |
| Phishing triage | rebuild from scratch | Mate says it translates SOAR playbooks into Gamebooks of investigative intent but its page names no source platform or format, so no documented path on 2026-11-03 (vendor claim, unverified). mate.security, read 2026-11-03 (vendor claim) |
| Endpoint containment | rebuild from scratch | Mate says it translates SOAR playbooks into Gamebooks of investigative intent but its page names no source platform or format, so no documented path on 2026-11-03 (vendor claim, unverified). mate.security, read 2026-11-03 (vendor claim) |
| Identity actions | rebuild from scratch | Mate says it translates SOAR playbooks into Gamebooks of investigative intent but its page names no source platform or format, so no documented path on 2026-11-03 (vendor claim, unverified). mate.security, read 2026-11-03 (vendor claim) |
| Ticketing and case sync | rebuild from scratch | Mate describes Gamebooks as investigation procedures and no page covers case sync, so no documented path on 2026-11-03. mate.security, read 2026-11-03 |
| Custom scripted logic | rebuild from scratch | Mate says "your custom logic stays" after translation but names no source platform, format or mechanism, so no documented path on 2026-11-03 (vendor claim, unverified). mate.security, read 2026-11-03 (vendor claim) |
| Scheduled or batch jobs | rebuild from scratch | Mate describes Gamebooks as investigation procedures and no page covers scheduled or batch jobs, so no documented path on 2026-11-03. mate.security, read 2026-11-03 |
Profiles
Mate Security. Torq. Alternatives: instead of Mate Security, instead of Torq.