PAGES
← all tools
◆ SOAR

Torq

changelog-20261018-b338ff6e commercial

Summary

Torq is a commercial SOARSOARSecurity orchestration, automation and response, coordinating incident workflows across tools. Playbooks can gather evidence, assign work or carry out approved response actions. platform that combines agentic SecOpsSecOpsThe practice of merging security and IT operations teams so that threat detection, response, and infrastructure management share the same workflows, giving cyber tools a single pipeline from alert to remediation. and Hyperautomation to triage, investigate, and respond to threats. It is available as a demonstration offering. It functions as a workflow orchestration solution aimed at SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts, and its documentation positions it alongside other security-automation cyber tools. The platform was launched in 2020.

How Torq helps

Which alerts in the queue actually need an analyst's attention right now?

triages incoming alerts against configured logic and workflows, surfacing the ones that meet escalation criteria while routing the rest to automated handling

Which of today's incidents match a pattern that has already been handled before?

runs the same orchestrated workflow used on prior cases and applies it automatically when the new alert fits the pattern

How far did an automated response get before it needed a human decision?

tracks each workflow run step by step and shows where it is currently paused waiting for analyst input

Which systems were touched during the investigation of a given threat?

records every action a workflow took across connected tools during triage and response, giving a step-by-step account tied to that incident

Is the SOC keeping up with the volume of alerts coming in?

shows how much of the queue is being triaged and resolved through automation versus what is still pending manual review

all 4 features, with the evidence for each →

Languages

Not documented

Features

4 capabilities

Built from Torq's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date.

Compare with peers →

  • Torq covers 2 of the 8 investigation and response capabilities we track.
All capabilities 4 capabilities
Cases Dashboard numeric filtering shipped Cases Dashboard widgets can be filtered by numeric thresholds — less than, more than, or a range — to focus displays on cases meeting a specific event count or value. 2 releases · 1 other source · first seen Oct 2026

Shared capability: Incident case management

release

  • Adds Actor Type grouping and filtering to Cases Dashboard widgets, letting teams break down case actions by analyst, workflow, Socrates, Agents, or Auto Triage. changelog · Oct 2026 · source · release history
  • Cases Dashboard widgets can now filter by numeric values — Less Than, More Than, and Range — to focus any widget on cases meeting a specific threshold or event count. changelog · Oct 2026 · source · release history

example

  • Focus a Cases Dashboard widget on high-volume incidents by filtering to only cases above a specific event count. In the Cases Dashboard, open a widget's filter settings, select 'More Than', and enter your event-count threshold to scope the widget to high-volume cases only. changelog · Oct 2026 · source
Context Graph shipped A visual map of identities, assets, and relationships that lets analysts start from any entity, expand connections step by step, and filter for critical, privileged, or weak-posture entities to understand blast radius. 1 release · 1 other source · first seen Oct 2026

release

  • Adds Context Graph — a visual map of identities, assets, and relationships — letting analysts start from any entity, expand connections step by step, and filter for critical, privileged, or weak-posture entities to scope blast radius; Auto Triage also injects graph context directly into… changelog · Oct 2026 · source · release history

example

  • Scope an active incident by visualising which privileged identities and assets are connected to a suspicious entity before escalating. In the Torq console, navigate to Context Graph, search for the entity under investigation, expand its direct connections, then apply the 'Privileged' filter to isolate high-risk nodes and assess… changelog · Oct 2026 · source
Socrates Builder for Auto Triage shipped Lets analysts create Auto Triage Guidance and Rules by attaching an existing playbook or describing needs in plain English, with AI-drafted entries reviewable before enabling. 1 release · 1 other source · first seen Oct 2026

Shared capability: Response playbook automation

release

  • Adds Socrates Builder for Auto Triage, enabling analysts to create Guidance and Rules by attaching a playbook/procedure or describing needs in plain English, with AI-drafted entries reviewable before enabling. changelog · Oct 2026 · source · release history

example

  • Rapidly draft Auto Triage rules from an existing runbook without writing rule syntax by hand. In the Torq console, open Auto Triage > Socrates Builder, attach your playbook or type a plain-English description of the triage logic, review the drafted Guidance and Rules entries, then enable the… changelog · Oct 2026 · source
Dashboard widget separators shipped Dashboards support separator elements that let users group related widgets under titled sections for clearer layout and reporting. 1 release · first seen Oct 2026

release

  • Adds separator support to dashboards, letting you group related widgets under titled sections for cleaner reports.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ changelog · Oct 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for Torq, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Torq puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Website history

torq.io, every change

Torq's 31 pages as they looked each month from October 2026 to October 2026: 31 renders, 0 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

23 entries

  1. October 20261
  2. September 20263
  3. August 20265
  4. July 20263
  5. June 20263
  6. May 20263
  7. April 20261
  8. March 20261
  9. June 20251
  10. May 20251
  11. March 20251

    23 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →