Preserve hardware evidence for every release.
Every Embroid validation run produces a self-contained record — firmware hash, target device, operator, commands, logs, assertions, artifacts, result — suitable for release review, customer support, regulated workflows, and regression history.
The proof should be captured by the run — not reconstructed after it.
Teams that care about release quality end up writing the same evidence captures over and over: what firmware, what target, what commands, what logs, who signed off. Embroid bakes that into every session, so the record exists whether anyone thought to capture it or not.
The record is a side effect of the run — not a separate artifact anyone has to remember to produce. Firmware hash, device, operator, commands, logs, assertions: all captured automatically, all signed, all exportable.
What an evidence record contains.
Every run produces the same fields in the same shape. Reviewers learn the format once; every release looks familiar.
Firmware hash, build metadata, and target device identifiers so you know exactly what ran.
Operator or system actor (human, CI, or agent) — whoever initiated the run.
When the session started, when it ended, and the time-ordered sequence of every verb in between.
Every flash, reset, power, serial, and accessory call, in the order they ran.
Serial logs, power traces, screenshots, and any other data the sequence produced.
Each declared check with its pass/fail result and the matching log or signal.
Exit status of the session — passed, failed, or flagged — with a human-readable summary.
Who reviewed the record and whether they approved, rejected, or deferred the release.
A real validation record.
This is what an Embroid evidence record looks like on disk. Pin it to a release tag and you have reproducible proof of what was validated and how.
{
"evidence_id": "ev_7f21",
"firmware_sha256": "c4a1...",
"target": "nrf52-04",
"product": "Embroid Basic",
"actor": "ci@acme",
"started_at": "2026-04-20T14:03:17Z",
"commands": ["flash", "power.cycle", "serial.assert"],
"assertions": [
{ "rule": "boot_ok=1", "result": "passed" }
],
"artifacts": ["serial.log", "session.json"],
"result": "passed"
}Evidence on every product.
Evidence capture is built into every run on every product. The scope scales with the product.
Exports local evidence from bench sessions. Great for individual developers and agent-driven loops.
Preserves session history on the node; syncs selected records to cloud on request.
Aggregates evidence across devices, jobs, and operators; integrates with formal release workflows.
Signed, append-only, and verifiable.
Evidence is only as useful as it is trustworthy. Embroid treats each record as a ledger: events append in order, artifacts bind to content hashes, and the final export is signed so downstream reviewers can verify that nothing was altered after the fact.
- Records are append-only within a session — the timeline is tamper-evident by construction.
- Each exported record is signed, so downstream reviewers can verify provenance.
- Artifacts are referenced by content hash, not just filename, to detect silent drift.
- Local-first operation: the record exists on the node whether or not cloud sync is enabled.
How evidence supports the rest of your workflow.
One record format, many uses downstream.
CI and PR gating
Attach an evidence record to every CI run. A reviewer sees what firmware flashed, which assertions passed, and which failed — without digging through CI logs.
Release review
Pin a record to a release tag. Anyone reviewing the release sees the exact hardware session that validated it.
Customer support
Hand a support record to a customer or internal escalations team — commands, logs, and outcome in one file.
Compliance workflows
Record structure aligns with CRA / FDA-style device-validation expectations. Embroid preserves evidence; your team maps it to your compliance framework.
Turn every hardware validation run into release evidence.
Tell us about your release process. We'll help you build the evidence workflow your reviewers and auditors are already asking for.