Which carrier actually fits this module?
Pick a module (or just a family) and the needs that matter — camera connectors, Ethernet, PoE, M.2, Wi-Fi, fanless, temperature range, price. The finder checks every carrier board, system, devkit and host SBC in the registry against each need and returns PASS, REQUIRES VALIDATION, FAIL or UNKNOWN — the worst check decides the verdict — with the vendor quote and link behind every field.
01 · Define search
Advanced
03 · How this works
Every field is a sourced fact, or it's UNKNOWN
Each carrier's specs come from the vendor's own product page, datasheet or a distributor listing, quoted verbatim with a link and an evidence class from A (vendor specification) to E (engineering heuristic). When a need isn't stated anywhere in the registry for a candidate, the check comes back UNKNOWN — not stated on the vendor page — never guessed — and an UNKNOWN check never counts as a fail.
MEETS vs. MEETS (unverified) vs. MISSES
MEETS means every need you set passed from a sourced fact. MEETS (unverified) means nothing failed, but at least one need is UNKNOWN — confirm it on the datasheet before you order. MISSES means at least one need failed outright. Candidates are ranked by fails first, then unknowns, so the closest match is always at the top even when nothing meets every need.
Near misses show exactly what to relax
When no candidate meets every need, the finder also looks for carriers that would pass if you dropped exactly one requirement, and names which one.
Full formulas, source list and what invalidates a result: methodology. Static tables: carrier boards by module.