Vehicle & Aircraft Control
Flight controllers, FPV, UGVs, robotic arms — the firmware layer.
Example: ESP32-S3 + ELRS receiver
Four domains
The device range Build Lab serves
Build Lab does not replace ESPHome.io's smart-home YAML template library. It picks up the projects that library does not cover — the ones that need ESP-IDF C/C++ — across four domains sharing one workspace.
IoT Device Tooling
Smart switches, sensors, JLCPCB devices, the bespoke hardware Xianyu engineers wire together.
Example: ESP32-C3 + custom PCB
Network Security
Router firmware, zero-trust mTLS, encrypted tunnels, SPIFFE edge nodes.
Example: ESP32-S3 + SPIFFE workload
Edge AI
Camera vision, tinyML, local inference, LLM integration.
Example: ESP32-S3 + camera + ONNX
Workflow
Three steps from blank device to firmware
Three independent steps; each one can be replayed or redone on its own. Build Lab does not share a panel with the Ops workspace.
01 · Model the device
Three wizards — RSHome for home setups, Sidecar for zero-trust mTLS, Bastion for standalone gateways. Fill in BOM, sensors, and protocol stack once; save as reusable profiles.
Every profile can be edited or replayed independently
02 · Compile in the cloud
Pre-warmed ESP-IDF v5.x / v6.x caches; the remote agent handles the compile. Logs stream back over WebRTC. Your machine never installs ESP-IDF, Python, or CMake.
Failure is data too — failed builds can be signed into a triple
03 · Hand off the firmware
When the build is green, flash directly over Web Serial from the browser. For offline targets, download .bin and use esptool or espflash locally.
Billed per build, not per minute
Where it sits
How Build Lab relates to the other product lines
Build Lab is a build workspace. It is not an IDE, not a device platform, and it does not absorb the Ops workspace.
Where it sits
Versus ESP-IDF MCP
MCP is the full ESP-IDF operating surface in the browser — command-line-level granularity. Build Lab folds that into "model → compile → hand off" for builders who want a path without learning the ESP-IDF CLI.
View ESP-IDF MCPWhere it sits
Versus espctl
espctl is the terminal and agent entry — for Claude Code, Cursor, and CI to drive. Build Lab is the browser entry. One project, two doors, same workspace state.
View espctlWhere it sits
Versus Ops
Build Lab is the build workspace; Ops is the operating workspace for funnel review, plugin governance, and audit. Neither absorbs the other.
View OpsIndependent product line · device build workspace
Ready to build?
No ESP-IDF install, no Python venv, no CMake. Open the browser, work through the wizard, and ship your first ESP32 firmware.