Customer-Licensed Deployment

Keep the AI Worker control plane inside your boundary.

License Scaled Agents for a customer-managed environment while keeping customer data, AI Workers, policies, credentials, evidence, integrations, and production decisions under customer control.

See the Ownership Boundary Compare Buy, Build, and License

Ownership Boundary

The platform is licensed. The operating environment remains yours.

Customer control and software ownership are different. The license provides the Scaled Agents platform; it does not transfer Scaled Agents software or IP, and it does not transfer customer operating authority to Scaled Agents.

Scaled Agents supplies

Licensed control-plane software and product updates
Governance records, workflows, templates, and validation patterns
Deployment documentation and separately scoped support
Platform IP, maintained under the applicable license agreement

The customer controls

Hosting environment, identity, access, keys, and credentials
AI Workers, configurations, policies, connectors, and data
Passports, review decisions, evidence, retention, and exports
Security, privacy, legal, compliance, production, and operational decisions

Deployment Path

Installation, activation, and action authority are separate decisions.

Installing licensed software does not activate a customer environment or authorize an AI Worker. Each stage requires its own evidence and accountable decision.

1 — License

Define the package

Agree the licensed platform scope, protected environments, support boundary, and applicable commercial and legal terms.

2 — Deploy

Install in your boundary

The customer provisions the approved environment, identity, storage, keys, network controls, backup, recovery, and operational ownership.

3 — Activate

Approve the environment

Customer owners validate configuration, security, privacy, integrations, operating procedures, evidence custody, and production readiness.

4 — Authorize

Govern each action

Passport scope, Toll Gates, Human Review, Runtime Permits, and the Action Broker govern what a specific AI Worker may do.

A software release, installation, passing test, preview, or active Passport does not by itself establish customer activation or exact-action authority.

Next Step

Evaluate the deployment model against your environment.

Start with the sourcing decision, then bring the customer’s architecture, security, privacy, operations, governance, and legal owners into deployment planning.

Compare Buy, Build, and License Review the Security Approach Request a Readiness Conversation

Explore integration, evidence, and review controls

Read-only first

MCP, API, and connector inventory should begin read-only until security and owner approval is recorded.

No destructive tools by default

Write, lifecycle, payment, or production-adjacent actions require tested implementation and approved authority.

Data minimization

Logs, Evidence, and support artifacts should prefer customer-safe metadata, redacted summaries, and non-secret identifiers.

Human Review

High-risk exceptions should route to customer-designated owners before the organization proceeds.

Boundary

Deployment planning does not authorize production operation.

This page does not provide legal advice, compliance approval, security authorization, production authorization, or proof that a customer environment already satisfies required controls.