Surge is an autonomous SOC: it watches protected files and logins on every enrolled endpoint, decides what's happening, and either acts automatically or asks a human -- everything below is that system's real, current state, not a simulation.
Current risk level
--
Loading live status…
System health -- 7 agents
Surge's pipeline is seven cooperating stages (Telemetry, Memory, Learning, Decision, Response Planner, Response Execution, Recovery). Each dot below is when that stage last did real work -- not a synthetic heartbeat -- so a stuck or idle stage is visible immediately, not discovered later.
Live event feed
Every file change Surge has observed and reached a verdict on, most recent first. File paths are pseudonymized here by design -- the full path is available in Incidents for anyone with access to investigate.
Approvals queue
Actions Surge has decided are needed but classified high-risk (e.g. revoking credentials, rotating a secret) -- these never run automatically. Nothing appearing here means nothing is currently waiting on a human.
Pipeline latency
Measured time from detecting a change to sealing a decision, per recent event -- a real number from the audit log, not a target or an estimate.
Detection → sealed decision, most recent events (ms)
SURGE