Choose your products
- Need model access? AAES Infer has a separate offer and account qualification process. Installing Operate or Govern does not activate inference.
- Need somewhere to organize agent work? AAES Operate works with your configured model connections and supported existing agent runtimes.
- Need control over actions your agents take? AAES Govern checks supported actions routed through it. You can keep an existing agent runtime.
- Need operations and governance together? Set up Operate + Govern and review the execution paths you want to govern.
An unconnected Infer offer does not prevent Operate from using your existing model access. Each product keeps its own permissions and readiness checks.
Choose who operates the deployment
You can operate AAES yourself or agree hosting by AAES.
Operate and Govern can be licensed directly without a design partnership. Implementation assistance, training and enhanced support are optional and agreed separately. Request product licensing.
Self-hosting still needs someone to manage the host, company sign-in, credentials, backups and updates. The guided setup checks its required inputs before activation. It cannot grant your identity provider's consent or qualify a live model offer for you.
The evaluation package runs in your environment and comes only with the paid design partnership. Request the selected evaluation package and its setup instructions. Package access and licensing remain separate from optional assistance.
Use the guided installation
The shared setup engine supports Govern, Operate and Operate + Govern on Docker Compose or Kubernetes. Review the plan, prepare the installation, then explicitly request activation. Setup retains confirmed progress; an uncertain outcome requires checking before another attempt.
The selected release, installation target and required acceptance records must match. Generating configuration files alone does not establish a working deployment. After deployment checks pass, an owner signs in to complete organization setup; new agents remain paused until authorized.
Platform launcher builds and signing requirements are documented with the setup package. Public signed desktop downloads and app-store listings are not available from this page.
Bring in your organization
In a configured Operate deployment, connect Microsoft Entra ID, Google Workspace or Okta through WorkOS Directory Sync. An authorized administrator completes provider setup, previews the people and available reporting relationships, then approves the import.
In Operate's Workforce organization view, an administrator can also create staff records manually and set their reporting relationships. These records describe the organization; they do not create sign-in accounts or grant access. Govern retains its separate reviewed person-entry and partial CSV import paths.
The organization view combines staff, agents, available reporting lines and recorded accountable owners. Missing or unresolved relationships remain visible as warnings. Provider attributes and immutable identity mappings determine which imported reporting lines can be resolved.
Create teams and add directory staff, manual staff records and agents. You can also review an available directory group and copy its current eligible members into a new team. This is a one-time import. Team membership does not change permissions, accountable owners or reporting lines.
Check one workflow before expanding
Use Workforce readiness and organization checks to find missing connections or unresolved ownership. Inspect an agent's configuration and access, then check its selected task. Requesting a run requires a separate confirmation. An accepted or queued run is not a completed result.
Verify the actual result and the controls for your workflow before inviting more staff or enabling more agents. The evaluation guide describes the product-specific checks.