Find the bug while it’s still a drawing.
Boardless keeps your schematic, your 3D-printed case and your firmware in one project, and checks them against each other every time you change something. In development.
↓ Try it: pick a module pin, then a pin on the board.
BME280
I²C sensor. 3.3 V breakout, no regulator, pull-ups on SDA/SCL
Soil probe
Analog. AOUT swings 0–75% of VCC: 0–2.5 V at 3.3 V
Pump MOSFET
Low-side switch. 10 kΩ pull-down keeps the pump off
$ boardless check greenhouse-node
ESP32-C3 SuperMini. The pin rules are the real ESP32-C3 ones. The editor around them is what I’m building now.
You're on the list.
Got a minute? Tell me which boards you use and I'll know what to support first.
Most hardware bugs are found at the bench.
A 5 V sensor on a 3.3 V pin. A pull-up on a strapping pin. A USB-C port that misses the case opening by two millimetres. You find them with a multimeter, after the boards have shipped and the print has finished.
Every one of them was already in the design.
The voltages are in the datasheets. The pin rules are in the ESP32 manual. The port position is in the board outline. They just never sit side by side.
So Boardless puts them side by side.
Schematic, enclosure and firmware live in one project. Move a wire and the firmware pin map follows; change the case and the check looks at every port again. Before you solder or print anything.
What it checks first
| Check | The bug it catches | Compares |
|---|---|---|
| Logic levels | A 5 V sensor output lands on a 3.3 V ESP32-C3 input. | parts, wiring |
| Strapping pins | A pull-down holds GPIO9 low at reset. The board starts in download mode, not your code. | parts, wiring |
| Pin capabilities | The analog read is on ADC2, which gives unstable results on the C3. | wiring, firmware |
| Power budget | The radio’s transmit spike browns out the regulator. | parts, wiring |
| Mechanical fit | The USB-C port sits 2.4 mm off the case cut-out. | board outline, enclosure |
| Pin map | Firmware drives GPIO5. The wire is on GPIO7. | wiring, firmware |
Why I’m building it
I wired a touch display to an ESP32-C3 the way an AI told me to, and lost three boards. I still don’t know which wire did it. What happened.
Hardware projects take real expertise and a lot of trial and error. I want to make that simpler.
I started building production-grade hardware with isbusy. Along the way I experimented with AI-driven development at every step, from picking the hardware to designing the case in 3D.
No single tool covered that whole journey, so I ended up building my own for every step of hardware development. Boardless brings them together.
Berkay Cubuk · berkaycubuk.com
Get early access
I’m letting people in by small groups. Tell me which boards you use and what keeps breaking; that decides what Boardless supports next. Price isn’t decided yet; the list hears first.
Only the email is required.
You're on the list.
I'll email you when there is something to try. If you described what broke on your last build, thank you. It goes into the list of checks.