Architecture

Nothing to attack.
Nothing to lose.

Threatmatic runs on the same real-time infrastructure powering the world's largest systems — with an attack surface small enough that most of what you're used to worrying about simply doesn't apply here.

0
open inbound ports, ever
1
persistent channel per agent — not three brittle ones
<5s
to reconnect after any network interruption
01 — Signaling

One channel. Everything on it.

Policy updates, tunnel commands, and live telemetry all travel over one persistent, mutually-authenticated connection — not three separate integrations that each need their own uptime, their own retries, their own failure modes.

gRPC over HTTP/2 — multiplexed streams, one TLS handshake, no polling.

agentengine
policy sync
tunnel commands
telemetry
02 — Availability

Never loses the signal.

A dropped connection isn't a dropped event. Agents reconnect automatically within seconds, and everything generated in between is queued, retried, and delivered — not silently discarded because the network hiccupped.

Automatic reconnect + backoff · durable delivery queue with retry and dead-letter handling.

connection dropsauto-reconnected
0
events lost in the gap
03 — Attack surface

There's nothing to scan.

Every connection is agent-initiated— nothing listens for inbound traffic, nothing accepts a connection it didn't ask for. An attacker running a port scan against a Threatmatic-protected endpoint finds exactly what they'd find scanning a locked room with no doors.

Outbound-only signaling · WireGuard-based reachability · deny-by-default at every zone.

TYPICAL VPN
443119450045008080
THREATMATIC
none open

Built like this from day one — not bolted on after.

If your current setup depends on exposed ports staying safe and connections staying up, it's worth seeing what the alternative actually looks like.