Probe - Design review that reads your datasheets, not just your netlist
A netlist check only confirms the board matches the schematic you drew — not that it does what you intended. Probe reads each part’s datasheet against the netlist and BOM, and catches the functional errors that pass ERC and DRC. Every finding cited to the data.
Why teams ship faster
An intent error that slips through review shows up at bring-up — where the fix is a respin and weeks of schedule. Probe puts those errors on screen during review, pre-layout if you want, so they’re caught while a fix is still an edit, not a spin.
Ask the board
The review runs through an AI assistant over MCP: you ask in plain language, Probe answers from the real board data, and shows the net or finding behind the answer as proof. You’re not clicking through a viewer — you’re querying the design.
Answers are traced, not guessed. Probe cites the netlist line, layout location or datasheet value it drew from, and where it can’t back a claim it says so. Citations are checked verbatim, and a claim the data can’t support is refused at the write boundary — not dressed up as a guess.
What Probe catches
Ten findings from our own boards. Every one passes DRC, ERC and a netlist check against the schematic — each looks locally correct. The error only shows when two facts from different places are put side by side.
A rule checker knows the rules of the board. Probe reads the parts.
See the technical documentation.
Evidence, not opinion
Review findings today are opinions that get lost in email — Probe makes them cited facts that stay. A finding carries its proof: the netlist line, the layout location, the datasheet value. The engineer who has to fix it verifies it in one click instead of re-deriving it.
And where Probe can’t ground a claim in the board’s data, it says so rather than guessing — an abstention you can act on beats a confident answer that’s wrong.
Across designs
A finding is worth more than the meeting it was raised in — but that’s usually where it dies, in a thread or a PDF margin, gone by the next project. Probe keeps findings as cited facts attached to the net and the component they concern.
A note stored on a part is inherited by every future board that carries it — so the next review starts from what the last one already found, not from zero.
open the design
A viewer shows you shapes; Probe knows what they’re connected to. Cross-probe a net from the schematic to the layout and back, follow it through connectors and planes, and search the whole design. Viewing is free — no CAD seat to look.
Any ECAD that exports ODB++ works. Verified on these; other exporters too — tell us your tool and we’ll confirm it.
