Shared responsibility
AgentDeploy protects and operates the control-plane services it provides. Customers protect their accounts, applications, data, provider configuration, runtime nodes and the permissions granted to users and agents.
// Trust / Security & Compliance
AgentDeploy combines control-plane safeguards with explicit customer responsibility for applications, provider accounts, data and infrastructure.
These public policies describe the current service model. A signed order form or separate agreement controls if it states different terms.
AgentDeploy protects and operates the control-plane services it provides. Customers protect their accounts, applications, data, provider configuration, runtime nodes and the permissions granted to users and agents.
Access is scoped by user identity, organization membership, application grants and current permissions. Browser authorization and local provider authorization should be completed only by an authorized user.
Supported artifacts are content-addressed and verified before release. Separate Preview environments and explicit production confirmation reduce the risk of publishing unreviewed output. Rollback behavior depends on workload and resource type.
Gateway, Mesh and Tunnel paths can separate service entry from workload location. Temporary tickets and policies may limit an agent task by resource, action and time where the connected environment supports them.
Keep secrets out of prompts, source bundles and public artifacts. Provider credentials and data remain subject to each connected service. Review current documentation and live capability responses before assuming a control is available.
This page describes product safeguards and does not claim a certification, audit result or regulatory status that has not been published. Customers should evaluate requirements with their legal and security teams and record them in the applicable agreement.
We may update this page as the service, law or operating model changes. Material updates will be identified by a new date and communicated through an appropriate product or account channel when required.