Skip to content
Join the waitlist
Join the waitlist

Compliance, inside the engineering loop.

Crado is the evidence layer for regulated hardware. It keeps every test result, design change and regulation tied to the product revision it belongs to.

Join the waitlistRead how it works
OBSERVED

It reads.

Every value Crado reads from a report shows its page.

KNOWN

It checks.

Margin is measured minus limit, from a versioned rule set.

INFERRED

Agents investigate.

Read reports, organise the evidence, propose likely causes with their evidence.

MISSING

Unknown stays unknown.

Each likely cause lists the evidence for it and the facts it still needs.

No guaranteed passes. No certification determinations. Unknown stays unknown.

How Crado works, in three lines.
How often the design changesHow often the evidence is checkedThe evidence gapTIME

Hardware compliance, as practised today, is falling behind. Products change every sprint: firmware, layouts, suppliers. The evidence that shows they still meet the rules changes a few times a year, in a lab, in a PDF. The knowledge that connects the two lives in email threads, spreadsheets and one engineer's memory. The result is retests nobody planned, fixes nobody can trace, and new designs that repeat old failures.

Crado is building the evidence layer for regulated hardware: one record between your engineering team and the regulations your product must meet.

It reads. It checks. It remembers. Agents organise the evidence, rules check the numbers, and your engineers make every decision.

How it works

A record your engineers can check

Your engineers
Set priorities, confirm facts, make every decision.
Crado agents
Read reports, organise the evidence, propose likely causes with their evidence.
Crado rules engine
Checks measurements against the regulation, with the citation and rule version recorded. Same input, same result.
Your product record
Revisions, test reports, changes and regulations, in one place.
Reads lab reports today (PDF, TXT, Markdown). Email, team chat and change tickets: ROADMAP.
The vision

Every change should arrive with its evidence.

Engineers should design, test and decide. Finding out what a change did to the evidence should not take a week of searching.

The record

A record that follows the revision.

Every report, confirmed fact, likely cause and change is filed with the product revision it belongs to, so the next one starts from what the last one learned.

The boundary

Agents investigate. Engineers decide.

In a regulated product, a confident wrong answer costs more than no answer. Agents propose and cite, a deterministic engine does the arithmetic, and nothing is marked known until a person confirms it.

In the product

Confirm what was read.

Every value Crado reads from a report shows its page. Nothing counts as known until you confirm it.

Numbers from rules, not prose.

Margin is measured minus limit, from a versioned rule set.

See what is still missing.

Each likely cause lists the evidence for it and the facts it still needs.

Example workspace
Agents

One record. Agents for every stage.

Specialist agents that each own one part of the compliance work. Every output cites its evidence.

  • LIVEWhen a test fails

    EMC investigator

    Ranks likely causes of a failed radiated-emissions test, each with its evidence, and suggests the next test.

    "Why did Rev D fail at 144.2 MHz?"
  • ROADMAPBefore a change

    Change reviewer

    Shows which evidence and certifications a design change touches.

    "What does ECO-214 do to our FCC evidence?"
  • ROADMAPBefore a retest

    Retest planner

    Proposes the smallest set of checks that settles an open question.

    "What would settle the 96 MHz risk?"
  • ROADMAPWith the lab

    Lab liaison

    Keeps test plans, samples and lab threads in step with each revision.

    "What did we agree with the lab about the cable?"
  • ROADMAPBefore review

    Compliance writer

    Drafts review packages for engineers to check and approve.

    "Draft the Rev E review package."
  • ROADMAPAfter shipping

    Evidence auditor

    Finds evidence that went stale after a change, before an auditor does.

    "Which Rev D results no longer apply to Rev E?"
Coverage

What Crado checks today

RegulationScopeMeasurementStatus
47 CFR 15.109(a)Class B, 3 mRadiated emissions, quasi-peakLIVE
47 CFR 15.109(b)Class A, 10 mRadiated emissions, quasi-peakROADMAP
EU EMC and Radio Equipment DirectivesRadiated and conducted emissionsPer harmonised standardROADMAP
EU Machinery Regulation 2023/1230Substantial modificationChange assessmentROADMAP
RTCA DO-160Qualification by similarityEnvironmental test evidenceROADMAP

Crado refuses a comparison when the test distance or detector does not match the limit.

The vision

Every change should arrive with its evidence.

Engineers should design, test and decide. Finding out what a change did to the evidence should not take a week of searching.

The record

A record that follows the revision.

Every report, confirmed fact, likely cause and change is filed with the product revision it belongs to, so the next one starts from what the last one learned.

The boundary

Agents investigate. Engineers decide.

The boundary

In a regulated product, a confident wrong answer costs more than no answer.

Agents propose and cite, a deterministic engine does the arithmetic, and nothing is marked known until a person confirms it.

FAQ

Before you trust Crado with your evidence

What engineering teams ask first.

No. Crado reports the margin to the limit and ranks likely causes. The decision stays with your engineers and your lab.

Bring us your next design change.

Join the waitlist. We invite engineering teams in small groups, starting with one of your own test reports.

Join the waitlist