Building with Zephyr, ESP-IDF, FreeRTOS, or embassy (Rust)? GreatCTO auto-detects the iot-embedded archetype and ships OTA update strategy, secure boot validation, watchdog patterns, power profiling, and ETSI EN 303 645 gates from day one.
CMakeLists.txt + prj.conf (Zephyr) / sdkconfig (ESP-IDF) →Compliance auto-suggested: iso27001 · etsi-en-303-645 · cra. Specialist agents activated:
OTA update strategy (A/B partitions, rollback) · ETSI EN 303 645 compliance · secure boot validation · hardware-in-the-loop test design · power profiling · watchdog patterns · RTOS-specific patterns.
EU Cyber Resilience Act · ETSI EN 303 645 (consumer IoT) · default-password ban · vulnerability disclosure · SBOM at gate:ship.
Hardware-in-the-loop test rigs · environmental stress (temp, vibration) · power-cycle endurance · OTA storm test · field-recovery scenarios.
Active / sleep / deep-sleep profiles · RAM / flash budget · BLE / Wi-Fi / LoRa range tests · battery-life projection.
Packs auto-attach when CLI detects pack-specific signals (e.g. twilio in deps → voice-pack). Each pack adds its own reviewer agents + human gates on top of the base archetype pipeline.
20 startups in this space. Click for full pack mapping.
Listed companies operate in this space. Inclusion is based on publicly available product descriptions and does not imply endorsement of or by GreatCTO.
$ npx great-cto init