New: Online Component GeneratorFree to get started

For researchers

Spin up test rigs fast.

Go from "I need a board that does X" to a real, editable schematic quickly — then iterate, version, and export for fabrication.

Fast iterationReal partsVersioned & local

TRUSTED BY ENGINEERS ATMIT·Stanford·Georgia Tech·Purdue·Texas·Cornell

01 | THE PROBLEM

Custom rigs should not take a week of schematic work

01

One-off test boards still demand full schematic capture you don't have time for.

02

Tracking design revisions across experiments is messy.

03

Sourcing real, available parts for a niche rig is tedious.

02 | HOW PROTOFLOW HELPS

Describe the rig

State what the board needs to do and get an editable first pass to refine, not a blank canvas.

Iterate and version

Built-in git and visual diff overlays keep every revision of an experimental board straight.

Source real parts

Search distributors in one place so your niche rig uses components you can actually get.

03 | FROM REQUIREMENT TO FAB FILES
1Describe

State what the rig needs

Describe the board’s job and constraints and get an editable starting schematic.

2Draft

Iterate and version

Refine the design, track every revision with git, and compare changes with visual diffs.

3Export

Export for fab

Hand a clean KiCad project to layout, then generate fabrication files.

04 | FAQ

Is it good for one-off boards?

Yes — compressing schematic capture is exactly where it helps, so a custom rig goes from idea to draft fast.

Can I track revisions?

Git integration and visual diff overlays version design changes like the rest of your stack.

Can I export for fabrication?

Export a clean KiCad project, finish layout and routing there, and generate fab files.

05 | EXPLORE MORE
06 | TRY PROTOFLOW

Less schematic busywork, more experiments.