Govern what you build, buy, or deploy
Bring internally built workers, purchased capabilities, and platform-based agents under one customer governance model.
AI Worker Control Plane
Scaled Agents is the provider-agnostic enterprise control plane for governed AI workers. It connects human ownership, bounded authority, review decisions, and evidence before AI-supported work becomes consequential action.
Use this page when you need the product-level answer: what Scaled Agents is, what it governs, and how Passport, Toll Gates, Runtime Permits, Action Broker, Human Review, Policy, Stamps, and Lifecycle Analytics fit together.
What It Is
Models, agent platforms, cloud services, enterprise systems, APIs, and connectors remain execution environments. Scaled Agents gives the AI workers operating across them a consistent governance record and accountable path from design through operation.
Bring internally built workers, purchased capabilities, and platform-based agents under one customer governance model.
Use customer-selected providers and tools without making any one provider the source of governance authority.
Owners and reviewers retain decisions for scope, risk, production readiness, exceptions, pause, renewal, and retirement.
Scaled Agents does not replace IAM, security, observability, GRC, legal review, audit, or accountable customer decision-makers. It connects AI worker governance to those customer control environments.
Identity To Evidence
The platform turns a complex control chain into four reviewable views. Each view uses connected governance records rather than creating a second source of authority.
Who owns this AI Worker, what is its purpose, and what standing scope is recorded in its Passport?
What data, tools, destinations, and actions are allowed—and what must remain prohibited or reviewed?
Did the Toll Gate allow, deny, pause, or escalate the exact request, and was Human Review required?
What Stamp, Evidence Record, and lifecycle context make the outcome reconstructable?
Fail closed when context is incomplete. Missing ownership, scope, evidence, current authority, or a safe recovery path should block or escalate the request—not become an optimistic assumption.
Customer Governance Intersection
Scaled Agents provides licensed control-plane capabilities and structured governance records. Your organization remains responsible for deployment, identity, data, configurations, integrations, monitoring, qualified review, production readiness, and operational decisions.
Governance workflows, Passport and Registry records, Toll Gates, Human Review paths, Runtime Permit and Action Broker controls, evidence, and lifecycle visibility.
Hosting, access, policies, risk acceptance, provider and connector selection, customer data, activation, operations, and final decisions.
A reviewable bridge between enterprise governance requirements and the AI Workers operating across customer-selected systems.
Governance Proof Stories
These illustrative governance scenarios show how Passport scope, Toll Gates, Human Review, action-time authority, controlled execution, and evidence are intended to stay connected when an AI Worker requests consequential action. They do not represent customer deployment or executable proof.
A Procurement Intake AI Worker has a named owner and approved purpose in its Passport. A proposed destination falls outside the reviewed boundary, so the Toll Gate blocks the request and routes it to Human Review. No Runtime Permit advances, the Action Broker has no basis to route the action, and the evidence trail records what stopped and what proof is needed next.
Inspect the sample PassportA proposed sensitive-tool action remains in review while required evidence and Human Review are incomplete. The Runtime Permit stays in a requires-review state, the Action Broker path remains blocked, and the linked Passport, Toll Gate, review item, and evidence records preserve the decision context.
Review the governed workflowA read-only connector request is evaluated as a specific action, not blanket integration approval. The Passport defines purpose and data scope; the Toll Gate checks the requested resource, evidence, and review posture before a scoped Runtime Permit or Action Broker path can be considered.
Open the provider-agnostic guideA coding AI Worker request identifies an approved repository and the independently reviewed boundary that would apply. A proposed protected-branch or deployment action remains blocked until the exact repository, commit, environment, evidence, and Human Review support a short-lived Runtime Permit. The scenario records why changed context, Permit replay, or Passport revocation prevents the Action Broker decision path from advancing.
Review the Control Plane product viewGoverned Execution Boundary. An AI Worker action must stop, obtain current authority, or route to review before crossing into a controlled system or consequential action. These illustrative scenarios do not access repositories, issue credentials, process customer data, call external tools, or execute changes. Customer configuration, identity, data, integrations, policies, approvals, and operating decisions determine the exact boundary in each licensed environment.
Solution
The control plane keeps AI worker identity, authority, evidence, and review paths visible through Passport Studio, Control Plane views, registry records, review gates, evidence records, and lifecycle status. Customers retain control over hosting, identity, data, configurations, integrations, monitoring, and production-readiness decisions.
Create and review Passport records that identify owner, purpose, approved scope, lifecycle state, authority limits, evidence needs, and open review gaps.
Review AI worker inventory, lifecycle status, evidence posture, open review items, risk signals, Runtime Permit posture, and operating context without treating a platform record as customer action authority.
Plan how AI worker ideas move from intake to ownership, risk review, evidence, Passport scope, review gates, and implementation handoff boundaries.
Passport Studio structures design-time governance records. The Control Plane organizes the customer-configured controls and evidence used to evaluate operating decisions. Neither surface replaces accountable customer approval or grants authority outside the applicable Passport, policy, evidence, Human Review, and Runtime Permit.
Two Entry Paths, One Governance Model
Organizations do not need to rebuild their existing AI estate to use the Scaled Agents governance model. Both entry paths converge on the same ownership, Passport, review, action-control, evidence, and lifecycle records.
Identify the use case, assign an owner, draft the Blueprint and Passport, classify risk, define data and tool boundaries, complete required review, establish Registry standing, and govern action requests.
Discover or register the worker, assign accountable owners, document current authority and dependencies, identify gaps, apply provisional restrictions where needed, remediate, review standing, and govern future action requests.
Identify, own, define, review, authorize actions, capture evidence, monitor, renew, constrain, suspend, revoke, or retire through shared governance records.
Evaluate Current Capability
The current platform baseline describes the licensed capabilities Scaled Agents provides. Each customer independently controls deployment, configuration, identity, data, integrations, activation, action authority, evidence custody, and operating decisions for its environment.
Capability Layers
Reusable AI Worker patterns and templates help teams start from known governance expectations instead of unmanaged prompt or tool sprawl.
Versioned questions, contextual answers, evidence expectations, review state, assessments, and scoped reuse help teams stop answering the same enterprise questions from scratch.
Explore Governed Q&AToll Gates, Runtime Permits, Action Broker routing, Human Review, and Stamps connect action-time control to evidence.
Human ownership, review rights, escalation paths, and lifecycle responsibilities remain part of the platform design, not an afterthought.
Start With One Worker
Define the purpose, owner, risk, data and system boundaries, review path, evidence needs, and next implementation decision before broader operating use.