TotalHealDatasheet · 27 October 2026

TotalHealResponseFlow

SOAR & Automation

Automate response with playbooks — and keep a person in the loop.

  • Cloud (SaaS)
  • On-premises
  • Air-gapped
ResponseFlow SOAR icon

The challenge

Alerts from many tools arrive faster than a team can open tickets, enrich them and act, and automation that acts on its own is a risk of its own.

The answer

ResponseFlow takes alerts from its own signed webhook or from other TotalHeal products and runs playbooks on them. Every action goes through your response policy and its approvals, and every step is on a tamper-evident audit chain.

Status
Available
Deploys as
Cloud (SaaS) · On-premises · Air-gapped
Runs on
Priced per
Analyst per year
Trial
30 days
Licence
Sold on its own; one TotalHeal console

Supported platforms

  • Any HTTPS senderHMAC-signed
  • Jira
  • ServiceNow
  • Slack
  • Microsoft Teams

How it works

  1. ReceiveA signed alert arrives; replays and old timestamps are refused.
  2. MatchA playbook matches on severity, type and your parameters.
  3. ApproveHigh-impact actions wait for a person.
  4. ActOpen a ticket, post to chat, isolate or notify.
  5. RecordRequest, approval and result on the audit chain.

Reference architecture

ResponseFlow SOAR reference architecture: Alerts arrive signed; playbooks act only through the response policy; outbound calls are signed and go only to public HTTPS addresses.
Alerts arrive signed; playbooks act only through the response policy; outbound calls are signed and go only to public HTTPS addresses.

Key capabilities

  • Its own alert sourceA signed inbound webhook per sending tool (JSON or CEF), each with its own secret; replays and old timestamps are refused. No SIEM or XDR licence is needed.
  • Template playbooksReady playbooks for third-party alerts, ransomware, credential theft, crypto-mining, SSH compromise and exposures. On Business you set their parameters — severities, risk threshold, messages, case titles and the webhook they call.
  • Custom playbooks (Enterprise)Build your own playbooks with conditions, versions and rollback.
  • A person approvesActions follow the response policy: recommend, approve or automatic; high-impact actions such as webhooks and isolation always wait for approval.
  • Signed outbound webhooksCalls to your ticketing or chat tool are signed and leave only to public HTTPS addresses. Business includes one endpoint; Enterprise up to 50.
  • Audit you can verifyEvery request, approval and result is on a hash-chained audit log that can be exported and verified.

Deployment options

Cloud (SaaS)AvailableSingle-region service.
On-premisesAvailableDelivered with our team from the on-premises kit.
Air-gappedAvailableOffline kit, offline licence file and offline update bundles.

System requirements

Protected platforms

  • Any HTTPS senderHMAC-signed

Works with

  • Jira
  • ServiceNow
  • Slack
  • Microsoft Teams

On-premises server

Operating system
RHEL, Rocky Linux or AlmaLinux 8 / 9; Ubuntu 20.04, 22.04 or 24.04; Debian 11 / 12
Processor
4 vCPU (tested configuration)
Memory
8 GB recommended (6 GB minimum)
Disk
10 GB free for software, releases and backups, plus data
Sign-in
Active Directory / LDAP, SAML 2.0 or OpenID Connect
Software
Nothing to pre-install: no container runtime, database, web server or Java

Network and access

  • An alert source: a tool that can send signed HTTPS requests, or other TotalHeal products

Alerts and tickets to

  • Splunk
  • Microsoft Sentinel
  • Elastic
  • Syslog / CEF
  • Jira
  • ServiceNow
  • Slack
  • Microsoft Teams

Technical specifications

FeaturesIncluded
Its own alert sourceIncluded
Template playbooksIncluded
Custom playbooks (Enterprise)Included
A person approvesIncluded
Signed outbound webhooksIncluded
Audit you can verifyIncluded
Availability by editionBusinessEnterprise
Inbound alert webhooks, template playbooks with parameters, approvals, auditIncludedIncluded
Outbound webhook endpoints1Up to 50
Custom playbooks, builder, versions and rollback—Included
Platforms and coverage
SendersAny tool that can send an HTTPS POST with an HMAC signature
ConsoleTotalHeal web console
Deployment options
SaaS (India region)AvailableSingle-region service.
On-premises control planeAvailableDelivered with our team from the on-premises kit.
Air-gappedAvailableOffline kit, offline licence file and offline update bundles.
Licensing
Priced perAnalyst per year
CountedPeople who run or approve playbooks
Trial30 days
Government profileGovernment is a profile, not a separate tier or price list: the Elite tier with Government defaults switched on — data residency in India, four-eyes approval of policy changes, a distinct approver for every approval-level action, retention of at least 180 days, and the CERT-In and DPDP reporting clocks.
Procurement dossierCompliance matrix, bill of materials, architecture and hardening, SLA and OEM authorisation letter, on request
On-premises server
Operating systemRHEL, Rocky Linux or AlmaLinux 8 / 9; Ubuntu 20.04, 22.04 or 24.04; Debian 11 / 12
Processor4 vCPU (tested configuration)
Memory8 GB recommended (6 GB minimum)
Disk10 GB free for software, releases and backups, plus data
Sign-inActive Directory / LDAP, SAML 2.0 or OpenID Connect
SoftwareNothing to pre-install: no container runtime, database, web server or Java
Requirements
Requirement 1An alert source: a tool that can send signed HTTPS requests, or other TotalHeal products
Get started30 days trial in the TotalHeal console. Quotes and the procurement dossier (compliance matrix, bill of materials, architecture and hardening, SLA, OEM authorisation letter): business@totalhealsecurity.com
Freaquer Corporation Pvt Ltdtotalhealsecurity.com/products/soar · whitepaper: totalhealsecurity.com/datasheets/totalheal-soar-whitepaper.pdf?v=8475d65569

No third-party certification is claimed. Figures are from our own tests where stated, with their dates. Specifications can change; this datasheet is dated 27 October 2026.