Sandbox
Model one governed action with the quickstart before discussing commercial scope.
Choose the boundary you need to govern first.
Choose the workload and adoption stage. 2AYE separates identity scale from consequential actions so teams can evaluate the right commercial unit.
Sandbox
Model one governed action with the quickstart before discussing commercial scope.
Guidance only. Commercial packaging remains indicative until deployment scope and currently available capabilities are confirmed.
Every plan meters the same unit: consequential actions evaluated, approved, executed, and evidenced. Authentication is included infrastructure, not the bill. These figures are positioning targets for customer validation, not final list prices.
Individuals and developers
Developer sandbox for evaluating a governed action
Start in sandboxTeams governing their first workflows
Design-partner scope confirmed during workflow review
Discuss availabilityContextual enterprise enforcement
Governed-action and integration scope confirmed during review
Discuss availabilityOrganizations evaluating regulated or security-sensitive workflows
Deployment and governed-action scope confirmed during review
Discuss availabilityAdd Living Intent Contracts, deterministic runtime constraints, resource-side enforcement, credential isolation, human approval, attenuation, revocation, execution receipts, and customer-boundary evaluation.
Discuss your workflowPlatform subscription + active governed agents + protected tools and connections + deployment and evidence tier, with generous bundled evaluations. 2AYE will not make the marginal price of a safety check encourage bypass.