The diagram below shows Adrian’s open-source architecture. The hosted version follows the same flow.Documentation Index
Fetch the complete documentation index at: https://docs.adrian.secureagentics.ai/llms.txt
Use this file to discover all available pages before exploring further.
Architecture
Flow
The Adrian SDK wraps your agent runtime and captures activity (tool calls, outputs, side effects) and reasoning traces as the agent runs. Each event is shipped to the Adrian backend over a persistent websocket connection. The backend assembles context across the agent’s session, sends the event to the classifier model, and returns a verdict. The verdict is routed back to the agent and to the control plane, where alerts surface and humans can intervene. The SDK can point at a hosted Adrian backend or a locally running open-source backend. See Hosted vs Open Source for the trade-offs.Detection engine
Adrian’s detection engine evaluates each event against a rule set focused on misaligned, malicious, and out-of-remit behaviour. The output is a classification verdict that the rest of the system uses to decide what happens next.Operating modes
| Mode | Behaviour | When to use |
|---|---|---|
| Audit | Alert-only. Adrian reports security alerts but does not block agent actions. | Observability without changing agent behaviour; default for most deployments. |
| Human Review | Adrian pauses potentially harmful actions until you (the human) approve or reject. | When you want a human in the loop for risky actions but don’t want to fully automate blocking. |
| Block | Adrian reviews every agent action prior to execution and automatically blocks actions deemed malicious, without human oversight. | High-stakes environments where the cost of an unsafe action outweighs the cost of latency. |