Who can start, see and stop what.
Give people Viewer, User, Editor or Manager on each sandbox, template and project. Whoever starts a sandbox owns it.
Roles
Give people Viewer, User, Editor or Manager on each sandbox, template and project. Whoever starts a sandbox owns it.
WhoRoleBecause
maya@acme.devManagerstarted it
payments projectUserproject members
lee@acme.devEditorshared by maya
- Roles
- Viewer, User, Editor, Manager
- On
- Sandboxes, templates, workspaces, projects
- Lists
- People only see what they can use
- Audit
- Every grant and decision recorded
How it works
What happens, in order.
01Own
The person who starts a sandbox is its Manager.
02Share
Share it with people or a project at the role they need.
03Ask
Request access, and someone other than you approves it.
Which plans
Roles and groups come with Team. Custom roles come with Enterprise.
See pricing →Give every agent
a box of its own
Start free with 100 vCPU-hours a month. Upgrade when your agents need more.
A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI