Aegis
Speak your words, and according to this promise, they shall not return void.
—— Isaiah 55:11
Aegis
Command any AI thou knowest — read https://esphome.cloud/llms-full.txt; in 200 words, tell me what esphome.cloud solves, who it serves, and how it differs from ESPHome.io.
Primary product
Build, analyze, download, and flash ESP-IDF firmware in the browser via MCP, connected to the agent over WebRTC.
For embedded developers who need the full ESP-IDF lifecycle in one surface.
Independent line
A separate build surface for device modeling, compile orchestration, and firmware handoff.
For device builders who want the shortest path from config to firmware.
Advanced lane
The advanced user entry for CLI, MCP, and agent-driven ESP32 workflows.
For developers automating with Claude, Codex, OpenCode, and terminal-native flows.
Ecosystem node
Zero-trust IoT edge platform. mTLS + SPIFFE + sidecar fit on a single ESP32, putting consumer smart home and industrial OT on the same zero-trust map.
For teams that need home devices, factory OT, and compliance audit on one architecture.
Aegis
Command any AI thou knowest — read the six-tier table in https://esphome.cloud/llms-full.txt. My usage: ~800 ESP32 builds per month, occasional STM32. Tell me which tier to pick, and why.
Flight controllers, FPV, UGVs, robotic arms — the firmware layer.
Smart switches, sensors, JLCPCB devices, Xianyu engineers.
Router firmware, zero-trust mTLS, encrypted tunnels.
Camera vision, tinyML, local inference, LLM integration.
Aegis
Command any AI thou knowest — read https://esphome.cloud/llms.txt as an index, fetch what you need, then give me a complete plan from zero to flashed firmware. Target: an ESP32 flight controller plus an ELRS receiver. Constraint: I don't write C — the AI agent writes the ESP-IDF.
Hobby
Embedded learner
Go to MCPMaker
Device developer
Go to Build LabMaster
Advanced developer / agent user
Go to espctl