AI place and route · For teams building robots and the hardware inside them

You set out to test an idea. Why are you testing your layout skills instead?

Your robot changes constantly. Sensors move, controllers change, prototypes need another revision. The decision is done. The board still waits.

On the robot
  1. Idea
  2. Iteration 1
  3. Iteration 2
  4. Iteration 3

Idea to on-the-robot. Fab is still fab. The waiting is what disappears.

  • Carrier and controller revisions
  • Sensor and interface boards
  • Motor-control support electronics
  • Evaluation and test hardware
  • Prototype boards that keep changing

The robot changes

Every new idea eventually needs a new board.

New sensor
Interface / connector change
New actuator
Motor control / power change
Compute update
Carrier / I/O / power change
Mechanical revision
Outline / connector move
Field learning
Another hardware change
Prototype result
Rev B

And then somebody has to implement it.

Where the week goes

PCB layout is the innovation bottleneck.

The decision takes an hour. The implementation waits in a queue.

  1. Learn
  2. Decide
  3. IMPLEMENT PCB
  4. Fab
  5. Assemble
  6. Test
  • carrier rev C
  • sensor board rev B
  • controller update
  • power board
  • test fixture
  • evaluation board
  • prototype #7

Every board that waits is an experiment that might not happen.

PCB expertise is the scarcest resource in the building.

Protect it. Don’t spend it on routine traces.

The question isn’t whether AI replaces your experts. It’s what their hours should go to.

Keep your tools. Keep your workflow. Lose the queue.

Add PCB implementation capacity with AI.

DeepPCB is an AI place-and-route engine. Point it at the routing your experts should never have to queue for; the decisions, the constraints, and the critical work stay theirs.

Your engineers keep

  • Architecture and design intent YOU
  • Placement YOU
  • Constraints and rules YOU
  • Critical nets and protected work YOU
  • Review and engineering responsibility YOU

DeepPCB takes more of

  • Routine routing volume AI
  • Repetitive implementation AI
  • Remaining board completion AI
  • Work waiting for layout time AI
  • Another routing pass AI

Keep the judgment. Automate the tedium.

  1. Upload

    Start with the placed board you already have.

  2. Check

    Confirm the stackup, classes, pairs, and protected work.

  3. Route

    DeepPCB routes the remaining board to your rules.

  4. Return

    Inspect it in your own EDA flow. Route again.

Your hardest board isn't the only board you build

One robot. Dozens of boards. Far more revisions.

  • Compute carrier

    Processing, connectivity, and system interfaces.

  • Motor controller

    Motor drive, feedback, and power stage.

  • Safety and I/O

    E-stop, interlocks, and safety circuits.

Robot platform

Every change here creates another PCB iteration somewhere.

  • Sensor interface

    I/O, signal conditioning, and protocol bridges.

  • Power distribution

    Regulation, protection, and power management.

  • Test fixture

    Programming, validation, and production test.

Which of these really needs your best PCB expert on every trace?

Expert hours for expert problems. Everyone else keeps shipping.

Good fit today

Prototypes · sensor and interface boards · controllers · carriers · evaluation boards · reference designs · customer variants · test hardware · routine revisions

Keep the expert

DDR and length-matched designs · big BGA fan-out · sensitive RF · production layouts

You’ve used an autorouter before. This one comes with files.

Smart MCU, STM32 board.

Routed output, returned to KiCad DRC clean
Manual placement, existing wires and vias protected, AI routing for the remaining board.
88
Components
43
Nets
4
Layers
KiCad
Flow
8 hrs
Estimated by hand
18m 8s
DeepPCB run
210/210 airwires, DRC-clean
Result
Manual
Placement

One of the published benchmarks: deeppcb.ai/benchmark/4-layer-stm32-pcb-routing. The setup ran from chat. Open the board and check the result yourself.

“Being able to generate more designs and iterate rapidly is truly a game changer. This allows us to focus more on optimizing the designs, saving time on revisions."
Issam Smaali, CEO, Wattnow

Your cloud. Your tools. Your rules.

Keep everything. Add capacity.

Keep the flow you trust. DeepPCB fits the implementation step, not a migration project.

  • Your CAD
  • Your rules
  • Your review
  • Your boundary

Scoped together. Run by us. Judged by you.

Test it on your board.

Public benchmarks prove the engine. Your board proves the fit. We agree on what good means before the run, and your engineers judge the result. You already know what you want to try next — bring that one.

  1. Bring it

    A board or revision your team would genuinely consider giving DeepPCB.

  2. Define good

    Agree on the success criteria before the run.

  3. Run it

    See what DeepPCB handles and what remains in your control.

  4. Inspect it

    Judge the output using your own engineering standards.

Thirty minutes. Your board if you have one, ours if you don't. No migration project, and no trust-the-AI pitch.

  • 7+ years of published research
  • InstaDeep
  • Part of BioNTech
  • Public benchmarks · inspectable files

The board session

Session
30 minutes, with an engineer
Bring
A placed board, or use ours
Formats
Altium, KiCad, EasyEDA, Zuken · OrCAD, Allegro and Eagle via DSN