concepts
Faramesh is the execution control plane for AI agents. It sits between the agent and the outside world. Every tool call passes through Faramesh before it runs. The agent never touches a real API, database, or file system directly , Faramesh decides whether the action is allowed, holds it for a human, or blocks it entirely.
Most "AI governance" tools add a second AI to watch the first one. That's probability watching probability. Faramesh uses deterministic rules , code that evaluates the same way every time. If your policy says "block all shell commands," no prompt injection, jailbreak, or edge case changes the outcome. The answer is always no.
Faramesh is built for high-impact agent actions where a single bad tool call can cause direct business harm. The primary threat classes are: prompt injection leading to unauthorized tools, credential exfiltration from runtime environments, lateral movement through delegated agents, policy bypass via framework internals, and post-incident ambiguity where no one can prove what happened.
The control boundary is explicit: the Action Authorization Boundary (AAB). Every action must cross this boundary in canonical form before execution. This is what makes enforcement non-bypassable in practice. If an action is not represented as a canonical action and evaluated by policy, it does not run.
Faramesh does not rank likely outcomes; it computes a deterministic verdict. Decision order is fixed: identity and session checks first, then selectors/context enrichment, then rule evaluation (first match wins unless deny! applies), then delegation/budget ceilings, then credential issuance, then execution routing. No model-generated judgement is used at decision time.
This is why incident response is tractable. When a decision is challenged, you can replay the same canonical action against the same policy and get the same result, then verify the corresponding DPR record in the hash chain.
Faramesh is the only governance platform that combines all of these in one system: identity verification, policy enforcement, session budgets, credential brokering, delegation chains, human approval workflows, kernel-level sandboxing, tamper-evident audit, provenance signing, incident response, and full observability , all enforced with code, not AI.
Each layer adds a different kind of protection. Together, they form a complete governance stack from identity to audit.
Faramesh exports metrics, traces, and logs in open formats. Connect to any observability platform you already use.
Need help? Use any of these support options.