Control real devices from anywhere in your workflow.
Flash, reset, switch power, read serial, and toggle GPIO from a local UI, CLI, MCP, or REST API — on your bench or across a lab.
Every hardware workflow depends on the same few verbs.
Flash, reset, power, serial, GPIO. Most teams re-implement them for each bench, each CI pipeline, each lab. Embroid collapses them into one typed surface so the same verb behaves the same way whether a person, a script, or an agent runs it.
What you get
- Flash firmware
- Reset targets
- Switch power
- Cut USB power
- Read serial
- Toggle GPIO
- Run vendor tools
- Trigger accessories
- Recover wedged devices
Recover a wedged board.
A stuck target is the worst place for ad-hoc scripts. With Embroid, recovery is a sequence you can run, automate, and share.
- 01Reserve the device with a short lease so nothing else touches it.
- 02Cut USB power to the target.
- 03Switch the external DC rail off.
- 04Wait five seconds for rails to fully drain.
- 05Restore USB and DC power.
- 06Flash a known-good recovery firmware.
- 07Stream serial logs and assert that the boot marker appears.
- 08Mark the session as recovered or failed, and export the evidence record.
$ embroid devices list $ embroid lease create device-04 --duration 20m $ embroid power cycle device-04 $ embroid flash device-04 ./firmware.bin $ embroid serial tail device-04 --assert "boot_ok=1"
Which product do you need?
Device control runs on all three products — choose based on how the bench lives.
Drives the hardware your workstation is already attached to. Great for personal benches and evaluation.
Adds a dedicated always-on node with switched USB, switched DC, and GPIO triggers for one bench.
Scales to multiple targets, 4 UART/debug channels, 8 GPIO lines, and accessory expansion for labs.
Safe by default — for humans, agents, and CI.
Every control verb runs under a scoped permission set and an explicit lease. Audit logs capture who ran what against which device, when, and with which firmware hash. Local-first operation means nothing leaves the host unless you opt in.
- Scoped permissions — agents and CI jobs only see the verbs they're granted.
- Exclusive leases — no two actors can drive the same device at the same time.
- Binary validation — firmware hashes are recorded before every flash.
- Audit log — who, what, when, and which device, preserved locally.