Loading…
Loading…
AGI for enterprise
Most AI tools ask you to accept their data boundary before you are allowed to evaluate them. Local and BYOK invert that: a reviewer runs the product on their own hardware or their own provider contract, and the evaluation finishes without a conversation reaching AGI infrastructure. When you do buy, identity, policy, audit, and retention are administered by your own owner in a workspace console, and the two ledgers below say which of those are built and which are still only commitments.
What an enterprise contract covers
| Status | Reviewed 23 August 2026. SSO and directory provisioning are implemented and live, gated on the enterprise_controls entitlement that ships with the Enterprise plan, your org's owner configures both directly once that entitlement is on the account. Org audit events are recorded to an append-only table, and your owner or admin can now read and filter them in the product and download the range as JSONL. Your owner can now set a retention window per workspace and switch enforcement on, which runs a nightly sweep that permanently deletes conversations past the window, withholds anything under legal hold, and records every run so the deletion is evidenceable. Legal holds are placed and released in the product. Your owner can also switch off public sharing for the whole workspace, which refuses new anonymous links on both the chat-share and artifact-publish paths. Dedicated capacity remains a contract-scoped commitment, not a self-serve toggle; we state dates for that in writing during procurement. |
| SSO | Implemented. SAML 2.0 and OIDC single sign-on, configured by your org owner at /workspace/identity once the account carries the enterprise_controls entitlement: domain verification and connection activation happen there, not through a separate rollout project. The limit the console states to your admin, and we will state to your reviewer: an active connection adds an authentication route without removing the others, so a member who already has a password can still sign in with it. |
| Directory provisioning | Implemented. SCIM 2.0 user and group provisioning from your IdP, with token issuance and a provisioning event log at /workspace/identity, gated on the same enterprise_controls entitlement as SSO. Deactivating a user at your IdP removes their membership; it does not yet terminate live sessions or device tokens on Desktop, Mobile, CLI, VS Code, or Chrome, and directory groups map to a role without carrying sharing grants, policy scope, or budgets. |
| Audit | Implemented, with a stated limit. Administrative and identity events are written through a security-definer function into a table the application role cannot update or delete. An owner or admin reads and filters them at /workspace/audit and exports the filtered range as JSONL; the export, and any refusal of one, is itself recorded. Streaming is built too: batches go to an HTTPS endpoint you nominate, signed with a per-workspace secret and drained on a ten-minute schedule, though that destination is configured through the API rather than from a screen. The limit worth knowing before you buy: coverage is administrative and identity events, not every action in the product, and we will tell you precisely which are captured rather than implying full coverage. |
| Retention | 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 a recorded position and nothing is deleted, the product labels it that way rather than implying deletion. With it on, a nightly sweep permanently deletes workspace conversations with no activity for the window, skips any subject under legal hold, and refuses to delete at all if it cannot read the hold set. Each run is recorded with what it removed and what it withheld. |
| BYOK posture | The strongest control available today, and it needs no feature work from us: every seat can run fully local, or on your own provider keys on Desktop, CLI, and VS Code, and no conversation content reaches AGI infrastructure at all. It is architecture rather than administration. There is no org-wide BYOK enforcement, so we cannot stop a member choosing managed cloud. Requiring it org-wide is a contract-scoped commitment. |
| Service levels | Response and uptime numbers are planned targets rather than binding commitments. See the SLA page for exactly which is which. |
| MSA | We negotiate against your procurement. No forced click-through. |
Compliance posture as of 23 August 2026
| SOC 2 Type II | Not 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, /trust carries the dated status. |
| GDPR: data subject rights | Implemented. Self-service export returns your account data as a download, and account deletion runs an enumerated erasure on a scheduled job. Our standard DPA is published at /dpa; we also negotiate against yours. |
| CCPA / CPRA | Implemented, through the same export and erasure paths. We do not sell personal information; the privacy policy carries that disclosure. |
| HIPAA | Not available. AGI does not offer HIPAA-covered workflows today. |
| ISO 27001 | Not held. No certification body is engaged and no date is claimed. |
| Everything else | On the roadmap with no date until there is a date. |
The artifact behind the audit row
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.
# newest first, one event per line, streamed as it is read
{"id":"1f8a4d6c-7b52-4a19-9e30-2c6d84b1f077","organizationId":"7d2c9b41-53e8-4f60-a1b7-9c0e5d8a3f24","actorUserId":"user_31Kk8fQpZ2mXvR7d","surface":"web","action":"data_exported","resourceType":"enterprise_audit_events","resourceId":"7d2c9b41-53e8-4f60-a1b7-9c0e5d8a3f24","outcome":"denied","severity":"warning","metadata":{"resourceType":"enterprise_audit_events","resourceId":"7d2c9b41-53e8-4f60-a1b7-9c0e5d8a3f24","reason":"audit_export_disabled"},"createdAt":"2026-08-23T16:41:07.402Z"}
{"id":"0b73e5aa-1c94-4d28-8f57-3ae0629b4d11","organizationId":"7d2c9b41-53e8-4f60-a1b7-9c0e5d8a3f24","actorUserId":"user_31Kk8fQpZ2mXvR7d","surface":"web","action":"admin_policy_changed","resourceType":"organization_admin_policy","resourceId":"7d2c9b41-53e8-4f60-a1b7-9c0e5d8a3f24","outcome":"success","severity":"warning","metadata":{"resourceType":"organization_admin_policy","resourceId":"7d2c9b41-53e8-4f60-a1b7-9c0e5d8a3f24","role":"owner","status":"updated","changedKeys":["auditExportEnabled"]},"createdAt":"2026-08-23T09:02:44.517Z"}Start the evaluation
Local and BYOK need no contract, no trial, and no seat, so a reviewer can run the product on their own hardware or their own provider key while procurement is still reading. Send the questionnaire whenever you are ready and you will get direct answers, including the ones where the answer is 'not yet'.