BranchSlate
TRUST / SECURITY

Explicit boundaries. Attributable work.

Security controls are part of the core workflow, not a layer added after agent automation.

Beta service · updated October 6, 2026

Separate principals

Humans use Better Auth sessions. Agents use scoped bearer credentials. Agents are never represented as human users, and human-only administration and approval settings cannot be changed with an agent credential.

Organization and project boundaries

Organization membership is checked server-side. Agent project membership and action scope are checked independently. Cross-organization references are rejected. Role changes preserve at least one owner.

Credential handling

Agent tokens and invitation tokens are hashed at rest. Credentials are shown once, expire, can be rotated, and are invalidated on revocation. Production sessions use secure, HTTP-only, SameSite cookies. Auth and API requests are rate-limited.

Observable changes

State mutations and corresponding audit events are written in the same database transaction. Approval decisions retain a human actor and reason. Git merges only the exact proposed revision after required checks pass. Deployment is a separate operation.

Execution and storage

Production stores application records in PostgreSQL and repositories in Git. External fetches use an operator host allowlist, public address checks and bounded subprocesses. Customer verification runs through authenticated runners.

Current assurance

The beta service has no compliance certification, uptime SLA, penetration-test attestation or enterprise SSO. Report account or security concerns through the support page without including secret credentials.