Your lab hardware, within reach of your agents

Connect Linux and macOS machines with the devices plugged into them. A run claims a device, a person approves when policy says so, and it’s released when the run ends.

Lab hosts › lab-bench-02Devices · Policy

lab-bench-02

A Linux machine on a desk in the firmware lab, with six USB devices plugged in. It reports what is connected every few seconds.

Devices
DeviceTypePortState
key-01Security keyusb 1-2Free
key-02Security keyusb 1-3Held by run_31c
tpm-01TPMusb 1-4Free
probe-01Debug probeusb 2-1Free
arm-dev-03ARM dev boardusb 2-3Waiting for approval
esp32-07ESP32 boardusb 2-4Free
Claude Code wants arm-dev-03 to flash the bootloader and run the hardware tests
Needs approval from Dana K.DenyApprove
Host
lab-bench-02
OS
Linux
Connection
Mutual TLS
Heartbeat
4 s ago
Devices
6, 1 held
Projects
firmware
Approver
Dana K., firmware leads
Owner
acme, on site

Some tests need real hardware. Lab hosts connect your own Linux and macOS machines, with the security keys, TPMs, debug probes and boards plugged into them, so an agent’s run can use a device and give it back.

FIG 0.1One device, one run

When a run claims a device nothing else can use it until the run ends.

FIG 0.2A person signs off

Your device policy decides which claims need approval and who gives it.

FIG 0.3Your machines stay yours

Bench PCs, Macs, the box under a desk. They stay where they are.

One board, one run,
until it’s done

A run claims a device for itself. If policy says so, a person approves the claim first. When the run ends the device goes straight back to the pool, and every step is in the audit log.

arm-dev-03 › Claim historyHash-chained
TimeWhoActionTarget
10:14:02Claude Code as mayadevice.claim.requestedarm-dev-03
10:14:40Dana K.approval.grantedarm-dev-03 for run_44a
10:14:41Sandscaledevice.claimedarm-dev-03 → run_44a
10:21:09Claude Code as mayaexecmake flash && make hwtest
10:26:55Sandscaledevice.releasedarm-dev-03, run ended

You decide who
gets which device

Write down which devices each project may claim, which ones need a person to sign off, and who that person is. Anything you didn’t allow is refused. A lab machine joins with one command.

How we secure it →
Device policy › firmware
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
Join a lab machine
01$ sandscale lab join --name lab-bench-02
02connecting with mutual TLS …
03joined acme as lab-bench-02
04found 6 USB devices
05 key-01 key-02 tpm-01 probe-01 arm-dev-03 esp32-07
06heartbeat every 4 s

Included in
your plan

Lab hosts come with Team and Enterprise. Windows isn’t supported yet.

Tell us about your lab →
Free and Pro
Not included

Sandboxes, workspaces and build hosts.

Team
Lab hosts

Your lab machines, with device policy, approvals and the audit log.

Enterprise
Lab hosts

The same, with your own encryption keys and dedicated capacity.

Put the hardware on your desk
within reach of your agents

Lab hosts are part of Team and Enterprise.

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