ForgeOS is not a report you read tomorrow. It is a decision made now, on the path the action has to take.
ForgeOS builds a live inventory of every agent, copilot and script touching production — including the ones nobody declared.
The action is captured at the execution boundary: an SDK call, an HTTP gate or an MCP proxy in front of your tools.
Policy is evaluated within a <50ms p99 budget and returns ALLOW, HOLD until you approve, or BLOCK. Unknown means blocked.
Every verdict, payload hash and approver is written to a hash-chained ledger you can hand to an auditor.
No. A gateway sees the request an agent makes. ForgeOS sees the action it executes, at the boundary where it lands.
Fail-closed by default. Sensitive actions do not run without a verdict; you can scope which classes fail open.
Agent payloads stay on your infrastructure — VPC, on-prem or fully air-gapped.
A design-partner pilot is typically scoped in one call and instrumented on one agent within days.
Policy is evaluated before the action reaches your tools, then enforced on the host, with an optional OS-level deny below that. One path, fail-closed.