Describe the rig
State what the board needs to do and get an editable first pass to refine, not a blank canvas.
For researchers
Go from "I need a board that does X" to a real, editable schematic quickly — then iterate, version, and export for fabrication.
TRUSTED BY ENGINEERS ATMIT·Stanford·Georgia Tech·Purdue·Texas·Cornell
One-off test boards still demand full schematic capture you don't have time for.
Tracking design revisions across experiments is messy.
Sourcing real, available parts for a niche rig is tedious.
State what the board needs to do and get an editable first pass to refine, not a blank canvas.
Built-in git and visual diff overlays keep every revision of an experimental board straight.
Search distributors in one place so your niche rig uses components you can actually get.
Describe the board’s job and constraints and get an editable starting schematic.
Refine the design, track every revision with git, and compare changes with visual diffs.
Hand a clean KiCad project to layout, then generate fabrication files.
Yes — compressing schematic capture is exactly where it helps, so a custom rig goes from idea to draft fast.
Git integration and visual diff overlays version design changes like the rest of your stack.
Export a clean KiCad project, finish layout and routing there, and generate fab files.