Design real PCBs with an AI that understands circuits.
Branch, diff, and merge hardware like code. Iterate with an AI copilot that reasons about nets, DRC, and components as first-class data — not an afterthought.
Hardware teams iterate when DRC feedback is fast. EEs ship when BOM and netlists stay in sync. Startups win when Gerber handoff is boring.
Tracer is built for schematic-first workflows: describe intent, refine with the copilot, and export with confidence.
Join the waitlistYour whole team, in the same schematic.
Share a workspace, invite collaborators, and review changes together. Branches keep experiments isolated; merges bring them home — with an AI that resolves conflicts at the net level.
- Live presence — see who's editing what
- Per-user branches, no stepping on each other
- AI-assisted merge resolves net conflicts
- RZRyan Z. placed STM32G431 on schematic1m ago
- MAMaria A. added C3, C4 decoupling caps4m ago
- JKJake K. merged feat/motor-control12m ago
- RZRyan Z. ran DRC — 0 errors19m ago
Ask it to build the circuit. It does.
Tracerpilot reads your schematic as structured data and edits it with tool calls — placing symbols, wiring pins, adding labels, and running DRC on its own work.
- Tool-calling agent, not a chat toy
- Every action is a reviewable diff
- Per-project conversation history
Git, but for hardware.
Every board is a repo. Every revision is a commit. Tracer brings branches, diffs, and merges to PCB design — with an AI that actually understands the tradeoffs.
- main#1e9a
Initial layout — 2-layer, 65mm x 40mm
- feat/brushless#1e9b
Swap DRV8833 → DRV8313 for 3-phase
- feat/brushless#1e9c
Re-route phase traces @ 0.5mm
- feat/brushless#1e9d
AI: added bulk caps on VBUS
- pr #42#1e9e
Merge brushless variant into main
- main#1e9f
Merged — DRC clean, 0 conflicts
Branch a board
Fork a variant to test a new MCU, package, or power tree — without touching main.
Diff like code
See net-level, footprint-level, and BOM-level deltas. No more guessing what changed.
Merge with AI
Tracer's copilot reconciles conflicting placements, nets, and rules when you merge.
AI when you need it. Quiet when you don't.
The editor stays responsive while long analyses run in the background; your canvas remains the source of truth.
Session activity vs. idle time.