Trust center

Trust center

Our security practices, assurance status and data handling.

Last updated: Applies to aaes.ai

Posture at a glance

AAES Operate, which runs and coordinates agents, has private-work permissions, operational reviews and recorded-spend limits; it does not include AAES Govern’s action controls. Its practices are in the AAES Operate section. AAES Govern checks whether an agent may take a proposed action routed through it. Where configured, it uses the required credential to carry out a permitted call without handing that credential to the agent. It signs records that the client can check offline for changes. This page states what is verified and what does not exist. These descriptions follow the current source. If a page and the release you receive disagree, email hello@aaes.ai. We will investigate and correct the page.

AAES Infer is for model access with jurisdiction controls, through your own Google Vertex AI or Azure account. Its supplier terms, processing locations and production acceptance must be qualified separately; the Operate and Govern controls described here do not establish Infer’s readiness.

StagePaid evaluation

The evaluation package runs in your environment and comes only with a paid, scoped evaluation. No production adoption claimed.

DeploymentSelf-hosted or hosted by AAES

Run Operate and Govern in your environment, on Docker Compose or Kubernetes, or have them hosted by AAES. AAES-hosted production runs across zones for high availability. Customer-hosted high availability requires a cluster that can power machines off through an API. Both deployment types use backup and restore.

CertificationsNone

No SOC 2 report exists. Infer has its own qualification and security scope.

Pen testScoped

No penetration-test report exists. AAES has a documented scope and test plan for an independent test.

AvailableReady to evaluate

AAES Operate: agents, the organization chart, projects and tasks, goals, the inbox and approvals. AAES Govern with Operate: approvals bound to the exact request, and budgets set aside before an action. Records you can check offline with the public verifier.

Support09:00 to 17:00, your time

09:00 to 17:00 in your time zone, Monday to Friday, except public holidays where you are. First response within 2 support hours for critical issues, 8 support hours for major issues and 2 support days for the rest. Faster response and round-the-clock cover for critical issues are available as paid upgrades. 99.9% monthly uptime for deployments hosted by AAES, under the service level agreement.

99.9% monthly uptime for deployments hosted by AAES, under the service level agreement.

Compliance and assurance status

The table records each assurance item’s status and supporting information.

ItemStatusDetail
SOC 2 Type INot startedA readiness program and control map exist internally; no auditor is engaged and no examination date has been set.
SOC 2 Type IINot startedExamines operating effectiveness over a defined period. The examination period will be agreed with the chosen auditor based on the controls and intended report users; no period or examination date has been set.
ISO 27001Not pursuedNot currently on the roadmap; SOC 2 is the first framework.
Penetration testScopedA documented scope, test plan and disclosure policy exist for an independent penetration test. No report exists; this page will name the firm and the date once it has.
Internal security reviewOngoingAI-assisted review supplemented by manual verification, with findings tracked and retested before release. An internal engineering control, not an independent audit.
Release integrityIn placeAAES Govern release files include signatures to check their origin, checksums to detect changes, and software bills of materials listing their components. These use Ed25519, SHA-256, and SPDX/CycloneDX formats and can be checked offline. Signing does not establish code safety.
Security evidence bundleImplementedFor a matching installed release on Docker Compose, aaesctl security-evidence export writes one signed bundle with the release’s signed-image list, SBOMs and attestations, the image digests actually running, the latest scan and the live TLS, identity-provider, egress and route settings. aaesverify security-evidence checks it offline. aaesverify v0.3.0 and earlier public releases do not include this command. The bundle says what it does not prove: settings it could not reach are recorded as unknown, an offline export records signature verification as not performed, and the threat-model review is recorded as unknown.

Security practices

The practices below are AAES Govern’s. The detailed statement (design principles, assurance claims with their boundaries, and known limitations) is on the security page. The short version:

  • Refuse new requests during an outageIf AAES Govern is unavailable or cannot write the required decision journal, new requests on enforced paths are refused. This is called fail closed. Grants issued before the failure remain usable until expiry, at most 15 minutes from issue. This does not stop observation-only activity or calls that bypass Govern.
  • Sealed recordsRecords are added to a journal with cryptographic links and signed summaries, making changes detectable. The public verifier checks exported fields and record-hash commitments offline. Checking stored-record fields also requires the records sidecar, an additional file, and its separate binding check. Technical details: hash-chained journal and signed Merkle tree heads.
  • Encryption

    Lab-only inline credential storage uses AES-256-GCM with per-tenant keys. The AAES Govern service serves TLS in process. Its API and console require TLS, including on loopback, unless the operator explicitly enables plain HTTP.

  • Access controlCallers are bound to their identity. Approval is required where policy specifies it; eligible manager agents may approve where policy permits, but an agent cannot approve itself and irreversible actions require human approval. Operators can use single sign-on (SSO) and multi-factor authentication (MFA) when configured.
  • Honest limitsRead the security page for the known limitations of these controls.

AAES Operate. AAES Operate refuses to start on a database or data volume unless it detects LUKS disk encryption or you attest the cloud KMS key or encrypted storage class that protects it, and encrypts its stored secrets in the application. In AAES Operate + Govern, model-provider keys stay in AAES Govern and agents hold only Govern-issued tokens. Credential handling for other capabilities depends on the integration.

The public Apache-2.0 aaesverify v0.3.0 source and release binaries verify the aaes.export/v3 exports that current AAES Govern deployments write, and retained aaes.export/v2 exports such as the public sample. The earlier v0.2.0 release reads v2 only.

Data handling and privacy

Self-hosted AAES Govern data. In a client-operated deployment, Govern’s records, identities, approvals, and operational state stay in your deployment. AAES receives no ordinary AAES Govern runtime traffic. Optional support transfers are agreed in writing before anything is sent.

On the brokered journal path, the service stores a digest of an action’s content rather than that content itself. Identifiers are stored as supplied unless journal encryption is enabled. Hosted workflow definitions separately retain step and reconciliation payloads in encrypted storage. Registered result modes may return bounded response bodies, and free-text metadata such as access justifications may be retained verbatim.

Self-hosted AAES Operate data. In a client-operated deployment, AAES Operate stores instructions and run transcripts on encrypted database and data volumes in your deployment, separate from the governance journal. Operate sends instructions, conversations, tool definitions and tool results to the client-selected model endpoint, which may be an external provider. The client assesses that provider's data handling and transfer arrangements. Run transcripts are removed after a retention period you set in days, except for runs still active, awaiting approval or not yet reconciled for cost. In AAES Operate + Govern, Operate also waits for Govern to confirm the run's calls are settled, and keeps the transcript whenever either check is uncertain. Each retention pass covers every run older than the retention period, oldest first, in bounded batches. A pass that reaches its time limit records itself as partial, and the next pass continues. Governance evidence is retained independently. See the client-operated product-data section for the retention boundaries.

AAES-hosted deployments. AAES processes runtime data to operate the agreed service. Before processing begins, the agreement and applicable processing terms identify the hosting environment, providers, locations, data access, retention and deletion arrangements. The client-operated statement that AAES receives no ordinary runtime traffic does not apply.

  • Privacy policyWhat the website collects, legal bases and rights, retention, and transfer safeguards for correspondence.
  • SubprocessorsNo AAES Govern subprocessors for ordinary client-operated runtime traffic. AAES-hosted providers are disclosed in the applicable processing terms. AAES Operate’s outbound connections are listed in the evaluation package. Website and correspondence providers are listed with roles, locations and safeguards.
  • Data Processing AgreementA draft DPA covering the client-hosted products is available under NDA on request from hello@aaes.ai. AAES-hosted deployments require applicable processing terms before processing client data. The operator is AAES LLC, a Delaware limited liability company. Registered address for legal notices: 8 The Green STE B, Dover, DE 19901, United States. Contact: support@aaes.ai.
  • Data-subject requestsFor data we hold (website and correspondence), email hello@aaes.ai; we respond within the period required by applicable law, generally one month under the GDPR or UK GDPR, with any lawful extension explained. For data in a client's deployment, contact the client operating it.

AAES Operate

AAES Operate runs and coordinates agents on your infrastructure or in an AAES-hosted environment. AAES Operate has private-work permissions, operational reviews and recorded-spend limits. 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. In a client-operated deployment, the client operates the infrastructure; AAES supplies a reference deployment configuration and upgrades, with assisted installation and optional enhanced support.

  • Corporate sign-in and SCIMSign in at your identity provider through OIDC or SAML. With Govern, SAML needs AAES’s help and WorkOS sign-in is refused. SCIM directory sync maps groups to workspaces; when someone leaves, their sessions and live connections end, their queued runs are canceled and their memberships are removed.
  • Workspace and project privacySeparate workspaces isolate everything, including costs and agent skills. Inside a workspace, project membership controls who sees tasks, comments, search results and inbox items, and workspace administrators get no bypass. Every member still sees costs, activity, skills, plugins, chat channels, API key details and routines that belong to no project, without the names, IDs or content of private work hidden from them. To anyone outside its audience, a private task or project answers exactly like a missing one. Gaps in task numbers can show that hidden tasks exist. A project imported under the name of a project hidden from the importer gets a numeric suffix, which shows that the name is taken. Run and recovery counts on workspace reports can include hidden work.
  • Agent sandboxesEach agent can run in its own sandbox whose only network peers are the endpoints you name. The sandbox is optional for Operate on its own; AAES Operate + Govern lists the agents that always run in it.
  • Signed activity exportActivity is written to a hash-chained export with a signed head, which you can check offline. It records what Operate logged and is kept apart from Govern evidence.
  • Backup and restoreScheduled database backups are encrypted and sealed with a signed manifest, which you verify before a restore. The configured backup interval is a recovery-point target. Actual data loss and recovery time depend on the latest usable backup and a successful restore; deployment-specific RPO and RTO have not yet been measured. For standalone Operate, back up storage, secret key files and logs separately.
  • Operate + Govern backup and restore drillFor a combined installation, aaesctl backup backs up AAES Govern, Operate’s database and storage, and the AAES front under one signed manifest. A restore refuses a partial set or a manifest whose signature, release or components differ. The restore drill restores the latest verified backup into a separate scratch environment, never the live one. It checks that every restored file matches by SHA-256 and that table row counts match exactly, then writes a signed report with the recovery point, recovery time and a result for each component. The drill shows the data came back; starting a restored copy stays an owner decision. No RPO or RTO has been measured on a customer installation yet.
  • API and telemetryThe API reaches the same workspace with API keys, through the same front and the same permissions. Telemetry is off in every packaged configuration.
  • Open-source componentsAAES Operate is built on open-source components. The component inventory and license notices are provided in the evaluation package.
  • Upgrades and vulnerability reportsAAES supplies a reference deployment configuration and upgrades for AAES Operate, with assisted installation and optional enhanced support. Report a vulnerability affecting its open-source components through the disclosure policy; AAES handles vulnerability reports for the software it supplies, including its open-source components.
  • Data flowsAAES Operate stores agent configuration, tasks, and run history in your deployment. It sends instructions, task context, and tool results to the model providers and agent runtimes the client configures, which may be external services. The client assesses those providers’ data handling and transfer arrangements.
  • Outbound connectionsThe outbound connections AAES Operate makes, including any made by its open-source components, are listed in the evaluation package. Verify them in your environment before production use.

Documents and requests

What we can share, and on what terms:

When a SOC 2 report or a penetration-test report exists, its status and a letter of engagement or attestation will appear on this page. Until then, nothing on this page should be read as an independent assessment.

Report a vulnerability

To encrypt a report, use our PGP public key for security@aaes.ai, fingerprint C53E B92A 9845 D5DF 0AB6 0434 B795 161C AEA6 B5B1. Check the fingerprint before you rely on the key.

Follow the vulnerability disclosure policy, or email security@aaes.ai with the subject line Security. The same contact and policy are published as an RFC 9116 security.txt at /.well-known/security.txt. We acknowledge reports within five business days and provide a substantive assessment within fifteen business days.

Evaluating AAES for your organization?

We answer security questionnaires and procurement reviews directly. Use the documents above to prepare your review.

Contact the team