How Svalin works under the hood.
Ultra-light endpoint engine
Zero workflow alteration
Engineers keep using Cursor, Claude Code, Gemini CLI, or custom MCP servers without switching tools or changing their terminal habits.
Account-agnostic governance
Developers switch between personal and corporate AI accounts constantly. Svalin governs at the process and device layer: regardless of which account or API key is active, it sees corporate code touched by AI on the device — whether or not the developer is signed into a corporate account.
5-minute MDM deployment
Deploys silently: macOS via Jamf, Kandji, or Intune; Linux via Intune or your existing configuration management. An ultra-light daemon with near-zero CPU and memory overhead.
Forensic Speed
Repository & file-bound filtering
Instantly filter sessions that touched a specific Git repository, branch, or critical file path. Pinpoint the exact AI conversation, tool call, or prompt that introduced a security flaw or caused a production outage.
Process-tree reconstruction
Svalin uses process lineage and PID tracking to automatically reconstruct the full conversation chain — no endless manual log stitching.
Real-time analysis
Beyond passive log dumps
Logs aren't stored just for an end-of-year security audit. Svalin analyzes tool calls, terminal commands, and file access in real time to highlight risky agent behavior as it happens.
Causal session reconstruction
Automatically links raw file reads, bash execution, and HTTP requests back to the specific session, prompt, and skill file that initiated them.
filesystem · initialize
claude-opus-4-20250514 — 7.1K tokens, tool_use
filesystem/write_file
claude-opus-4-20250514 — 6.6K tokens, end_turn
Accountability
Who made the call?
A clear separation between human developer actions, explicit slash commands, background agent loops, and auto-invoked MCP skills.
Skill & prompt provenance
Tracks the exact chain of execution — from prompt input to tool output — giving security teams a verifiable, audit-ready trail.
built-in-filesystem/edit_file · index.html
built-in-shell/shell_exec
Shadow AI & tool registry
Automatic discovery
Inventories every AI CLI agent, IDE extension, and MCP server running across your developer fleet.
Inline guardrails
Block unapproved tool calls, prevent credential leakage, and enforce local boundaries before destructive commands or unauthorized API requests hit the network.
If policy verification fails, Svalin fails closed.
The Svalin data flow.
How raw endpoint actions become evidence.
The ultra-light local daemon captures tool invocations and file modifications directly on the device — independently of developer account context.
Telemetry is correlated into causal session graphs and process hierarchies, identifying intent, repository impact, and risk scores.
Block violations inline, query repository-level incidents in seconds, and automatically export audit-ready evidence.
What Svalin doesn't touch.
The part a security review — or a works council — checks first: what the agent reads, what leaves the device, and what happens to a prompt when capture is off.
Detects everything, reads only what it governs
Svalin inventories which AI tools are installed and running, and reads configuration and activity only from the agents it governs. Never your source code, personal files, or any other file on the machine.
Prompt capture is opt-in
Prompt content is captured only when your policy turns it on. With it off, the words in a prompt never leave the device — Svalin still records what a session did (tool calls, files touched, timing), just not what was typed.
Encrypted, with controlled decryption
When capture is on, prompt content is encrypted at rest. Decryption is gated by policy and reason-logged, with employee notification — no one reads a prompt silently.