The Supply Chain Is Ready

First post. A position note — what we do, what we don't, and why.

The Supply Chain Is Ready

Turning an idea into a thing that ships used to require five or six rows of specialist time stacked together: two to four years of circuit design, six to twelve months of PCB layout, factory experience for production, sales background for supply negotiation. Five to ten years of professional credentials.

That stack is being dismantled, square by square.

Circuit design

AI assistants turn a spec paragraph into a draft schematic. JLCEDA is a free, browser-resident KiCad wired into the Chinese parts library. The LCSC open-hardware platform has hundreds of thousands of forkable public projects.

PCB layout

JLCEDA's autorouter is good enough for most boards. Independent hardware engineers on Xianyu and Taobao take complex boards in a week or two for a few hundred yuan.

Prototyping

JLCPCB ships ¥5 prototypes in a week.

Mass production

JLCPCB SMT runs from a few hundred boards. Huaqiangbei OEMs take orders below a thousand units.

Supply chain

LCSC sells single components at single-piece prices. Taobao and Pinduoduo fill in the loose parts and accessories. Independent shops on Xianyu source, label, and box.

Every square has someone doing it. None require a credentialed background.

One square left.

The Row Left

Embedded programming.

ESP-IDF takes a weekend to install. Python venvs collide. You don't know where IDF_PATH should point. idf.py emits ten lines of stack trace in stack-trace English. The datasheet is a hundred pages.

That's the wall between an ordinary person and a working device. esphome.cloud handles that square.

What We Do

Compile ESP32 in the browser

No ESP-IDF install, no venv. Open a tab, import the project, hit build.

AI reads the stacktrace

Paste the stack trace. The agent answers in plain language: what broke, the next command to run.

espctl remote build

cd to the project, espctl build . The firmware comes back. Claude Code, Cursor, and Codex connect through MCP embedded development.

Solution library

Smart switches, temp/humidity sensors, custom Home Assistant devices. Start from a working project, not a blank repo.

End-to-end encrypted

WebRTC direct. The build server only ever sees ciphertext.

What We Don't Do

Robot-arm / CNC / 3D-printer coordination

Out of scope.

OTA service

OEM territory; ordinary makers don't need it.

Device-management platform

Ordinary makers have 5–50 devices, no platform required.

IoT one-stop-shop / IoT protocol stacks

Not the ordinary maker's pain.

Collaboration / team features

Ordinary makers don't run embedded teams.

Hardware sales

Not a tool company's job.

In twelve to eighteen months the line may extend to OpenWrt router, CNC controller board, and 3D-printer controller board firmware compilation — but only the firmware layer.

Our position is the embedded programming row.

Common Questions

Is this ESPHome?

No. ESPHome is a YAML framework for Home Assistant devices and an open-source project. esphome.cloud is a remote build SaaS for ESP-IDF projects.

Do I need to know C?

No. The AI agent writes the code; we compile it.

Really no local ESP-IDF install?

Really. The browser path and espctl remote both work.

How do I wire it into Claude Code?

One MCP config block. Paste it in; Claude Code calls esphome.cloud. The full walk-through is on the espctl page.

Can the build server read my code?

No. WebRTC end-to-end encrypted; the build host only ever sees ciphertext.