Architon checks KiCad hardware designs for voltage, power, and interface mismatches before they become board re-spins.
Runs locally on KiCad project data and blocks architecture violations before fabrication.
Runs locally. No account required.
git clone https://github.com/badimirzai/architon-cli
cd architon-cli/examples
rv scan .Example hardware projects used for testing and demonstration.
Architon is built for architecture-level mistakes that can survive normal schematic and PCB checks.
Traces voltages from sources through regulators across your full netlist. Flags rails that exceed component input limits.
Checks module and logic-level assumptions so connected interfaces agree on voltage ranges and electrical limits.
Aggregates current draw estimates per rail. Catches designs where load or stall current exceeds regulator, source, or driver limits.
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.
Flags shared-bus integration issues such as address conflicts and incompatible assumptions between connected devices.
PCB DRC catches layout and manufacturing rule violations. ERC catches basic schematic electrical issues. Architon checks cross-component and cross-board integration assumptions before they become bring-up failures.
Architon complements KiCad, Altium, ERC, DRC, and SPICE by checking the system assumptions that sit above individual schematic, layout, and simulation views.
ERC and DRC remain necessary. Architon adds deterministic checks for cross-component and cross-board assumptions before fabrication.
| Check | EDA ERC/DRC | Architon |
|---|---|---|
| Unconnected pins | ✓ | — |
| Copper clearance / layout rules | ✓ | — |
| Cross-component voltage compatibility | ✗ | ✓ |
| Power budget limits | ✗ | ✓ |
| Interface and bus conflicts | ✗ | ✓ |
| CI failure before fabrication | Not native | ✓ |
Example: an MPU-6050 IMU and DS3231 RTC sharing address 0x68 can pass normal layout checks but fail during bring-up.
No cloud. No account. Runs locally on your hardware project directory. No design data leaves your machine.
Install the rv binary via Go. 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 skeleton for project-specific assumptions that cannot be inferred 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.