Skip to content

Security

Agents build. People approve.

Agents cannot push to protected branches, and a secret's value is never shown back. A person approves each merge unless an owner has allowed self-merge.

The promises are in the code.

Choose a rule to see where it is enforced.

Model-agnostic on purpose. Nothing here depends on which model the agent uses.

01 of 7 promises

Where it is enforced

Enforced at: In the workspace, DevBench server, Your git provider.

In the workspace (enforced here)

The git wrapper sets the author

DevBench server (enforced here)

DevBench's own commits follow the same rule

The owners

The audit log and the owners' Inbox

Your git provider (enforced here)

Shows whoever asked as the author

Every commit is authored as the person who asked for it.

Whoever asked is the author. DevBench is added as co-author.

Read the detail

Authorship

Every commit is by the person who asked for it.

One rule, for every commit.

  1. 1

    The author is the person who asked

    Whoever asked, by message, button or schedule.

  2. 2

    Every other co-author is removed

    Any other co-author line goes.

  3. 3

    DevBench is added as co-author

    Exactly once. DevBench stays the committer.

Every commit in a workspace

One rule for every commit

Author
The person who asked
Committer
DevBench
Co-author
DevBench, exactly once
Any other Co-authored-by:
Removed
The author line says whose work it is.

Where it is enforced

The git wrapper

Sets the author, and does not let commits skip checks.

A message check

Catches messages the wrapper cannot read, such as ones from an editor.

DevBench's own commits

Commits DevBench makes follow the same rule.

Merge request descriptions

Credit lines are removed.

A person keeps their own name. Committing from the workspace terminal keeps it too.

Refused in the workspace. Refused again on the server.

The agent can push only its workspace's own branch.

  1. 1. The agent pushes its own branch. Both checks let it through.
  2. 2. It tries to push to main. The workspace refuses.
  3. 3. Even past that check, the DevBench server refuses it again.
  4. 4. A person reads the merge request and merges it. That is the way into main.

Owner-edited

An owner can switch pushing off for a repo, or allow extra branches, such as release/*.

No token in the workspace

The workspace holds no GitHub or GitLab token. Clones and pushes go through DevBench.

For work that reads code and never changes it.

Nothing is pushed from it. Chosen at creation and fixed afterwards.

  1. 1. The agent reads the code: an audit, a review, an investigation.
  2. 2. Anything that would change code is refused: pushes and merge requests.
  3. 3. What it found becomes a report.
  4. 4. The team reads it as a doc.
  1. The clone

    Repos are checked out on the base branch. No branch is created or pushed.

  2. The git wrapper

    push is refused for every repo and branch, tags included.

  3. The server check

    Refuses every push, whatever the workspace sends.

  4. Merge requests

    Opening and landing are both refused, with an audit entry.

  5. Backups

    The push step of a backup is skipped.

The agent is told, too

It reads code and writes reports only.

what it may write
  • $ devbench doc create

  • $ devbench media put

  • $ devbench task add

  • $ devbench notify

Who sees what

Access is checked before any data loads.

Access follows a person's role and the workspace's assignees.

Show the access of

Can manage deployments

A separate flag that no role implies, not even owner.

Members reach only the workspaces they are assigned to, plus any they created.

CapabilityOwnerMaintainerMember
Workspaces
Every workspace in the organizationYesYesNo
The workspaces they are assigned to, plus any they createdYesYesYes
Change the assignees of a workspace they are onYesYesYes
The organization
Roles, API keys and organization settingsYesNoNo
Edit a repo's push guardrailsYesNoNo
Switch on self-merge for a workspaceYesNoNo
Approve a changed server keyYesNoNo
Organization backupsYesNoNo
Alerted on repeated refused requestsYesNoNo
Deployments
Deploy a previewYesYesYes
Cloud accounts, recipes, seed data and environmentsOnly with Can manage deploymentsOnly with Can manage deploymentsOnly with Can manage deployments
Deploy or stop anywhere but DevBench computeOnly with Can manage deploymentsOnly with Can manage deploymentsOnly with Can manage deployments

Not found, not forbidden

Asking for someone else's workspace gets a plain “not found”. The same rule covers the code editor and the live chat.

Assignees

Anyone on a workspace can change its assignees. Only team members can be added.

Refusals reach an owner

Repeated refused requests alert the owners.

Can manage deployments

A separate flag no role implies, not even owner. Only people who hold it can change an environment or a cloud account.

Encrypted at rest, never read back.

Every secret is encrypted with a key you generate. The API never returns one.

One key, yours. Generated by you.

  1. 1. The agent tries to open the secret file. The guard refuses and names the variables it holds instead.
  2. 2. It runs its tests through devbench secrets run.
  3. 3. The vault hands the values to that one command, not to the agent.
  4. 4. The output comes back with each value replaced by its name.
  1. 1. Someone pastes a live key into the chat.
  2. 2. Before anyone sees the message, the key is saved in the vault, encrypted.
  3. 3. The message is posted with the key's name in its place.
  4. 4. The agent sees only the name, and uses the key by name.

Cloud credentials

Held by the organization. Shown by ID and account, never read back.

Git tokens

Checked before they are saved. Encrypted, never shown back.

Credential profiles

Decrypted only for the command that uses them.

Host keys are verified, not accepted

Checked on every connection. A changed key is refused until an owner trusts it.

The workspace never holds cloud keys

Cloud calls go through DevBench, which refuses destructive changes unless granted.

Backups stay encrypted

Secrets stay encrypted in backups.

API keys are your account

Treat a key like a password. Each workspace's key can be revoked on its own.

Failures reach the people who can act

Credentials are checked again on a schedule. A key that stops working reaches the owners.

What an agent may do.

Where the agent's work ends and a person's decision starts.

What an agent may do, beside what a person may do
Action An agent A person
Push the workspace's own branch
YesYes
YesYes
Push a protected branch
NoRefused in the workspace and on the server
Through a merge request or a release
Open a merge request
YesYes
YesYes
Merge
NoOnly if an owner allows self-merge; then logged and announced
YesYes
Deploy a preview on DevBench compute
YesYes
YesYes
Deploy or stop an environment
NoNo
With Can manage deployments
Push anything out of an info-only workspace
NoNo
NoNo
Read a stored secret back
NoNo
NoNot through the API
Author a commit as itself
NoCommits are by the person who asked
YesFrom the workspace terminal, with their own identity

Trust

Where your data is, and who can reach it.

Full terms are on the privacy, terms and DPA pages.

Hosting model

Two kinds of data, two places.

Account data

Who you are, your organization, roles, keys and billing. Held in the EU.

Workspace data

Repos, chat, docs, media and previews. Held on DevBench compute in the EU, or on your own host.

Where each kind of data is at rest, and who can see it
DataAt restWho can see it
Account dataIn the EU, on encrypted storageYou and your owners; DevBench staff for support and billing
Workspace data on DevBench computeIn the EU, on encrypted storageYour members by role. DevBench staff only when you ask for support.
Workspace data on your hostYour disk, your encryption, your backupsYour members by role. DevBench has no access
Provider tokens, cloud credentials, secretsEncrypted at restNobody through the API
Organization backupsEncrypted archivesOwners
Isolation
Each workspace runs in its own container. No provider token is kept in it.
Audit
Every action is logged with who, what and when. Self-merges are announced.
Staff access
Named staff only, and logged. Support access only when you ask.
Subprocessors
Listed in the privacy policy. DPA customers hear of changes 30 days ahead.
Retention
Account data 30 days after the account closes. Workspace data on DevBench compute until the workspace is deleted. Invoices for as long as tax law requires.
Location
Vesprr LLC is a US company. Account data and DevBench compute are held in the EU.

If there is a breach

If a breach affects your data, your owners hear from us within 48 hours.

Set up with you

Start with one real project.

We set up your factory with you and ship one project from your roadmap.