Catch hardware integration failures before fabrication

The deterministic verification layer between your schematic and your first board spin.

Run rv locally or in CI, then review graph-linked failures in Architon Studio.

Try Studio Preview View CLI on GitHub
  • Open source
  • AGPL-3.0
  • KiCad native
  • Schematic in, truth out
Architon Studio graph with a selected failing hardware node and linked findings panel
CLI Proof

Block the failure before the board is built

Run rv scan . locally or in CI. The CLI is the deterministic source of truth, and Studio is the visual review layer for 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
Studio Preview

Visualize failures in context

Studio is a static visual report viewer for rv scan output. It shows the graph, linked findings, contracts, rails, components, raw JSON, provenance, and recommended fixes.

Open Studio Preview
Full Architon Studio dashboard showing graph, findings, contracts, rails, components, and raw JSON tabs
One deterministic engine. Two ways to review.

rv CLI

Deterministic verification engine for local projects and CI.

Runs scans, evaluates contracts, emits reports, and returns stable exit codes.

View CLI on GitHub

Architon Studio

Visual report viewer for scan reports, GraphIR, contracts, rails, components, and findings.

See exactly where and why a design fails with 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

Traditional ERC and DRC check schematic and layout rules. Architon checks system-level integration contracts.

What’s available now
  • rv CLI
  • CI-friendly exit codes
  • JSON reports
  • GraphIR
  • Offline HTML reports
  • Studio v0.1 preview
Test Architon on a real hardware project

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

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.