Let AI agents work.
Keep your team
in control.

AAES (Autonomous Agentic Enterprise Systems) makes two self-hosted products for enterprise AI agents. AAES Govern checks whether an agent may take a requested action: for actions routed through it, it checks permissions, required approvals, and spending limits, then records the decision. AAES Operate runs and coordinates agents on your infrastructure, with its own approvals, tool permissions, and budgets; it does not include Govern’s controls. Use either one, or both.

With Govern, each registered agent has at least one accountable manager, ultimately answerable to a person, and employee access stays in your existing identity provider. On enforced paths, a request needing a new decision cannot proceed if Govern cannot record that decision. Previously issued grants can remain usable for up to 15 minutes from issue. Govern cannot stop observation-only activity or calls that bypass its controlled path. You operate AAES on your infrastructure; no availability SLA is offered today.

If you already run agents and need control over what they do, start with AAES Govern: connect the agents you run and route their actions through it. If you need to create, run, and coordinate agents, deployed on your infrastructure and supported by AAES, choose AAES Operate. Whether the actions of agents that Operate runs can be routed through Govern is evaluated in the design partnership.

Not in the AAES Govern sense. AAES Operate has its own operational controls: approval steps, per-tool permissions, and budgets that stop work once recorded spend reaches a limit, so work already running can overrun. It does not include AAES Govern. Govern adds spending reserved before an action is authorized, signed decision records you can check offline, and governance for agents you already run on other platforms. Govern applies only to actions routed through it.

If AAES Govern is unavailable or cannot write the required decision record, requests needing a new decision are refused on enforced paths. Govern authorizes no new grant or brokered execution through that path. This behavior is called fail closed.

Previously issued grants remain usable until expiry, at most 15 minutes from issue. An outage does not cancel work already authorized, undo downstream effects, or stop observation-only and bypass activity. Employee access stays with your identity provider. You operate AAES on your infrastructure; no availability SLA is offered today.

The design-partner offer is USD 40,000 for three months and covers AAES Govern and AAES Operate; the term begins once the agreement is signed and onboarding is complete. The platform evaluation package for AAES Govern and AAES Operate runs in your environment and is included only in the paid design partnership.

Production rates are unpublished. Neither product has a license fee per person or per agent, and neither has a licensed-agent-count limit. For AAES Govern, the planned production model meters governed-decision capacity: capacity for requests Govern evaluates and records, including permits and refusals. 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. Other charges and billing details remain unsettled; the pricing comparison explains those open questions.

If you stop using AAES Govern, you retain your exported records and the offline verifier supplied with your deployment. Check exported AAES Govern records for integrity without connecting to an AAES service. Offline verification checks export integrity using a separately trusted public key. It cannot prove complete capture or downstream execution. An optional independent witness or timestamp authority can corroborate the signed journal summary.