Built to eliminate the preventable re-spin
Every netlist error that reaches the fab house was catchable. CADY exists to catch those errors earlier, automatically, every time.
Hardware review done manually is slow, inconsistent, and expensive
Every hardware team we spoke to had the same story: a senior engineer catches most netlist errors during review, but the process is manual, time-consuming, and catches different things on different days. When that engineer is busy, errors slip through. When a deadline is close, review gets compressed. The fab house does not run a rule check. The error ships.
Gilad and Noa built CADY in 2023 after years of writing static analysis tooling for embedded hardware systems and applying formal verification methods to netlist rule enforcement. They had the technical building blocks to make schematic review deterministic, and the firsthand experience of what it costs when review fails.
CADY does what a thorough senior engineer would do on every review: it evaluates every net, every component reference, every BOM entry against a comprehensive rule library. It does not get tired and it does not skip steps when a deadline is close. The goal is not to replace the engineer's judgment but to handle the mechanical layer so they can focus on the design decisions that actually require experience.
Every schematic gets the same rules applied in the same order with the same severity thresholds. No variability by reviewer or by day.
Catching a missing decoupling cap at commit time costs a comment. Catching it after the board comes back costs a re-spin, new components, and three weeks.
The 870+ built-in rules cover industry patterns. Your team's specific supplier restrictions, naming conventions, and component policies belong in custom rules you own.
The people behind CADY
A two-founder team, angel-backed, building out of Tel Aviv.
Spent years building static analysis and design-rule tooling for embedded hardware systems before founding CADY to automate schematic review. Gilad leads product direction, customer relationships, and the ongoing expansion of the rule library.
Brings formal verification methods and distributed systems experience to the problem of netlist rule enforcement. Noa architected CADY's rule evaluation engine and the analysis pipelines that make parallel rule execution feasible on large multi-sheet schematics. Leads core engine, API, and infrastructure.
Talk to the team
We reply to every message. If you have a question about the rule engine, a custom integration, or team pricing, reach out directly.