Vibe hardware.
Describe the board you want. Your AI builds it from blocks that already power on.
- Added a flight MCU
- Added a 6-axis IMU
- Added a barometer
- Added power, 5 V to 3.3 V
- Added a CAN FD transceiver
- Added a USB-C connector
- Connected the IMU to the MCU over SPI
- Connected the barometer over I2C
- Connected CAN to the MCU
- Connected USB power to the regulator
- Connected the 3.3 V rail to the MCU
- Checked every connection

It already shipped.
Our first board is an ESP32-S3 flight controller built from these blocks. It went from description to production, not just to a render.
| Processor | ESP32-S3 |
|---|---|
| Sensors | [IMU, barometer, magnetometer] |
| Interfaces | [CAN, UART, PWM outputs, USB-C] |
| Board | [Size, layer count] |
| Produced | [Units built] |
Your AI picks the blocks. We make sure they fit.
Anoda plugs into the AI you already use through MCP. It never draws traces from scratch, so far less can go wrong.
- 1
Describe what you need
In Claude Code, in plain words: sensors, interfaces, size, power.
- 2
Your AI composes verified blocks
It chooses blocks from the Anoda library and decides how they connect.
- 3
Anoda checks every connection
Voltage, current, bus addresses and required pins, then routing and manufacturing rules.
- 4
Order the board
Download fabrication files with a verification report, or order fabrication and assembly directly.
Why the boards power on.
Blocks keep their layout
The inside of each block is placed exactly as it was when we tested it. Routing only happens between blocks, like hard macros on a chip.
Type checks for hardware
Every port declares its voltage, current budget and protocol. Mismatches fail before anything is routed, and your AI gets an error it can fix.
Files any factory accepts
Standard fabrication outputs with real, purchasable part numbers, plus a report of every check the board passed.
The block library
Each block has been fabricated and powered on. Its record shows which board it was tested on.
| Block | Function | Ports | Tested on | Status |
|---|---|---|---|---|
| mcu-esp32s3 | ESP32-S3 module | SPI, I2C, UART, USB, Wi-Fi | [Board, revision] | Verified |
| power-5v-3v3 | Power | 5 V in, 3.3 V out | [Board, revision] | Verified |
| imu-6axis | Motion sensing | SPI | [Board, revision] | Verified |
| baro-i2c | Barometer | I2C | [Board, revision] | Verified |
| can-fd | CAN FD transceiver | CAN, 5 V | [Board, revision] | Verified |
| usb-c | USB-C with ESD protection | VBUS, USB 2.0 | [Board, revision] | Verified |
- mcu-esp32s3VerifiedESP32-S3 modulePorts: SPI, I2C, UART, USB, Wi-FiTested on: [Board, revision]
- power-5v-3v3VerifiedPowerPorts: 5 V in, 3.3 V outTested on: [Board, revision]
- imu-6axisVerifiedMotion sensingPorts: SPITested on: [Board, revision]
- baro-i2cVerifiedBarometerPorts: I2CTested on: [Board, revision]
- can-fdVerifiedCAN FD transceiverPorts: CAN, 5 VTested on: [Board, revision]
- usb-cVerifiedUSB-C with ESD protectionPorts: VBUS, USB 2.0Tested on: [Board, revision]
Design free. Pay when you build.
Exploring, composing and checking cost nothing. You pay when you take the files to a factory.
Free
- The full block library
- Compose and check designs
- One simple board export a month
Per board
- Gerber, BOM and pick-and-place files
- Verification report
- First power-on guarantee
Pro
- Monthly board exports
- Free revisions
- KiCad source files
First power-on guarantee
If a board built only from verified blocks does not power on because of its design, we fix it and pay for the next prototype run.
Build your first board.
Early access opens to the waitlist first, at a founding price.