You decide who gets which device.
Write down which devices each project may claim, which claims need a person to sign off, and who that person is. Anything you didn’t allow is refused.
Device policy
Write down which devices each project may claim, which claims need a person to sign off, and who that person is. Anything you didn’t allow is refused.
- Can claim
- ARM and ESP32 boards, probes
- Needs approval
- ARM dev boards
- Approver
- firmware leads
- Security keys
- payments project only
- TPMs
- not allowed
- Anything else
- refused
- Devices
- Security keys, TPMs, debug probes, boards
- Claims
- One run at a time; released when the run ends
- Hosts
- Your Linux and macOS machines, over mutual TLS
- Audit
- Every claim, approval and release recorded
How it works
What happens, in order.
01Allow
Name the devices a project may claim.
02Require sign-off
Mark the ones that need a person, and name who.
03Refuse the rest
A claim for anything else is refused and recorded.
Which plans
Lab hosts come with Team and 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