Embroid
Platform · Automation

Turn hardware steps into repeatable workflows.

Run sequences locally, add a queue for shared hardware, and trigger the same workflow from CI or from an agent.

Automation makes hardware work repeat itself — so the same flash, reset, and validate sequence that worked on the bench runs the same way on every PR and every nightly build.
Why it matters

Manual device work is where reliability goes to die.

The firmware that worked on someone's desk rarely works the same way on everyone else's. Sequences, leases, and assertions make the same workflow run the same way everywhere — local bench, shared lab, CI pipeline.

Capabilities

What you get

  • Sequences
  • Job queues
  • Resource locks
  • Leases
  • Retries
  • Assertions
  • Scheduled runs
  • CI triggers
  • Agent-triggered runs
  • Nightly validation
Example workflow

CI validation on a real device.

A pull request triggers a real-device run. The workflow is the same one you ran on your bench — just executed on Embroid-managed hardware.

  1. 01Pull request opens and CI builds firmware.
  2. 02CI requests an Embroid device lease.
  3. 03Embroid flashes the target with the new build.
  4. 04Embroid runs the validation sequence.
  5. 05Serial logs and assertions are captured as the run progresses.
  6. 06An evidence record is attached to the CI run.
  7. 07CI passes, fails, or flags for human review.
  8. 08The lease is released and the device returns to the queue.
# .github/workflows/hardware-ci.yml
- uses: embroid/actions/lease@v1
  with:
    device-tag: "nrf52-ci"
    duration: "10m"
- run: embroid flash $EMBROID_DEVICE ./firmware.bin
- run: embroid sequence run boot-smoke.yaml
- uses: embroid/actions/export-evidence@v1
Product support

Which product do you need?

All three products run the same sequence model. Choose based on where the automation lives.

Embroid Client

Great for local sequences and experiments. CI works if a developer is at the laptop.

Embroid Basic

Good fit for one always-on CI bench with a local job queue and a single active lease.

Embroid Pro

Built for shared validation labs — scheduler, resource locks, and parallel workflows across multiple targets.

Security & audit

Jobs run inside typed permissions and explicit leases.

Sequences declare which device verbs they need and which targets they touch. Queues coordinate leases so two jobs never fight for the same device. Every run produces an audit trail.

  • Typed verbs — sequences can only call permissions their lease includes.
  • Retry and recovery paths are declared in the sequence, not improvised in CI.
  • Every run record ties firmware hash, target, operator, and assertion results together.
Related

Where automation shows up

CI hardware testing

Validate firmware on real devices in CI.

Firmware bring-up

Turn first-boot steps into a replayable sequence.

Shared lab management

Coordinate many jobs on shared hardware.

Platform

Automate a hardware workflow end-to-end.

Automate a workflowSee CI integrationLogin →