Aegis ecosystem entry
The homepage now explains the ecosystem before it asks for a click. Visitors can see the product matrix first, then move into Ops, Build Lab, espctl, or future ecosystem lines with intent.
Aegis ecosystem entry
Navigation gets cleaner when the ecosystem states clearly what is primary, what is a workspace, and what is an advanced lane.
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
A future ecosystem node for home and field collaboration, held in the map now so the architecture stays explicit.
For teams extending device workflows into operational environments beyond the build loop.
Aegis ecosystem entry
The site now routes by role and task instead of forcing product marketing, control panels, and build flow into one shell.
The homepage shows the product matrix before the visitor chooses operations, build flow, or automation.
Build, analyze, download, and flash firmware through the browser MCP surface without leaving the browser.
Device configuration, compile orchestration, and firmware handoff stay concentrated in /app.
Users who need CLI, MCP, and agent workflows enter through the advanced lane instead of the main CTA lane.
Aegis ecosystem entry
Different audiences enter through distinct doors so the homepage stops trying to behave like marketing, console, and wizard at the same time.
Embedded developer
Open the MCP console to build, flash, and manage ESP-IDF projects.
Go to MCPDevice builder
Enter Build Lab for device setup, compile flow, and firmware handoff.
Go to Build LabAdvanced developer or agent user
Open espctl for CLI, MCP, and automated build workflows.
Go to espctl