AAES
Request an evaluation

AAES Operate + Govern / Together

Operate runs the work.
Govern checks
the actions.

Use AAES Operate and AAES Govern together. Operate’s agents send their model and tool calls through Govern, and the manager answers Govern’s approvals from the Operate inbox. Both run on your infrastructure.

Request an evaluationExplore AAES Govern

AAES Operate + Govern runs both products together. Operate’s agents send their model and tool calls through Govern, and approvals that Govern requires reach the manager’s Operate inbox.

Follow a call from an Operate agent.

A call from an Operate agent in AAES Operate + GovernAn Operate agent runs in a confined sandbox and sends its model or tool call to AAES Govern. Govern checks permissions and policy and seals the decision. When policy requires an approval, Govern posts the request to the manager's Operate inbox. The manager decides under their own identity, Govern seals that decision and the agent is woken to retry. For the permitted call, Govern reserves the spend, forwards it with the credential it holds, seals the outcome and, for a model call, settles the actual usage.Operate agentin a confined sandboxAAES Governmodel gateway and MCPManagerOperate inboxProvider or toolGovern holds the credential1 Model or tool call2 Check permissions and policy, seal the decision3 Approval needed: request in the inbox4 Manager decides, under their own identity5 Agent is woken and retries6 Retry permitted: reserve spend, forward the call7 Outcome sealed, model usage settled
When Govern is unavailable, routed model and tool calls fail closed. There is no direct route to a provider from the sandbox.

What you get with both.

Every agent known to Govern

Each agent in a workspace you connect to Govern gets an accountable manager and its own Govern credentials, so Govern sees which agent asked. Projects and routines map to Govern tasks.

Sandboxed agents

The sandbox can reach only Govern and the Operate API, and holds no provider key. Claude and Codex agents run in the sandbox, so all their model and tool calls go through Govern; HTTP agents call a runtime you host and are governed only for the calls it sends to Govern.

Approvals in the manager’s inbox

When Govern policy needs a person, the request lands in the manager’s Operate inbox. The manager decides under their own identity, Govern seals the decision, and the agent retries.

One approval per call

Operate’s own ask-first rules are off on the Govern connection, so an MCP tool call is never approved twice.

Who decides what.

DecisionDecided byHow
Hire an agent, approve a plan, enable a routineAAES OperateOperate’s approvals and inbox
Who can see private workAAES OperateWorkspace and project membership from your directory
Operational budget on recorded spendAAES OperateOperate budgets, set above Govern’s limit so Govern refuses first
A model call and its spendAAES GovernModel gateway: decide, reserve, forward, settle, seal
A tool call with an external effectAAES GovernMCP bridge: decide, reserve, execute with Govern’s credentials, seal
An effect Govern policy marks approval-requiredAAES Govern, decided by a personRequest in the manager’s Operate inbox; decision sealed by Govern

Govern checks only the calls routed through it. If Govern is unavailable, those calls are refused and people keep working in Operate.

Evaluate one real workflow.

Pricing and availability

The design-partner offer is USD 40,000 for three months and covers AAES Operate and AAES Govern; the term begins once the agreement is signed and onboarding is complete. Production rates are unpublished. For AAES Govern, the planned production model meters governed-decision capacity, and model-gateway calls do not count toward it. The planned production model for AAES Operate is an annual subscription per production deployment, including high-availability nodes, non-production environments, setup, and standard support.

The platform evaluation package for AAES Operate and AAES Govern runs in your environment and is included only in the paid design partnership.

Request an evaluation

Build with both products.

Read the combined integration documentation, or start from AAES Operate or AAES Govern.

Frequently asked questions

Are Operate and Govern merged into one product?

No. Each product keeps its own sign-in, permissions and records. AAES Operate + Govern adds the routes between them: Govern credentials for each agent, the sandbox and approvals in the Operate inbox.

What happens if AAES Govern is unavailable?

Routed model and tool calls fail closed: there is no direct route from the sandbox to a provider and no provider key in Operate. Operate itself stays up, so people keep planning, assigning and reviewing. Approvals that Govern raised wait until it returns. Grants issued before the outage stay usable until they expire, at most 15 minutes from issue.

Which agents are governed?

Claude and Codex agents run in the sandbox, so all their model and tool calls go through Govern; HTTP agents call a runtime you host and are governed only for the calls it sends to Govern.

How is AAES Operate + Govern priced?

The design-partner offer is USD 40,000 for three months and covers AAES Operate and AAES Govern; the term begins once the agreement is signed and onboarding is complete. Production rates are unpublished. For AAES Govern, the planned production model meters governed-decision capacity, and model-gateway calls do not count toward it. The planned production model for AAES Operate is an annual subscription per production deployment, including high-availability nodes, non-production environments, setup, and standard support.