Define agent permissions as code

Credentials scoped below any developer and revoked at teardown, zero source code retention, and an audit trail for every action. Security your team can verify, not take on trust.

01

Scoped credentials, revoked at teardown

Every session gets its own credentials: a GitHub token limited to the permissions and repos you allowed and an API token scoped to that session, all revoked when the sandbox is torn down. GitHub enforces the scopes at the token mint, so nothing in the sandbox can exceed them.

Sandbox credentialssession #1842
GH_TOKEN
scoped to web-repo, api-repo
ANTHROPIC_API_KEY
synthetic key, valid for this session only
ELLIPSIS_API_TOKEN
scoped to this session
All credentials revoked at teardown

Permissions minted per session, enforced by GitHub

02

Every action, logged and visible

Zero source code retention: your code exists only inside a session’s sandbox and is deleted when the sandbox is torn down. Every agent action is logged and auditable, so security is something your team can verify, not take on trust.

What Ellipsis stores
Stored
  • Session logs and transcripts, with retention you set
  • A config snapshot per session
  • Cost and token counts per session
Never stored
  • Your source code
  • Repos are cloned into the sandbox
  • Deleted when the sandbox is torn down

The transcript outlives the sandbox, the code does not

03

SOC 2 certified, audited controls

Ellipsis is SOC 2 Type 1 certified, with Type 2 in progress. Controls cover security, availability, and confidentiality. Request our report at team@ellipsis.dev.

SOC 2audited controls
Type 1Certified
Type 2In progress
SecurityAvailabilityConfidentiality
Request the report: team@ellipsis.dev

Security, availability, and confidentiality controls

The full control surface

Everything the platform enforces for you, so governance is not each developer’s job.

Scoped GitHub tokens

Minted per session, narrowed to the repos and permissions in the agent config, enforced by GitHub.

One-hour credentials

Every sandbox credential expires or is revoked when the sandbox is torn down.

Write-only secrets

Stored values inject into allowed sandboxes and can never be read back out.

Attribution

Every session is tied to a person, an API key, or a parent session.

Full transcripts

Every turn, tool call, and diff is recorded and searchable, with retention you control.

Audit log

Account, installation, and billing events on record.

Zero source retention

Code exists only inside a session sandbox and is deleted when the sandbox is torn down.

SOC 2 Type 1

Certified, with Type 2 in progress. Request the report at team@ellipsis.dev.

Self-host in your VPC

Deploy into your AWS account so credentials, code, and LLM calls never leave it.

Bring your own models

Route tokens through your own Anthropic key or your AWS Bedrock account.

Frequently asked questions

Explore the platform