About
Made by someone who needed it.
PCBKit started as a tool for one robot. It became the engine we think every hardware agent needs.
Who makes it
Hi, I’m Sergey Alekseev.
I’m a software engineer: fifteen years of big systems at Yandex (the Alice voice assistant), Canva, Dovetail and now ProfitPeak. In my free time I build Rabbit, a robot that drives around my flat, maps it in 3D and goes to things you name. I write about it atrabbit0.dev.
Rabbit’s electronics were a nest of wires. When I tried to make it a proper 8-layer board, KiCad was too hard for me and every autorouter I tried gave up. So I asked a coding agent to write a router and it routed the board. That router grew into PCBKit: an engine that places, routes, checks and simulates a whole device, made to be driven by an agent.
I build PCBKit with a team of coding agents (Claude Code and Codex): I design and check, they write the code and separate agent teams measure what the others build. That is why every claim here has a benchmark behind it.
Write to support@pcbkit.io if you build something with PCBKit, if it gets in your way or if you want to talk about where it is going. I read every message.
How we work
Four rules, no exceptions.
Measured, not promised
Every number on this site comes from a run we can repeat, with its date. Where we lose, we write down what it would take to win and work on it.
The agent does the hard part
All the engine’s power sits behind the agent: a beginner says what they want in plain words, an engineer sees and controls everything.
Your files, your tools
A board is a KiCad project with a small text file beside it, kept in git. Nothing is locked in: KiCad opens every board as it is.
Free
The engine runs in your browser or on your computer and the AI is your own agent, so one more person costs almost nothing. No sign-up to start.