TestMachine is targeting 11 of 12 governance requirements.
Agent governance for workflows that move money
AGIS is being built to connect business mandates to policy, testing, enforcement and evidence. R10 vendor oversight is the sole scope exclusion.
| Governance requirement | AWS | Google Cloud | Microsoft | Cloudflare | AGIS product scope11/12 requirements · Intended scope only* |
|---|---|---|---|---|---|
| R1Inventory and identity | DRegistry + identityRegistry GA · A1 · A2 | DRegistry + identityRegistry GA · G1 · G2 | DRegistry + EntraAgent 365 GA · M1 · M7 | PPortal + attributionWriteGuard private beta · C1 · C2 | Know the agent and its ownerTargeted scope |
| R2Mandate and policy | DCedar policy gatePolicy GA; extensions vary · A1 · A2 · A9 | DIAM + semantic policySemantic policy Preview · G2 · G3 | PAccess + guardrailsGA administration / Preview agents · M1 · M2 · M3 | PTool allowlists + tiersWriteGuard private beta · C1 · C2 | Bind actions to a written mandateTargeted scope |
| R3Hard money limits | PPayment-session capsPayments GA · A3 · A2 | UHard aggregate cap unverifiedNo verified mechanism in scope · G3 | UHard aggregate cap unverifiedNo verified mechanism in scope · M2 · M3 | UHard aggregate cap unverifiedNo verified mechanism in scope · C1 · C2 · C3 | Stop spend before it commitsTargeted scope |
| R4Semantic checks | PRules + content signalsDocumented; region limits · A2 · A4 | DSemantic policy enginePreview · G3 | DTask AdherencePreview · M2 · M3 | PContent moderationDocumented / private beta tiers · C2 · C3 | Check purpose as well as permissionTargeted scope |
| R5Human approval | PStrands approval flowSDK; managed hooks documented · A5 · A1 | PADK confirmationExperimental SDK feature · G4 | PFunction-tool approvalSDK feature · M4 | PSDK needsApprovalSDK example · C4 · C1 | Bind approval to the exact actionTargeted scope |
| R6Pre-deployment testing | PEvaluations + policy testsEvaluations GA · A1 · A2 | PADK trajectory testsPython SDK evaluation · G5 | PAI red teamingRestricted hosted-agent scope · M5 | PVitest + Workers poolDeveloper testing tools · C5 | Attack the composed workflowTargeted scope |
| R7Tamper-evident audit | PLogs + signed digestsSeparate logging services · A2 · A3 · A6 | PLogs + retention lockLogging service feature · G3 · G6 | PPurview audit + retentionIntegrated / licensed scope · M6 | PPortal logs + exportExport Enterprise / beta audit · C1 · C2 | Preserve the complete decision recordTargeted scope |
| R8Model-risk documentation | PEvaluation + policy evidenceGA evaluation; assembled dossier · A1 · A2 | PEvaluation evidenceSDK; assembled dossier · G5 | PRed-team + audit evidenceService/integration scope · M5 · M6 | PTest + log evidenceDeveloper / logging tools · C1 · C5 | Give reviewers evidence they can checkTargeted scope |
| R9Kill switch and revocation | PStop Runtime sessionDocumented runtime API · A7 · A2 | PGateway access denialConfigured IAM/gateway controls · G2 | PDisable identity blueprintEntra identity control · M7 | PDisable portal toolsPortal / private beta controls · C1 · C2 | Stop every route to actionTargeted scope |
| R10Vendor oversight | PAWS Artifact reportsProvider/participating ISV reports · A8 | PCompliance catalogueProvider assurance resources · G7 | PService Trust PortalProvider assurance resources · M8 | PTrust Hub resourcesProvider assurance resources · C6 | Check each supplier and dependencyOutside AGIS scope |
| R11Cross-vendor and A2A | PGateway + framework routesDocumented; routing required · A1 · A2 | PA2A + gateway policiesA2A v1 Registry GA · G1 · G2 | PPartner agents + auditingAgent 365 integrations · M1 · M6 | PMCP + multi-model proxyRemote HTTP / beta controls · C1 · C2 · C3 | Carry authority across handoffsTargeted scope |
| R12Explainability and data scope | PPolicy + IAM + logsConfigured services · A2 · A4 · A9 | PRationale + access boundarySemantic rationale Preview · G2 · G3 | PReasoning + Purview DLPPreview signal / integrated data · M3 · M6 | PTool policy + DLP routeConfigured portal / beta tiers · C1 · C2 | Explain the rule and bound the dataTargeted scope |
Cloud ratings describe documented mechanisms. D is direct within stated limits; P needs material integration; U means unverified in reviewed sources. SDK approvals require application implementation.
*AGIS scope describes what we are building. Product scope is confirmed by TestMachine. Targeted requirements describe our direction, not completed coverage, a release commitment or a measured deployment result.
Our vision for how the controls work together
Native cloud controls
Operate the control points
Identity, routed authorization, guardrails, service logs and resource access.
Providers operate these controls within their configuration, licensing and release-stage limits.
TestMachine · AGIS
Build the governance layer
AGIS product scope spans 11 of 12 requirements, from agent inventory to policy enforcement and linked evidence.
Intended product scope, not a statement of completed coverage. Each integration and execution boundary needs deployment validation.
Customer-operated controls
Own execution and acceptance
Ledger limits, trusted approval, bypass prevention, incident response and risk review.
Integrate and test each boundary. No provider score or AGIS assessment replaces this work.