Delegate separates what an agent can reason about from what it can reach, change, spend, and reveal — with people at every consequential boundary.
Explore the layers that contain agents, limit their authority, protect credentials, and preserve a record of what happened.
Each agent works in an isolated workspace surrounded by layered controls. Network access, tools, permissions, and credentials remain separate decisions — granting one never silently grants the others.
User roles define who can view, delegate, approve, and administer. Separately, an agent can act only where its own permission ceiling overlaps with the authority of the person delegating the work. New destinations, credentials, skills, and consequential actions can stop for approval.
Secrets are encrypted, write-only after entry, and kept outside prompts, files, logs, and transcripts. When an approved tool needs one, the broker adds it to the outbound request and scrubs sensitive material from the response before the agent receives the result.
Full audit logs record every platform-mediated action: what happened, who or what did it, and what came back. Role changes, workspace commands, approvals, and costs remain attributable instead of disappearing into an AI transcript.
Delegate separates durable work records from captured evidence and keeps model access, retention, and deletion visible for review.
Delegate stores the account, board, message, file, usage, and audit data needed to operate the service. Credentials are handled separately as brokered secrets.
Agent requests can be sent to the selected model provider. Tool calls can reach only destinations permitted by the workspace network policy.
Core work records remain until changed or deleted. Browser captures and file snapshots from work streams default to 90 days and can be configured from 1 to 3,650 days.
Deleting a team removes its team-scoped database records and associated storage folders. Artifact cleanup is queued and retried so a temporary storage failure does not silently abandon deletion.
Exact model-provider data use, infrastructure subprocessors, backup retention, and residency depend on the deployment and are confirmed during data-processing and architecture review.
Open the trust centerThe control model addresses the AI risks identified by OWASP and follows the least-privilege, continuous-governance approach used by NIST and the Cloud Security Alliance. This is design alignment, not a claim of certification.
These controls are on our roadmap and are not available yet.
Connect Delegate to the identity provider your organization already governs.
Use phishing-resistant login without reusable passwords.
Require an additional factor for sensitive accounts and administrative access.
Use our managed service, place Delegate inside your cloud, or run it on premises. Deployment location does not have to become the argument that stops the project.
The fastest path to production. We operate the platform while your team sets agent, data, network, approval, and spending policy.
Keep the enterprise control plane inside the cloud boundary, accounts, and operational model your organization already governs.
A containerized deployment keeps the application and database where policy requires them, including environments without a public marketing surface.
Enterprise deployment scope, infrastructure ownership, and operating responsibilities are defined during architecture review.
Security teams should not have to reverse-engineer a sales claim. These are the boundaries we expect you to test.
No. Secret values are write-only after entry. The credential broker adds them only to an approved outbound request and removes sensitive material before the response returns to the agent.
Yes. Workspace egress can use approved destinations, require approval for a new destination, or be disabled when the work does not need a network connection.
No. User roles and agent ceilings are separate. Effective agent access is the overlap between the agent’s configured ceiling and the authority of the person delegating the work.
Delegate records every platform-mediated human and agent action, including work-stream activity, approvals, role changes, workspace commands, and cost attribution.
Yes. Enterprise deployments can run in your GCP or AWS environment, or as a containerized on-premises deployment. Delegate is also available as a managed cloud service.
We’ll walk through permissions, secrets, network paths, evidence, and the deployment boundary with them.