AGI
Contact salesSign inTry AGI Web
AGI for enterprise

Identity, policy, audit and retention, run by your own workspace owner.

Contact salesRead the dated trust ledger
What an enterprise contract covers

Scoped on a contract, stated without inflation.

Reviewed 5 September 2026. Everything below is implemented and live, gated on the enterprise_controls entitlement that ships with the Enterprise plan. Once that entitlement is on the account, the workspace owner configures single sign-on and directory provisioning directly, an admin can read and filter the audit trail, and the owner can set a retention window and decide whether it is enforced.

Identity

SSO and directory provisioning, configured by your owner.

SAML 2.0 and OIDC single sign-on, and SCIM 2.0 user and group provisioning from your IdP, with token issuance and a provisioning event log at /workspace/identity. Deactivating a user in your IdP removes their membership; an owner who wants to keep a seat nominates a successor first.

  • SAML 2.0 and OIDC, one connection per workspace
  • SCIM 2.0 users and groups, with a provisioning log
  • A member who already has a password can still sign in with it
Policy and retention

A ceiling the console enforces, not a preference it records.

Which routes the workspace allows, whether managed cloud may be used at all, and which client surfaces may sync. Your workspace owner sets a retention window between 1 and 3650 days and decides whether it is enforced; until enforcement is on, the window is recorded, nothing is deleted. On a plan that carries the enterprise controls entitlement that window is a contractual commitment, so the console reports it as required and says plainly when it is not yet being deleted against. Legal holds exempt any thread.

  • Local, BYOK and AGI Cloud allowed per workspace
  • Public share links and phone sync switch off server side
  • Retention enforced only when the owner turns it on
  • A plan-required window that is not enforced is reported as a gap, not as a control
Audit

Every administrative and identity event, readable and streamable.

Events are written through a security-definer function into a table the application cannot update or delete, read by an admin with filters, exported as JSONL, and streamed to your SIEM in batches signed with a per-workspace secret. A refusal is recorded in the same trail as the change that caused it.

  • Append-only table, streamed as it is read
  • JSONL export, newest first
  • Signed batches drained to your endpoint every thirty minutes
  • BYOK postureThe CLI can run fully local or on your own provider keys, so that work does not reach AGI Cloud. The CLI and VS Code are coming soon. Desktop is managed-cloud only and is coming soon. A member who moves a CLI thread to managed cloud does so through an explicit, reviewed handoff.
  • Service levelsYour named contact gets a first response within 4 business hours (Central Time) for a service-down report, and within 1 business day otherwise, with an escalation path and the status page. Uptime numbers remain planned targets rather than binding commitments; see the SLA page for exactly which is which.
  • MSAWe negotiate against your procurement. No forced click-through.
Compliance posture as of 5 September 2026

We claim only what is complete.

  • SOC 2 Type IINot held. No report exists, no auditor is engaged, and no audit is in progress. We are not going to describe internal work as an audit programme.
  • GDPR: data subject rightsImplemented. Self-service export returns your account data as a download, and account deletion runs an enumerated erasure on a scheduled job.
  • CCPA / CPRAImplemented, through the same export and erasure paths. We do not sell personal information; the privacy policy carries that disclosure.
  • HIPAANot available. AGI does not offer HIPAA-covered workflows today.
  • ISO 27001Not held. No certification body is engaged and no date is claimed.
  • Everything elseNot claimed here. The trust ledger carries the remaining rows, each with the artifact that would prove it and the date it was checked.
The artifact behind the audit row

Your reviewer can read the export line by line.

These two rows are the shape your admin downloads. Read them together: an owner switched export off that morning, and the afternoon attempt to download the trail was refused, so the denial is in the trail, next to the change that caused it.

$ jq -c '{action, outcome}' agi-audit-*.jsonl{"action":"data_exported","outcome":"denied"}{"action":"admin_policy_changed","outcome":"success"}
Two rows out of the JSONL your admin downloads.
Start the evaluation

Two ways to evaluate.

On your own hardware, in the CLI

Local and BYOK run in the CLI and need no contract, no trial, and no seat. The CLI is coming soon. The download page shows what is published.

  • In Local mode, conversations stay on your device and are never uploaded
  • BYOK traffic goes straight to your provider contract
  • The status bar names the route in use
See what's live

Send the questionnaire

You will get direct answers, including the ones where the answer is 'not yet'.

  • Dated claims on the trust ledger
  • A contract negotiated against your procurement
  • A named contact with a first-response window
Contact sales