Architon catches voltage mismatches, power budget failures, and integration errors in your embedded designs - before you spin a board. Architecture checks for hardware.
Fails CI before fabrication when electrical limits are violated
KiCad and Altium verify that your copper is routed correctly. They don't know if your motor driver can handle the battery voltage you've chosen. That failure shows up at bring-up - after you've paid for boards.
ERC and DRC catch schematic and layout issues. Architon checks cross-component electrical assumptions before fabrication.
| Check | EDA ERC / DRC | Architon |
|---|---|---|
| Unconnected pins | ✓ | — |
| Copper clearance / layout rules | ✓ | — |
| Cross-component voltage compatibility | ✗ | ✓ |
| Power budget limits | ✗ | ✓ |
| Driver / load current headroom | ✗ | ✓ |
| CI failure before fabrication | Not native | ✓ |
Example: a 24V rail connected to a 5.5V-rated component may pass ERC/DRC, but Architon fails the scan before fabrication.
Rule coverage for the failure modes that destroy board spins and delay shipping.
Traces voltages from battery sources through regulators across your full netlist. Flags any net where a component's rated maximum is exceeded.
Validates H-bridge and DC motor driver configurations. Checks supply ranges, continuous and peak current, and logic voltage compatibility.
Aggregates current draw estimates per rail. Catches designs where total load exceeds regulator or source current limits before the hardware arrives.
Exit codes 0–3. Drop rv scan . into GitHub Actions and block merges on architecture violations, not just linting.
Reads .net and BOM exports directly. Auto-discovers project structure. Designed to run on real KiCad projects, not toy demos.
JSON violation output with net names, component refs, voltages, and margins. Parse in scripts, attach to design reviews, or feed into your own tooling.
No cloud. No account. Runs locally on your hardware project directory. No design data leaves your machine.
Install the rv binary via Go or download a pre-built release. Run rv scan . in any directory containing a KiCad .net file.
On first run, Architon auto-discovers your netlist and creates a .architon/meta.yaml pre-filled with your nets and component refs. You add voltage sources and component ratings - nothing Architon can't infer from your BOM.
Architon propagates voltages through regulators, checks each net against component max ratings, and applies rule modules for motors, power, and logic interfaces. No probabilistic inference. Same input → same output, every time.
Exit code 2 stops the build. Violations include net name, component reference, measured voltage, rated maximum, and margin. The team sees the failure before anyone orders boards.
The CLI core is open source forever. Paid tiers add AI-assisted explanations, team features, and priority parts coverage. Used on real hardware designs during development
Custom rule libraries for your component ecosystem, on-premise deployment, SSO, audit logs, and SLA-backed support. Pricing by seat volume or design-file throughput.
If your team is building robotics, EV, or industrial equipment - we want to work with you directly. 30-day evaluation for hardware teams building real systems.
No sales calls. No commitment. We'll reply within 48 hours.