Build Electronics With Confidence

Architon checks your schematic against real electrical limits before a single board gets fabricated - voltage rails, current margins, pull-ups, and the contracts between them.

  • Open source
  • AGPL-3.0
  • KiCad native
  • Runs in CI
See the failure in context
Architon Studio

Read the failure in context, not in a stack trace

Studio is a visual report viewer for rv scan output: the graph, linked findings, contracts, rails, components, raw JSON, provenance, and the fix Architon recommends.

Open Studio Preview
Full Architon Studio dashboard showing graph, findings, contracts, rails, components, and raw JSON tabs

See the failure before you spend money on a board

Run rv scan . locally or in CI. The CLI is the deterministic source of truth; Studio is the visual layer for reading the same report.

$ rv scan .
→ found KiCad project
→ extracting nets and BOM data
→ propagating voltage rails

info VBAT = 24.0V (source)
info +5V = 5.0V (U3 regulator out)

RULE_OVERVOLTAGE
component: U2 (AMS1117-3.3)
pin: VIN
net: 5V_USB
measured: 5.25V
allowed: 0V..5.00V
margin: -0.25V

1 violation found · exit code 2
# build blocked before fabrication
One engine, two ways to read it

rv CLI

The deterministic verification engine for local projects and CI. Runs scans, evaluates contracts, emits reports, and returns stable exit codes.

View the CLI on GitHub

Architon Studio

The visual report viewer for scan output, GraphIR, contracts, rails, components, and findings - measured values, margins, and recommended fixes.

Try Studio Preview

GitHub CI

Run rv in pull requests and review contract failures before hardware is fabricated - CI-ready output, annotations, and exit codes that block bad designs early.

Beyond ERC and DRC

System-level checks traditional tools miss

ERC and DRC check schematic and layout rules in isolation. Architon checks the contracts between parts of the system - the checks that only show up once current is actually flowing.

Available now
  • rv CLI
  • CI-friendly exit codes
  • JSON reports
  • GraphIR
  • Offline HTML reports
  • Studio v0.1 preview
Early access

We're looking for hardware engineers and embedded teams using KiCad, GitHub, or CI workflows who want to catch integration failures before fabrication.

Teams: early access includes a conversation about commercial licensing.

Your information is used only to follow up about early access. No spam.

Request received.

Thanks. We'll review the project context and reply by email.