The git wrapper
Sets the author, and does not let commits skip checks.
Security
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.
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
In the workspace (enforced here)
The git wrapper sets the author
DevBench server (enforced here)
DevBench's own commits follow the same rule
Your git provider (enforced here)
Shows whoever asked as the author
The owners
The audit log and the owners' Inbox
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
Whoever asked is the author. DevBench is added as co-author.
Read the detailThe agent can push only its workspace's own branch.
An owner can switch pushing off for a repo, or allow extra branches, such as release/*.
The workspace holds no GitHub or GitLab token. Clones and pushes go through DevBench.
Nothing is pushed from it. Chosen at creation and fixed afterwards.
Repos are checked out on the base branch. No branch is created or pushed.
push is refused for every repo and branch, tags included.
Refuses every push, whatever the workspace sends.
Opening and landing are both refused, with an audit entry.
The push step of a backup is skipped.
It reads code and writes reports only.
$ devbench doc create
$ devbench media put
$ devbench task add
$ devbench notify
Who sees what
Access follows a person's role and the workspace's assignees.
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.
Asking for someone else's workspace gets a plain “not found”. The same rule covers the code editor and the live chat.
Anyone on a workspace can change its assignees. Only team members can be added.
Repeated refused requests alert the owners.
A separate flag no role implies, not even owner. Only people who hold it can change an environment or a cloud account.
Every secret is encrypted with a key you generate. The API never returns one.
One key, yours. Generated by you.
Held by the organization. Shown by ID and account, never read back.
Checked before they are saved. Encrypted, never shown back.
Decrypted only for the command that uses them.
Checked on every connection. A changed key is refused until an owner trusts it.
Cloud calls go through DevBench, which refuses destructive changes unless granted.
Secrets stay encrypted in backups.
Treat a key like a password. Each workspace's key can be revoked on its own.
Credentials are checked again on a schedule. A key that stops working reaches the owners.
Where the agent's work ends and a person's decision starts.
| 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
Two kinds of data, two places.
Who you are, your organization, roles, keys and billing. Held in the EU.
Repos, chat, docs, media and previews. Held on DevBench compute in the EU, or on your own host.
| Data | At rest | Who can see it |
|---|---|---|
| Account data | In the EU, on encrypted storage | You and your owners; DevBench staff for support and billing |
| Workspace data on DevBench compute | In the EU, on encrypted storage | Your members by role. DevBench staff only when you ask for support. |
| Workspace data on your host | Your disk, your encryption, your backups | Your members by role. DevBench has no access |
| Provider tokens, cloud credentials, secrets | Encrypted at rest | Nobody through the API |
| Organization backups | Encrypted archives | Owners |
We reply within one working day. Do not test against organizations you do not own.
The same address is in it.
/.well-known/security.txtIf a breach affects your data, your owners hear from us within 48 hours.
Set up with you
We set up your factory with you and ship one project from your roadmap.