Circuit design at the speed of thought

Not software. Describe the board — the schematic draws itself, parts place themselves, copper routes itself. You approve, verify, and manufacture.

Open benchSee a real board
18/18 nets drawnDRC 0 errors
audio-to-light converter · schematic — rendered live from circuit data
Schematic of an audio-to-light converter, zoned and boxed automatically
the flow, end to end

Words in

01

Describe

Type the board like you'd brief an engineer — parts, functions, constraints. The agent plans first and waits for your yes; nothing moves without approval.

Re-layout power zone
  1. Float regulator + bulk caps for pack
  2. Recompile and verify zero overlaps
  3. Frame the measured positions
files · index.circuit.tsx
Approve planRequest changes
Structured plan first — nothing moves without your yes
02

Schematic draws itself

tscircuit's layout engine places symbols and draws wires from your zones. No coordinates, no dragging — sections in, readable sheet out.

Schematic draws itself — real render
Real schematic from a real agent-built board — 5 zones, 5 boxes, zero hand placement
03

PCB places and routes

The pack solver fits every footprint; the autorouter draws copper for every net it can reach. Overlaps, clearance, and unconnected ports are measured live.

PCB places and routes — real render
Real copper — 32 of 32 nets drawn, zero DRC errors
04

It stands up

The same circuit data renders in 3D instantly. Rotate it, check clearances against the enclosure in your head, keep going.

It stands up — real render
Isometric render from the same circuit data — no remodel
05

Factory-ready

Gerbers, drill, BOM with real JLCPCB part numbers, pick-and-place, a full KiCad project, shareable SVGs. Leaves here manufacturable.

an open letter

To those who ship hardware

Boards were never meant to be drawn twice — once as an idea, once as a thousand mouse clicks.

It begins with intent: what it does, where it flies, what it must survive. Then comes the translation tax — symbols, footprints, copper, clearances — hours of it, error-prone all the way down.

We built fluxboard for the way the work actually happens: you state intent and approve plans, deterministic engines do the placing and routing, and every claim is measured — nets drawn, errors counted, parts orderable.

Describe.Approve.Manufacture.

pricing

Your keys, your bill

No credits, no per-click meter. Bring any provider key — the bench runs on it, and you pay them directly.

Bench

BYOK · free for limited time
  • Full studio + agent
  • Unlimited boards
  • Gerbers, BOM, KiCad, SVG
  • Your keys stay local
Open bench

Studio

coming soon
  • Everything in Bench
  • Team boards + shared threads
  • Priority support
  • New engines first

Enterprise

coming soon
  • Self-hosted bench
  • SSO + audit trail
  • Your cloud, your keys
  • SLA + security review
need help?

Questions

Can AI really design a PCB end to end?
fluxboard designs the full loop — schematic, placement, routing, verification, manufacturing files — from a plain-English brief plus your approvals. The engines are tscircuit's deterministic layout, packing, and routing algorithms; the agent directs, zones, and fixes. Every output is measured (DRC, net counts, coverage), never vibes.
How does this fit my KiCad workflow?
One click exports a complete KiCad project (.kicad_sch + .kicad_pcb + .kicad_pro) that opens directly in KiCad, including hierarchical sheets when the board uses them. Design here, finish there — or never leave.
Is the BOM really orderable at JLCPCB?
Parts resolve to real LCSC C-numbers through tscircuit's JLC search, footprints matched to the ordered part, and the export receipt shows coverage per row with a one-tap fix for gaps. Unsupported categories are flagged explicitly, never invented.
Do I need to learn prompting?
No. Approve plans, tap Fix on errors, answer the rare question with numbers. The harness enforces discipline (locks, gates, quoted errors) so weak prompting still lands clean boards.
Who owns my designs? Are my keys safe?
You own everything. API keys live in your browser vault or your own server env — they never leave your machine except to the provider you chose. Your boards are never used for training.