Why Soarcery

Legacy SOAR automated the clicking. We automate the thinking.

SOAR was supposed to give analysts their time back. Instead it traded triage work for playbook maintenance. Soarcery is what the category looks like when you ask a Familiar in plain English and three Watcher orders, not flowcharts, do the work.

Side by side

The same job, done two ways.

Legacy playbook SOAR
Soarcery
Build
Drag flowcharts, write glue code, wire every branch by hand before anything runs.
Ask the Familiar in plain English. The Watchers wire it to your tools and ask about anything ambiguous.
Maintain
An API changes, a playbook breaks, a person fixes it. The backlog is the product.
The Watchers adapt to tool changes instead of breaking on them. No YAML to babysit.
Investigate
Enrich, look up, route. The analyst still does the actual thinking on every escalation.
The Attack order investigates at analyst depth: read the omens, weigh evidence, reason to a conclusion you can read.
Verdicts
One score from one feed, collapsed to a number that hides the disagreement.
The full multi-engine verdict spread, kept inside the inquiry, with the confidence of the call made explicit.
Respond
All-or-nothing automation. Most teams turn the risky half off and click manually.
The Defend order casts Spells on an autonomy dial: full speed where you trust it, a Seal where you do not.
Defend it
Execution logs that show what fired, not why.
The Scholar order keeps a replayable Scroll: evidence, reasoning, and the seal behind every action.
The shape of it

One console. Three orders. A seal on every move.

The Familiar

Ask, do not click

One plain-English console. The analyst asks; the Familiar queries the lake, narrates the inquiry, and proposes the response, never disposes of it.

The Watchers

Three orders that do the work

Attack detects, Defend responds, Scholar records. A concrete division of labor mapped to MITRE ATT&CK and D3FEND, not a vague swarm.

The Seals

Propose and dispose

A Watcher proposes; a human disposes. Every destructive action waits for a seal, with the evidence attached. The AI is never above the law.

Detect
Attack Watchers

Read the omens, correlate the signals, and name what is happening. They open and build the inquiry.

Owns
Omens
MITRE
ATT&CK
Respond
Defend Watchers

Cast response spells to contain, evict, and restore, under gated authority. Destructive casts pause at a seal.

Owns
Spells
MITRE
D3FEND
Record
Scholar Watchers

Document the inquiry, collect the seals, and keep your ticketing in sync: Jira, ServiceNow, Resilient.

Owns
Scrolls
Record
& sync
Attack detects Defend responds Scholar records every step
The honest part

What we will not claim

We are an early company and we market like one. No invented customer counts, no logos we have not earned, no certifications in progress presented as done. What you see on this site is what the product does today, labelled as illustrative where it is illustrative.

  • Our security posture, stated plainly on the trust page.
  • Real product screenshots are labelled, and run on demo data.
  • If a capability is on the roadmap, we say roadmap.
app.soarcery.ai/approvals
The Soarcery Seals queue: high-blast-radius actions waiting on an explicit human seal

Actual product. Demo data.

See the difference

Bring an alert. Watch it think.

A 30-minute walkthrough on your real triage flow. No slideware.