Signal — CyberCLI notification channel

End-to-end encrypted, self-hosted via signal-cli. Nothing but the message leaves.

Where to get it

A self-hosted signal-cli / signal-cli-rest-api instance with a registered number.

Install / what you need

Run signal-cli (or the REST wrapper) on your box and register a sender number.

How to connect

1 Stand up signal-cli-rest-api and register your sender number.
2 Dashboard → Notifications → Add destination → signal, point it at your signal-cli endpoint + recipient.
3 Send test.

When you'd use it

Privacy-first alerting.

Regulated environments that require E2E.

Sovereign, self-hosted delivery.

What Herald sends through this channel

4 setup fields

Herald hands every alert to the SignalAdapter as a DispatchPlan. The fields below are what the dashboard form asks for; the sample is the plan the adapter receives. The adapter renders it into the channel-native shape (Discord embeds, Teams MessageCards, PagerDuty Events-API payloads, TwiML, JSON POST bodies) on the way out — that wire transcript varies per channel.

Setup form fields

field	type	required	description / default
server_url	string	required	Self-hosted signal-cli-rest-api base URL (e.g. http://signal:8080)
number	string	required	Registered sender number in E.164 (e.g. +15551234567)
recipient	string	required	Recipient number (E.164) or a group id to deliver alerts to
timeout_seconds	number	optional	no description · default: 15

Sample DispatchPlan (input to the adapter)

{
  "decision_id": "tdc-2026-06-20-abc12",
  "channel": "<channel-type>",
  "recipient": {
    "recipient_id": "soc-oncall",
    "display_name": "SOC on-call",
    "addresses": [
      {
        "channel": "<channel-type>",
        "address": "<destination>",
        "min_defcon": 5
      }
    ]
  },
  "urgency": "high",
  "retry_policy": {
    "max_attempts": 3,
    "initial_backoff_seconds": 5
  },
  "subject": "Suspicious login on CEO-LAPTOP",
  "body": "Warden flagged a PowerShell child of WINWORD.EXE. The encoded command resolved to a base64-wrapped Invoke-WebRequest to a newly-registered domain. Trust ladder: L3.",
  "approval_link": "https://app.cybercli.local/approve/abc12",
  "incident_ref": "case-2026-0142",
  "signal_id": "sig-2026-06-20-9f3"
}

Sovereignty: byo_external · Min tier (BYO): free · End-to-end-encrypted Signal via self-hosted signal-cli-rest-api (Free+).

Sovereignty

You run the signal-cli bridge — delivery is E2E encrypted and never touches a CyberCLI relay.

Who notifies through it

Herald — the Guild's voice role — routes alerts, daily digests, and AI verdicts here, on a per-CYCON-state matrix you control. CYCON 1/2 alerts repeat until an operator acks.

The Guild →

Other Chat channels

Go deeper