Credentials stay outside the sandbox
Agents run in sandboxes that do not hold your provider credentials.Encryption
- Integration tokens and API keys are encrypted with AES-256-GCM before storage, with a fresh random nonce for each encryption.
- Database storage and application logs use managed encryption keys with rotation enabled.
- Public traffic and database connections require TLS.
Short-lived cloud access
- AWS uses temporary credentials from an IAM role in your account. An explicit deny blocks secrets, SSM parameters, and KMS decryption.
- Google Cloud uses Workload Identity Federation. No service account key is created or stored.
- The roles you create define the access boundary.
Isolated runs
- Every automation, integration, secret, run, and member belongs to one workspace. Queries and API routes enforce that ownership.
- Each run gets its own sandbox. Sandboxes are never shared across workspaces.
- Each run keeps the exact automation configuration it started with.
Limited tools
- Most built-in integrations expose only read-only tools. Write actions are limited to opening pull requests, posting to Slack, and creating Linear issues.
- Datadog and custom MCP servers pass their tools through. Scope the credentials you give them.
- Custom MCP servers must use HTTPS and resolve to public addresses. Authorization is never forwarded across origins.
- Agents treat trigger events as untrusted input.