Certification intelligence for hardware

Know how hardware changes affect certification before you build.

Every engineering change becomes a traceable certification decision.

Runs in your environment · No data leaves your network
Crado Intelligence - Certification intelligence for FCC & global compliance | Product Hunt
Request pilot
DecisionsECR-2184
Export record

Increase antenna gain — 3 dBi → 5 dBi

MCMaya Chenopened 2 days ago·Rev C·RF-MAIN
Re-verification required
Change
Antenna gain — ANT-2.4G3 dBi5 dBi
SourceAltium · a91f2e
Files changed2
Certification impact · 3 requirements
FCC Part 15.247
§15.247(b)(3) · EIRP limit
Re-test required
RED EN 300 328
v2.2.2 · §4.3.2.2
Affected
ISED RSS-247
Issue 2 · §5.4
Unaffected
Decision
Re-verification required
Recorded by Crado · just now
Traced to 12 evidence sources
Activity
DR
Daniel Roth · 2h
Gain increase pushes EIRP past the previously certified margin. Re-test before fab.
AssigneeMCMaya Chen
ReviewersDRSRLP
LabelsRFantenna
Trusted ecosystem

Proud member of the NVIDIA Inception Program

Building AI infrastructure for regulated engineering.

Proud member of the NVIDIA Inception Program
The problem

Certification problems surface in the lab, weeks after the decision that caused them.

DAY 048121620DAY 24
Change shippedAntenna 3→5 dBi · no cert check
Lab failureFCC 15.247 · EIRP exceeded
24days
undetected
A certification-breaking change shipped on day 0. Nothing caught it until the lab — 24 days later, with a re-test booked and the launch slipping.
The solution

Every hardware change becomes an engineering decision.

Crado watches your engineering systems and evaluates each change as it lands — so the certification impact is known the moment the work happens, not in the lab.

Change appears
from Altium / Git
Crado
Crado evaluates
impact analysis
Decision recorded
evidence attached
Memory updated
trace retained
Decisions
AllRe-verifyApproved
IDChangeRequirementsOwnerDecisionAge
ECR-2291Antenna relocated +4.0 mmFCC 15.247MCMaya ChenRe-test required2h
ECR-2289Wi-Fi module → QCA6391FCC 15.247RED 300 328DRDaniel RothDeviation5h
ECR-2287Increase antenna gain 3→5 dBiFCC 15.247SRSam RiveraApproved · cond.1d
ECR-2284Reduce PCB stackup to 6 layers—LPLena ParkNo impact1d
ECR-2280Swap LDO regulator U7—TVTomás VidalNo impact2d
ECR-2278Relocate BT antenna feedRED 300 328PNPriya NairRe-test required3d
How it works

From change to certification decision.

Crado turns engineering context into traceable decisions before products reach the lab.

Jira
KiCad
GitHub
Capture engineering context
Crado connects to the systems where hardware work already happens.
ECR-2184changed
Antenna gain changed
3 dBi5 dBi
Source·Altium / Jira / GitHub
Understand the change
Crado identifies what changed, where it came from, and which product revision it affects.
Certification impact
FCC 15.247Affected
RED EN 300 328Affected
UKCAAffected
StatusRe-test required
Evaluate certification impact
The change is evaluated against certification requirements, product history, and evidence.
CradoEngineering Decision Record
Decision
Re-verification required
Evidence12 linked sources
TraceAvailable
ExportPDF / audit record
Record the decision
Every decision becomes a persistent, traceable engineering record.
The artifact

This is what your team receives.

Every evaluation produces a signed Engineering Decision Record — portable, auditable, and ready for your certification file.

Crado
Crado
Engineering Decision Record
EDR-2184 · REV C
Controlled · Northwind RF

Increase antenna gain — 3 dBi → 5 dBi

Re-verification required
Owner
Maya Chen · RF
Source
Altium · a91f2e
Opened
Mar 4, 2026
1
Change summary
Antenna ANT-2.4G gain raised from 3 dBi to 5 dBi on board RF-MAIN. The increase raises radiated power and affects emissions compliance.
2
Certification impact
FCC Part 15.247§15.247(b)(3) · EIRP limitRe-test required
RED EN 300 328v2.2.2 · §4.3.2.2Affected
ISED RSS-247Issue 2 · §5.4Unaffected
3
Evidence
12 sources
TR-0912 · EIRP scanFCC §15.247(b)(3)Antenna datasheet rev 2+9 more
4
Decision
Re-verification required before fabrication.
Computed EIRP of 38.1 dBm exceeds the certified 36 dBm limit by 2.1 dB. A confirmatory radiated-power test is required before release.
M. Chen
RF Engineer · Mar 4
D. Roth
Compliance Lead · Mar 5
Evaluated by Crado
sha256:7f3a…e1 · Mar 4
Page 1 of 3 · Generated by CradoExport PDF
Evidence

Every decision traces back to evidence.

Open any decision and follow the trace — from the requirement, through the governing clause, to the verified result.

Evidence trace/ECR-2184
Requirement
RF emissions within FCC limit
Regulation
FCC Part 15.247
Clause · selected
§15.247(b)(3) — EIRP ≤ 36 dBm
Evidence
Test report TR-0912
Verification
EIRP 38.1 dBm — over by 2.1 dB
Decision
Re-verification required
Clause text · FCC §15.247(b)(3)
“...the maximum EIRP shall not exceed 36 dBm. Systems using transmitting antennas of directional gain greater than 6 dBi shall reduce conducted output power accordingly.”
Test report TR-0912EMC Lab · Feb 2026
Certified
36.0 dBm
Computed
38.1 dBm
Margin
−2.1 dB
Trace verified · linked to decision EDR-2184
Workflow

Crado fits the tools your engineers already use.

A change discussed in Slack, a pull request, a swapped module — Crado picks it up and turns it into a routed, labeled certification decision for the right reviewer.

1.0Intake
Intake7
PCB-1487
BT antenna relocated 4 mm
FCC 15.247Re-test
FW-924
TX power raised +2 dBm
EIRP
ENC-1882
Enclosure material change
SAR
Evaluating3
RF-2088
2.4 GHz module swap
EMC
MECH-1028
Battery vendor change
UN 38.3
Cleared31
PCB-1402
Ground plane stitching
Passed
Thread in #hardware-eng
M
maya11:02 AM
Moved the BT antenna 4 mm to clear the new camera bracket. Should be fine mechanically.
D
daniel11:03 AM
That's close to the RF keep-out. Does it move our FCC margin?
@Crado evaluate certification impact
Send
CradoEvery source flows into Crado — evaluated automatically on every change.
Slack
Conversations
GitHub
Pull requests
Jira
Issues
Altium
PCB design
KiCad
PCB design
SolidWorks
CAD
MATLAB
Sim & analysis
PLM
Part data
Requirements
Specs & standards
Test reports
Lab results
Deployment

Built to run inside your environment.

On-premise
Runs entirely inside your network
Private cloud
Single-tenant VPC deployment
Air-gapped
Supported for classified programs
SOC 2 Type II
Independently audited controls
RBAC & SSO
Role-based access · SAML
Audit logs
Every action recorded
No model training
Your data never trains models
Data residency
No data leaves your network
FAQ

Frequently asked questions

The questions engineering and certification teams ask before running a pilot.

No. Crado does not make certification decisions with a language model. AI is used only to read and structure engineering documents — every regulatory decision is produced by a deterministic verification engine that follows explicit rules, references source evidence, and returns the same result every time.

Every conclusion traces back to the regulation, requirement, evidence, and engineering change that produced it.

Every result is backed by evidence. Crado never returns an answer without showing:

Affected requirementsApplicable regulationsSupporting evidenceVerification rules executedConfidenceDecision rationale

If evidence is missing or conflicting, Crado fails safely instead of guessing.

No. Crado works inside the workflow engineering teams already use. Engineers keep discussing hardware changes in Slack, Teams, or their existing process — Crado listens for engineering changes, analyses the impact, and returns structured certification guidance directly inside the conversation.

No new workflow is required.

Crado is built for regulated hardware industries. Examples include:

FCC Part 15CE / REDUKCAETSIIEC 62304ISO 26262DO-160GUN 38.3

It is built around structured knowledge rather than hard-coded checklists, so organisations can extend it with internal standards and proprietary engineering requirements.

Crado complements existing engineering tools — it doesn't replace them. It ingests requirements, specifications, test reports, certification documents, and engineering changes from your existing workflow, then produces traceable impact analysis and evidence packages for engineering and certification teams.

The goal is to remove weeks of manual impact analysis without changing how teams build products.

Crado

Engineering decisions deserve evidence.

Request pilot