Skip to main content

Vibe hardware.

Describe the board you want. Your AI builds it from blocks that already power on.

Claude Code, connected to Anoda
YouBuild a flight controller with an IMU, a barometer, CAN and USB-C. 36 by 36 mm.Your AI, building with Anoda
  • 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
Waiting for a description
U1ESP32-S3U2 IMUU3 BAROU4 POWERU5 CANJ1 USB-CD1VerifiedVerifiedVerifiedVerifiedVerified
The flight controller: an ESP32-S3 module surrounded by connectors, an SD card slot and power parts on a green board

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.

ProcessorESP32-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. 1

    Describe what you need

    In Claude Code, in plain words: sensors, interfaces, size, power.

  2. 2

    Your AI composes verified blocks

    It chooses blocks from the Anoda library and decides how they connect.

  3. 3

    Anoda checks every connection

    Voltage, current, bus addresses and required pins, then routing and manufacturing rules.

  4. 4

    Order the board

    Download fabrication files with a verification report, or order fabrication and assembly directly.

YouAdd CAN to my flight controller.
Your AIAdding a CAN FD transceiver and connecting it to the 3.3 V rail.
AnodaThis transceiver needs 5 V. The rail supplies 3.3 V.
Your AIMoving it to the 5 V rail.
AnodaAll checks passed. 4-layer board routed, DRC and DFM clean.

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.

imu.spiSPI, 3.3 V logic
can.vccneeds 5 V
power.3v3supplies 3.3 V

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.

gerber.zipbom.csvpick-and-place.csvverification-report.pdf

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.

  • mcu-esp32s3Verified
    ESP32-S3 modulePorts: SPI, I2C, UART, USB, Wi-FiTested on: [Board, revision]
  • power-5v-3v3Verified
    PowerPorts: 5 V in, 3.3 V outTested on: [Board, revision]
  • imu-6axisVerified
    Motion sensingPorts: SPITested on: [Board, revision]
  • baro-i2cVerified
    BarometerPorts: I2CTested on: [Board, revision]
  • can-fdVerified
    CAN FD transceiverPorts: CAN, 5 VTested on: [Board, revision]
  • usb-cVerified
    USB-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

$0
  • The full block library
  • Compose and check designs
  • One simple board export a month

Per board

$19–49per design
  • Gerber, BOM and pick-and-place files
  • Verification report
  • First power-on guarantee

Pro

$39a month
  • 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.